NOTE: Billing module required
Description
In the near future this module will contain the functionality .Debt management options
You can configure your NMSPrime instance to manage overdue debts / outstanding customer payments by one of the following 2 ways by editing /etc/nmsprime/env/overduedebts.env in your NMSPrime VM.
Note: If you already use your financial accounting software to create dunning letters and you import the bank transaction file to that software you would have the same work of assigning transactions with bad transfer reason to your customers. In this case option 2 does better suit for you.
Parse bank transaction file
| Code Block | ||||
|---|---|---|---|---|
| ||||
DEBT_MGMT_TYPE=sta |
This way the settlement run will create a debt for every customer. It automatically closes the created debt by another debt if the customer has a valid SEPA mandate.
On uploading the bank transaction file of the format MT940/Swift NMSPrime tries to clear open debts or creates new ones if the direct debit failed. A logging tab shows all infos, errors and warnings of the assigned or not assigned transactions - e.g. if the reason of transfer didn't contain the invoice number.
NOTE: all manually done customer transactions need to have the invoice number in its reason of transfer.
(Refer to the internal page Dunning Design Decisions for the reasons of this design decision)
Upload resulting debt list from financial accounting software
| Code Block | ||||
|---|---|---|---|---|
| ||||
DEBT_MGMT_TYPE=csv |
The CSV to upload must contain the infos in the following format:
dunning indicator
Content
| Feature | State | Details | Start here.. |
|---|---|---|---|
| Overview Dashboard | (//) | Obtain an overview of all overdue debts. | |
| Allocation | (//) | Allocate corresponding transactions as liabilities. | |
| Dunning Letters |  | Create automated dunning letters for customers having overdue payments. | |