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
14 matching entries · Page 1 of 2
Verify reversal evidence · Programme management · all
NSIPA local workflow
Provisional guidance
Review the evidence that links the reversal to the approved revision and original payment.
What to do
- Use Refresh report and Download report to capture the current envelope evidence.
- Compare the reversal and linked batch references with the approved list, approval history and available statement evidence.
- Keep the evidence with the related issue or audit record through the approved process.
What you need
Use the submitted revision to identify what was authorised and what actually occurred.
Next step
Escalate any missing or inconsistent evidence to the designated owner for resolution. If this is a corrective payment that has also reversed, preserve both approval histories and match each envelope, batch and bank statement entry to its submitted list. Escalate gaps in the chronology or evidence. If another payment is authorised, trace the new list to the decision and both prior reversals. If the case is closed, verify the closure evidence and retain both approved revisions with their payment and reversal references. If a reversal is recorded after case closure, preserve the original closure decision and evidence. Verify the late reversal against the affected approval, envelope, batch and bank statement before reviewing the reopening. If a new payment is authorised after reopening, trace the closure, reopening and payment authorisation to the new list. Keep each prior approval and reversal reference available for review. If that newly authorised payment also reverses, retain the new approval and reversal trail alongside the earlier decisions. Verify both the new payment and the reversal evidence. For closure after reopening, verify the full decision history, including the earlier closure, reopening, new authorisation and final closure. Link each submitted revision and reversal to the case. For a possible duplicate after closure, preserve the original closure and retransmission evidence. Check the payment, bank movement and duplicate confirmation against the original reversal. For a confirmed duplicate on a second statement, verify that the first reversal reference is preserved and attach the second receipt to the audit record. For a later statement with a different amount, preserve both statements and the original closure decision. Trace both entries to the submitted instruction and retain the bank confirmation.
Published version 10 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Close a case after payment reversals · Programme management · all
NSIPA local workflow
Provisional guidance
Use this workflow when the authorised decision closes a case after payment reversals, including a case that was reopened and had a further payment reverse.
What to do
- Finance matches each payment and reversal to its bank statement entry, verifies the amounts, dates and reasons, and records the final case balance. Record the approved disposition for any remaining difference.
- Audit verifies all submitted revisions, approval histories, envelope and batch references, and the bank statement evidence. For a reopened case, verify the earlier closure, reopening and any subsequent payment authorisation as part of the same decision history.
- CEO records the closure reason, date and disposition in the authorised case process. For a reopened case, add a dated closure decision under the existing case reference and retain the prior decisions.
- Programme Admin archives the closure with all submitted lists and payment references. Payment ends further payment activity for the closed case and retains the reports.
What you need
Use the existing case reference, final Finance reconciliation, Audit evidence and the recorded CEO closure decision. Close report in PBMS dismisses the report window. Record case closure through the authorised case process.
Next step
Keep all submitted lists and payment reports available for audit with their original approval and reversal records. If a later statement records a new reversal, follow Reopen a closed case after a late reversal under the same case reference. For a retransmitted reversal, follow Handle a duplicate payment reversal. Keep the existing closure when Finance confirms the same bank movement. Use the reopening process for a genuinely new reversal or another exception that requires a case decision. If a later statement gives a different amount for an existing reversal, follow Resolve a reversal amount discrepancy before making a new case decision.
Published version 5 · 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?
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?
Reconcile the reported reversal · Programme management · all
NSIPA local workflow
Provisional guidance
Determine the financial impact using the reported reversal and the matched statement entry.
What to do
- Compare the reconciled and reversed counts with the approved totals.
- Match the statement entry to the relevant payment reference and verify the amount and effective date against the bank evidence available to you.
- Record the discrepancy and the reconciliation disposition through the authorised process.
What you need
A reconciled count can include a reversed instruction. Check the individual evidence before recording the outcome.
Next step
Share the reconciliation summary with the designated reviewer or decision owner. Preserve the original list, revision and references. If this is a corrective payment that has also reversed, match both payments and both reversals against the bank statement. Confirm the net amount and any unresolved difference, then send the reconciliation summary for an authorised decision. If another payment is authorised, validate the newly authorised amount against the reconciliation and check the new list. If the case is closed, record the final reconciliation outcome and any residual exception in the case. If a reversal is recorded after case closure, match the new bank statement entry, recalculate the case balance across all linked payments and reversals, and submit the updated reconciliation for reopening review. If a new payment is authorised after reopening, verify all linked payments and reversals against the updated case balance and check the new authorised amount. Reconcile the new instruction separately. If that newly authorised payment also reverses, match the new debit and reversal, verify the statement amount, date and reason, and update the reconciliation for the case. For closure after reopening, record the final case balance after matching each payment and reversal, and document any remaining difference and its disposition. For a possible duplicate, compare the bank transaction reference, amount and value date against the reversal already matched to this instruction. Verify the bank movement before recording the original reversal once in the case total. Investigate any difference in the entry or totals. Compare both statement references when a repeat entry arrives on a separately issued statement. For the same movement on a second statement, check that the report still counts the first reversal once and retain both statement references in the case. If the values differ, record the original amount, the later amount and the difference. Verify the movement and effective date with the bank before using either figure to update the case balance.
Published version 11 · 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?
Review a reported payment reversal · Programme management · all
NSIPA local workflow
Provisional guidance
An envelope can contain reconciled disbursements and recorded reversals. Review both counts before closing the reconciliation.
What to do
- Check the number of disbursements reversed alongside the reconciled count.
- Compare both counts with the approved beneficiary count and total.
- Use Refresh report or Download report to capture evidence for the existing envelope and linked batch.
What you need
Keep the list, revision, envelope and batch references with the report.
Next step
Refer the reversal through the authorised reconciliation process. A corrective payment requires an authorised decision. If this is a corrective payment that has also reversed, keep both submitted lists and payment references on the case and escalate before any further payment attempt. After both payments reverse, check the authorised case decision. A further payment goes through a new approval list. Closure records the disposition and ends payment follow-up for the case. If the reversal arrived after case closure, route the new evidence through the authorised reopening process using the same case reference. If a reopened case has a separate payment authorisation, follow it through a new approval list and keep all earlier reversals linked to the case. If a payment authorised after reopening also reverses, retain its report and statement entries with the existing case. Use the authorised process to resolve the new exception. If the CEO closes the reopened case, retain every submitted list and reversal record under the same case reference and follow the recorded closure disposition. If the bank reports the same reversal again, confirm the underlying movement with Finance before changing the case balance or closure status. For an already recorded reversal on a second statement, verify the bank movement and retain both receipt references with the first reversal. If a later statement reports a different reversal amount for the same instruction, use Resolve a reversal amount discrepancy and refer the bank evidence to Finance.
Published version 10 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Review a reversal amount exception · Programme management · all
NSIPA local workflow
Provisional guidance
Bridge recorded an exception for a later statement after comparing it with the first reversal. The envelope can still show the original reconciliation and reversal counts.
What to do
- Refresh and download the report. Share the existing case, instruction, envelope and batch references with Finance. Keep the original and later bank statements with the case.
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
Keep further payment activity on hold while the authorised reconciliation process resolves the bank evidence.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Trace the reversal amount exception · Programme management · all
NSIPA local workflow
Provisional guidance
Check the audit trail for the original reversal and the later statement.
What to do
- Preserve both statements and the original closure decision. Match the exception to the instruction, approved revision, envelope and batch. Record the Finance conclusion and supporting bank evidence.
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
Retain the new record with the earlier decisions and refer any unresolved difference to the authorised case owner.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Decide at Audit stage · Programme management · all
NSIPA local workflow
Provisional guidance
Record the Audit decision on the current revision.
What to do
- Check the Finance approval in Verification history for the same revision.
- Complete the approved Audit checks and enter Approval comment.
- Use the decision action shown to your account.
What you need
The current revision requires an independent approver at each level. For a corrective payment, verify that the case reference links the original reversal evidence and the separately reviewed list. After two reversals, trace the new list to both reversal records and the escalation decision reference. After case reopening, trace the closure, reopening and payment authorisation to the new list and its revision. Check both the Finance decision and the retained prior records.
Next step
Approval moves the list to Awaiting CEO. Rejection returns it for correction.
Published version 4 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Decide at Finance stage · Programme management · all
NSIPA local workflow
Provisional guidance
Record the Finance decision on a list awaiting that stage.
What to do
- Check programme, revision, count and total using the approved Finance checks.
- Enter Approval comment and attach supporting evidence if required.
- Choose Approve and save or Reject and save.
What you need
Use the assigned Finance group and current revision. For a corrective payment, match the authorised amount and case reference to the original reversal evidence before approving the current list. After two reversals, verify the newly authorised amount against both reversal records. After case reopening, verify all linked payments and reversals, the updated case balance and the newly authorised amount before approving the new list.
Next step
Approval moves the list to Awaiting Audit. Rejection returns it for correction.
Published version 4 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Hold payment activity while Finance reviews the amount · Programme management · all
NSIPA local workflow
Provisional guidance
A recorded reversal amount exception needs bank evidence review before further payment activity.
What to do
- Refresh and download the report. Share both statement references, the existing case reference and the list, envelope and batch details with Finance.
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
Keep payment activity on hold while Finance verifies the amount. A further payment requires its own authorised decision and approvals.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?