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.

534 published entries across 18 services · 64 source-linked guides

Persona workspace

464 matching entries · Page 13 of 39

Hand over the corrected disbursement list · Programme management · all

NSIPA local workflow

Provisional guidance

Check the saved correction and hand the existing list back to Payment.

What to do

  1. Review the correction in Verification history against the rejection reason.
  2. Check the affected beneficiary row, inclusion and list total. If more changes are needed, open Beneficiaries and use Correct.
  3. Once the return is addressed, hand the programme, cycle and revision to the assigned Payment user.

What you need

The correction is recorded on the current revision. The list remains Returned for correction until Payment resubmits.

Next step

Payment uses Resubmit for approval. The new revision starts at Finance.

Published version 1 · 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?

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?

Hold payments while Finance checks the reversal totals · Programme management · all

NSIPA local workflow

Provisional guidance

The reversal count exceeds the reconciled count. Confirm the statement evidence before any further payment activity.

What to do

  1. Refresh and download the report for the same envelope. Share it with Finance along with both bank statement references, the approved list and the batch.

What you need

Keep the current payment, list and envelope references with the referral.

Next step

Hold further payment activity while Finance confirms the bank movement and resolves or escalates the discrepancy.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Households · Programme management · all

NSIPA local workflow

Provisional guidance

Find households available in this PBMS view.

What to do

  1. Search the list and open the intended record.
  2. Check the link to the target Registry before interpreting displayed data.

What you need

Use the source Registry for authorised record corrections.

Next step

Return to the selected programme to see its eligibility results.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Initiate or resubmit list approval · Programme management · all

NSIPA local workflow

Provisional guidance

Send the complete or corrected disbursement list to Finance.

What to do

  1. Confirm programme, cycle, revision, count and total.
  2. Use Initiate approval for a Complete list.
  3. For a returned list, check the corrections and choose Resubmit for approval.

What you need

Use the assigned Payment account. For a corrective payment, check the authorised case reference and confirm that this is the separate list for review. For a further payment after two reversals, enter the escalation decision reference and confirm the new list matches its scope. After case reopening, include both the reopening and payment authorisation references with the existing case reference when you initiate approval of the new list.

Next step

Resubmission creates a new revision and starts again at Awaiting Finance.

Published version 4 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Investigate a reversal count discrepancy · Programme management · all

NSIPA local workflow

Provisional guidance

The envelope shows more reversals than reconciled instructions. Compare the report with the matched bank evidence before using the totals.

What to do

  1. Refresh and download the envelope report. Record the approved list, revision, envelope and batch references.
  2. Ask Finance to compare the original and latest statement entries and confirm whether they describe the same bank movement.

What you need

Use both statements when a repeat appears on a separately issued statement. The count discrepancy is a signal for review.

Next step

If the case is already closed, hold payment activity while the discrepancy is reviewed through the authorised process.

Published version 1 · public guidance

Open 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

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

Open this guide · Download plain text

Was this guide helpful?

Review programme lists before finalisation · Programme management · all

Upstream reference — confirm feature availability

Provisional guidance

Configured verifications provide evidence and accountability before a list is finalised.

What to do

  1. Open the relevant enrolment or disbursement list.
  2. Check the required verification stage.
  3. Review the supporting information and record your authorised assessment.

What you need

Assigned verification permission.

Next step

Send the list to the next configured reviewer.

Common issues

Do not claim a list is verified simply because it has been generated.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

List verification history · Programme management · all

NSIPA local workflow

Provisional guidance

Trace approval and correction decisions by revision.

What to do

  1. Check the Revision shown on the list.
  2. Read each event’s stage, decision and recorded comment.
  3. Open the attached evidence only if it is needed for an authorised review.

What you need

Earlier revisions can show decisions that belong to an earlier approval chain.

Next step

Use the current revision for approval and export checks.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Local administrative areas · Programme management · all

NSIPA local workflow

Provisional guidance

Check the local area and its parent area.

What to do

  1. Search by the local area name or code.
  2. Open the record and confirm the expected parent state or region.

What you need

Use the approved geography reference.

Next step

Verify the linked parent when a local area appears in the wrong scope.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

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

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

Open this guide · Download plain text

Was this guide helpful?