Open Master Beneficiary Registry workspace ↗Skip to main content
NSIPA — National Social Investment Programmes AgencyNSIPA
Registration & enrollment
SYNTHETIC SANDBOX • Use fictional people and households. This service does not verify NIN or issue real payments.

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

Persona workspace

37 matching entries · Page 1 of 4

Registry configuration · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Review the Registry, register, data model and intake form settings.

What to do

  1. Open the relevant configuration list and locate the exact item.
  2. Review linked sections, tabs, fields and form versions before saving an approved change.

What you need

Use a reviewed configuration and verify downstream dependencies.

Next step

Recheck the affected form or register using a synthetic record after release.

Published version 2 · public guidance

Open 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

  1. Open the intended key path, subscription, semantic pattern, template or topic.
  2. Check the source and destination against the approved integration contract.
  3. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Map field collection data into the registry · Field data collection · all

Upstream reference — confirm feature availability

Provisional guidance

An ODK importer transforms selected submission fields into individual or group records.

What to do

  1. Identify the ODK form and target registry.
  2. Check that the form has its intended importer and field mapping.
  3. Test a fictional submission and inspect the transformed values.

What you need

ODK/import administration access and a supported mapping configuration.

Next step

Validate the imported record and its processing status.

Common issues

Mappings are form-specific. An ODK submission is not automatically a verified beneficiary.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

District Configuration · Beneficiary programme administration · all

NSIPA local workflow

Provisional guidance

Maintain the district configuration reference values used by registry or programme records.

What to do

  1. Search for an existing value before adding a duplicate.
  2. Check its label, code and related or parent records before editing.
  3. Save only an authorised correction and confirm that dependent record selections still show the intended value.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Registry · Beneficiary programme administration · all

NSIPA local workflow

Provisional guidance

Review the registry recorded in this registry.

What to do

  1. Find the intended person or household using the available search and filters.
  2. Open the record and check its identifying details, household links and supporting information.
  3. Use permitted edits only for evidenced corrections and confirm the saved values or required review status.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

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

  1. Check the source service and the target individual or group register.
  2. Have the authorised administrator confirm endpoint and authentication configuration.
  3. 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 guidance

Open this guide · Download plain text

Was this guide helpful?

Monitor imported registry submissions · Master Beneficiary Registry · all

Upstream reference — confirm feature availability

Provisional guidance

Partner and staff ingestion can create intake submissions or proposed updates.

What to do

  1. Identify the source, target register and intake form.
  2. Retain the returned correlation reference.
  3. Check classification, transformation and processing status where available.
  4. Investigate failed items before resubmitting.

What you need

An authorised integration and supported ingestion configuration.

Next step

Verify the resulting submission or change request.

Common issues

Acceptance by an API is not proof of successful registry processing; do not repeatedly send the same payload.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Outgoing integration configuration · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Maintain the configured topics and templates for outgoing registry integration.

What to do

  1. Select the intended topic or template.
  2. Check its field mappings, destination and expected record type.
  3. Save authorised changes and verify an approved test message before relying on the integration.

What you need

Integration configuration permission and the approved destination schema.

Next step

Inspect outgoing message status for the configured integration.

Common issues

A template change can affect future messages. Confirm dependencies and avoid using live personal data in troubleshooting examples.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

District Configuration · Master Beneficiary Registry administration · all

NSIPA local workflow

Provisional guidance

Maintain the district configuration reference values used by registry or programme records.

What to do

  1. Search for an existing value before adding a duplicate.
  2. Check its label, code and related or parent records before editing.
  3. Save only an authorised correction and confirm that dependent record selections still show the intended value.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Registry dashboard · Master Beneficiary Registry administration · all

NSIPA local workflow

Provisional guidance

Read registry summary counts with their recorded scope and reporting context.

What to do

  1. Check the labels for households, individuals and other displayed measures.
  2. Use a record list to inspect the information behind a count.
  3. Treat summary counts as registry information, not proof of programme eligibility or payment.

What you need

An account with permission for this screen and the correct record or configuration reference.

Next step

Confirm the resulting values or status in the related record before continuing with the next authorised task.

Common issues

Check filters, required fields and related records if an entry is missing or cannot be saved. Do not delete a referenced value or repeat a processing action to bypass an error. Contact the administrator with the record reference and displayed message if the issue remains.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Registry administration · Master Beneficiary Registry administration · all

NSIPA local workflow

Provisional guidance

Manage record and reference configuration for the administration workspace.

What to do

  1. Choose the appropriate record list or reference table.
  2. Check identifiers, relationships and current use before saving an approved change.

What you need

Use administrative permissions only for the authorised configuration task.

Next step

Check the affected Registry screen or record after a configuration change.

Published version 4 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Create or edit a programme · Programme management · all

NSIPA local workflow

Provisional guidance

Enter the approved programme settings in the programme form.

What to do

  1. Review the programme identifiers, target registry and workflow configuration.
  2. Save the authorised changes and reopen Programme information to confirm the result.

What you need

Some settings are locked after creation or when they are in use.

Next step

Review the programme’s benefit mappings and approval configuration before creating cycles.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?