# PBMS

The **Program and Beneficiary Management System (PBMS)** of OpenG2P enables the management of multiple programs and beneficiaries. PBMS provides user-friendly interfaces for program managers and, frontline workers, and beneficiaries to interact with a country’s social protection programs digitally. It also helps policymakers at higher levels of government get a bird’s eye view of program performance, beneficiary coverage, and public expenditure.

The PBMS is based on [Odoo ERP/MIS](https://www.odoo.com/) and leverages Odoo's strength of easily extending modules to implement new functionality. The underlying database used is [Postgres](https://www.postgresql.org/).

Some of the key benefits for a country or an organisation using PBMS are:

* Manage **multiple** programs in one system
* Define eligibility and entitlement rules like [Proxy Means Test](https://docs.openg2p.org/products/pbms/previous-generation/functionality/eligibility/proxy-means-test) (**PMT)** to automatically create eligible beneficiaries
* Maintain[ **beneficiary registry**](https://docs.openg2p.org/products/pbms/previous-generation/functionality/beneficiary-management/beneficiary-registry)**.**
* Enable [**digital cash transfer**](https://docs.openg2p.org/products/g2p-bridge) by seamlessly connecting to payment systems
* Offer [**self-service portal**](https://docs.openg2p.org/products/pbms/previous-generation/functionality/self-service-portal) to residents
* Send [**notifications**](https://docs.openg2p.org/products/pbms/previous-generation/functionality/notifications) to beneficiaries via SMS and email
* Issue digitally signed [**e-Vouchers**](https://docs.openg2p.org/products/pbms/previous-generation/functionality/disbursement-cycles/e-voucher) to beneficiaries
* **Share** beneficiary data with other systems/departments in an interoperable fashion
* Pull beneficiary data from other registries (departments) to avoid the collection of the same data multiple times

The functional architecture of PBMS is shown below.

<figure><img src="https://3034178245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZcdob2emEcLMvLyIxqT%2Fuploads%2FyiRs0YqxaHgmaDeDmFE5%2Ffunctional-architecture.jpg?alt=media&#x26;token=a944015a-7d05-4d1f-bb95-35a2bc017a68" alt=""><figcaption></figcaption></figure>

## Benefit disbursement process flow

The visual below depicts the typical process flow from identifying beneficiaries to disbursement of benefits. The primary demographic data resides in the Social Registry (a separate module) while the processing of this data to generate a disbursement list is carried out in the PBMS. Notice that the PBMS holds the [Beneficiary Registry](https://docs.openg2p.org/products/pbms/previous-generation/functionality/beneficiary-management/beneficiary-registry).

<figure><img src="https://3034178245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZcdob2emEcLMvLyIxqT%2Fuploads%2FNdbu63p6Va7n554joWzW%2Fimage.png?alt=media&#x26;token=4b8fa522-6a5b-488e-a316-1a531afde9b0" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openg2p.org/products/pbms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
