Bundle 7 — Receive Credit Committee Report Data upon Questionnaire Submit OR upon Report Status Update "Approval"
Triggers: Questionnaire submitted or report status updated to "Approval" in YAPU
Business purpose
Bundle 7 extends Bundle 1 by adding a credit decision trigger. In addition to receiving data when a questionnaire is submitted, your system also receives a data push when a YAPU supervisor or credit committee officer updates the report status to "Approval". This allows downstream systems — such as loan origination or disbursement modules — to act on a formally approved credit decision without manual notification or data re-entry.
Capabilities
- Outbound on submit: CCR data is pushed to your system when the questionnaire is first submitted
- Outbound on approval: CCR data is re-sent when the report status is explicitly set to "Approval" in YAPU
- Enables automated workflows tied to the credit decision outcome
- No inbound data flow required
How it works
Trigger 1 — Questionnaire Submit:
- A loan officer completes and submits a questionnaire in YAPU.
- YAPU sends Data Set A to your system automatically.
Trigger 2 — Report Status Update "Approval":
- A YAPU user opens an existing customer profile and the Credit Committee Report.
- The user updates the report status to "Approval".
- YAPU sends Data Set A again to your system with the latest data, including the updated status.
Data exchange
| Direction | Data set | Content | Trigger |
|---|---|---|---|
| Outbound (YAPU → Client) | Data Set A | Configurable selection of questionnaire and CCR fields | Submit |
| Outbound (YAPU → Client) | Data Set A | Same data set, with updated report status | Report status → "Approval" |
:::info Data format All outbound data is delivered as JSON strings. The client system is responsible for identifying whether the push corresponds to an initial submission or an approval event, and acting accordingly. :::
When to use Bundle 7
Bundle 7 is the right fit when:
- Your institution's downstream process (e.g., loan disbursement, core banking update) should be triggered by a formal credit approval — not just submission
- You need data on both events: when the assessment is first completed and when it is approved
- You do not need inbound autofill or an eligibility check
Consider Bundle 1 if approval-based triggers are not needed. Consider Bundle 8 if you also want questionnaire autofill. Consider Bundle 9 if you also need an eligibility check.
Limitations
- Requires a YAPU questionnaire already configured for the integration
- Only a single questionnaire can be used per integration
- The "Approval" trigger is specifically tied to the report status field being set to the designated approval value — no other status updates trigger a data push
- Inbound data flow is not part of this bundle
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 1 | Bundle 7 with submit-only trigger |
| Bundle 4 | Bundle 7 using "update" as the second trigger instead of "Approval" |
| Bundle 8 | Bundle 7 + autofill from client system |
| Bundle 9 | Bundle 7 + eligibility check |
| Bundle 10 | Bundle 7 + eligibility check + update trigger |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 7 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::