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

23 matching entries · Page 2 of 2

Partner consent bindings · Consent manager · all

NSIPA local workflow

Provisional guidance

Review the association between a partner and the policy that limits its access.

What to do

  1. Open the partner binding and check the partner, policy and applicable scope.
  2. Before creating a binding, confirm that the intended partner and policy are correct.
  3. Save only an authorised change and verify the resulting binding.

What you need

An authorised consent-management account and the correct partner or request reference.

Next step

Confirm the current request, policy and consent state before continuing with the related sharing workflow.

Common issues

If no record appears, check the selected filters and account permissions. Consent approval does not approve programme enrollment or payment. Ask the service administrator to investigate inconsistent or unavailable records.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Beneficiary lists · Programme management · all

NSIPA local workflow

Provisional guidance

Inspect a list’s programme, stage, counts and processing status.

What to do

  1. Find the list in the relevant enrollment or disbursement workflow.
  2. Check the calculation status and open the list details.
  3. Use the verification or approval controls available to your role.

What you need

Confirm the programme and cycle, especially when the results are scoped.

Next step

Review corrections and current revision before relying on calculations.

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

Disbursement cycles · Programme management · all

NSIPA local workflow

Provisional guidance

Find the disbursement cycle and its beneficiary list.

What to do

  1. Confirm the programme and cycle schedule.
  2. Open the related list to check calculation, approval and payment status.

What you need

Use the authorised cycle and matched enrollment information.

Next step

Follow the programme approval or payment workflow for the selected list.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Eligibility · Programme management · all

Provisional guidance

Evaluate a programme application against approved programme rules.

What to do

  1. Open the programme and its configured criteria.
  2. Review the relevant application evidence.
  3. Run or review the existing eligibility workflow and its results.

What you need

Approved programme rules and authorised programme access.

Next step

Complete the required approval before enrollment.

Common issues

Do not treat registration approval as an eligibility decision.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Enrollment cycles · Programme management · all

NSIPA local workflow

Provisional guidance

Review enrollment windows and find a programme’s enrollment list.

What to do

  1. Confirm the programme and open the relevant cycle.
  2. Check its dates and approval status before opening or creating the list allowed by your role.

What you need

Use approved cycle dates and check whether the registration window has closed where required.

Next step

Follow calculation and list status in the enrollment workflow.

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?

Reopen a closed case after a late reversal · Programme management · all

NSIPA local workflow

Provisional guidance

Use this workflow when a bank statement records a reversal against a payment after the case was closed. The PBMS envelope report can show the instruction as both reconciled and reversed.

What to do

  1. Payment refreshes and downloads the affected envelope report, records the list, revision, envelope and batch references, and gives the evidence to Finance. Hold further payment submissions.
  2. Finance matches the late statement entry to the affected instruction. Check the amount, effective date and reason, then recalculate the net balance across all linked payments and reversals. Record any unresolved difference.
  3. Programme Admin requests reopening under the existing case reference. Attach the late reversal evidence, the updated Finance reconciliation and the original closure decision.
  4. Audit verifies the chronology from approval through dispatch, reconciliation, closure and late reversal. Keep the original closure evidence and trace each payment to its own submitted revision, envelope, batch and bank statement entry.
  5. CEO reviews the Finance and Audit evidence and records the reopening decision, reason, date and follow-up owner in the authorised case process. Keep any later payment decision separate from reopening.

What you need

Use the same case reference and retain the closure decision, all linked approval histories, payment and reversal references, and the new bank statement evidence. PBMS reports provide Refresh report and Download report. Record reopening through the authorised case process.

Next step

Update the reopened case with the reconciliation outcome and assigned follow-up. A further disbursement requires separate authorisation and the applicable list approvals. When a separate payment authorisation is recorded, follow Process an authorised payment after case reopening.

Published version 2 · 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 the current registration · Registration review · all

NSIPA local workflow

Provisional guidance

Complete the three checks for the current household case before deciding.

What to do

  1. Check the household details and roster. Review any earlier return and verify the correction against the current details.
  2. Apply the approved procedure to any missing location or membership information. When a correction is needed, select Return for correction and give a specific reason.
  3. Complete the three checks before using Approve registration & connect, then review the confirmation.

What you need

An independent verifier decides the case. The workspace shows unrecorded and unverified location information explicitly.

Next step

After approval, check registry connection status. Programme eligibility and payment follow their own workflows.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?