Bundle 2 — Receive ID, Autofill Questionnaire and Receive Credit Committee Report Data upon Questionnaire Submit
Trigger: Questionnaire submitted in YAPU
Business purpose
Bundle 2 builds on Bundle 1 by adding a two-way data flow at the start of the questionnaire. Rather than requiring loan officers to manually re-enter customer data that already exists in the client's system, YAPU retrieves it automatically. The officer simply enters the customer's ID number — YAPU checks your system, pulls the relevant data, and autofills the questionnaire. This saves time for both the loan officer and the end-customer, reduces errors, and ensures consistency between systems.
Capabilities
- Inbound autofill: YAPU sends the customer ID to your system and receives back customer data to pre-populate the questionnaire
- Eligibility bypass: If the customer ID is not found in your system, the questionnaire continues without autofill
- Outbound CCR data: On questionnaire submission, Credit Committee Report data is pushed back to your system
- End-to-end integration covering both directions of the data flow
How it works
- A loan officer opens a questionnaire in YAPU and answers the "ID number" question.
- YAPU sends Data Set A (the customer ID) to the client system.
- The client system checks whether the ID exists.
- If found: The client system returns Data Set B (customer profile data). YAPU autofills the questionnaire fields automatically.
- If not found: The questionnaire continues without autofill; the officer fills in all fields manually.
- The officer reviews, finalizes, and presses Submit.
- YAPU sends Data Set C (CCR output data) to the client system.
Data exchange
| Direction | Data set | Content |
|---|---|---|
| Outbound (YAPU → Client) | Data Set A | Customer identification number entered by the loan officer |
| Inbound (Client → YAPU) | Data Set B | Customer profile data from the client system, used to autofill the questionnaire — selection from a list provided by YAPU Solutions |
| Outbound (YAPU → Client) | Data Set C | Configurable selection of questionnaire and Credit Committee Report fields |
:::info Data format Inbound data (Data Set B) must conform to the YAPU-specific data format. Outbound data (Data Sets A and C) is delivered as JSON strings. The client system is responsible for transformation into its own format. :::
When to use Bundle 2
Bundle 2 is a good fit when:
- Your system already holds customer data that would otherwise need to be re-entered in YAPU
- You want to reduce loan officer effort and data entry errors
- Submit is the only event that should trigger the outbound data push
If you also want data sent on questionnaire or report updates, consider Bundle 5. If you also want a trigger on "Approval" status, consider Bundle 8.
Limitations
- Requires a YAPU questionnaire already configured for the integration
- Only a single questionnaire can be used per integration
- Inbound data must use the YAPU-specific format — client systems must transform their data accordingly
- The autofill only activates when the customer ID is found in the client system; unrecognized IDs proceed without autofill
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 1 | Bundle 2 without autofill |
| Bundle 3 | Uses ID lookup for eligibility check instead of autofill |
| Bundle 5 | Bundle 2 + additional trigger on update |
| Bundle 8 | Bundle 2 + additional trigger on "Approval" |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 2 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::