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.

Resolve a row already in the Registry import pipeline

Master Beneficiary Registry · Resolve a row already in the Registry import pipeline · all · Published version 2

Public task guidance

Provisional guidance

An included row has the same source key as a received or in-progress row in another batch using the same source and destination mapping.

What to do

  1. If the warning offers Reload batch, use it to refresh the affected rows. Under Reconcile records, open the row and use Open existing batch when available. Ask the Registry Administrator if your account cannot see that batch.
  2. When two approved corrections try to send the same row, the first transfer reserves it. For Registry transfer in progress, refresh the earlier receipt and wait for its outcome. A received row stays outside any correction file.

What you need

Keep the original source key and evidence. Submission, approval and transfer are blocked while an included row conflicts with an earlier transfer.

Next step

Continue only with rows confirmed outstanding. If every row was received, leave the repeated batch unsubmitted or return it with the receipt evidence.

Source · Data Imports source-key guard and Registry receipt reconciliation