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

4 matching entries · Page 1 of 1

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?

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?

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?

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?