GITBOOK-1119: No subject

g2p-bridge/features/README.md

@@ -14,13 +14,24 @@ layout:
 
 # Features
 
-The module will support the following functionalities at a high level
+The g2p-bridge subsystem offers the following functional features
+
+Incoming APIs from MIS/PBMS systems
+
+1.  creation of disbursement envelope
+
+    A disbursement envelope is an object that represents the header level information for a single benefit program - for a single disbursement cycle.
+
+    A benefit program will typically go through multiple disbursement cycles - some programs might have weekly disbursement cycles, some monthly, some quarterly and so on. Every disbursement cycle will potentially have 1000s of beneficiaries with their individual disbursement amounts.\
+    The disbursement envelope is an object that summarizes a single disbursement cycle - in terms of number of beneficiaries,  the total disbursement amount, the program identification and the cycle identification.
+2. status enquiry on a disbursement envelope\
+   The status enquiry will provide a snapshot of the current state of the envelope. It will provide the following details\
+   **a.** program identification\
+   **b.** cycle identification\
+   **c.** number of beneficiaries\
+   **d.** total disbursement amount in the envelope\
+   **e.** number of disbursments received from the upstream PBMS/MIS system\
+   **f.** number of disbursements shipped downstream to the Sponsor Bank\
+   **g.** number of disbursements reconciled with the Sponsor Bank\
+   **h.** number of disbursements reversed by the Sponsor Bank based on errors reported from further downstream destination banks 
 
-1. Ingestion (API as well as File based) of Benefit Transfers from upstream MIS/PBMS systems (compliant to G2PConnect and similar standards) - with extensibility to create custom interfaces with upstream MIS/PBMS systems.
-2. Handoff (API as well as File based) to Downstream Sponsor Banks (with G2PConnect and similar standards) with extensibility to create custom interfaces with Sponsor Banks
-3. Ingestion (API as well as File based) from Downstream Sponsor Banks of Reconciliation information (success/failure with appropriate reason codes) against every disbursement transaction - Reconciliation
-4. A lookup to resolve / fetch the Financial Address using the Beneficiary ID using a G2P-Connect standard API interface)
-5. Reporting - On Current and Historical Data with Search features on Disbursement Transactions based on Benefit Programs, Date/Month/Year of Disbursement, Beneficiary ID, Reconciliation Statuses etc.
-6. Notifications to Beneficiaries on
-   1. Receipt of Disbursement List for a Benefit program/disbursement cycle
-   2. Receipt of Reconciliation failures from Sponsor Bank (originating from Destination banks)