Open Master Beneficiary Registry workspace ↗Skip to main content
NSIPA — National Social Investment Programmes AgencyNSIPA
Registration & enrollment
SYNTHETIC SANDBOX • Use fictional people and households. This service does not verify NIN or issue real payments.

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

Persona workspace

13 matching entries · Page 1 of 2

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

  1. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Review the amount exception before deciding on reopening · Programme management · all

NSIPA local workflow

Provisional guidance

Use the Finance reconciliation and Audit evidence to determine the disposition for the closed case.

What to do

  1. Review the unresolved amount before deciding whether to reopen. Record the decision, reason and owner under the existing case reference through the authorised process.

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 on hold pending that decision. Authorise any further payment separately if required.

Published version 1 · public guidance

Open 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

  1. 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 guidance

Open 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

  1. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Process a further payment after two reversals · Programme management · all

NSIPA local workflow

Provisional guidance

Use this route when the authorised case decision permits a further disbursement after the original and corrective payments both reversed.

What to do

  1. CEO records the decision, reason, scope and amount under the authorised case process. Keep the decision reference with the case reference, Finance reconciliation and Audit evidence.
  2. Programme Admin prepares a separate disbursement list for the authorised programme and cycle. Link its revision to the decision and both reversed payment records. Use the approved sponsor bank route.
  3. Payment uses Initiate approval and includes the escalation decision reference. Finance validates the authorised amount and both reversals. Audit checks the links and prior approval history. CEO records final list approval in PBMS.
  4. Once this separate list shows Fully verified and routing is ready, Payment uses Proceed to payments and checks the count, amount and revision before choosing Confirm and proceed.
  5. Finance and Audit track the new envelope and batch independently. Record their references and final reconciliation in the existing case alongside both reversed payments.

What you need

Use the authorised case reference, CEO decision reference, both earlier lists and bank reconciliation evidence. Preserve both submitted lists under their existing payment references.

Next step

Follow the new payment to reconciliation and update the case with its outcome. Route a further exception through the authorised case process. If the new payment reverses after case closure, follow Reopen a closed case after a late reversal and hold any further submissions pending an authorised decision.

Published version 2 · public guidance

Open 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

  1. Compare the reconciled and reversed counts with the approved totals.
  2. Match the statement entry to the relevant payment reference and verify the amount and effective date against the bank evidence available to you.
  3. 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 guidance

Open 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

  1. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Review the reversal escalation · Programme management · all

NSIPA local workflow

Provisional guidance

Review the reversal with the Finance reconciliation summary and Audit evidence.

What to do

  1. Confirm the affected payment references and the outcome established by Finance.
  2. Review the proposed response through the organisation’s authorised decision or escalation process.
  3. Record the resulting direction in the approved process with the supporting evidence.

What you need

Refresh or download the envelope report when reviewing the escalation. The existing approval history identifies the submitted revision.

Next step

Any corrective payment requires a separate authorised decision and the applicable review process. If this is a corrective payment that has also reversed, review Finance and Audit evidence for both payments and record the escalation decision through the authorised process. The prior approval applies only to the submitted corrective list. To authorise another payment, record the scope and amount of the new authorisation in the authorised case process. To close the case, record the closure decision and reason with the final reconciliation and Audit evidence. Approve and save applies to the current PBMS list revision. If a reversal is recorded after case closure, review the updated Finance and Audit evidence and record the reopening decision, reason and assigned follow-up through the authorised case process. A further payment requires its own authorised decision and approvals. If another payment is warranted after reopening, record a separate payment authorisation with its amount, scope and reason in the authorised case process. The new list then needs its own Finance, Audit and CEO approvals. If that newly authorised payment also reverses, review the new exception under the reopened case and record the next disposition. Any further payment requires its own authorisation and approvals. To close the reopened case, use the updated Finance reconciliation and Audit evidence to record the new closure decision and reason under the same case reference. Include the date and disposition. If the bank reports a possible duplicate after closure, keep the existing closure if Finance confirms the duplicate. Review any new movement or unresolved difference through the authorised case process. If Finance confirms that the later statement shows a different amount, review the unresolved amount before deciding whether to reopen. Record the disposition under the existing case reference.

Published version 9 · public guidance

Open 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

  1. 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.
  2. 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.
  3. 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.
  4. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Process an authorised payment after case reopening · Programme management · all

NSIPA local workflow

Provisional guidance

Use this workflow when the CEO records a separate payment authorisation after a reversal case is reopened. Keep the reopening and payment decisions under the existing case reference.

What to do

  1. CEO records the new payment decision, scope, amount and reason through the authorised case process. Reopening restores case follow-up. A separate authorisation is required for a new payment.
  2. Programme Admin prepares a separate disbursement list in the authorised programme and cycle. Link the new list to the case reference, reopening decision, new authorisation and each earlier payment and reversal. Configure the approved sponsor bank route.
  3. Payment initiates approval of the new list with the case and decision references. Finance verifies the net balance and authorised amount. Audit traces the decisions and earlier payment records. CEO records final approval of the new list revision.
  4. After the new list shows Fully verified and routing is ready, Payment compares the beneficiary count, amount and revision with the authorisation. Use Proceed to payments and Confirm and proceed for that approved list.
  5. Finance matches the new instruction to its bank statement entry. Audit preserves the new envelope, batch and reconciliation outcome alongside the earlier payment records and the closure, reopening and authorisation decisions.

What you need

Use a reopened case reference, a dated reopening decision, a separate payment authorisation, the updated reconciliation, and the prior approval and reversal evidence.

Next step

Record the new reconciliation outcome in the existing case. Use the authorised case process for any subsequent exception or closure decision. If the statement records another reversal while the case is reopened, keep the case active during review. Payment holds further attempts. Finance matches the debit and reversal, verifies the amount and reason, and updates the case balance. Audit retains the new approval and reversal trail. CEO reviews the new exception and records the disposition through the authorised case process. If the CEO decides to close the reopened case, follow Close a case after payment reversals and retain the earlier closure, reopening and payment authorisation.

Published version 3 · public guidance

Open 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

  1. 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.
  2. 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.
  3. 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.
  4. 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 guidance

Open 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

  1. 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.
  2. 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.
  3. 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.
  4. 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 guidance

Open this guide · Download plain text

Was this guide helpful?