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

21 matching entries · Page 1 of 2

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?

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 the earlier job ends with no Registry row receipt for the affected row, reconcile that receipt and reopen the already-approved correction. If every row was received, leave the repeated batch unsubmitted or return it with the receipt evidence.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Track a queued Registry import · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The native Registry accepted the batch into its import queue.

What to do

  1. Record the batch and Registry references. Select Refresh Registry receipt to see the latest row counts and attempts.
  2. Use Activity to track the original handoff.

What you need

Queue acceptance confirms delivery to the queue. Row ingestion completes separately.

Next step

Continue on the same batch once the native receipt updates.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Data Imports administration · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Monitor batches and manage versioned source mappings.

What to do

  1. Use Transfers to inspect batch status and receipts.
  2. Use Sources and mappings to review the active source configuration.
  3. Open Access to check which Registry roles can operate the module.

What you need

An administrator needs native intake edit permission to transfer approved files.

Next step

Check the source and mapping version recorded on a batch when investigating a transfer.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Data Imports and Data Bridge workflow · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Follow a Data Imports batch through validation, independent approval and native Registry ingestion by the Data Bridge.

What to do

  1. The operator uploads the approved structured file, or fetches CSV from a configured connection, and verifies the included mapped rows.
  2. The first reviewer approves or returns the current batch. The operator corrects any return in the same batch and sends it back for approval.
  3. An authorised operator transfers the approved batch. The Data Bridge submits the included rows to the native Registry import queue and tracks the receipt.
  4. Compare the ingested and found counts, row evidence and native reference. Refresh an uncertain, queued or in-progress receipt on the existing batch.

What you need

Use the chosen source’s approved mapping and an assigned Registry role. The hosted pilot accepts only synthetic records with the required sample headers.

Next step

Follow Registration review for registrations created by a production mapping. The sandbox pilot confirms ingestion without creating beneficiary registrations.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Data Imports transfer history · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Follow a batch from upload through Registry ingestion.

What to do

  1. Use the transfer filters to find the batch and open it.
  2. Check its status and mapping version before continuing.
  3. Refresh history if you expect a recent change.

What you need

Operators see their own batches. Approvers and administrators see batches according to Registry scope.

Next step

Use the batch receipt for ingestion and Registration review for resulting registration decisions.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Inspect an import batch · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Check the source, mapping version, validation counts and available action.

What to do

  1. Read the batch status, source and counts.
  2. Open Reconcile records to inspect source and mapped values.
  3. Use the action shown for your role and the batch’s current status.

What you need

Check which rows are included before requesting approval.

Next step

Read Activity for changes and use the Registry receipt after transfer.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

My Data Imports batches · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Create, correct and transfer the imports assigned to your account.

What to do

  1. Use New import to start a batch or open a batch in Transfers.
  2. Resolve row issues and send the batch for approval.
  3. Reopen an approved batch to transfer it to the Registry.

What you need

Use a configured source and remain in the original batch for corrections.

Next step

Check the Registry receipt after transfer.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Read an approved import · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Approval is complete and the batch is ready for authorised transfer.

What to do

  1. Confirm the version and included count. Track the existing batch from Transfers.

What you need

The owner or an administrator with native intake-edit access can transfer the batch.

Next step

Check the Registry receipt once the authorised staff member transfers it.

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?