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

4 matching entries · Page 1 of 1

Submission comment · Programme management · all

NSIPA local workflow

Provisional guidance

This comment is optional for Payment when initiating or resubmitting a list. On a return, you can summarise how the correction addressed the reviewer’s reason. PBMS records the comment with the submission in Verification history.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Resubmit a corrected disbursement list · Programme management · all

NSIPA local workflow

Provisional guidance

Send the corrected list through a fresh approval chain.

What to do

  1. Compare the rejection reason and Programme Admin correction in Verification history.
  2. Review the affected beneficiaries, included count, amount and list total.
  3. Add a submission comment if needed, then choose Resubmit for approval.

What you need

Confirm all requested changes are addressed before resubmitting.

Next step

Check that the new revision shows Awaiting Finance. PBMS increases the revision number. Prior decisions remain visible under the earlier revision.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Compare an existing Registry record · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

This tab compares the current submission with a published record in the Master Registry. The tab shows one entry per candidate.

What to do

  1. Open View More on the candidate. If several comparisons matched it, this opens the comparison with the highest match score. Compare Incoming and Candidate values and review the field-level Similarity and the overall match score.
  2. Check identifiers, household membership and location against authorised source information where those details are available.
  3. Record the evidence and any differences in the assigned review. If the applicant can correct the data, use Revalidate — return to field agent and name the fields to confirm.

What you need

A match score flags a candidate for review. Base the decision on the available evidence and approved duplicate procedure. Keep full identifiers out of free-text comments.

Next step

Use the assigned review task to record the outcome. If you are reviewing evidence as a Registry Administrator, share the scoped result with the assigned reviewer using the approved process.

Common issues

If the tab says No duplicates found, the current workspace has returned no visible comparison. Scope affects which records you can see. If you still suspect a match, give the submission reference and the reason to an authorised Registry Administrator for a scoped check.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Compare an intake duplicate · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

This tab compares the current submission with another submission still in the intake workflow. The tab shows one entry per candidate.

What to do

  1. Open View More on the candidate. If several comparisons matched it, this opens the comparison with the highest match score. Compare Incoming and Candidate values and review the field-level Similarity and the overall match score.
  2. Check identifiers, household membership and location against authorised source information where those details are available.
  3. Record the evidence and any differences in the assigned review. If the applicant can correct the data, use Revalidate — return to field agent and name the fields to confirm.

What you need

A match score flags a candidate for review. Base the decision on the available evidence and approved duplicate procedure. Keep full identifiers out of free-text comments.

Next step

Use the assigned review task to record the outcome. If you are reviewing evidence as a Registry Administrator, share the scoped result with the assigned reviewer using the approved process.

Common issues

If the tab says No duplicates found, the current workspace has returned no visible comparison. Scope affects which records you can see. If you still suspect a match, give the submission reference and the reason to an authorised Registry Administrator for a scoped check.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?