Bundle 6 — Receive ID, Check Client Eligibility 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 6 combines the eligibility gate of Bundle 3 with the extended trigger set of Bundle 4. Your system is consulted at the start of every questionnaire to confirm whether the customer is eligible to proceed. If not, the questionnaire is terminated immediately. For eligible customers, CCR data is delivered both at submission and on any subsequent update — ensuring your system stays synchronized across the full credit cycle.
Capabilities
- Eligibility gate: YAPU checks your system before the questionnaire proceeds; ineligible customers are stopped early
- Outbound on submit: CCR data is pushed to your system when the questionnaire is submitted
- Outbound on update: CCR data is re-sent whenever the questionnaire or CCR report is modified
- Combines compliance enforcement with ongoing data synchronization
How it works
Questionnaire start — Eligibility check:
- 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 an eligibility signal:
- Not eligible (B.1): YAPU notifies the officer — questionnaire ends immediately, no data saved.
- Eligible (B.2): Questionnaire proceeds.
Trigger 1 — Submit:
- The officer completes, finalizes, and submits. YAPU sends Data Set C to your system.
Trigger 2 — Update:
- If the questionnaire or CCR report is later modified, 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.1 | Eligibility signal: not eligible — questionnaire terminated | Response to ID lookup |
| Inbound (Client → YAPU) | Data Set B.2 | Eligibility signal: eligible — questionnaire continues | 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 eligibility signals (B.1 and B.2) must use the YAPU pre-defined format. All outbound data is delivered as JSON strings. :::
When to use Bundle 6
Bundle 6 is the right fit when:
- Your institution enforces eligibility rules (exclusion lists, blacklists, risk filters) that must be respected before any credit assessment
- You also need your system to stay in sync with YAPU after any post-submission changes
- You do not need questionnaire autofill
Consider Bundle 3 if the submit-only trigger is sufficient. Consider Bundle 10 if you also need the "Approval" status trigger.
Limitations
- Requires a YAPU questionnaire already configured for the integration
- Only a single questionnaire can be used per integration
- Eligibility signals must conform to the YAPU pre-defined format
- When a customer fails the eligibility check, no questionnaire data is recorded — this is intentional
- The update trigger fires on any modification; your system should be prepared to handle multiple data pushes per record
- API connectivity must be available when the ID is entered for the eligibility check to function
Related bundles
| Bundle | Relationship |
|---|---|
| Bundle 3 | Bundle 6 with submit-only trigger |
| Bundle 4 | Bundle 6 without the eligibility check |
| Bundle 5 | Uses autofill instead of eligibility check, same triggers |
| Bundle 10 | Bundle 6 + approval trigger |
:::tip Ready to integrate? Contact your YAPU representative to confirm whether Bundle 6 matches your use case and to begin the specification process. See Integration Process for timelines and next steps. :::