← Agent catalogue

AI Agent Profile · LendingIQ · Agent #80 · COA

Co-Applicant Onboarding Agent AI

Function: Joint Application ProcessorInvoked via: joint application received · guarantor addition · relationship mapping requestRuntime: AWS Bedrock · ap-south-1Model: Claude Sonnet 4Context window: 200K tokens

DivisionOnboarding

Resume

What this agent does

The Co-Applicant Onboarding Agent AI manages the parallel KYC collection, document verification, and relationship mapping process for joint loan applicants and guarantors — ensuring that the co-applicant's identity, address, and income documentation is collected to the same standard as the primary applicant's, that the relationship between borrower and co-applicant is documented for the credit file, and that any income claim discrepancies between the borrower and co-applicant are flagged before the application proceeds to credit assessment.

Primary functions

Co-Applicant KYC Collection

Per joint application · parallel with primary KYC

Invoked when: a joint application is received in the LOS with a co-applicant or guarantor named

  • Initiates the co-applicant KYC collection workflow in parallel with the primary applicant's KYC — sending the co-applicant an onboarding link that requests the same identity (Aadhaar, PAN), address (Aadhaar or utility bill), and income documentation (salary slips, ITR, or bank statement) that the primary applicant provides. Parallel processing is critical — sequential KYC (primary first, co-applicant second) adds 2–5 days to the application timeline for no credit risk benefit. The co-applicant receives their onboarding link within 2 hours of the joint application being received.
  • Validates each co-applicant document through the KYC Verification Agent AI — the same identity verification, face match, and liveness check process applied to primary applicants. Co-applicants who fail the KYC verification are flagged immediately with the specific failure reason; the application is placed on hold pending resolution of the co-applicant's KYC status. A co-applicant who cannot be KYC-verified cannot be included in the application under RBI KYC norms regardless of the primary applicant's verification status.
  • Pulls the co-applicant's bureau report in parallel with the primary applicant's bureau check — ensuring that the credit team receives both bureau reports simultaneously rather than sequentially. The co-applicant bureau report is passed to the Credit Decision Agent AI as part of the joint credit assessment; it is not used by this agent to make any credit judgment.
Output: Co-applicant KYC status — documents received, verified, and linked to the application. KYC failure flags with specific reason. Co-applicant bureau report pulled and passed to credit workflow. All co-applicant documents stored in the application file in the document management system.

Guarantor Verification

Per guarantor · on guarantor addition to application

Invoked when: a guarantor is added to a new or existing application

  • Collects guarantor identity, address, and financial documents through a guarantor-specific onboarding flow — structured to the RBI's guarantor KYC requirements, which differ from the primary applicant requirements in that the guarantor's income documentation establishes the capacity to service the loan in the event of borrower default, not the capacity to service it as a primary income earner. The guarantor's income documentation standard is therefore assessed against a different threshold than the primary applicant's.
  • Documents the guarantor's understanding of their obligation — the guarantor declaration that confirms the guarantor has understood the nature and extent of their liability before providing the guarantee. The guarantor declaration is a regulatory requirement under the Fair Practices Code; a guarantee provided without a documented declaration of understanding is invalid and creates both credit and regulatory risk.
  • Links the guarantor record to the application and to the primary borrower's profile — ensuring that if the borrower applies for a future product, the underwriter is aware that this borrower has an existing guarantor relationship and can assess its implications for the new application.
Output: Guarantor verification record — identity, address, and income documents collected and verified. Guarantor declaration signed and stored. Guarantor record linked to application and primary borrower profile. Guarantor bureau report passed to credit workflow.

Relationship Mapping & Income Discrepancy Detection

Per joint application · before credit assessment

