submit-credit-application

Submit Credit Application

When the user requests to submit a credit application, execute according to the following process.

Target Role

Role: Corporate Relationship Manager, Credit Approval Officer
Use Cases: First loan application for new customers, loan renewal for existing customers, additional credit applications
Output Purpose: Evaluate material completeness, guide the relationship manager to confirm submission, initiate the credit approval process
Decision Level: Pre-approval step for credit approval, directly affecting whether the case enters the approval process
Execution Frequency: Executed once before each credit application

Data Sources

Required Data

Data Item	Source	Acquisition Method	Sensitivity Level
Customer Notes	Credit System Imaging Archive	API: /api/notes/list	Internal
Customer Materials	Imaging Archive System	API: /api/documents/list	Internal
Case Status	Credit System Case Management	API: /api/cases/status	Confidential
Credit Ledger	Core System Credit Module	API: /api/credit/ledger	Confidential

Data Masking Rules

Customer ID Number: Show first 3 and last 4 digits, replace the middle with *
Bank Account Number: Show only the last 4 digits
Case Number: Display in full (required for internal circulation)
Credit Amount: Display in full (required for approval decisions)
Customer trade secret information (such as key customer lists): Use "a certain customer" instead in the assessment report

Degradation Strategy

If the credit system imaging archive is unavailable: mark "customer notes and materials not verified" and continue the assessment based on the information provided by the user
If the case status query times out: mark "case conflict not checked" and prompt the user to manually confirm that there are no active cases
If the credit ledger is unavailable: mark "credit expiration status unknown" and have the user confirm the case type (renewal/new/additional)
If the historical due diligence report is unavailable: mark "due diligence report missing" and prompt the user to upload or supplement it

Constraints

Regulatory Basis: Guidelines for Due Diligence in Commercial Bank Credit Work, Guidelines for Loan Risk Classification, Article 35 of the Commercial Bank Law on loan review requirements, CBRC Interim Measures for the Administration of Working Capital Loans

Strict Confirmation Prerequisite: Without explicit user confirmation, initiating case creation is prohibited, regardless of whether the materials are sufficient
Independent Judgment in Material Assessment: Completeness assessment is based on the substantive content of the materials; "sufficient quantity of materials" must not be used in place of "content quality meets standards"
Case Conflicts Not Overridden: When the same customer has an active approval case, duplicate submission is prohibited, and the conflict must be prompted to the user
Explicit disclosure of uncertainty: When materials are questionable or missing, the user must be clearly informed; do not subjectively judge that they "may not be important" and skip them
No guessing of case type: The types of renewal loan and new credit granting must be confirmed by the user, and must not be automatically inferred based on the customer's historical records
Refusal of ultra vires judgment: Do not predict approval results (such as "this should be approved"), and focus on material completeness
Data traceability: Material evaluation must indicate the source, upload date, and validity status of each material
Prohibition of skipping steps: Step 0 (data validation) and Step 1 (case conflict check) must not be skipped; continue only after confirming that there is no active case
Mandatory enforcement of red lines: If any red line (R1-R3) is triggered, generation must stop immediately and the user must be prompted

Financial compliance red lines (one-vote veto)

In the following situations, submission must stop immediately and the user must be prompted:

R1: Missing required materials (due diligence report, visit records, financial materials, business license)
R2: There is an active approval case (to prevent duplicate submission)
R3: The user has not explicitly confirmed submission (silent submission is prohibited; ambiguous expressions such as "OK" must not be judged as confirmation)

Credit application material checklist (evaluation baseline)

The following is the standard material system for bank pre-loan due diligence and the basis for completeness evaluation. Materials are divided into three levels:Required(if missing, it is recommended to suspend),Recommended(if missing, the user must be prompted),Supplementary(better if available).

