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.
531 published entries across 18 services · 64 source-linked guides
5 matching entries · Page 1 of 1
Read an approved import · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Approval is complete and the batch is ready for authorised transfer.
What to do
- Confirm the version and included count. Track the existing batch from Transfers.
What you need
The owner or an administrator with native intake-edit access can transfer the batch.
Next step
Check the Registry receipt once the authorised staff member transfers it.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reload an import changed in another browser · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Check the current batch when another session may already have started the Registry transfer.
What to do
- Use Reload batch on the existing batch. If the batch is submitting, unconfirmed or queued, use Refresh Registry receipt as available. If it is ingested, check the existing receipt and counts.
- If the refreshed batch is still Approved and no Registry transfer has started, follow the action available for your role.
Next step
Use the batch reference and its Registry receipt to follow the existing transfer.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Data Imports approval queue · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Find submitted batches ready for independent review.
What to do
- Open Transfers and use the approval status filter.
- Open the submitted batch and inspect its mapped values and issues.
- Use Review decision to approve or return it with a reason.
What you need
You must have the assigned first reviewer role.
Next step
An approved batch becomes available for authorised transfer.
Published version 1 · 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?
Sources and mappings · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Manage the mapping that translates source columns into Registry fields.
What to do
- Choose Source to configure and confirm the destination register and native import template.
- Choose file upload or an available connected source. Map the spreadsheet columns, required values, transforms and the field for duplicate checks.
- Use Test mapping with sample values to inspect the output. Save the source mapping when authorised.
What you need
Use approved destination fields and configured connections. The server manages connector URLs and credentials.
Next step
New batches use the new mapping version. Existing batches retain their original mapping and version.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?