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

8 matching entries · Page 1 of 1

Exclude an import row · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Exclude a row when it should stay out of the transfer. The row remains visible during reconciliation. Check the excluded count and confirm the remaining included rows before sending the batch for approval.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Prepare an import for approval · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Complete the validation and reconciliation checks on a draft.

What to do

  1. Read the four counters and checked mapping version.
  2. Expand rows with issues. Correct a source value or exclude a row, then Save row and verify the mapped result.
  3. Use Send for approval once there are included rows and their validation checks pass.

What you need

Missing headers require a corrected file and a new import. The operator works on their own batch.

Next step

Track Awaiting approval or any return in Transfers.

Common issues

If a connected fetch retry reopened this draft, continue here. Use Fetch a new CSV only to start a separate import from that source.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Correct a returned import · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Apply the reviewer’s requested corrections in the existing batch.

What to do

  1. Read the return reason above the batch totals.
  2. Open affected rows and correct or exclude values as authorised.
  3. Check validation counts and use Send for approval again.

What you need

The owner edits a returned batch.

Next step

Confirm it appears in the review queue after resubmission.

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?

Registry import receipt · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Confirm how many included rows the Data Bridge logged in the native Registry.

What to do

  1. Check for Ingested by Registry and compare the reported ingested and found counts.
  2. Expand a row to check Registry logged. Excluded rows remain visible in the batch for traceability and stay outside the transferred set.
  3. Keep the Registry reference and Download audit report for authorised follow-up.

What you need

Ingestion records receipt by the Registry pipeline. Follow registration approval and publication separately where the configured source creates registrations. The hosted synthetic pilot verifies ingestion only.

Next step

Use the batch history to reopen this receipt. Follow Registration review where downstream registrations exist.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reconcile a partial Registry receipt · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Reconcile the original transfer with the native Registry job and identify any rows that still need action.

What to do

  1. Select Refresh Registry receipt on the original batch. Capture the batch reference, Registry reference, attempts and row counts with Download audit report.
  2. Use Reconcile records to distinguish rows marked Registry logged, No Registry row receipt and Excluded. Compare included row numbers with the native import job and its row logs through the authorised integration owner.

What you need

Preserve the original batch and audit evidence. The native Registry worker owns ingestion retries after queue acceptance.

Next step

Ask the integration owner to confirm the native outcome for each outstanding row. Coordinate a separate correction for confirmed outstanding rows only. Compare the correction receipt against the original receipt and the source keys, then retain both batch and Registry references with the audit reports.

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