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

16 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. If an earlier correction blocked this batch, confirm that its native job has ended and the Registry Administrator has verified the affected rows are still outstanding. Reopen this approved batch after the earlier receipt is refreshed.
  3. Choose Transfer to Registry when your account has permission. 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 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Follow a correction blocked by an earlier Registry transfer · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

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

What to do

  1. If the warning offers Reload batch, use it to update the affected rows. Open the affected row in Reconcile records and select Open existing batch 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, select Refresh Registry receipt on the earlier batch and wait for the earlier receipt to settle. Reopen the blocked batch to see the updated row status. 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

If the earlier correction failed, ask the Registry Administrator to confirm that the native job has ended and the row was never logged. Refresh the earlier receipt, then reopen the already-approved correction. If Transfer to Registry is available, transfer that batch and check its receipt. If all rows were already received, leave the repeat batch unsubmitted. Keep the existing receipt.

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

Check a correction against the 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. When the earlier transfer fails and the row is confirmed outstanding, check the existing approval and retain both batch references. Review a revised correction only for confirmed outstanding rows.

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

Investigate Registry ingestion that needs attention · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The native ingestion job reported a problem after transfer.

What to do

  1. Refresh the receipt and check status, counts, attempts and Registry reference.
  2. Check row evidence and Activity. Refer the batch and queue references to authorised Registry support.

What you need

Confirm the native job is terminal and match the row logs to the receipt. A zero count with complete row evidence confirms there are outstanding rows. While the outcome is uncertain, keep any competing transfer on hold.

Next step

If a separate approved correction was blocked and the Registry Administrator confirms the row is still outstanding, refresh this receipt, then reopen the already-approved correction. The authorised Field Agent can transfer it when the action becomes available. Keep both Registry references and audit reports.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reconcile a blocked repeat Registry row · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Confirm whether the affected source key already has a receipt or is still in a native Registry job.

What to do

  1. Open the affected row and the existing batch. Compare the mapped source key, both batch references, the native Registry reference and the row receipt. If two approved corrections competed to send the row, check Activity to confirm which batch entered the Registry queue. Refresh that receipt and coordinate any uncertain outcome with the integration owner.

What you need

A duplicate correction stays blocked from transfer after approval. Preserve the earlier receipt and both audit trails.

Next step

Confirm which rows were already received and share the evidence with the Field Agent and First Reviewer. If the earlier transfer failed, verify that its native job has ended and no row log exists for the affected key. Refresh the earlier receipt, then reopen the already-approved correction and check whether the hold cleared. Retain both receipts when the Field Agent completes the recovery transfer.

Published version 3 · public guidance

Open this guide · Download plain text

Was this guide helpful?