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
10 matching entries · Page 1 of 1
Correct a source value · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Edit the incoming value on the affected row, then Save row and recheck the mapped Registry value.
What you need
Use the verified source information. If a row should stay out of the transfer, use Exclude this row from the transfer.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Compare an intake duplicate · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
This tab compares the current submission with another submission still in the intake workflow. 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?
Fetch and validate a connected CSV · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Retrieve the latest CSV from the selected connection and validate it using the saved source mapping.
What to do
- Choose the connected Data source and check Expected columns.
- Select Fetch and validate. A new fetch opens a draft with the source and mapping version. After a lost response, use the same Registry login and source from either browser to reopen the saved batch. Both browsers can reopen the same batch if they retry together.
- Open Reconcile records. Compare source and mapped values, then save any corrections or exclusions before sending for approval.
What you need
The connection must be configured and active. The CSV can contain up to 2 MB, 1,000 data rows and 40 columns.
Next step
Use the same draft through approval and the Data Bridge transfer. If it is returned, correct that batch and send it for approval again.
Common issues
For a sandbox test, select Synthetic connected CSV test only. Its headers are Reference and Test note. The fixture includes two versions of the same reference to exercise duplicate validation.
Published version 5 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Prepare an import for approval · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Complete the validation and reconciliation checks on a draft.
What to do
- Read the four counters and checked mapping version.
- Expand rows with issues. Correct a source value or exclude a row, then Save row and verify the mapped result.
- Use Send for approval once there are included rows and their validation checks pass.
What you need
Missing headers require a corrected file and a new import. The operator works on their own batch.
Next step
Track Awaiting approval or any return in Transfers.
Common issues
If a connected fetch retry reopened this draft, continue here. Use Fetch a new CSV only to start a separate import from that source.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Analytics datasets · Analytics · all
NSIPA local workflow
Provisional guidance
Review the datasets that supply analytics charts and dashboards.
What to do
- Find the dataset used by the intended report.
- Check its source, columns and calculated measures before editing.
- Make only authorised changes and verify the affected chart with its existing filters.
What you need
An account authorised for this screen and the correct record, application or project reference.
Next step
Confirm the saved values or displayed status before continuing with the related task.
Common issues
Check active filters and resolve the displayed validation message before retrying. If a control is unavailable, ask the service administrator to verify your permissions. Do not use a configuration change to bypass an approval or access requirement.
Published version 2 · 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?
Review and decide on an import batch · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Approve a submitted batch for transfer or send it back to the operator.
What to do
- Check the source and mapping version, included row counts and mapped Registry values.
- Choose Approve batch when the approved checks are satisfied.
- For a return, enter a specific reason and choose Return for correction.
What you need
Use the assigned first reviewer account and approved source criteria.
Next step
The operator corrects a returned batch or transfers an approved batch.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
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?
Check expected import columns · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Find the headers and required values for the selected source.
What to do
- Open Expected columns and compare the names with the file header row.
- Check identifier formatting and use Validate file or Fetch and validate for the selected source.
What you need
Headers must match the selected source’s mapping.
Next step
If required headers are missing, correct the file and start a new import.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Reconcile imported records · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Compare each source row with its mapped Registry values.
What to do
- Use Issues and exclusions only to focus on rows requiring attention.
- Open a row and compare its source values with the mapped output.
- When the batch is editable, correct the row or exclude it with the available toggle, then save.
What you need
Resolve required-value errors and duplicates among included rows before sending for approval.
Next step
A native row receipt appears after ingestion and indicates what reached the Registry pipeline.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?