Material type	Level	Evaluation points
Due diligence report / credit investigation report	Required	Must include the enterprise's basic information, business analysis, financial analysis, and repayment source analysis
Visit records (last 6 months)	Required	Must contain substantive business information; purely greeting-type records are not counted
Financial materials (last 2-3 years)	Required	Must at least include operating revenue, net profit, and assets and liabilities
Business license and qualification certificates	Required	Must be within the validity period, and the business scope must match the application purpose
Guarantee/collateral evaluation materials	Recommended	Must be provided when there is a guarantee arrangement; may be exempted for pure credit loans
Bank statements (last 6-12 months)	Recommended	Supports verification of the authenticity of repayment sources
Shareholder/actual controller information	Recommended	Includes identity proof and personal credit authorization
Industry-specific qualifications	Supplementary	For franchised industries (food/pharmaceutical/construction, etc.), industry licenses must be verified

Integration note: The material inventory capability is mapped to your bank's customer file query interface, and the returned fields must include: material type, file name, upload date, status (valid/expired/pending review)

Execution workflow (Workflow)

Interaction mode: Mode B - Step-Gated

When the user requests to submit a credit application, execute the following process:

Step 0: Data Confirmation and Verification (Read Before Write)

List all input data sources: customer notes list, customer materials list, case status, credit ledger
Confirm data time ranges: due diligence report date, financial statement period, visit record time span
Confirm case type intent: renewal/additional/new
Run verification script: python scripts/validate_application.py --check-materials --check-conflicts
After verification passes, proceed to Step 1; if verification fails, output the missing items list and ask the user to supplement

📋 Data source:system_api(credit system image archive, case management, credit ledger) 📋 Executing entity:ai 📋 Confirmation mechanism:none ⚠️ Mandatory instruction: Do not skip the data verification step; the validity of all input data must be confirmed

Step 1: Pre-condition Status Check

Gating step: If this step does not pass, subsequent processes must not be entered

Case Conflict Check

Check whether the customer has any active cases in the "under review/pending supplementary documents/pending signing" status
Gating branches:
- ✅ No active cases → proceed to credit expiration check
- ❌ Active cases exist → Stop immediately, inform the user of the conflict, indicate the existing case number and current status, ask whether to cancel or continue waiting, and do not enter subsequent processes
- ⚠️ Query timeout → mark as "case conflict not verified", prompt the user to manually confirm that there are no active cases, and continue only after the user confirms

📋 Data source:system_api(credit system case management module) 📋 Executing entity:ai 📋 Confirmation mechanism:approve(when a conflict exists, an explicit user decision is required)

Credit Expiration Check

Check the expiration date of the customer's existing credit limit, and determine whether this application is a renewal (within 90 days before expiration) or new credit
Automatically mark the suggested case type, and display it to the user at submission confirmation

📋 Data source:system_api(core system credit module) 📋 Executing entity:ai 📋 Confirmation mechanism:none

Step 2: Materials Inventory

Enumerate customer notes: list all existing notes for the customer (due diligence reports, visit records, visit briefs, etc.) and summaries
Enumerate customer materials: list the customer's uploaded files and published materials list
Key notes or material contents must be read, to understand the substantive content of the materials (rather than merely confirming that the files exist)
Compare againstreferences/material-checklist.mdand check item by item against the materials list in it

📋 Data source:system_api(credit system image archive) 📋 Executing entity:ai 📋 Confirmation mechanism:none ⚠️ Mandatory instruction: Do not merely count the number of files; the substantive content must be checked (for example, a due diligence report must include business analysis and financial analysis)

Step 3: Completeness Assessment

Based on the inventory results, compare against thecredit application materials checklist(seereferences/material-checklist.md) and judge item by item:

Assessment Display Format

材料完备性评估结果:

✅ 已具备(必备)
  - 尽调报告(2024-01-15,含经营分析和财务分析)
  - 拜访记录(近3个月共2次,有实质经营信息)
  - 财务资料(2021-2023年三年数据)

⚠️ 建议补充
  - 银行流水(仅有3个月,建议补充至6个月)

❌ 缺失(必备材料)
  - 营业执照(档案中未见,请上传)

综合评估:[可以提交 / 建议补充后提交 / 暂缓提交]
原因说明:[1-2句话说明评估依据]

