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 2 of 2

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?

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?

Retry an import transfer · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Retry a failure that occurred before the Registry queue accepted the batch.

What to do

  1. Open the batch and verify that Retry transfer is available.
  2. Read the latest error and resolve the indicated issue.
  3. Choose Retry transfer and check the resulting Registry receipt.

What you need

The retry action is available only for a safe pre-queue failure.

Next step

Native workers own ingestion retries after queue acceptance.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Choose which connected CSV batch to resume · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Identify the correct batch when several connected CSV imports may match the retry.

What to do

  1. Open Transfers and select Refresh history. Use Batch reference to identify the batch you intend to resume. Connected imports can share a source, filename and time.
  2. When different originals have separate drafts, use Previous batch reference to match each draft to its original batch. Open the intended batch and continue from its status. Each batch has its own review, transfer and Registry receipt.

Next step

Continue from the selected batch’s status. Check its rows before approval or refresh its existing receipt if it was sent.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Continue with the separate CSV draft · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Identify the separate draft and the earlier batch it belongs to.

What to do

  1. Compare Batch reference if both browsers used Fetch a new CSV from the same earlier batch. Both browsers open the same separate draft. Use one browser to reconcile the rows and Send for approval.
  2. If the browsers started from different originals, each opens its own separate draft even when the source and filename match. Check Previous batch reference before sending either draft for approval.
  3. Open Transfers to find the earlier batch by reference. Choosing Fetch a new CSV from the separate draft starts another import.

Next step

After independent approval, use Transfer to Registry on the selected batch and follow its existing Registry receipt.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Field for duplicate checks · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Choose the required Registry field that identifies a source row across imports using the same source and destination.

What you need

Data Imports compares mapped values after the configured transforms. The check applies within a batch and against earlier receipts and in-progress transfers for the same source, register, template and key field. The Registry’s later record-level checks are a separate stage.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Incoming messages · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Follow data received by the Registry through its processing stages.

What to do

  1. Open the message matching the source and reference.
  2. Check validation, transformation and processing information displayed for the message.

What you need

Use the sender and message reference to locate the right event.

Next step

For Data Imports, compare the batch receipt with the native message status.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Resolve a connected CSV fetch error · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Recover when the connection is unavailable or Data Imports cannot read the response.

What to do

  1. Note the selected source, error and time. Use the same Registry login and select the same source under New import. Use Fetch and validate to reopen a saved batch whose response was lost. This works from another browser, including when both browsers retry together. If the workspace asks you to choose a match, open Transfers. Select Refresh history and use the batch reference because connected batches can share a filename.
  2. When the batch is reopened, continue from its current status. Use Fetch a new CSV only when you intend to start a separate import from that source. Repeat that action from the same earlier batch to find its separate import. To resume the original, open it by reference in Transfers.
  3. If the fetch never saved a batch, use the same action again once the source is available. Ask the integration administrator to verify the endpoint, credentials and CSV response if the error persists.

What you need

The endpoint requires HTTPS and a CSV response. Integration administrators check any server-side access credential.

Next step

Continue from the existing batch’s current status. Review a draft in Reconcile records. For a batch already sent to the Registry, check or refresh its receipt in Transfers.

Published version 9 · public guidance

Open this guide · Download plain text

Was this guide helpful?

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?