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

15 matching entries · Page 2 of 2

Report a partial Registry receipt · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Identify which included rows still lack a Registry receipt and report them to the Registry Administrator.

What to do

  1. Select Refresh Registry receipt on the existing batch and compare the ingested and found counts.
  2. Under Reconcile records, select Issues and exclusions only. Note the included rows marked No Registry row receipt. Clear the filter to compare rows marked Registry logged. Excluded rows were outside the transfer.
  3. Use Download audit report to save the evidence alongside the batch and Registry references.

What you need

Keep the original batch and receipt. A partial receipt needs native reconciliation before any further transfer.

Next step

Send the batch reference, Registry reference and outstanding row numbers to the Registry Administrator. After confirmation, use New import with the approved source mapping and a separate file containing only the confirmed outstanding rows. Correct their values, keep their existing source keys, and record the original batch reference in the correction evidence. Send the correction for approval and transfer that batch after approval.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Resolve a row already in the Registry import pipeline · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

An included row has the same source key as a received or in-progress row in another batch using the same source and destination mapping.

What to do

  1. If the warning offers Reload batch, use it to refresh the affected rows. Under Reconcile records, open the row and use Open existing batch when available. Ask the Registry Administrator if your account cannot see that batch.
  2. When two approved corrections try to send the same row, the first transfer reserves it. For Registry transfer in progress, refresh the earlier receipt and wait for its outcome. A received row stays outside any correction file.

What you need

Keep the original source key and evidence. Submission, approval and transfer are blocked while an included row conflicts with an earlier transfer.

Next step

Continue only with rows confirmed outstanding. If every row was received, leave the repeated batch unsubmitted or return it with the receipt evidence.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Review a partial Registry receipt · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Check whether the Registry receipt accounts for the rows you approved.

What to do

  1. Open the original batch in Transfers and select Refresh Registry receipt. Compare the included rows, the ingested count and the row evidence against the approved batch.
  2. Use Issues and exclusions only to find included rows marked No Registry row receipt. Clear the filter to confirm which rows were logged. Check Activity for the original approval and transfer.

What you need

The original approval remains in the audit trail. The partially ingested batch has no new approval or return action.

Next step

Share any discrepancies with the Registry Administrator. When a separate correction appears under Awaiting approval, compare it with the original receipt and the confirmed outstanding rows. Approve it if it contains only those rows with the expected keys, or return the correction with a reason.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?