> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/use-cases/case-studies/service-provider-reimbursement.md).
# Service Provider Reimbursement
## Introduction
OpenG2P has a reference implementation for the Service Provider Portal. A service provider can submit the reimbursement application on this portal after assisting the beneficiary. Subsequently, the reimbursement request is inspected and approved by accountants and cash managers. Post reimbursement approval, the payment switch transfers the reimbursement amount to the service provider account.
## Process
1. The service provider logs into the Service Provider Portal and searches for the beneficiary record.
2. The QR code in the beneficiary entitlement voucher is scanned to verify the issuing authority's digital signature and read the beneficiary entitlement details.
3. If the scan is successful, the service provider provides cash/medical assistance to the beneficiary.
4. The service provider uploads the supporting documents for assistance and submits the reimbursement application.
5. The accountant inspects the reimbursement application and approves the reimbursement amount.
6. The cash manager also inspects the application and approves it.
7. Post approval, the system generates an account payable PDF file with the account details required for the payment transfer. A QR code is embedded in this PDF to establish the source of truth and make the PDF tamper-proof.
8. The cash manager sends the PDF digitally to the payment switch.
9. The payment switch transfers the reimbursement amount per service provider account details in the PDF.
## Reference scenario
## Customizations
1. The program manager/administrator can custom-assign an approving officer for multiple approvals.
2. Though this example shows two approval stages, the number of stages can be customized.
3. The payment mode for reimbursement can be customized.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openg2p.org/1.3/use-cases/case-studies/service-provider-reimbursement.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
