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

3 matching entries · Page 1 of 1

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?

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?

Review the reversal discrepancy before deciding on reopening · Programme management · all

NSIPA local workflow

Provisional guidance

Use the Finance and Audit findings to determine the disposition for an already closed case.

What to do

  1. Review whether the statements show the same bank movement and whether the discrepancy has been resolved. Keep the closure when the duplicate is confirmed and the discrepancy is resolved or handled under the authorised process.

What you need

Refer a confirmed new bank movement or an unresolved exception through the authorised case process. The report count alone calls for reconciliation review.

Next step

Record any required case decision and the reason under the existing case reference. Further payment requires separate authorisation and the applicable approvals.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?