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
2 matching entries · Page 1 of 1
Data Imports transfer history · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Follow a batch from upload through Registry ingestion.
What to do
- Use the transfer filters to find the batch and open it.
- Check its status and mapping version before continuing.
- Refresh history if you expect a recent change.
What you need
Operators see their own batches. Approvers and administrators see batches according to Registry scope.
Next step
Use the batch receipt for ingestion and Registration review for resulting registration decisions.
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?