Bundle 8 — Receive ID, Autofill Questionnaire and 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 8 combines the autofill capability of Bundle 2 with the approval-based trigger of Bundle 7. Loan officers benefit from pre-populated questionnaires using existing customer data, while downstream systems receive a data push both at submission and at formal credit approval. This is well-suited for institutions that want to streamline data entry at the front end and automate approval-driven processes — such as loan disbursement or CBS record updates — at the back end.
Capabilities
- Inbound autofill: YAPU queries your system with the customer ID and pre-fills the questionnaire with existing customer data
- 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 set to "Approval" in YAPU
- Covers both directions of the data flow across two trigger events
How it works
Questionnaire start — Autofill:
- A loan officer opens a questionnaire in YAPU and enters the customer ID.
- YAPU sends Data Set A (ID) to your system.
- Your system returns Data Set B (customer data) if the ID is found; YAPU autofills the questionnaire.
- If not found, the officer fills in the questionnaire manually.
Trigger 1 — Submit:
- The officer finalizes and submits. YAPU sends Data Set C to your system.
Trigger 2 — Report Status Update "Approval":
- A YAPU user opens the customer's CCR and updates the report status to "Approval".
- YAPU sends Data Set C again to your system with the updated status reflected.
Data exchange
| Direction | Data set | Content | When |
|---|---|---|---|
| Outbound (YAPU → Client) | Data Set A | Customer identification number | On ID entry |
| Inbound (Client → YAPU) | Data Set B | Customer profile data for autofill | Response to ID lookup |
| Outbound (YAPU → Client) | Data Set C | Questionnaire and CCR fields | On submit |
| Outbound (YAPU → Client) | Data Set C | Updated CCR fields including approval status | On "Approval" status update |
:::info Data format Inbound data (Data Set B) must conform to the YAPU-specific format. All outbound data is delivered as JSON strings. :::
When to use Bundle 8
Bundle 8 is a strong fit when:
- Your institution wants to reduce manual data entry with autofill
- Downstream systems (e.g., disbursement, CBS) need to act on a formal approval — not just a questionnaire submission
- You do not require an eligibility check before the questionnaire starts
Consider Bundle 2 if approval-based triggers are not needed. Consider Bundle 9 if you need an eligibility check instead of autofill. Consider Bundle 10 if you need both eligibility checking and all trigger events.
Limitations
- Requires a YAPU questionnaire already configured for the integration
- Only a single questionnaire can be used per integration
- Inbound data (Data Set B) must conform to YAPU-specific format requirements
- The "Approval" trigger fires only when the report status is explicitly set to the designated approval value
- Autofill only activates when the customer ID is found in your system
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 2 | Bundle 8 with submit-only trigger |
| Bundle 7 | Bundle 8 without autofill |
| Bundle 5 | Uses "update" as the second trigger instead of "Approval" |
| Bundle 9 | Uses eligibility check instead of autofill, same triggers |
| Bundle 10 | Bundle 8 + eligibility check + update trigger |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 8 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::