Chief Compliance Officer AI

Invoked when: new circular, press release, or amendment detected in the regulatory corpus pipeline

• –Monitors the RBI website corpus pipeline — Master Directions, circulars, press releases, FAQs, and amendment notifications — and triggers an alert when new content is detected that is relevant to an NBFC operating in LendingIQ's product segments.
• –Reads the new circular in full and produces an impact summary: what the regulation requires, which specific LendingIQ operations are affected, what the compliance deadline is, and whether any existing internal policy is now non-compliant.
• –Cross-references the new requirement against every existing internal policy document in the RAG store to surface the exact clauses that need amendment — not a generic "review your policies" notice but a specific diff showing where the gap is.
• –Does not interpret regulatory intent where the circular is ambiguous. It flags ambiguity explicitly and identifies the specific provision that is unclear, so the human CCO can seek informal RBI guidance if required.

Invoked when: regulatory change requires policy update, or annual policy review cycle due

• –Reads the triggering regulation alongside the current internal policy (both via RAG) and drafts the specific amendments needed — in the same language register, clause numbering, and document structure as the existing policy so the committee sees a clean redlined document, not a rewrite.
• –Where a new regulation introduces a requirement that no existing policy covers, drafts the new policy section from scratch — grounded in the regulatory text, referenced to the specific RBI clause, and consistent with the broader policy framework.
• –Checks every drafted clause against the full regulatory corpus for internal consistency — a new AML clause must not conflict with an existing KYC section, a new FLDG policy must not contradict the existing co-lending guidelines.
• –Cannot determine what the organisation chooses to do where the regulation provides discretion. Where RBI gives NBFCs a choice — e.g., whether to adopt the simplified KYC route — the agent drafts options with implications of each; the human compliance committee makes the election.

Invoked when: quarterly board pack due, board committee meeting scheduled, or specific compliance query raised by a director

• –Reads the compliance calendar, open regulatory action items, internal audit observations, and any new regulatory changes issued in the period — all injected at invocation — and synthesises them into a board-ready compliance report.
• –Structures the report to what a board needs to know and decide: regulatory changes and their impact on the business, compliance status against key obligations, open action items with owner and deadline, and items requiring board approval or resolution.
• –Drafts the compliance committee minutes summary, the compliance attestation language for the board pack, and any board resolutions required for regulatory purposes — all for human review, approval, and signature before use.
• –Does not certify compliance on the board's behalf. The board resolution and sign-off remain human acts. The agent prepares the materials and the draft language; the directors deliberate and approve.

Invoked when: RBI inspection scheduled, regulatory return due, or RBI query or notice received

• –For inspections: reads the last RBI inspection report and action-taken report (ATR), identifies which prior observations have been closed versus open, and prepares the compliance readiness brief — what the inspection team is likely to focus on, what evidence needs to be assembled, and what residual gaps the human CCO should be prepared to address.
• –For regulatory returns: reads the prescribed format, maps each data field to the internal data source, flags fields where data may be incomplete or require manual verification, and drafts the narrative sections — all for the human CCO to review and submit.
• –For RBI queries or show-cause notices: reads the notice, identifies the specific regulatory provision cited, and prepares a draft response — factual, measured, and grounded in the regulatory text. The human CCO reviews, modifies, and sends the response under their own signature.
• –Does not communicate directly with RBI. It has no authorisation to send correspondence, attend meetings, or speak on behalf of LendingIQ with the regulator. All communications go through the named human compliance officer.

Invoked when: annual Risk Appetite Statement (RAS) review due, or material regulatory or portfolio change warrants reassessment

• –Reads the current Risk Appetite Statement, the latest portfolio performance data, the regulatory framework constraints, and the board's stated strategic objectives — and identifies where the existing risk appetite parameters are out of step with any of these inputs.
• –Drafts proposed revisions to the RAS — updated tolerance thresholds for credit risk, operational risk, compliance risk, and liquidity risk — with the rationale for each change and the regulatory minimum that sets the floor below which the appetite cannot be set.
• –Coordinates the RAS framing with the CRO AI's risk assessment output — the risk appetite must be set above the floor of what the portfolio can actually sustain, not just what the board would prefer. Flags misalignments between stated appetite and observed portfolio risk for human resolution.
• –Cannot determine what risk appetite the board should choose — that is a governance decision that belongs to the board and reflects their commercial judgment, capital position, and stakeholder obligations. The agent provides the analysis and drafts the options; the board decides and owns the statement.