Overview
This release adds payment method visibility to Customer Ledger Entries and CPM Transactions, so anyone looking at a posted payment or refund can see which card or bank account was charged without leaving Business Central or opening the payment platform. It also carries forward two production hotfixes: a fix for transaction fees in a foreign currency posting with the wrong amount, and a fix for nightly CPM automations failing with a write-transaction error.
Added
- Payment Method Visibility on Customer Ledger Entries and CPM Transactions
- Users can now see which card or bank account was charged for a posted payment or refund, directly from the record they are already viewing. This is an invaluable feature for support/service staff as they can easily access and manage payment data inside of one view in BC.
- A new payment method panel shows the card brand and last four digits, or the bank account's last four digits, for the selected transaction.
- This appears on both the Customer Ledger Entries page and the CPM Transactions list.
- Refunds show the same card or account that was originally charged, even though refund records themselves carry no payment method details of their own.
- The Transaction ID on a Customer Ledger Entry is now clickable and opens the full Transaction Card.
- Faster Payment Account Selection for Saved Payment on File
- A new “Ignore Contact No. for Saved Payment Methods” setting on the CPM Payment Platform card lets that platform's lookups match on Customer only, for platforms that don't track a linked Contact.
- This allows for granular filtering if needed but ensures it won't restrict your accessible cards if you don't need that lever of filtering.
- A new “Select Payment Account” list shows how many payment methods are already saved on each candidate account, with drill-down to view them, instead of a bare list.
Fixed
- Nightly CPM Automations Failing with a Write-Transaction Error
- Scheduled automations that link or post CPM transactions (linking invoices, payments, refunds, and transactions; posting transactions; updating payment request status; retrieving invoice lines) could fail with an internal write-transaction error, stopping the job overnight instead of completing.
- This has been corrected.
- Foreign Currency Transaction Fees Posted with the Wrong Amount
- A transaction fee in a foreign currency (for example, a USD fee for a company whose local currency is EUR) was posted without a currency code, so Business Central treated the foreign amount as if it were already in the local currency.
- The fee now carries the transaction's currency, so it converts correctly before posting.
- Payment Application Status Could Reflect Another Platform's Transactions
- Payment application status was worked out by matching on Transaction ID alone.
- If two payment platforms happened to issue a transaction with the same ID, one platform's status could be calculated from the other platform's ledger entries.
- The match now requires Payment Platform and Transaction ID together to ensure accuracy.
- Opening a Transaction Card Could Fail for Read-Only Users
- Every time a Transaction Card was opened, its payment application status was recalculated and saved, even when nothing had changed, which could throw a permission error for users without write access.
- The status is now saved only when it has actually changed, and only for users with permission to save it.