Bundle 4 — 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 4 extends Bundle 1 by adding a second trigger: not only does your system receive Credit Committee Report data when a questionnaire is first submitted, it also receives an updated data push whenever the questionnaire or the CCR report is subsequently modified. This ensures your core banking or CRM system stays in sync with YAPU throughout the credit lifecycle — not just at the point of initial submission.
Capabilities
- Receives CCR data on questionnaire submission (same as Bundle 1)
- Receives updated CCR data whenever the questionnaire or report is modified after submission
- Keeps the client system continuously synchronized with YAPU data
- No inbound data flow required — questionnaire fields are filled manually by the loan officer
How it works
Trigger 1 — Questionnaire Submit:
- A loan officer completes and submits a questionnaire in YAPU.
- YAPU sends Data Set A to the client system automatically.
Trigger 2 — Questionnaire or Report Update:
- A YAPU user opens an existing customer profile and modifies a questionnaire or CCR report.
- YAPU detects the update and sends Data Set A again to the client system with the latest values.
In both cases, the client system receives the same data set and is responsible for updating or reconciling the record in its own system.
Data exchange
| Direction | Data set | Content | Trigger |
|---|---|---|---|
| Outbound (YAPU → Client) | Data Set A | Configurable selection of questionnaire and Credit Committee Report fields | Submit |
| Outbound (YAPU → Client) | Data Set A | Same data set, refreshed with updated values | Questionnaire or report update |
:::info Data format All outbound data is delivered as JSON strings. The client system is responsible for parsing and updating its own records accordingly. :::
When to use Bundle 4
Bundle 4 is the right fit when:
- Your system needs to remain synchronized with YAPU beyond the initial submission (e.g., for ongoing portfolio management or reporting)
- Loan officers or supervisors frequently update questionnaire data or CCR reports after initial submission
- You do not need inbound autofill or eligibility checking
If you need to also autofill the questionnaire from your system's data, consider Bundle 5. If you need an eligibility gate, consider Bundle 6. If you additionally want a trigger on "Approval" status, consider Bundle 10.
Limitations
- Requires a YAPU questionnaire already configured for the integration
- Only a single questionnaire can be used per integration
- The update trigger fires on any modification to the questionnaire or report — your system should be prepared to handle repeated pushes for the same customer record
- Inbound data flow is not included in this bundle
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 1 | Bundle 4 with submit-only trigger |
| Bundle 5 | Bundle 4 + autofill from client system |
| Bundle 6 | Bundle 4 + eligibility check |
| Bundle 10 | Bundle 4 + eligibility check + approval trigger |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 4 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::