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
21 matching entries · Page 1 of 2
Understand importing a registry data source into PBMS · Beneficiary programme administration · all
Upstream reference — confirm feature availability
Provisional guidance
Legacy PBMS can use configured data sources to retrieve social registry records.
What to do
- Check the source service and the target individual or group register.
- Have the authorised administrator confirm endpoint and authentication configuration.
- Test a small fictional dataset and check field mapping.
What you need
Approved integration access and a configured data source.
Next step
Verify imported records before programme processing.
Common issues
Do not place passwords or tokens in knowledge content. Source and target identifiers must remain consistent.
References
Sources checked: 2026-10-05
Published version 2 · 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?
Data source · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Choose the configured source whose headers and mapping match the file or CSV connection.
What you need
Check Expected columns before validating. Use the Synthetic Data Imports test only source for fictional hosted-pilot rows.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Correct the source of beneficiary lists · Programme management · all
Upstream reference — confirm feature availability
Provisional guidance
Documented PBMS list generation uses registry data as its source.
What to do
- Identify the incorrect source record.
- Correct it through the registry workflow.
- Confirm the approved change before generating a replacement list where permitted.
What you need
Registry correction and programme permissions.
Next step
Review the regenerated list and its cycle state.
Common issues
Approved cycles may prevent new lists. Do not edit exported lists to simulate a registry correction.
References
Sources checked: 2026-10-05
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Data Imports administration · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Monitor batches and manage versioned source mappings.
What to do
- Use Transfers to inspect batch status and receipts.
- Use Sources and mappings to review the active source configuration.
- Open Access to check which Registry roles can operate the module.
What you need
An administrator needs native intake edit permission to transfer approved files.
Next step
Check the source and mapping version recorded on a batch when investigating a transfer.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
My Data Imports batches · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Create, correct and transfer the imports assigned to your account.
What to do
- Use New import to start a batch or open a batch in Transfers.
- Resolve row issues and send the batch for approval.
- Reopen an approved batch to transfer it to the Registry.
What you need
Use a configured source and remain in the original batch for corrections.
Next step
Check the Registry receipt after transfer.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Source selection and name · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Select an existing source to inspect its current mapping, or name a new source clearly for operators.
What you need
Identify the approved dataset or connection. Source mappings are versioned.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Start a data import · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Load structured records from an authorised file or configured connection.
What to do
- Choose the Data source and expand Expected columns.
- For an uploaded file, choose CSV or XLSX and select Validate file. For a configured connection, use Fetch and validate to retrieve its CSV.
- Open Reconcile records before requesting approval.
What you need
Files can contain up to 2 MB, 1,000 data rows and 40 columns. XLSX uses the first worksheet. Keep identifiers as text to preserve leading zeros. Extract and verify scanned or PDF data before preparing a structured file.
Next step
If validation lists missing headers, fix the file and start a new import.
Common issues
For the hosted synthetic pilot, select Synthetic Data Imports test only and use fictional rows with Reference and Test note headers.
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?
Households · Programme management · all
NSIPA local workflow
Provisional guidance
Find households available in this PBMS view.
What to do
- Search the list and open the intended record.
- Check the link to the target Registry before interpreting displayed data.
What you need
Use the source Registry for authorised record corrections.
Next step
Return to the selected programme to see its eligibility results.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
CSV or XLSX file · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Select a structured CSV or XLSX file for the chosen Data source.
What you need
Use the expected headers and keep identifiers as text. Upload up to 2 MB, 1,000 data rows and 40 columns. XLSX reads the first worksheet. For a configured connection, use Fetch and validate instead.
Published version 2 · 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?