The connector, built in-house by Mambu, offers a significant part of the full Mambu <-> Oracle NetSuite integration, but it is not a complete end-to-end solution, it covers 3 out of 4 sections of the full end to end integration:
- Journal data extraction: extract all Journal entries from Mambu created in the previous day;
- Journal data enrichment: enrich each Journal line with its corresponding information (ex: Client id, Loan id, Transaction type etc);
- Journal data batch construction: the batches of Journal data are balanced and ready to be sent to Oracle NetSuite.;
The final step of the integration would be the creation of the NetSuite RESTlet that will allow the posting of Journal lines into NetSuite, this should be provided by an Oracle NetSuite partner.
In order to make full use of the connector, the following three items are therefore required:
The Mambu - Oracle NetSuite connector runs on the Mambu Process Orchestrator (MPO). In order to use it, you will need an active MPO subscription.
As support for the newer OAuth 2.0 standard is not optimal for long-lived, system to system connections, OAuth 1.0 is used, which has complex cryptographic requirements not currently available in MPO. A lambda function in AWS is used to compute the signature and an AWS API Gateway composes the Authorization header and includes it in requests to Oracle NetSuite.
Oracle NetSuite partner
Since it will be handling large amounts of accounting data, the integration has been implemented by taking into account that the customer, through an Oracle partner or a system integrator that is a SuiteCloud Developer Network member, will be creating the necessary RESTlets to push the information into NetSuite. As Oracle only works through resellers, the customer would not get direct access to an Oracle NetSuite environment so a partner is the only way to go.