The Deposit Manager add-on lets you receive settlement confirmations from various Payment Service Providers (“PSP”) (like banks or credit card merchants) that you use for your customers to deposit cash into their accounts with you.
Each deposit from a PSP will then be automatically matched to a customer account in Broker using the transaction reference that you provided to the PSP when you initiated the payment.
Deposit Manager supports multiple account matching algorithms which contain the logic for how to match a deposit to an account in Broker. For each PSP it is possible to define a selection of account matching algorithms to use and what order of priority those algorithms should be used.
New account matching algorithms can be created on request and the two standard algos are Account Number matching and Account Id matching. These algos will interpret the transaction reference received from the PSP for each deposit as either being an account number or an account id in Broker and search Broker to find a match based on those properties.
If a match cannot be identified the add-on will book the deposit into an exception account in Broker (which you can define as a different exception account for each PSP if you would like).
There will also be transactions created in a custody account in Broker which you can define as a specific custody account per PSP. There is also a configuration available where you can set if custody transactions should be created as a batch or not. A batch is when numerous customer deposits are batched together for the custody account transaction.
| Info |
|---|
Let’s say that you have 10 customers depositing 1,000 each on the same day and the PSP will make a deposit of 10,000 into your account with the custodian it means that the custody transaction is batched. If this was not batched there would be 10 individual transactions posted to the custody accounts as well. For each PSP you can define if custody transactions should be batched or not. |
Deposit Manager will keep you posted on what it has done by creating tasks in Broker and upload files to the House reflecting what has been implemented. Here you will find exception messages and details about everything. Typically these tasks will be set to status Done if nothing requires manual interaction.
If there are unmatched transactions there will be new tasks created as an active task for each unmatched transaction that needs to be handled manually with as much details about the original transaction as possible to let you research it.