Correct or reverse a transaction

The correction method depends on both the Transaction's Approval status and its Processing status. Editing changes an unposted draft. Reversal creates a new, linked counter-posting for a processed Transaction.

Correct a Captured or Rejected transaction

The original maker needs Create Transaction to edit their own Captured or Rejected record. Editing another maker's correctable record requires Update Transaction. The record must also be within the user's maker-oriented data scope.

1. Open Customer Relationship → Transactions → Transactions and select the reference.
2. Select Edit.
3. Correct the Value Date, Narrative, posting batches, lines, FX evidence, or commission decisions as required.
4. Select Save as Draft to keep the current draft state, or Save & Submit to revalidate and start approval.

Posting Date, booking Branch, and Intent are locked after creation. Changing posting lines replaces the draft's line set atomically and causes applicable commission decisions to be reviewed again.

A pending Transaction cannot be edited. An approver must Reject it with a reason before the maker can correct and resubmit it. A Denied Transaction is terminal. Authorized Transactions do not support amendments and cannot be edited.

Only a Captured draft can be deleted, and deletion requires Delete Transaction. A posted financial event must be reversed instead of deleted.

Reverse a processed transaction

You need Reverse Transaction and access to the original Transaction. You do not also need Create Transaction or Update Transaction.

The Reverse action is available only when all of the following are true:

• Processing is Processed;
• the Transaction has not already been reversed and has no reversal in progress;
• it is not a loan-system Transaction that requires loan-specific unwind handling;
• it posted on the current working day or the preceding working day;
• an authorized work-day calendar is available.

To reverse:

1. Open the processed Transaction and select Reverse.
2. Enter a Reason for Reversal of at least 10 characters.
3. Choose the Reversal Value Date:
   • Current Working Day reverses balances now and is the default;
   • Original Value Date retroactively unwinds the value-dated effect and can recalculate value-dated balances and accruals.
4. Select Reverse Transaction. remoteEaze creates the linked reversal and submits it in one operation.
5. If approval is required, a different eligible user completes the displayed approval levels. Reviewers can approve or deny a reversal; generated reversal instructions are not returned for editing.
6. Confirm that the reversal's Processing status becomes Processed.

The new record uses the original booking Branch, flips each Debit and Credit, copies the financial values and FX provenance needed for the counter-posting, and posts on the current company working day. Its generated financial lines cannot be edited. Transaction commissions are not recalculated for the reversal.

The reversal follows the configured Transaction authorization policy, but it cannot require fewer approval levels than the original Transaction completed. If a reversal is denied, initiate a new reversal from the original Transaction with the corrected reason or Value Date.

The original remains in history. After the reversal posts, its Processing status becomes Reversed. Reversal Chain links the original and reversal and retains the reason for audit.

What a reversal does not do

A reversal is not an edit and does not erase the original record. Do not create an unrelated manual posting as a substitute when the Reverse action is available; doing so loses the controlled relationship and reversal safeguards.

A Failed posting is not eligible for reversal because it did not reach Processed. Review the displayed failure reason and escalate it to the system administrator or support team. The Transaction screen does not currently provide an operator retry or recovery action; do not delete or reverse the record as a workaround.