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

Approval request evidence · Approval workflows · all

NSIPA local workflow

Provisional guidance

Review the request, policy version and approval steps.

What to do

  1. Open the intended request and check the active stage and recorded evidence.
  2. Read earlier actions and confirm the permitted next step.

What you need

Use the policy version recorded for this request.

Next step

Inspect decision and delivery history when an outcome has not reached the source application.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Approval audit log · Approval workflows · all

NSIPA local workflow

Provisional guidance

Inspect recorded approval events to understand the sequence of actions.

What to do

  1. Filter the log to the relevant request, policy or actor.
  2. Read timestamps, action names and related identifiers in sequence.
  3. Open the related request to confirm its current state.

What you need

An account authorised for this service and the correct record or task reference.

Next step

Use the event references when asking the approval administrator to investigate a discrepancy.

Common issues

An audit event records an action at a point in time; it may not describe the current request state. Avoid including unrelated personal information in exported evidence.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Review evidence · Approval workflows · all

Provisional guidance

Assess the information supporting an approval request before deciding.

What to do

  1. Open the request and check its subject and proposed change.
  2. Read the attached evidence and earlier review history.
  3. Resolve missing or inconsistent information through the available workflow before approving.

What you need

The information requested by the screen and an authorised account.

Next step

Confirm the resulting status or saved information before continuing to the next task described on this screen.

Common issues

Resolve displayed validation errors. If access is denied, contact an authorised administrator.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Assigned tasks · Approval workflows · all

NSIPA local workflow

Provisional guidance

Find and inspect approval tasks for the active workflow.

What to do

  1. Open the task assigned to your account and check the current stage.
  2. Review the linked request and evidence before deciding.
  3. Follow the source application when the task belongs to the Registry.

What you need

Use the current policy and assigned decision authority.

Next step

Check the resulting request status in its owning application.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Record decision · Approval workflows · all

Provisional guidance

Record an approval or rejection with a clear explanation.

What to do

  1. Confirm that the request is assigned to you and is awaiting a decision.
  2. Review the evidence and enter a reason where required.
  3. Submit the decision once and verify the recorded status and history.

What you need

The information requested by the screen and an authorised account.

Next step

Confirm the resulting status or saved information before continuing to the next task described on this screen.

Common issues

Resolve displayed validation errors. If access is denied, contact an authorised administrator.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Role assignment · Staff access administration · all

Provisional guidance

Maintain account access through the existing authorised identity workflow.

What to do

  1. Open the existing account administration service.
  2. Check the requested role and approval evidence.
  3. Apply only approved access changes through the native controls.

What you need

Account administration authority and approval evidence.

Next step

Verify the intended user access.

Common issues

Choosing a persona or reading help never grants permissions.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Coordinate reversal follow-up · Programme management · all

NSIPA local workflow

Provisional guidance

Connect the reported reversal to the original programme, cycle and approved list.

What to do

  1. Check the programme, cycle and revision against the submitted list and Verification history.
  2. Keep the original approved list and payment reference in the case record.
  3. Give Payment and Finance the list, envelope and batch references through the authorised follow-up process.

What you need

The submitted payment report supports refresh and download. List correction and sponsor bank routing are locked for this submission.

Next step

Coordinate supporting information for the reconciliation owner. Route any proposed corrective action through the authorised process. If this is a corrective payment that has also reversed, link both submitted lists, their revisions and both envelope and batch references in the existing case. Notify Payment and Finance that the case remains open. If the CEO authorises another payment, prepare a separate disbursement list and link it to the decision and both reversals. If the CEO closes the case, archive both submitted lists and their references with the closure record. If a reversal is recorded after case closure, request reopening under the same case reference. Link the newly reversed payment and the closure decision to the existing case. If a new payment is authorised after reopening, prepare a separate list for the authorised amount. Link the reopening, new authorisation and earlier reversal records to that list under the existing case reference. If that newly authorised payment also reverses, keep the reopened case active during review and link the new reversal and bank reason to its approval, envelope and batch. If the CEO closes the reopened case, archive all submitted lists and payment references with the new closure decision and retain the earlier closure and reopening records. If the bank reports a possible duplicate after closure, log the confirmed duplicate under the existing case reference and retain the closure decision. Send unmatched evidence to the reconciliation owner. If the amounts differ, log the amount discrepancy under the existing case reference. Attach both statements and the approved list, envelope and batch references.

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

Understand proposed and approved record changes · Master Beneficiary Registry · all

Upstream reference — confirm feature availability

Provisional guidance

A proposed change is separate from the approved record until its workflow completes.

What to do

  1. Open the record and identify the section to change.
  2. Describe the proposed correction and attach required evidence.
  3. Submit through the configured review process.
  4. Check the request status before assuming the live record changed.

What you need

Record editing permission and evidence.

Next step

Track verification and approval.

Common issues

A saved proposal does not by itself prove that the approved record has changed.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Attach and review record documents · Master Beneficiary Registry · all

Upstream reference — confirm feature availability

Provisional guidance

Record file fields and evidence attached to a change request serve different purposes.

What to do

  1. Check the file field label, allowed type and maximum size.
  2. Upload the required file into its intended slot.
  3. Confirm it appears before saving or submitting.
  4. Use the view control to inspect the file when reviewing evidence.

What you need

Document access and the required file.

Next step

Submit the proposed record or change for review.

Common issues

Supporting evidence on a change request may not become a permanent record file after approval.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?