Ask the local knowledge assistant
NSIPA knowledge library
Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.
531 published entries across 18 services · 64 source-linked guides
6 matching entries · Page 1 of 1
Log the reversal discrepancy · Programme management · all
NSIPA local workflow
Provisional guidance
Keep the reported discrepancy and the closure history traceable to the same case.
What to do
- Attach the latest PBMS envelope report and both statement references to the existing case reference. Record the referral to Finance and Audit.
What you need
Keep the previous closure decision and the submitted list references with the new evidence.
Next step
Use the Finance and Audit findings to update the authorised case record. Route any reopening decision through the authorised process.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Investigate the reversal count discrepancy · Programme management · all
NSIPA local workflow
Provisional guidance
The report totals need verification against the bank entries before they are used in the case balance.
What to do
- Match the original and latest statement entries to the same instruction. Compare the bank transaction reference, amount and value date and verify whether a new bank movement occurred.
- Record a confirmed duplicate once in the case balance. Log any remaining difference between the report count and the bank evidence.
What you need
Use the original reversal, latest statement and downloaded envelope report for the comparison.
Next step
Share the reconciliation and any unresolved discrepancy with Audit and the authorised decision owner.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Record the reversal amount exception in the case · Programme management · all
NSIPA local workflow
Provisional guidance
Link the Bridge exception and both bank statements to the existing case.
What to do
- Log the amount discrepancy under the existing case reference. Attach the current report, both bank statement references and the earlier closure decision.
What you need
The Number Of Reversal Amount Exceptions field counts recorded exceptions for this envelope. Use both bank statements to verify the amount and disposition.
Next step
Record the Finance and Audit findings and the authorised disposition with the submitted list and payment references.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Resolve a reversal amount discrepancy · Programme management · all
NSIPA local workflow
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.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Coordinate reversal follow-up · Programme management · all
NSIPA local workflow
Provisional guidance
Connect the reported reversal to the original programme, cycle and approved list.
What to do
- Check the programme, cycle and revision against the submitted list and Verification history.
- Keep the original approved list and payment reference in the case record.
- Give Payment and Finance the list, envelope and batch references through the authorised follow-up process.
What you need
The submitted payment report supports refresh and download. List correction and sponsor bank routing are locked for this submission.
Next step
Coordinate supporting information for the reconciliation owner. Route any proposed corrective action through the authorised process. If this is a corrective payment that has also reversed, link both submitted lists, their revisions and both envelope and batch references in the existing case. Notify Payment and Finance that the case remains open. If the CEO authorises another payment, prepare a separate disbursement list and link it to the decision and both reversals. If the CEO closes the case, archive both submitted lists and their references with the closure record. If a reversal is recorded after case closure, request reopening under the same case reference. Link the newly reversed payment and the closure decision to the existing case. If a new payment is authorised after reopening, prepare a separate list for the authorised amount. Link the reopening, new authorisation and earlier reversal records to that list under the existing case reference. If that newly authorised payment also reverses, keep the reopened case active during review and link the new reversal and bank reason to its approval, envelope and batch. If the CEO closes the reopened case, archive all submitted lists and payment references with the new closure decision and retain the earlier closure and reopening records. If the bank reports a possible duplicate after closure, log the confirmed duplicate under the existing case reference and retain the closure decision. Send unmatched evidence to the reconciliation owner. If the amounts differ, log the amount discrepancy under the existing case reference. Attach both statements and the approved list, envelope and batch references.
Published version 9 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Handle a duplicate payment reversal · Programme management · all
NSIPA local workflow
Provisional guidance
Review a bank reversal that may already be recorded on the same PBMS instruction, including after case closure.
What to do
- Payment refreshes and downloads the existing envelope report. Share the original and latest bank notices with Finance, along with the approved list, revision, envelope and batch references. Keep payment activity stopped for the closed case.
- Finance matches the payment instruction and bank transaction reference, amount and value date to the reversal already reconciled. Check the original and latest statement reference. An exact resend can reuse the original receipt. When Bridge accepts a second statement for an instruction with a recorded reversal, it keeps the first reversal and its count. Compare the bank entries to confirm that the second receipt refers to the same movement. Compare both statement references even when the PBMS totals appear consistent. If reversals exceed reconciled instructions, log a report discrepancy and verify the case balance from the matched bank evidence.
- If the same movement is confirmed, use the original reversal once in the case total. Audit retains the original closure, bank evidence and duplicate confirmation. Programme Admin logs the repeat receipt against the existing case reference.
- If evidence indicates a new movement or an unresolved difference, document the discrepancy and route it through the authorised case process. CEO reviews the Finance and Audit evidence and records any required decision on reopening.
What you need
Use the existing case reference, the original payment and reversal evidence, and the latest bank evidence. The PBMS envelope totals can support the review. Confirm duplication from the bank entries.
Next step
Keep the existing closure once the duplicate is confirmed. Follow the authorised reconciliation process for an unresolved difference or a separate reversal. When the amounts differ, use Resolve a reversal amount discrepancy and record the disagreement while Finance verifies the bank movement. Bridge records a reversal amount exception when the amounts differ or the original amount cannot be verified.
Published version 5 · public guidanceOpen this guide · Download plain text
Was this guide helpful?