Reversals

• Transaction Reversals.

• Payment Reversals.

Transaction Reversals

A Transaction Reversal can be initiated using the appropriate web service. The unique Transaction Reference number that needs to be reversed will be the input for initiating such a reversal.

On receipt of such a reversal request, Aura will -

1. Gather all the accounting entry legs of the original Transaction Reference Number

2. Execute the group validations. Example: Total of Debit should be equal to Total of Credit

3. Execute Leg wise validations. Examples: Valid account number, Balance check, Transaction code, Account Settings etc.

4. Post reversal for the entire set as follows:

   a. Debit / Credit indicator will remain the same, but the amount will be posted with a negative sign.

   b. Book date will be the system date.

   c. Replace value date only for the credit card account leg using the transaction code reversal leg value date

   d. Reverse the Transaction account trace entry + Billing account entries

   e. Update Balance class / Replenishment

   f. Reverse all the transactions where the Related Reference Number = Transaction Reference Number being reversed. Example: Bonus points or Discounts posted

   g. Transaction Code and all other details will remain the same as they were in the original transaction.

   h. If any of the related transaction reversal fails, the same will be logged into an exception table, but, the main entry reversal will be completed without any impact

Payment Reversals

These are treated exactly the same way as Transaction Reversals using Web Service described above, except that, in this case, the Debit / Credit indicator will be Credit, instead of the Debit for a Transaction.