Assessment Judgment Criteria

Can be submitted: all required materials are complete and content quality meets standards
Recommend supplementing before submission: required materials are complete but "recommended" materials are missing; after informing the user of the risk, the user decides
Postpone submission: Required materials are missing; clearly recommend that the user supplement them first.
Gating branch:
- ✅ Assessed as "can submit" or "recommend supplementing then submit" → proceed to step 4
- ❌ Assessed as "suspend submission" → trigger red line R1, stop immediately, show the user the missing items, and recommend supplementing the materials first
- ⚠️ Materials in doubt → mark the doubtful items, explain the specific situation to the user, and let the user decide whether to continue

📋 Data source:context(step 2 inventory results) 📋 Executing entity:ai 📋 Confirmation mechanism:inform(assessment results must be shown to the user)

Step 4: Case Type Confirmation

Case type	Applicable scenario	Recognition signal
Renewal	Renew before the existing credit expires, with the amount and conditions basically unchanged	The user says "renewal", "it's due", "renew it"
First credit	This customer establishes a credit relationship for the first time	The user says "new customer", "first time", "no credit limit"
Additional credit	The existing credit is insufficient; apply to increase the limit	The user says "the limit is not enough", "add more", "increase some"

Prioritize automatic determination based on the conclusion of the credit expiration check in step 1
When there is ambiguity, ask the user to confirm;do not make assumptions
Gating branch:
- ✅ Case type is clear → proceed to step 5
- ⚠️ There is ambiguity → ask the user to confirm, and only continue after the user confirms

📋 Data source:context(step 1 check results + user input) 📋 Executing entity:ai 📋 Confirmation mechanism:inform(show to the user and confirm)

Step 5: Confirm Submission

Gating step: if this step is not passed, case creation must not be initiated

Show the user the assessment results and the recommended case type
If the materials are sufficient: recommend submission and ask the user to confirm ("Do you confirm submission?")
If anything is missing: inform the user of the missing items and their impact, and let the user decide whether to continue submitting or supplement the materials first
User confirmation gate:
- ✅ The user explicitly says "submit" or "confirm" → initiate case creation
- ❌ The user says "do not submit yet" or "wait a moment" → terminate the process, and do not create a case
- ⚠️ The user says something vague such as "okay" → must not be judged as confirmation, and the question "Do you confirm submission?" must be asked again explicitly

📋 Data source:context(step 3 assessment results) 📋 Executing entity:ai 📋 Confirmation mechanism:explicit(the user must explicitly confirm) ⚠️ Red line R3: without the user's explicit confirmation, initiating case creation is prohibited, regardless of whether the materials are sufficient

Output Format

This output can be parsed and used by the credit-approval-decision Skill

Use the assets/credit-application-template.md template. The assessment report must contain the following 6 sections:

Section	Content	Downstream parseable field
1. Pre-check of status	Case conflict check results, credit expiry check	`conflict_detected`(bool)、`existing_credit_expiry`(date)
2. Material inventory checklist	Customer notes checklist, customer materials checklist	`materials_found`(array)、`notes_count`(int)
3. Completeness assessment	✅Already available, ⚠️Suggested to supplement, ❌Missing	`assessment_result`(enum)、`missing_essentials`(array)
4. Comprehensive assessment conclusion	Can submit / Suggest submit after supplement / Temporarily suspend submission	`recommendation`(enum)、`reason`(string)
5. Case type confirmation	Loan renewal / New credit / Additional credit	`application_type`(enum)
6. User confirmation record	Confirmation time, confirmation method, case number	`confirmed`(bool)、`case_id`(string)

Data annotation requirements: All data annotations: Data source + data date + whether it is the latest data.

Disclaimer: A disclaimer must be appended at the end of the output, citing shared/disclaimer-template.md template, ensuring it includes necessary statements such as "This assessment is only a completeness check based on the provided materials and does not constitute a credit approval recommendation".

Audit Trail

After each credit application submission is completed, generate an audit log audit/{客户简称}_{日期}_audit.json：

