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 10 of 39

Configure sponsor bank routing · Programme management · all

NSIPA local workflow

Provisional guidance

Assign the approved sponsor bank route for the verified programme list.

What to do

  1. Confirm the intended programme and disbursement revision.
  2. Select the approved Sponsor bank routing entry and choose Save payment routing.
  3. Check that the saved route is reflected before the Payment role proceeds.

What you need

Use the authorised Programme Admin account and approved bank assignment. After case reopening, confirm the programme and cycle for the newly authorised list before setting its sponsor bank route.

Next step

Payment submits the verified list through the separate payment action.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Confirm the approved payment submission · Programme management · all

NSIPA local workflow

Provisional guidance

Verify exactly which approved list PBMS is about to submit for payment processing.

What to do

  1. Compare the beneficiary count, Total NGN and revision in the confirmation with the verified list.
  2. Use Cancel if anything differs from the approved information.
  3. Choose Confirm and proceed when the displayed snapshot is correct.

What you need

Use the authorised Payment account and the configured sponsor bank route. For a corrective payment, verify the case reference and confirm that the count, total and revision belong to the separately approved list. After two reversals, check the escalation decision reference and authorised amount against this new list before confirming. A closure decision ends payment follow-up. After case reopening, match the new payment authorisation and the approved revision to the count and amount shown. Use Cancel if they differ.

Next step

After submission, use View payment progress to track the existing envelope and batches.

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

Coordinate the partial payment follow-up · 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. Check the approved list revision and the routed batch. Ask Payment and Finance to identify affected instructions and the reason each remains open.

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

Keep the approved list and its revision intact. Coordinate any authorised new list after Finance confirms the outcome.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Correct a returned list · Programme management · all

NSIPA local workflow

Provisional guidance

Apply the authorised changes requested by the reviewer.

What to do

  1. Read the rejection reason for the current revision in Verification history.
  2. In Beneficiaries, choose Correct on the affected row.
  3. Update the authorised amount or inclusion, enter a Correction reason and choose Save correction.
  4. Check the saved change and list total before handing the list to Payment.

What you need

Use the assigned Programme Admin account.

Next step

The correction stays on the current revision. Payment resubmits the same list to create a new revision starting at Finance.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Correction reason · Programme management · all

NSIPA local workflow

Provisional guidance

Describe the reason for changing the amount or inclusion on the disbursement list. The reason is required to save the correction and is recorded in list history.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Create or edit a programme · Programme management · all

NSIPA local workflow

Provisional guidance

Enter the approved programme settings in the programme form.

What to do

  1. Review the programme identifiers, target registry and workflow configuration.
  2. Save the authorised changes and reopen Programme information to confirm the result.

What you need

Some settings are locked after creation or when they are in use.

Next step

Review the programme’s benefit mappings and approval configuration before creating cycles.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Review cycle manager settings · Programme management · all

Upstream reference — confirm feature availability

Provisional guidance

A cycle manager defines the configured behaviour of programme benefit cycles.

What to do

  1. Open the programme configuration.
  2. Inspect its cycle manager and available settings.
  3. Confirm the intended cycle behaviour with the programme owner before changing it.

What you need

Programme configuration authority.

Next step

Test the configuration using a demonstration cycle.

Common issues

Older cycle-manager screens differ from newer PBMS. Do not enable automatic approval without an approved policy.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Decide at Audit stage · Programme management · all

NSIPA local workflow

Provisional guidance

Record the Audit decision on the current revision.

What to do

  1. Check the Finance approval in Verification history for the same revision.
  2. Complete the approved Audit checks and enter Approval comment.
  3. Use the decision action shown to your account.

What you need

The current revision requires an independent approver at each level. For a corrective payment, verify that the case reference links the original reversal evidence and the separately reviewed list. After two reversals, trace the new list to both reversal records and the escalation decision reference. After case reopening, trace the closure, reopening and payment authorisation to the new list and its revision. Check both the Finance decision and the retained prior records.

Next step

Approval moves the list to Awaiting CEO. Rejection returns it for correction.

Published version 4 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Decide at Finance stage · Programme management · all

NSIPA local workflow

Provisional guidance

Record the Finance decision on a list awaiting that stage.

What to do

  1. Check programme, revision, count and total using the approved Finance checks.
  2. Enter Approval comment and attach supporting evidence if required.
  3. Choose Approve and save or Reject and save.

What you need

Use the assigned Finance group and current revision. For a corrective payment, match the authorised amount and case reference to the original reversal evidence before approving the current list. After two reversals, verify the newly authorised amount against both reversal records. After case reopening, verify all linked payments and reversals, the updated case balance and the newly authorised amount before approving the new list.

Next step

Approval moves the list to Awaiting Audit. Rejection returns it for correction.

Published version 4 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Disbursement · Programme management · all

Provisional guidance

Prepare and follow the existing benefit disbursement workflow.

What to do

  1. Check the approved benefit list and cycle.
  2. Complete the required independent authorisations.
  3. Monitor the existing disbursement status and exceptions.

What you need

Approved benefits and the required financial authorisations.

Next step

Reconcile reported payment outcomes.

Common issues

This sandbox does not issue real payments. Help content cannot grant financial authority.

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