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

13 matching entries · Page 1 of 2

Transfer an approved batch · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Send an approved batch to the native Registry import queue.

What to do

  1. Confirm the batch reference, source version and Approved status.
  2. Choose Transfer to Registry when your account has permission.
  3. Record the Registry reference shown in the batch and check the receipt.

What you need

Transfer requires the batch owner or administrator and native intake edit access.

Next step

Use Refresh Registry receipt to track processing.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reload an import changed in another browser · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Check the current batch when another session may already have started the Registry transfer.

What to do

  1. Use Reload batch on the existing batch. If the batch is submitting, unconfirmed or queued, use Refresh Registry receipt as available. If it is ingested, check the existing receipt and counts.
  2. If the refreshed batch is still Approved and no Registry transfer has started, follow the action available for your role.

Next step

Use the batch reference and its Registry receipt to follow the existing transfer.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Review and decide on an import batch · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Approve a submitted batch for transfer or send it back to the operator.

What to do

  1. Check the source and mapping version, included row counts and mapped Registry values.
  2. Choose Approve batch when the approved checks are satisfied.
  3. For a return, enter a specific reason and choose Return for correction.

What you need

Use the assigned first reviewer account and approved source criteria.

Next step

The operator corrects a returned batch or transfers an approved batch.

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?

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?

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?

Return a correction with an existing Registry receipt · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Compare the conflicting row against the earlier receipt before deciding on the correction.

What to do

  1. Open the affected row and its existing batch. Compare the source key and receipt. If the earlier transfer is still in progress, wait for its receipt or ask the Registry Administrator to reconcile it.

What you need

Approval is blocked while the correction includes a conflicting row.

Next step

If the correction is Awaiting approval, use Return for correction and give the earlier batch reference and affected row number. If the batch was already approved, send the evidence to the Registry Administrator. Review a revised correction only for confirmed outstanding rows.

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 approval queue · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Find submitted batches ready for independent review.

What to do

  1. Open Transfers and use the approval status filter.
  2. Open the submitted batch and inspect its mapped values and issues.
  3. Use Review decision to approve or return it with a reason.

What you need

You must have the assigned first reviewer role.

Next step

An approved batch becomes available for authorised transfer.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Exclude a row already received by Registry · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Check the earlier receipt before you continue with the affected batch.

What to do

  1. Open the affected row in Reconcile records. Use Open existing batch to see the earlier receipt when the button is available. Ask the Registry Administrator to verify the receipt if it belongs to another account.
  2. If the status is Registry transfer in progress, wait for the earlier receipt to settle. If it is Already received by Registry, keep the existing source key and exclude the row from an editable batch.

What you need

An approved batch with a conflict stays blocked from transfer. Ask the Registry Administrator to reconcile the approved batch before taking further action.

Next step

Keep the existing receipt. Submit only confirmed outstanding rows for independent approval. If all rows were already received, leave the repeat batch unsubmitted.

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?

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?