NSIPADocumentation
Open platform

Data Imports and Data Bridge

Prepare and approve a batch, then follow its native Registry transfer and receipt.

Open workspace ↗

Prepare the batch

Select the configured data source and check Expected columns. Upload CSV or XLSX, or fetch CSV from a configured connection. The workspace supports up to 2 MB, 1,000 data rows and 40 columns. XLSX uses the first worksheet.

Check source and mapped Registry values. Resolve required fields and duplicate keys within the batch. Save each correction or exclusion and confirm which rows will transfer.

Fetch a connected CSV

In New import, choose a connected source, check Expected columns and select Fetch and validate. A new fetch opens a draft. Use Reconcile records to review the mapped rows before sending the draft for approval.

For a sandbox test, choose Synthetic connected CSV test only. Its CSV contains Reference and Test note columns and a duplicate reference. Resolve or exclude the duplicate and save the row before requesting approval.

If the browser loses the response, sign in with the same Registry login, choose the same source and use Fetch and validate. If the batch was saved, it opens at its current status even when both browsers retry together. Use Fetch a new CSV on the recovered batch only when you intend to start a separate import. Transfers and Refresh history can also locate the attempted batch by source and time.

Ask the integration administrator to verify the server-side HTTPS configuration and CSV response if the error persists. To check a batch already sent to the Registry, refresh its existing receipt in Transfers.

Choose between separate connected imports

When one browser starts a separate CSV import and another retries the original, each action keeps its own batch. If two browsers use Fetch a new CSV from the same earlier batch, both open the same separate draft. If they start from different originals, each original gets its own follow-up, even when both use the same source.

If a browser asks you to choose a match, open Transfers and select Refresh history. Use Batch reference to open the intended import and Previous batch reference to confirm which original it follows. A source, filename and time may appear on multiple batches.

Verify parallel CSV imports by role

As Field Agent, open two different original batches for the same connected source and use Fetch a new CSV in each browser. In the sandbox, use the synthetic source and distinct fictional rows for each fetch. Expect one follow-up per original. Compare Previous batch reference in each draft. Repeating the action from either original reopens its own follow-up.

As First Reviewer, open the submitted follow-ups by Batch reference. Check each batch’s included and excluded rows, then approve or return each independently. The Field Agent transfers each approved batch and follows its own Registry receipt.

As Registry Administrator, compare each follow-up’s receipt with the downloaded audit report. Verify the batch reference, native Registry reference, rows found, rows ingested and attempt count. If another browser has already started a transfer, reload that batch and check its existing receipt. The Second Reviewer sees the Data Imports access guidance for their role.

Review and transfer

Send the reconciled batch for approval. The approver checks included rows and returns issues with a reason when needed. Correct the same batch and send it back for review.

Check the Registry receipt

After approval, the authorised operator uses Transfer to Registry. The Data Bridge sends the included mapped rows to the native import queue. Check the Registry reference and Refresh Registry receipt on the same batch.

If another browser has changed the batch, use Reload batch and check the current status or receipt before transferring again.

Queued status confirms queue acceptance. Ingested by Registry and the receipt counts show native ingestion. If the receipt is partial or needs attention, use row evidence and the native reference for reconciliation. Keep the original batch and audit report. The hosted synthetic source exercises receipt tracking without publishing beneficiary registrations.

Configure sources and access

Administrators maintain versioned mappings. Check the destination register and template, input connection, required values, field transforms and duplicate key in Sources and mappings. Use Test mapping with sample values before saving an authorised change.

Existing batches retain the mapping version they started with. Access shows the assigned roles for data preparation, independent approval and administration.

Task and field reference

Workflow guides 1
Screen guides 33
Field reference 13