Resolve a reversal amount discrepancy
Programme management · Resolve a reversal amount discrepancy · all · Published version 2
Public task guidance
Provisional guidance
Use this when Bridge flags a later reversal with a different amount or cannot verify the first amount. Number Of Reversal Amount Exceptions can increase while the reconciliation and reversal counts stay the same.
What to do
- Payment keeps further activity on hold for the closed case. Refresh and download the report and give Finance the two bank statements, the existing case reference and the approved list, envelope and batch references.
- Finance matches the instruction, currency, value date and bank transaction references. Record the original reversal amount, the later reversal amount and the difference. Confirm with the bank whether the later entry is a correction, a separate movement or a reporting error.
- Programme Admin logs the amount discrepancy under the existing case reference. Audit preserves both statements, the original matched reversal, the approval history and the closure decision. Keep the bank confirmation with the case.
- CEO reviews the confirmed bank evidence and any unresolved difference through the authorised case process. Record any decision to reopen under the same case reference. Further payment requires separate authorisation.
What you need
Use both statement references and the first matched reversal. Bridge keeps the first reversal while recording the exception. Compare the bank entries and verify any missing original amount with Finance.
Next step
Keep the original reconciliation as evidence and hold payment activity while the discrepancy is reviewed. Record the verified amount and the case disposition through the authorised process.
Source · Installed Bridge reconciliation exceptions and PBMS envelope status. Case decisions and role handoffs are provisional for agency procedure validation.