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

5 matching entries · Page 1 of 1

Issues and exclusions only · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Narrow reconciliation to flagged or excluded rows and, for partial or failed ingestion, rows with no Registry receipt.

What you need

Clear the filter to see the complete batch including rows already logged.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reconcile a partially ingested import · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The Registry logged only part of the transferred batch.

What to do

  1. Use Refresh Registry receipt on the original batch. Compare the ingested and found counts. Under Reconcile records, select Issues and exclusions only to find included rows marked No Registry row receipt. Clear the filter to see rows marked Registry logged. Excluded rows were outside the transfer.
  2. Field Agent: send the batch reference, Registry reference and affected row numbers to the Registry Administrator.
  3. First Reviewer: compare the outstanding rows with the approved batch and share any discrepancies.
  4. Registry Administrator: reconcile the receipt against the native job and row logs, and coordinate any correction with the integration owner.

What you need

Keep the original receipt and audit report. The Registry worker owns ingestion retries after queue acceptance. Keep the original transfer intact to avoid duplicating rows that were already logged.

Next step

After the integration owner confirms the outstanding rows, use New import for a separate correction file containing only those rows. Keep their existing source keys, link the original batch reference in the evidence, and send the correction through independent approval before transferring it.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reconcile imported records · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Compare each source row with its mapped Registry values.

What to do

  1. Use Issues and exclusions only to focus on rows requiring attention.
  2. Open a row and compare its source values with the mapped output.
  3. When the batch is editable, correct the row or exclude it with the available toggle, then save.

What you need

Resolve required-value errors and duplicates among included rows before sending for approval.

Next step

A native row receipt appears after ingestion and indicates what reached the Registry pipeline.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

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?

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?