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
1 matching entries · Page 1 of 1
Resolve a row already in the Registry import pipeline · Master Beneficiary Registry · all
NSIPA local workflow
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
- 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.
- 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. Check the earlier job for saved-row evidence and receipt logs before reopening an approved correction. Registry receipt needs reconciliation means an earlier result remains uncertain. Keep the hold and ask the Registry Administrator to check it.
Published version 4 · public guidanceOpen this guide · Download plain text
Was this guide helpful?