☰

Business Flows

Jump to Section

The Mambu-Oracle NetSuite connector’s business flow consists of extracting all journal lines created in the previous day from Mambu at midnight and sending them as balanced batches of journal lines to Oracle NetSuite.

The journal lines are enriched with custom fields defined in Oracle NetSuite. Custom fields are attributes and values that categorize accounting lines, such as transaction, client, account, product, or branch and can be set for the following entities: transaction, loan account, deposit account, client, product, or branch. This enrichment allows for deeper and more robust analysis and reporting of the accounting data.

Oracle netsuite connector business flows

Types of journal entries handled by the integration

Automatic journal entries

Mambu will automatically log corresponding journal entries for each transaction posted to a customer account. The journal line posted to Oracle NetSuite can be enhanced with custom data from the following entities: transaction, client, account, product, or branch.

Manual journal entries

A manual journal entry can be associated with a branch. The journal line posted in Oracle NetSuite can be enhanced with custom data from the branch entity.

Daily and monthly accruals

These types of journal entries are logged during end-of-day processing in Mambu and contain information about the product and branch. The journal line posted to Oracle NetSuite can be enhanced with custom data from the following entities: product, or branch.

Negative use cases

The Mambu Process Orchestrator (MPO) processes handle and record all errors generated during different phases of the connector: extracting the data, performing transformations, and loading the enriched journal entries into Oracle NetSuite.

Each negative use case is handled differently depending on which phase of the process the issue occurs in.

Data extraction

If an error occurs during this phase, the following steps are executed automatically:

  • The API call is retried a configurable number of times.
  • The error is stored in a dedicated state diagram.
  • The journal lines queue is emptied.
  • A task is logged in Mambu and assigned to a designated user.

The following steps should be manually executed: trigger the Main process, specifying the date.

Data enrichment

If an error occurs during this phase, the following steps are executed automatically:

  • The API calls will be retried a configurable number of times.
  • The error is stored in a dedicated state diagram.
  • A task is logged in Mambu and assigned to a designated user.

The following steps should be manually executed: add custom field values to the journal lines posted to NetSuite.

Batch reconstruction

If an error occurs during this phase, the following steps are executed automatically:

  • The error is stored in a dedicated state diagram.
  • A task is logged in Mambu and assigned to a designated user, which will indicate which of the following steps are required:

Case 1

  • Trigger the process specified in the notification (Listener).

Case 2

  • Check if the journal lines queue is empty.
  • Check that the state diagrams listed in the notification are empty.
  • Trigger the Main process, specifying the date.

Data dispatch

If an error occurs during this phase, the following steps are executed automatically:

  • The error is stored in a dedicated state diagram.
  • A task is logged in Mambu and assigned to a designated user.

The following steps should be manually executed:

  • Check that the state diagrams listed in the notification are empty.
  • Delete the journal lines already posted to NetSuite for that specific date.
  • Trigger the Main process, specifying the date.