Invoked when: co-applicant KYC is complete — relationship map is assembled and income claims are cross-checked before the application proceeds to credit assessment

  • Documents the relationship between the primary borrower and the co-applicant — spouse, parent, sibling, business partner, or other — and the basis on which the co-applicant's income is being included in the joint assessment. The relationship type affects the credit assessment: a spouse co-applicant's income is typically treated as a household income contribution; a business partner co-applicant's income requires additional documentation of the business relationship. The relationship type is documented in the application file and presented to the credit underwriter alongside the co-applicant's KYC.
  • Cross-references the co-applicant's stated income against their bureau data — checking whether the credit obligations reflected in the bureau report are consistent with the income level the co-applicant has declared. A co-applicant declaring a monthly income of ₹1.5 lakh but with existing EMI obligations totalling ₹80,000 per month has a net income for credit assessment purposes of ₹70,000, not ₹1.5 lakh. Income discrepancies above 30% between the stated income and the bureau-implied income capacity are flagged for the underwriter's review.
  • Checks for mismatched information between the primary borrower and co-applicant applications — address discrepancies that contradict the stated relationship (a spouse who claims to live at a different address), inconsistent income declarations (primary borrower and co-applicant who claim to be co-directors of the same company but declare different company revenues), or KYC document inconsistencies. Mismatches are flagged to the Fraud Detection Agent AI for assessment before the application proceeds.
Output: Relationship map — relationship type, basis of income inclusion, and documentation. Income discrepancy flags — co-applicant stated income vs bureau-implied income capacity where discrepancy exceeds 30%. Mismatch flags for Fraud Detection Agent AI review. Complete co-applicant and guarantor package passed to Credit Decision Agent AI for joint credit assessment.

Knowledge base

LOS — Primary Application Record

The primary application context — links co-applicant KYC to the correct application and provides the primary borrower's data for relationship mapping and income cross-referencing.

RBI KYC Norms — Co-Applicant and Guarantor Requirements

The regulatory KYC requirements specific to co-applicants and guarantors — including the guarantor declaration requirement and the documentation standards for different relationship types.

Fair Practices Code — Guarantor Obligations

The requirement that guarantors receive a clear explanation of their obligations before providing a guarantee — the basis for the guarantor declaration collection step.

Bureau Integration — Co-Applicant and Guarantor Reports

Co-applicant and guarantor credit bureau reports pulled in parallel with the primary applicant's bureau check.

Fraud Detection Agent AI — Cross-Application Signal Feed

Cross-application fraud signals — the same co-applicant appearing on multiple concurrent applications with different primary borrowers, or KYC documents used across multiple applications.

Pre-Training — Joint Application and Guarantor Knowledge

Joint loan application processing, guarantor KYC requirements, and relationship mapping methodology for Indian NBFC lending up to knowledge cutoff.

Hard guardrails

Will notMake any credit judgment on the co-applicant or guarantor. Credit assessment of the co-applicant's income contribution and the guarantor's capacity is performed by the Credit Decision Agent AI — this agent collects and validates the data, it does not assess creditworthiness.
Will notAccept a guarantor guarantee without a completed guarantor declaration. The declaration is a regulatory requirement; a guarantee without a declaration is invalid and cannot be relied upon in a credit assessment.
Will notProceed with a co-applicant whose KYC verification has failed without flagging the failure to the underwriter and placing the application on hold. An unverified co-applicant cannot be included in the application under RBI KYC norms.
Will notOverride the income discrepancy flag based on the primary applicant's request. Income discrepancy flags are for the underwriter's review; the agent does not have the authority or the information to determine whether a discrepancy has a legitimate explanation.

Known limitations

The relationship between the primary borrower and co-applicant is documented based on the declarations and documents provided — it is not independently verified. A co-applicant who falsely claims to be a spouse, parent, or business partner of the primary borrower creates a fraudulent application that this agent cannot detect from the documents alone.The Fraud Detection Agent AI's cross-application analysis is the primary check on relationship fraud — particularly co-applicants who appear on multiple applications with different primary borrowers, or who claim different relationships to different primary borrowers in concurrent applications. Ensure the Fraud Detection Agent AI has access to the full co-applicant and relationship mapping data from this agent.
The parallel KYC workflow assumes that the co-applicant is reachable and responsive on the contact details provided by the primary borrower. A co-applicant who is unreachable, unresponsive, or unwilling to complete the KYC process creates a bottleneck that delays the primary application regardless of the primary borrower's own KYC completion.Set a co-applicant KYC completion SLA — if the co-applicant has not completed their KYC within 5 business days of receiving the onboarding link, the application is flagged for underwriter review to determine whether to proceed without the co-applicant or to extend the co-applicant KYC window.
Agent Profile · Co-Applicant Onboarding Agent AI · LendingIQ · Agent #80Last updated April 2026 · For internal use

Important Reads

Learn more about how to deploy Co-Applicant Onboarding Agent AI to your lending workflow.