Mambu Process Orchestrator

This connector runs on the Mambu Process Orchestrator (MPO). In order to use it, each customer would need an active MPO subscription.


  1. Have the Chart of Accounts configured as per the bank’s requirements.
  2. Create a user for the integration and grant necessary permissions. Take note of the username and password, it will be required for the calls made from MPO to Mambu APIs.
  3. Decide on a Mambu user who will be default assignee for tasks and notifications related to this connector and responsible for taking any necessary actions.

Azure Active Directory

Azure Active Directory (Azure AD) is used to manage authentication and identity for the connector. You will need to configure an Azure App for your company and provide the necessary API permissions to the application. Azure AD is also the place where tenantID, clientID, and clientSecret are kept.

Microsoft Dynamics 365 Business Central

  1. Create the Chart of Accounts in Microsoft Dynamics 365 Business Central and map the general ledger code, account name, account type, and other necessary settings to obtain a one-to-one relationship with Mambu.

  2. Create a set of custom dimensions that will hold the dimension values. Dimension values will be attached to journal lines for reporting purposes.

    List of dimensions implemented in the current version of the connector:

    • Account dimension: holds the account id (code field) of the loan or savings account and account name (name field)
    • Branch dimension: holds the branch id (code field) and branch name (name field)
    • Client dimension: holds the client id (code field) and client name (name field)
    • Product dimension: holds the product id (code field) and product name (name field)
  3. A scheduled job that will post the journal lines to the general ledger accounts will need to be configured in Business Central.