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
3 matching entries · Page 1 of 1
Report a partial Registry receipt · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Identify which included rows still lack a Registry receipt and report them to the Registry Administrator.
What to do
- Select Refresh Registry receipt on the existing batch and compare the ingested and found counts.
- Under Reconcile records, select Issues and exclusions only. Note the included rows marked No Registry row receipt. Clear the filter to compare rows marked Registry logged. Excluded rows were outside the transfer.
- Use Download audit report to save the evidence alongside the batch and Registry references.
What you need
Keep the original batch and receipt. A partial receipt needs native reconciliation before any further transfer.
Next step
Send the batch reference, Registry reference and outstanding row numbers to the Registry Administrator. After confirmation, use New import with the approved source mapping and a separate file containing only the confirmed outstanding rows. Correct their values, keep their existing source keys, and record the original batch reference in the correction evidence. Send the correction for approval and transfer that batch after approval.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reconcile a partial Registry receipt · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Reconcile the original transfer with the native Registry job and identify any rows that still need action.
What to do
- Select Refresh Registry receipt on the original batch. Capture the batch reference, Registry reference, attempts and row counts with Download audit report.
- Use Reconcile records to distinguish rows marked Registry logged, No Registry row receipt and Excluded. Compare included row numbers with the native import job and its row logs through the authorised integration owner.
What you need
Preserve the original batch and audit evidence. The native Registry worker owns ingestion retries after queue acceptance.
Next step
Ask the integration owner to confirm the native outcome for each outstanding row. Coordinate a separate correction for confirmed outstanding rows only. Compare the correction receipt against the original receipt and the source keys, then retain both batch and Registry references with the audit reports.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reconcile a partially ingested import · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
The Registry logged only part of the transferred batch.
What to do
- Use Refresh Registry receipt on the original batch. Compare the ingested and found counts. Under Reconcile records, select Issues and exclusions only to find included rows marked No Registry row receipt. Clear the filter to see rows marked Registry logged. Excluded rows were outside the transfer.
- Field Agent: send the batch reference, Registry reference and affected row numbers to the Registry Administrator.
- First Reviewer: compare the outstanding rows with the approved batch and share any discrepancies.
- Registry Administrator: reconcile the receipt against the native job and row logs, and coordinate any correction with the integration owner.
What you need
Keep the original receipt and audit report. The Registry worker owns ingestion retries after queue acceptance. Keep the original transfer intact to avoid duplicating rows that were already logged.
Next step
After the integration owner confirms the outstanding rows, use New import for a separate correction file containing only those rows. Keep their existing source keys, link the original batch reference in the evidence, and send the correction through independent approval before transferring it.
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?