Who can withdraw a transaction from reconciliation?

Only users with a dedicated permission. A withdrawn transaction leaves totals and further matching but stays in the logs with its documented reason. Every action, automatic or manual, is written to an immutable log with timestamp, identifier, user and action type, and an exportable audit file can be generated at any time.

A permissioned action

Sometimes a transaction should leave the matching process: a test payment, a duplicate receipt, a payment that belongs to another entity. Withdrawing it changes totals, so it is restricted to users with a dedicated permission, typically finance leads, not every operator of the back office.

What withdrawal does

• Removes the transaction from totals and from further matching attempts.
• Keeps it in the logs, with the documented reason entered by the user.
• Leaves the original records untouched, so the withdrawal can be reviewed or reversed.

The audit trail

Every action in reconciliation, automatic or manual, is written to an immutable log with a timestamp, the identifier of the record, the user and the type of action. An exportable audit file can be generated at any time for internal audit, external auditors or an acquirer. This is what lets a finance team hand over reconciliation to more people without losing control: the permission limits who can change figures, and the log shows exactly what was changed and why.