{
  "skill_name": "submit-credit-application",
  "skill_version": "1.0.0",
  "execution_time": "2026-05-05T10:30:00+08:00",
  "input_params": {
    "customer_name": "XX企业",
    "application_type": "renewal/first_credit/additional",
    "application_amount": 50000000
  },
  "operator": "客户经理姓名（工号：XXX）",
  "steps": [
    {
      "step": "前置状态核查",
      "executor": "ai",
      "data_source": {"type": "system_api", "system": "信贷系统案件管理模块"},
      "result": "pass",
      "conflict_detected": false
    },
    {
      "step": "材料盘点",
      "executor": "ai",
      "data_source": {"type": "system_api", "system": "信贷系统影像档案"},
      "result": "pass",
      "materials_found": 8,
      "materials_missing": 1
    },
    {
      "step": "完备性评估",
      "executor": "ai",
      "data_source": {"type": "context"},
      "result": "pass",
      "assessment": "建议补充后提交"
    },
    {
      "step": "确认提交",
      "executor": "ai",
      "data_source": {"type": "context"},
      "confirmation": {"type": "explicit", "confirmed_by": "客户经理姓名（工号：XXX）", "confirmed_at": "2026-05-05T10:35:00+08:00"},
      "result": "pass",
      "case_id": "CASE-2026-001234"
    }
  ],
  "red_line_triggered": [],
  "warnings": ["银行流水仅有3个月，建议补充至6个月"],
  "references_used": ["references/material-checklist.md"]
}

Gotchas

#1: Sufficient quantity of materials but quality does not meet standards

Symptom: The due diligence report is only 1 page and lacks business analysis and financial analysis, but the system determines it is "already available"
Cause: Only counts the number of files, without checking substantive content
Solution: Must read the content of key materials and verify whether they include the necessary analysis dimensions (basic enterprise information, business analysis, financial analysis, repayment source)

#2: Case conflict not detected

Symptom: The same customer has two active approval cases, causing confusion in the approval process
Cause: The case status query interface timed out, and no degradation strategy was triggered
Solution: A query timeout must be marked as "case conflict not checked" and prompt the user to confirm manually

#3: User submits without explicit confirmation

Symptom: The user says "OK", and the system determines it as confirmation to submit
Cause: The confirmation mechanism is not strict; "OK" may be acknowledgment of the assessment result rather than a submission instruction
Solution: Case creation can only be initiated after the user explicitly says "submit" or "confirm"

#4: Incorrect case type inference

Symptom: The user says "renew it", and the system determines it as loan renewal, but it is actually additional credit
Cause: Did not combine the credit expiry check conclusion, and judged only based on the user's colloquial expression
Solution: Give priority to automatic judgment based on the credit expiry check conclusion; when there is ambiguity, ask the user for confirmation

#5: Still recommend submission when required materials are missing

Symptom: The business license is missing, but the assessment conclusion is "can submit"
Cause: Did not strictly enforce red line R1 (missing required materials)
Solution: Missing required materials (due diligence report, visit records, financial materials, business license) must trigger the red line, and "temporarily suspend submission" is recommended

Examples

Example 1: Standard loan renewal submission

User input：

请为XX制造企业的续贷申请提交授信申请。客户授信5000万将于2026-06-15到期，需要续贷。

Skill Execution Flow：

Precondition check → No active case, 41 days before credit expiration, determined as renewal
Material inventory → Due diligence report, visit records, and financial materials are complete; bank statements cover only 3 months
Completeness assessment → Required materials are complete, recommended materials are missing; assessed as "recommend supplementing before submission"
User confirmation → User explicitly said "submit", initiating case creation
Submission successful → Case number CASE-2026-001234 returned

Output Highlights：

Overall assessment: Recommend supplementing before submission
Missing items: Bank statements (only 3 months available; recommend supplementing to 6 months)
Case type: Renewal (renewal)

Example 2: First-time credit submission (red line triggered)

User Input：

为新客户YY贸易公司提交首次授信申请。