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.
534 published entries across 18 services · 64 source-linked guides
464 matching entries · Page 16 of 39
Read the current approval stage · Programme management · all
NSIPA local workflow
Provisional guidance
Follow the state and decisions recorded for this list.
What to do
- Check the list Status and Revision.
- Read Verification history for decisions on the current revision.
- Ask the assigned group to review the list when the current stage belongs to them.
What you need
The action displayed depends on the signed-in account and list state.
Next step
A returned list goes to Programme Admin before Payment resubmits it.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Read the envelope reconciliation report · Programme management · all
NSIPA local workflow
Provisional guidance
Check how many disbursements in this envelope have been reconciled or reversed.
What to do
- Compare the reconciled and reversed counts with the expected beneficiary count and quantity on the envelope and approved list.
- Choose Refresh report for the latest status or Download report for approved evidence handling.
- Investigate any shortfall, reversal or inconsistency using the envelope and linked batch references.
What you need
Use the report for this list and revision when recording the reconciliation result. For a corrective payment, record the new envelope and batch separately from the original reversal evidence.
Next step
If counts are incomplete, continue tracking the existing envelope and raise unresolved differences through the authorised reconciliation process. For a new payment after case reopening, record the new reconciliation outcome in the existing case and retain the earlier reversal reports.
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reconcile the flagged reversal amount · Programme management · all
NSIPA local workflow
Provisional guidance
Bridge keeps the first reversal record and lists the repeat amount for reconciliation review through the recorded exception.
What to do
- Match both statements to the approved instruction. Record the original amount, the later amount and the difference. If the original amount is unavailable, obtain it from the bank before resolving the exception.
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
Confirm the bank movement and effective date. Give Audit and the authorised decision owner the verified balance and any unresolved difference.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reconcile the partial payment · Programme management · all
NSIPA local workflow
Provisional guidance
Some declared instructions still await reconciliation, or this envelope includes both reconciled instructions and reversals.
What to do
- Open View payment progress and Refresh report. Compare Disbursements declared, reconciled and reversed. Check batch dispatch and financial address resolution when an instruction has no statement match.
- Match the statement entry and amount to each available instruction. Separate unreconciled instructions and confirmed reversals in the exception record.
What you need
Use the original envelope, batch and approved list revision. The counts describe instructions. Confirm the amount against authorised payment and statement evidence.
Next step
Give Payment the confirmed and outstanding items. Refer unresolved bank discrepancies through the approved reconciliation route.
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?
Reconciliation · Programme management · all
Provisional guidance
Compare payment processing with the settlement information returned by the payment backend.
What to do
- Open the payment batch or envelope report.
- Review dispatch, reconciliation and reversal states separately.
- Investigate pending or failed items with the payment operations team before treating the payments as settled.
What you need
The information requested by the screen and an authorised account.
Next step
Confirm the resulting status or saved information before continuing to the next task described on this screen.
Common issues
Resolve displayed validation errors. If access is denied, contact an authorised administrator.
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Record final list approval · Programme management · all
NSIPA local workflow
Provisional guidance
Record the final decision for the current disbursement revision.
What to do
- Confirm the current revision has Finance and Audit approvals in Verification history.
- Complete the approved final checks and enter Approval comment.
- Choose Approve and save or Reject and save.
What you need
Use the assigned final approval group. For a corrective payment, review the authorised case reference and the Finance and Audit evidence for this separate list. For a further payment after two reversals, check the escalation decision reference. This action approves the current list revision. After case reopening, confirm the separate payment authorisation and the Finance and Audit approvals for this revision. Payment submits the approved list after routing is ready.
Next step
Approval sets Fully verified. Rejection returns it to Programme Admin for correction.
Published version 4 · 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?
Registration and disbursement window dates · Programme management · all
NSIPA local workflow
Provisional guidance
Use the date picker to enter the date authorised for the labelled start or end of this window. Registration and disbursement have separate windows. Compare all four dates with the approved programme calendar before creating the cycle.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Correct the source of beneficiary lists · Programme management · all
Upstream reference — confirm feature availability
Provisional guidance
Documented PBMS list generation uses registry data as its source.
What to do
- Identify the incorrect source record.
- Correct it through the registry workflow.
- Confirm the approved change before generating a replacement list where permitted.
What you need
Registry correction and programme permissions.
Next step
Review the regenerated list and its cycle state.
Common issues
Approved cycles may prevent new lists. Do not edit exported lists to simulate a registry correction.
References
Sources checked: 2026-10-05
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reopen a closed case after a late reversal · Programme management · all
NSIPA local workflow
Provisional guidance
Use this workflow when a bank statement records a reversal against a payment after the case was closed. The PBMS envelope report can show the instruction as both reconciled and reversed.
What to do
- Payment refreshes and downloads the affected envelope report, records the list, revision, envelope and batch references, and gives the evidence to Finance. Hold further payment submissions.
- Finance matches the late statement entry to the affected instruction. Check the amount, effective date and reason, then recalculate the net balance across all linked payments and reversals. Record any unresolved difference.
- Programme Admin requests reopening under the existing case reference. Attach the late reversal evidence, the updated Finance reconciliation and the original closure decision.
- Audit verifies the chronology from approval through dispatch, reconciliation, closure and late reversal. Keep the original closure evidence and trace each payment to its own submitted revision, envelope, batch and bank statement entry.
- CEO reviews the Finance and Audit evidence and records the reopening decision, reason, date and follow-up owner in the authorised case process. Keep any later payment decision separate from reopening.
What you need
Use the same case reference and retain the closure decision, all linked approval histories, payment and reversal references, and the new bank statement evidence. PBMS reports provide Refresh report and Download report. Record reopening through the authorised case process.
Next step
Update the reopened case with the reconciliation outcome and assigned follow-up. A further disbursement requires separate authorisation and the applicable list approvals. When a separate payment authorisation is recorded, follow Process an authorised payment after case reopening.
Published version 2 · 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?