Bundle 10 — Receive ID, Autofill Questionnaire and Receive Credit Committee Report Data upon Questionnaire Submit OR upon Questionnaire or Report Update OR upon Report Status Update "Approval"
Triggers: Questionnaire submitted or questionnaire/report updated or report status updated to "Approval" in YAPU
Business purpose
Bundle 10 combines the autofill capability with all three outbound trigger events — submission, update, and approval. Loan officers benefit from pre-populated questionnaires using existing customer data, while your system receives a data push at every significant point in the credit lifecycle: when the questionnaire is first submitted, whenever it is subsequently modified, and when the report is formally approved. This provides maximum data currency between YAPU and your core banking or CRM system while reducing manual data entry at the start of each assessment.
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 update: CCR data is re-sent whenever the questionnaire or CCR report is modified
- Outbound on approval: CCR data is re-sent when the report status is set to "Approval"
- Full two-way integration across all 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 checks whether the ID exists:
- Found: Returns Data Set B (customer data); YAPU autofills the questionnaire.
- Not found: Questionnaire continues without autofill; officer fills in fields manually.
Trigger 1 — Submit:
- The officer finalizes and submits. YAPU sends Data Set C to your system.
Trigger 2 — Questionnaire or Report Update:
- A YAPU user opens the customer profile and modifies the questionnaire or CCR report fields. YAPU sends Data Set C again with updated values. This step can repeat as many times as needed until the CCR status reaches "Approved" or "Rejected".
Trigger 3 — Report Status Update "Approval":
- A YAPU user sets the report status to "Approval". YAPU sends Data Set C once more, reflecting the final approval.
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 |
| Outbound (YAPU → Client) | Data Set C | 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. Your system should be prepared to receive multiple pushes for the same customer record across different trigger events. :::
When to use Bundle 10
Bundle 10 is a strong fit when:
- Your institution wants to minimize loan officer data entry using autofill
- Your system must stay fully synchronized with YAPU across submission, revisions, and approval
- Downstream workflows depend on both data changes and the formal credit decision event
Consider a lighter bundle if not all triggers are needed:
If you need an eligibility check instead of (or in addition to) autofill with all triggers, see Bundle 11.
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 can fire multiple times per record — your system should handle repeated pushes correctly
- Autofill only activates when the customer ID is found in your system
- The "Approval" trigger fires only when the report status is explicitly set to the designated approval value
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 5 | Bundle 10 without the approval trigger |
| Bundle 8 | Bundle 10 without the update trigger |
| Bundle 2 | Bundle 10 with submit-only trigger |
| Bundle 11 | Uses eligibility check instead of autofill, same triggers |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 10 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::