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 2 of 2
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?
Field for duplicate checks · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Choose the required Registry field that identifies a source row across imports using the same source and destination.
What you need
Data Imports compares mapped values after the configured transforms. The check applies within a batch and against earlier receipts and in-progress transfers for the same source, register, template and key field. The Registry’s later record-level checks are a separate stage.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Incoming messages · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Follow data received by the Registry through its processing stages.
What to do
- Open the message matching the source and reference.
- Check validation, transformation and processing information displayed for the message.
What you need
Use the sender and message reference to locate the right event.
Next step
For Data Imports, compare the batch receipt with the native message status.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Registry import receipt · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Confirm how many included rows the Data Bridge logged in the native Registry.
What to do
- Check for Ingested by Registry and compare the reported ingested and found counts.
- Expand a row to check Registry logged. Excluded rows remain visible in the batch for traceability and stay outside the transferred set.
- Keep the Registry reference and Download audit report for authorised follow-up.
What you need
Ingestion records receipt by the Registry pipeline. Follow registration approval and publication separately where the configured source creates registrations. The hosted synthetic pilot verifies ingestion only.
Next step
Use the batch history to reopen this receipt. Follow Registration review where downstream registrations exist.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Registry integration configuration · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Inspect incoming or outgoing data mappings.
What to do
- Open the intended key path, subscription, semantic pattern, template or topic.
- Check the source and destination against the approved integration contract.
- Verify the change using a synthetic message.
What you need
Use the scope and environment shown in the configuration.
Next step
Trace the message through Incoming messages or Outgoing messages.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Resolve a connected CSV fetch error · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Recover when the connection is unavailable or Data Imports cannot read the response.
What to do
- Note the selected source, error and time. Use the same Registry login and select the same source under New import. Use Fetch and validate to reopen a saved batch whose response was lost. This works from another browser, including when both browsers retry together. If the workspace asks you to choose a match, open Transfers. Select Refresh history and use the batch reference because connected batches can share a filename.
- When the batch is reopened, continue from its current status. Use Fetch a new CSV only when you intend to start a separate import from that source. Repeat that action from the same earlier batch to find its separate import. To resume the original, open it by reference in Transfers.
- If the fetch never saved a batch, use the same action again once the source is available. Ask the integration administrator to verify the endpoint, credentials and CSV response if the error persists.
What you need
The endpoint requires HTTPS and a CSV response. Integration administrators check any server-side access credential.
Next step
Continue from the existing batch’s current status. Review a draft in Reconcile records. For a batch already sent to the Registry, check or refresh its receipt in Transfers.
Published version 9 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Prepare a dashboard import · Analytics · all
Upstream reference — confirm feature availability
Provisional guidance
Superset can import packaged dashboard definitions linked to configured datasets.
What to do
- Have an authorised analytics administrator confirm the target data connection.
- Choose a compatible dashboard ZIP package.
- Import through the available dashboard controls.
- Open the result and check every chart and filter.
What you need
Dashboard import permission and an approved data connection.
Next step
Validate counts against the source dataset.
Common issues
Never paste database credentials into help text; imported charts may require connection or schema corrections.
References
Sources checked: 2026-10-05
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Use programme reports and dashboards · Analytics · all
Upstream reference — confirm feature availability
Provisional guidance
Programme reporting can cover beneficiary statistics, transactions and reconciliation.
What to do
- Open the relevant dashboard.
- Confirm its dataset, period and programme filters.
- Check whether its numbers represent people, households, applications or transactions.
What you need
Dashboard viewing permission and a configured dataset.
Next step
Use the filtered results in authorised reporting.
Common issues
A dashboard may not refresh immediately when source records change; check its update time.
References
Sources checked: 2026-10-05
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?