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

2 matching entries · Page 1 of 1

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. For failed jobs, check the saved rows and receipt logs. If the job saved the row, keep the alternate row blocked and investigate the existing job. For a confirmed outstanding row, refresh the earlier receipt, then reopen the already-approved correction and check whether the hold cleared. Older jobs without saved-row tracking need native reconciliation before resubmission.

Published version 5 · 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 check whether the Registry logged the row or recorded its save. A saved row keeps the alternate blocked even if that native job failed. For a confirmed outstanding row, 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 6 · public guidance

Open this guide · Download plain text

Was this guide helpful?