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.

534 published entries across 18 services · 64 source-linked guides

Persona workspace

4 matching entries · Page 1 of 1

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. If a failed job saved the row, keep the alternate correction blocked and retain the approval evidence. 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 6 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Read a Registry receipt when the native job fails · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The Registry logged all included rows before the native job ended with an error.

What to do

  1. Compare the ingested count with the included rows. Under Reconcile records, confirm Registry logged for each affected row. Record the batch reference and native Registry reference with Download audit report.
  2. Field Agent: Keep the receipt and report the job error to the Registry Administrator. Any alternate correction for a logged row stays blocked.
  3. First Reviewer: Keep the existing approval and link its evidence to the received rows.
  4. Registry Administrator: Investigate the native job error using the existing Registry reference and row logs. Keep both batch references and the audit reports if another correction competed for the same row.

What you need

The row log confirms ingestion into the Registry pipeline. Check later registration decisions separately where the source creates registrations.

Next step

Preserve the received row and keep any matching correction on hold. Resolve the job error against the existing Registry reference.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Reconcile a saved Registry row with a missing receipt log · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The Registry saved the row and recorded that save in the same transaction. The normal receipt log is still missing for the indicated row.

What to do

  1. Open Reconcile records and check Registry saved, receipt log missing. Use Download audit report and keep the original batch and Registry references.
  2. Field Agent: Report the missing receipt log to the Registry Administrator. Keep the saved row out of follow-up corrections.
  3. First Reviewer: Keep the existing approval and use the original and alternate batch references to follow the reconciliation.
  4. Registry Administrator: Compare the saved-row evidence with the native job and receipt log. If both retries have ended and the log is still missing, keep the failed attempts with the incident evidence. Coordinate with Registry integration support to retry the existing native job once the log error is resolved. Refresh the original receipt to verify the restored log.

What you need

A saved row continues to block alternate transfers for its source key. Native retries reuse the same saved row and share the same receipt, even if they overlap. If another worker is still retrying when a worker fails, keep the alternate blocked and refresh the original receipt when the retry settles.

Next step

Resolve the missing log against the original transfer. After both retries fail, ask Registry integration support to retry that same job once the log error is resolved. Keep the saved row out of alternate batches throughout.

Published version 7 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Verify a restored Registry receipt log · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

The Registry restored the normal receipt log for a previously saved row on the original transfer.

What to do

  1. Check the original Registry reference and confirm Registry logged under Reconcile records. In Activity, look for Registry receipt log restored. Use Download audit report to retain that event.
  2. Field Agent: Keep the restored receipt and leave alternate transfers for the same row on hold.
  3. First Reviewer: Preserve the existing approval and link the restored receipt to the original and alternate batch references.
  4. Registry Administrator: Verify the restored log against the original job and saved-row evidence. If retries overlapped, confirm one receipt-log entry per saved row. If one worker failed after another restored the log, confirm the job stays Processed. If a later retry restored the log after both earlier retries failed, verify Processed and keep the earlier failures with the restored receipt and audit report. If a retry reaches an already Processed job, refresh the original receipt. Confirm the same Registry reference, the existing saved row and receipt log, and a single restoration event.

What you need

Retries use the original save and job reference. The attempt count can increase while the row and its receipt stay single. If a retry succeeds after an earlier worker failure, the job becomes Processed and clears the earlier job error. Once the job is Processed, any later worker failure stays in worker diagnostics. The logged row continues to block a matching alternate correction.

Next step

Use the original receipt and Registry reference for any follow-up. Where the source creates registrations, follow the relevant registration decisions separately.

Published version 6 · public guidance

Open this guide · Download plain text

Was this guide helpful?