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.

From programme setup to payment reconciliation

Programme management · From programme setup to payment reconciliation · all · Published version 2

Public task guidance

Provisional guidance

Follow the installed PBMS workflow from programme configuration through list approval, payment and reconciliation.

What to do

  1. Programme Admin configures the source registry, eligibility rule, benefit and enrolment and disbursement cycles. Use the authorised programme rules and review the calculated list.
  2. Payment submits the list to Finance. Finance, Audit and CEO decide in order. Programme Admin corrects a returned list and Payment resubmits it as a new revision for review.
  3. After final approval, Programme Admin can export the fully verified list and configures the approved sponsor bank route when needed. The assigned Payment role confirms the verified count, amount and revision before submitting the payment.
  4. Open View payment progress. Use the batch report to check dispatch and the envelope report to check reconciliation and reversals. Bridge exchanges and tracks payment instructions and reconciliation evidence between PBMS and the bank.
  5. Refer a failed, incomplete or reversed payment through the authorised reconciliation process. Retain the submitted list, envelope, batch and bank statement references for review.

What you need

Use the approved programme rules and the assigned roles. Eligibility, authorisation limits, sponsor bank controls and reconciliation rules require the applicable approved sources.

Next step

Record the verified outcome against the existing payment references. Refer unresolved differences through the authorised process before closing the reconciliation.

Source · Installed PBMS approval, payment and envelope controls verified with synthetic sandbox records. Business rules and role handoffs require client validation.