Bundle 5 — Receive ID, Autofill Questionnaire and Receive Credit Committee Report Data upon Questionnaire Submit OR upon Questionnaire OR Report Update
Triggers: Questionnaire submitted or questionnaire/report updated in YAPU
Business purpose
Bundle 5 combines the autofill capability of Bundle 2 with the extended trigger set of Bundle 4. Your system pre-populates YAPU questionnaires with existing customer data, and CCR output is delivered both at submission and whenever the questionnaire or report is subsequently updated. This is the most efficient option for institutions that want to minimize manual data entry and need ongoing synchronization throughout the credit lifecycle.
Capabilities
- Inbound autofill: YAPU queries your system with the customer ID and pre-fills questionnaire fields with your existing customer data
- Outbound on submit: CCR data is pushed to your system when the questionnaire is first submitted
- Outbound on update: CCR data is re-sent whenever the questionnaire or CCR report is modified
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 the ID is 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 — Update:
- If a YAPU user later modifies the questionnaire or CCR report, YAPU sends Data Set C again with updated values.
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 questionnaire and CCR fields | On questionnaire or report 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 5
Bundle 5 is a strong fit when:
- Your institution wants to reduce manual data entry with autofill and maintain real-time synchronization
- Questionnaires are frequently revisited and updated after initial submission
- You do not require an eligibility check at the start of the questionnaire
Consider Bundle 2 if you only need the autofill without the update trigger. Consider Bundle 10 if you also need an eligibility check and/or an "Approval" status trigger.
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 update trigger fires on any modification — your system should handle repeated data pushes for the same record
- Autofill only activates when the customer ID is found in your system
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 2 | Bundle 5 with submit-only trigger |
| Bundle 4 | Bundle 5 without autofill |
| Bundle 6 | Uses eligibility check instead of autofill, same triggers |
| Bundle 10 | Bundle 5 + eligibility check + approval trigger |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 5 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::