Back-value-dated transactions are essential for maintaining accurate account balances. They play a crucial role in adjusting account values to correct errors, provide timely compensation to customers, and meet regulatory requirements. By ensuring that the back-value-dated balance accurately reflects the correct payment date, even if the transaction was processed later, these transactions help maintain the integrity of financial records and ensure compliance with regulations.

Objectives of back-value-dated transactions

Banks use back-value-dated transactions for the following reasons.

• Correcting errors: Banks use back-value-dated transactions to rectify processing mistakes by adjusting the funds to the correct date. For example, if a bank erroneously credits USD 100 to a customer's account on the 1st of the month, but the payment was actually made on the 15th of the previous month, the bank can back-value-date the funds to the 15th to ensure that the account balance is correct.
• Customer compensation: Banks sometimes back-value-date transactions to compensate customers for processing delays. For example, if a bank takes two weeks to process a payment, it might back-value-date the funds to the original payment date. This compensates the customer for the lost interest they would have earned if the funds had been available sooner.
• Regulatory compliance: Regulatory requirements might mandate that banks back-value-date transactions. For example, in the United States, banks are required to back-value-date funds if a processing error occurs to ensure that customer balances are accurate.

How to post a back-value-dated transaction

Use the Post payment or the Post multi-leg payment endpoint to post a back-value-dated transaction by setting the payment_datetime field to the past date.

After posting, balance history events are generated for all days affected by the balance adjustment. No clearing process is needed.

💡

Notes

• If the administrative division of the account has the skip_cycle_closing parameter set to true, no balance history is sent on non-business days or holidays.
• If the deny_value_date parameter is true and the payment_datetime falls on a non-business day or holiday, the transaction is denied.
• For details about skip_cycle_closing and deny_value_date, refer to the Parameters section of Posting transactions on holidays.
• Before performing back-value-dated transactions, ensure you check the number of days specified in the retroactive_payment_time_restriction field of Create acceptance configuration by Org. The transactions are processed based on the date you provided.

Impact on account balances

When back-value-dated transactions occur, account balances are adjusted accordingly. This has the following results.

• The account balance is higher if funds received are back-value-dated.
• The account balance is lower if funds paid are back-value-dated.

This adjustment happens because the interest earned or owed on the account is recalculated, as the value-dated balance is adjusted for a longer period of time. This process is closely linked to the management of balance history and the bank's end-of-day procedures. The effects on various types of balances are detailed in the following table.

Examples

Here are some examples of how you use back-value-dated transactions in different scenarios.

Rules for performing a back-value-dated transaction

Here are the key rules to remember when you perform back-value-dated transactions.