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

7 matching entries · Page 1 of 1

Track the submitted payment · Programme management · all

NSIPA local workflow

Provisional guidance

Follow the payment request already recorded for this approved list.

What to do

  1. Check the submission record and displayed Envelope and Batch status.
  2. Choose View payment progress, then open Payments for the linked envelopes and batches.
  3. Use the reports to check dispatch and reconciliation separately.

What you need

Use the same programme, cycle, list and approved revision when following progress.

Next step

If the status is pending, refresh the workflow or report for this request. Escalate an error with the list and payment references. For a further payment after two reversals, record this new envelope and batch in the existing case and track the reconciliation separately. After case reopening, link the new envelope and batch to the existing case reference and keep its reconciliation separate from the earlier payments.

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

Track outstanding payment instructions · 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

  1. 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.
  2. Keep the submitted batch and envelope references. Give Finance the unresolved instruction references, including any reversed items.

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

Continue tracking the existing envelope. Hold any further submission until the outcome and authorisation are confirmed.

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

Payment Batches · Beneficiary programme administration · all

NSIPA local workflow

Provisional guidance

Track payment batches and distinguish processing from confirmed settlement.

What to do

  1. Select the payment or batch for the correct programme and cycle.
  2. Check participants, totals and the recorded processing status.
  3. Use available details or reports to confirm the outcome; a generated or submitted payment instruction is not proof of bank settlement.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Payments · Beneficiary programme administration · all

NSIPA local workflow

Provisional guidance

Track payments and distinguish processing from confirmed settlement.

What to do

  1. Select the payment or batch for the correct programme and cycle.
  2. Check participants, totals and the recorded processing status.
  3. Use available details or reports to confirm the outcome; a generated or submitted payment instruction is not proof of bank settlement.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?