☰

Prerequisites

Jump to Section

General Prerequisites

  • Mambu Process Orchestrator (MPO) subscription.
  • Mambu environment with a user for MPO process execution.
  • ComplyAdvantage environment and user account.

Setup Prerequisites

MPO

If external data is required to be mapped, configure the MPO process AML External Data.

ComplyAdvantage

  1. Configure rules and actions for Hard Stop and Soft Stop.
  2. Configure the source format (payment details and fields).
  3. Set up the alerts webhook and link it to the MPO process Alerts Analyser Router [to be linked to CA].

Mambu

  1. Grant necessary permissions or configure a role for the Mambu user.
  2. Create four Chart of Accounts as _Assets_ with the option Allow Manual Journal Entries enabled for each General Ledger (GL): Transit, Scheme, Suspense, and Withhold.

Chart of Accounts

  1. Define Accounting at the Deposit Product level and link the corresponding Chart of Accounts to a Transaction Channel. For Outbound and Inbound payments the Transaction Channel accounting should be linked to Transit GL.
Transaction ChannelAccountingUsage
CB_Deposit_BacsTransitInbound Direct Credit
CB_Withdrawal_BacsSchemeInbound Direct Debit
CB_Return_BacsSchemeInbound Direct Debit
MBU_Withdrawal_FPSTransitOutbound FPS
MBU_Withdrawal_CHAPSTransitOutbound CHAPS
MBU_TransferTransitOutbound Intrabank/Interbank
CB_Withdrawal_FPSSchemeOutbound FPS (Reversal)
  1. Create custom fields for any Mambu entity that is needed, with the data model used and grant access rights based on user roles or permissions.
  2. The client should be in an valid state to open accounts (deposit).
  3. Deposit Account should be in an valid state to post Deposit or Withdrawal transactions.
  4. The Deposit Account should have sufficient funds for Withdrawal transactions.
  5. An IBAN should be mapped to a Deposit Account using External Account Representation (EAR) or custom fields. If you use an EAR for the IBAN linkage then the Payments capability must be enabled. Additionally, you must create an API key from an API Consumer that has appropriate permissions to access the Payments capability.

Please Note:

  • The GL code can have any format.
  • If there is a Transaction Channel for manual reconciliation when a transaction exists in a third-party system, but not in Mambu, the Transaction Channel accounting should be linked to Scheme.
  • If the bankCode and/or bankCountry fields for CounterParty should be mapped in ComplyAdvantage and the full IBAN format is not used for the creditor, then these fields must be set as optional in the source format.