Example 1: Disability Cash Transfer Scheme
Last updated
Was this helpful?
Last updated
Was this helpful?
This process workflow provides an example of a the generic use case PRS.IBR.02 (SP-MIS publishes data on a batch of beneficiaries or households and the benefits that they have received). The example given here is for a scheme that provides cash transfer benefits to people with disabilities.
In this example, a disabled person has been enrolled in the scheme and is due to receive their first monthly cash transfer, alongside other members of the scheme. The SP-MIS completes its monthly payment cycle and reconciles the responses from the payment system to verify which beneficiaries have received their cash transfer. Depending on the scheme's business rules, failed payments may be re-tried.
Once the payment batch is closed, the SP-MIS has a confirmed list of beneficiaries that received the monthly cash transfer. The SP-MIS now uses the API to transmit the UIN of the beneficiaries confirmed to have received the benefit to the IBR, along with the identifier code for the scheme, the value of the payment made and the date on which the payment was made.
The IBR confirms receipt of the data to the SP-MIS. This ensures that the IBR has current information on the benefits provided by the scheme and the beneficiaries who received them.
The process steps below describe this flow in more detail.
Actors and Entities
SP-MIS, IBR, applicant
Prerequisites
Refer to Assumptionsfor prerequisites.
The beneficiary is enrolled in at least one scheme and has received a benefit.
Process Inputs
Setting up period updates from SP-MIS to IBR
Process Flow Steps
Step 1: SP-MIS sends a batch of UINs to the payment system for disbursement of payments.
The payments system returns a response confirming for which UIN a payment was made and for which a payment failed.
The SP-MIS records the benefits received by a batch of beneficiaries. As this is a cash transfer, it includes the date and monetary value of the benefit provided.
Step 2: The SP-MIS shares the benefit details with the IBR via the API.
For this example, the schedule is monthly, following the benefit distribution cycle for the scheme. The information transmitted includes the beneficiary's UIN, sex, date of birth, sub region code, marital status, poverty score, disability status, household ID, programme ID, programme name, registration date, enrolment date, status, benefit date, benefit value, benefit type, payroll date, payroll amount, payment credit date, payment credit amount, payment charges and payment status.
The IBR confirms receipt of the data.
Outputs
The IBR is updated with the details of the type of benefit received by a batch of beneficiaries.
Control Points
None