It is a common requirement from customers to have a payment reference for non-check payments. That is if there is a payment file being generated instead of a check being printed. This usually aids helping the companies to setup reconciliation based on payment reference instead of relying on amounts and transaction dates.
Comments
This is a common occurrence when dealing with large EDI drop-ship retailers like Amazon, Wayfair, Walmart.com... Consolidated list of invoices are sent to Trading Partner(TP) and paid via ACH. TP will then send merchant a list of Invoices and/or PO's paid. These .xlsx, .csv or .txt files are sent via EMAIL or FTP and are in no way standardized. Manual manipulation or custom parsing with external/internal code is usually written to create an importable file. Using the DMF CustomerPaymentJournalLineEntity to import one of these ACH Payment remittance files should be simple, but it is a nightmare. Even when a template is exported and then imported, the Dimensions for customer and Ledger offset somehow do not match. The number of dimension values specified in [CustAccount] is different from the number set up in the active format for data entities.
Category: Cash and bank management
Which format and country context do you use to generate the payment files?
Generally, there are existing fields which should serve this request like Payment Id, Payment Reference. In some cases, it can be affected by the Method of payment setup or some country-specific settings. Some features can use more complex logic depends on the payment format.
Category: Cash and bank management