·Business Focused Problem Description
The system is allowing to create customers direct debit mandates. As payments and remittances can be made from different bank accounts, several mandates must be created and signed for each customer even if they have same Direct Debit ID.
· During customer payment journal or remittance journals as there are multiple customers and multiple bank accounts (Aguirre), with multiple mandate id’s per customer due to actual system limitations it will be difficult to select the right mandate per payment transaction which is exactly related to the specific bank.
· What is the business impact to the customer? Customer expecting only one direct debit mandate for each customer when same Direct Debit Id is identified for banks. This is an important limitation for companies that work with discount lines agreements with banks. Customers don’t define the bank at customer level but at payment or remittance level depending on the available credit with the bank or cash flow situation. Only one mandate is signed with the customer and can be used with any of the company bank accounts using the same Direct Debit Id identified as identified in the mandate.
Actual Results: The system is allowing all customers direct debit mandates during customer payment journal and as there are multiple customers, there will be multiple mandate id’s and it will be a difficult to select the mandate which is exactly related to the specific customer.
Expected results: The system should allow to maintain one mandate in case the customer bank account and the direct debit id in the company bank account is the same. In this way it forces to have just one mandate and always use the same bank account as we cannot ask a customer to sign several mandates.
Comments
This functional limitation in Dynamics 365 Finance regarding Direct Debit Mandates (SEPA) is causing significant operational, financial, and compliance issues for companies working with multiple company bank accounts under the same creditor identifier (Direct Debit ID). Today, D365 Finance forces the mandate to be linked to a single company bank account, even when the creditor identifier (Direct Debit ID) is the same across all company bank accounts. As a result, customers must sign multiple mandates, and users must manually select the correct mandate depending on which company bank account is used for settlement.This behavior is not aligned with SEPA standards, where one mandate per customer per creditor should be sufficient—regardless of how many bank accounts the creditor uses.This limitation impacts organizations that operate with multiple bank accounts due to treasury optimization, discount lines, credit facilities, or multi-bank strategies. The consequences include:Additional administrative effort. Companies must manage and store 2–10× more mandates per customer depending on the number of bank accounts used.Manual errors in mandate selection. Risks increases in high volume payment environments. This process is critical for many business and companies.Slower onboarding, Take longer to create a customer. Time to create a mandate increases 2–10× per customer depending on the number of bank accounts used.Inefficiency in collections. Finance teams spend significant time validating which mandate applies to each transaction.
Category: Accounts Receivable
We should have also an option to update open transaction (invoice / order /...) when customer changed mandate ID.Previous mandate is closed and new mandate is created, then mandate on all invoices not paid and orders created should change automatically (on demand)
Category: Accounts Receivable
Great idea to correct SEPA Direct Debit Mandates. Mandates should be open to be used with several company bank accounts when creditor identifier (Direct debit Id) is the same in all of them.Unfortunately in Dynamics 365 Finance limited to be used by only one company's (own) bank account Mandates and it has been defined as a required field. This is not correct by concept!Dynamics should allow a single mandate to be signed by a customer and used from any of the company's bank accounts (not the client company bank accounts but the bank accounts owned by the remittance company) as long as the direct debit is the same. This is a great pain point and limitation for those companies that are used to work with several bank accounts and wants to use indistinctly one or the other. Right now, due to the limitation of one mandate to one bank account, you need to create and get signed by the customers several mandates which is not acceptable and also the system is not really prepared to that. This is specially critic for business where work with several banks with discount lines of credit for remittances at discount.
Category: Accounts Receivable