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

10 matching entries · Page 1 of 1

Record final list approval · Programme management · all

NSIPA local workflow

Provisional guidance

Record the final decision for the current disbursement revision.

What to do

  1. Confirm the current revision has Finance and Audit approvals in Verification history.
  2. Complete the approved final checks and enter Approval comment.
  3. 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 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?

Follow up a reversed payment · Programme management · all

NSIPA local workflow

Provisional guidance

Track the existing payment and share the reversal evidence with Finance.

What to do

  1. Refresh the envelope report and record the reconciled and reversed counts for the current reference.
  2. Use Download report and include the programme, cycle, list revision, envelope and linked batch references.
  3. Send the evidence to Finance through the authorised reconciliation process.

What you need

Use the existing submitted payment as the record of the original instruction.

Next step

Follow the reconciliation outcome with Finance. Any corrective payment requires a separate authorised decision. If this is a corrective payment that has also reversed, put further payment attempts on hold. Send both payment reports and the case reference to Finance for escalation. If another payment is authorised, submit only the newly approved list after routing and final approval. If the case is closed, stop further payment attempts and retain both reports with the case reference. If a reversal is recorded after case closure, refresh and download the affected envelope report, send it to Finance, and hold further submissions while the case is reviewed. If a new payment is authorised after reopening, submit only the newly approved revision once sponsor bank routing is ready. Track its new envelope and batch in the case. If that newly authorised payment also reverses, hold further payment attempts for the reopened case. Download the latest report and give Finance the new payment references. When the CEO closes the reopened case, end further payment activity for the closed case. Retain the reports under the same case reference. When a possible duplicate arrives, refresh and download the existing envelope report and share both bank notices with Finance. Keep payment activity stopped for the closed case. If a later statement shows a different reversal amount, keep payment activity on hold while Finance verifies the amount. Share both bank statements and the current PBMS report.

Published version 9 · public guidance

Open this guide · Download plain text

Was this guide helpful?

From programme setup to payment reconciliation · Programme management · all

NSIPA local workflow

Provisional guidance

Follow the installed PBMS workflow from programme configuration through list approval, payment and reconciliation.

What to do

  1. Programme Admin configures the source registry, eligibility rule, benefit and enrolment and disbursement cycles. Use the authorised programme rules and review the calculated list.
  2. Payment submits the list to Finance. Finance, Audit and CEO decide in order. Programme Admin corrects a returned list and Payment resubmits it as a new revision for review.
  3. After final approval, Programme Admin can export the fully verified list and configures the approved sponsor bank route when needed. The assigned Payment role confirms the verified count, amount and revision before submitting the payment.
  4. Open View payment progress. Use the batch report to check dispatch and the envelope report to check reconciliation and reversals. Bridge exchanges and tracks payment instructions and reconciliation evidence between PBMS and the bank.
  5. Refer a failed, incomplete or reversed payment through the authorised reconciliation process. Retain the submitted list, envelope, batch and bank statement references for review.

What you need

Use the approved programme rules and the assigned roles. Eligibility, authorisation limits, sponsor bank controls and reconciliation rules require the applicable approved sources.

Next step

Record the verified outcome against the existing payment references. Refer unresolved differences through the authorised process before closing the reconciliation.

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

Process an authorised corrective payment · Programme management · all

NSIPA local workflow

Provisional guidance

Follow the approved corrective decision while keeping the original reversal and any new PBMS payment traceable.

What to do

  1. Confirm the authorised decision and its case reference, affected instruction and approved amount. Keep the original list revision, envelope, batch and reversal evidence on the case.
  2. If the authorised procedure calls for a PBMS disbursement, Programme Admin prepares a separate list in the authorised programme and cycle. Record the link to the original reversal using the approved case record or available reference fields.
  3. Payment initiates approval of the separate list. Finance checks the amount and reversal evidence, Audit checks the approval trail and references, and CEO records the final list decision under the configured workflow.
  4. Once the separate list is Fully verified and routing is configured, Payment reviews its beneficiary count, total and revision in the confirmation and submits it through the normal payment action.
  5. Finance and Audit compare the new envelope and batch with the corrective approval and reconcile the new instruction separately. Keep both sets of references. Escalate a further reversal through the authorised process.

What you need

An authorised corrective decision and its supporting evidence are required. PBMS keeps the original submitted list available for review and uses its regular approval flow for the separate list.

Next step

Record the new dispatch and reconciliation outcome in the corrective case while retaining the original reversal evidence. If the corrective payment is reversed, follow the escalation guidance for a reversed corrective payment and hold further payment attempts pending an authorised decision.

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

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?

Verification queue · Programme management · all

NSIPA local workflow

Provisional guidance

Find lists requiring evidence or verification.

What to do

  1. Confirm the programme, cycle and list status.
  2. Open the list and compare the existing evidence with the approved checklist.
  3. Where available, record verification and check the history.

What you need

A completed verification and final approval are separate workflow steps.

Next step

Check the list’s next status after saving.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

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

  1. Use Refresh report and Download report to capture the current envelope evidence.
  2. Compare the reversal and linked batch references with the approved list, approval history and available statement evidence.
  3. 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 guidance

Open this guide · Download plain text

Was this guide helpful?