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
7 matching entries · Page 1 of 1
Compare an existing Registry record · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
This tab compares the current submission with a published record in the Master Registry. The tab shows one entry per candidate.
What to do
- Open View More on the candidate. If several comparisons matched it, this opens the comparison with the highest match score. Compare Incoming and Candidate values and review the field-level Similarity and the overall match score.
- Check identifiers, household membership and location against authorised source information where those details are available.
- Record the evidence and any differences in the assigned review. If the applicant can correct the data, use Revalidate — return to field agent and name the fields to confirm.
What you need
A match score flags a candidate for review. Base the decision on the available evidence and approved duplicate procedure. Keep full identifiers out of free-text comments.
Next step
Use the assigned review task to record the outcome. If you are reviewing evidence as a Registry Administrator, share the scoped result with the assigned reviewer using the approved process.
Common issues
If the tab says No duplicates found, the current workspace has returned no visible comparison. Scope affects which records you can see. If you still suspect a match, give the submission reference and the reason to an authorised Registry Administrator for a scoped check.
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Data Imports and Data Bridge workflow · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Follow a Data Imports batch through validation, independent approval and native Registry ingestion by the Data Bridge.
What to do
- The operator uploads the approved structured file, or fetches CSV from a configured connection, and verifies the included mapped rows.
- The first reviewer approves or returns the current batch. The operator corrects any return in the same batch and sends it back for approval.
- An authorised operator transfers the approved batch. The Data Bridge submits the included rows to the native Registry import queue and tracks the receipt.
- Compare the ingested and found counts, row evidence and native reference. Refresh an uncertain, queued or in-progress receipt on the existing batch.
What you need
Use the chosen source’s approved mapping and an assigned Registry role. The hosted pilot accepts only synthetic records with the required sample headers.
Next step
Follow Registration review for registrations created by a production mapping. The sandbox pilot confirms ingestion without creating beneficiary registrations.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Find a record · Master Beneficiary Registry · all
Provisional guidance
Locate an existing registry record before creating or changing information.
What to do
- Search using the available name or reference fields.
- Compare the matching records to avoid selecting the wrong person or household.
- Open the correct record and check its current status and history.
What you need
The information requested by the screen and an authorised account.
Next step
Confirm the resulting status or saved information before continuing to the next task described on this screen.
Common issues
Resolve displayed validation errors. If access is denied, contact an authorised administrator.
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
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?
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
- Under Reconcile records, open the affected row. If Open existing batch is available, use it to compare the earlier receipt. Ask the Registry Administrator if your account cannot see that batch.
- 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.
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?
Link members to a household or group · Master Beneficiary Registry administration · all
Upstream reference — confirm feature availability
Provisional guidance
Legacy groups can link existing individual registrants as members.
What to do
- Open the group or household.
- Use the Members section to select existing individuals.
- Check each person and membership relationship.
- Review and save the proposed membership.
What you need
Group-editing permission and the member records.
Next step
Check the saved membership and any applicable review status.
Common issues
A person’s name alone is insufficient to identify the correct record; compare the authorised identifiers.
References
Sources checked: 2026-10-05
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?