Finance legal-AI skills in General

31 legal AI skills for finance in General.

AI Disclosure Requirements Before Tribunals

MITGeneralFinance

Use when a lawyer or user indicates that AI-assisted work product (research, drafts, briefs, or submissions) will be filed with or presented to a court, tribunal, or regulatory body. Triggers the appropriate AI-disclosure reminder and citation-verification warning based on the forum's rules. Covers US courts (post-Mata v. Avianca standing orders), UK Bar Standards Board guidance, DIFC/ADGM courts, KSA/UAE onshore courts, French ordre des avocats, and EU AI Act implications. Hard-blocks any request to conceal AI use from a tribunal.

AML/KYC Policy

MITGeneralFinance

Use when drafting an AML/KYC policy for a fintech company or financial institution, covering customer identification, risk assessment, ongoing monitoring, suspicious activity reporting, record-keeping, and regulatory filing obligations. Applies to MENA jurisdictions (UAE, KSA, EG, DIFC, ADGM) and globally, with particular attention to FATF 40 Recommendations and jurisdiction-specific AML regimes.

Anti-Money Laundering Policy

MITGeneralFinance

Use when drafting a comprehensive AML/KYC policy for a financial institution (bank, finance company, insurance firm) covering customer due diligence, enhanced due diligence, suspicious activity reporting, record-keeping, and staff training. Closely related to the fintech-focused AML/KYC policy skill; this skill addresses the broader financial institution context with additional emphasis on correspondent banking, trade finance, and institutional EDD.

Bar Rule 1.1 — Competence and AI Use

MITGeneralFinance

Use when a lawyer user needs guidance on the professional-responsibility duty of competence as it applies to AI tool use in legal practice. Covers ABA Model Rule 1.1 and its analogs in MENA bars (Lebanese Bar, Saudi Bar, UAE Bar, DIFC/ADGM Rules of Professional Conduct) and European bar codes (UK SRA, French CNB/RIN). Specifically addresses what "understanding the technology" means in practice, verification obligations, hallucination risk, and how to document AI use in matter files to satisfy competence duties.

BNPL Platform Agreement

MITGeneralFinance

Use when drafting a buy-now-pay-later (BNPL) platform agreement between a BNPL provider and a merchant, covering integration requirements, payment terms, merchant fees, customer credit assessment, default handling, returns and refunds, and consumer credit regulation compliance. FinTech/payments practice area with MENA-specific attention to consumer credit licensing (UAE, KSA, EG) and Sharia-compliant BNPL structures.

Cryptocurrency Exchange Terms

MITGeneralFinance

Use when a crypto exchange or virtual asset service provider (VASP) needs to draft Terms of Service covering account registration, KYC/AML requirements, trading rules, asset custody, security measures, withdrawal limits, fee structure, risk disclosures, and regulatory compliance. MENA-aware: covers UAE (VARA, DIFC, ADGM), KSA (SAMA sandbox), Bahrain (CBB), Qatar (QFC), and also EU (MiCA), UK (FCA), and global FATF VASP framework.

Debt Restructuring Agreement

MITGeneralFinance

Use when drafting a debt restructuring agreement between a distressed borrower and one or more creditors — covering extension of maturities, interest-rate renegotiation, debt-to-equity conversion, haircuts, standstill provisions, and inter-creditor arrangements. Relevant pre-insolvency, during distressed M&A, or in workout contexts across MENA (UAE, KSA, LB), DIFC, ADGM, UK, and EU. Should be paired with insolvency-law review and financial modeling of recovery scenarios.

Digital Wallet Terms

MITGeneralFinance

Use when a FinTech or payments company needs to draft Terms of Service for a digital wallet application — covering account setup, funding methods, transaction limits, security features, unauthorized transaction liability, data privacy, and dispute resolution. MENA-aware: UAE (CBUAE Stored Value Facility licensing, DFSA/ADGM), KSA (SAMA), and addresses consumer protection requirements that apply to e-money and digital wallet products across MENA, EU (PSD2), and UK.

Draft — AML / KYC Policy

MITGeneralFinance

Use when asked to draft an Anti-Money Laundering (AML) and Know-Your-Customer (KYC) policy for a financial services or fintech business. Covers the mandatory components under FATF Recommendations and jurisdiction-specific frameworks (SAMA/KSA, UAE Federal, DFSA, ADGM/FSRA, DIFC, Lebanon BDL/SIC, EU 6AMLD, US BSA/FinCEN). P0 priority for regulated entities — incomplete AML policies are a regulatory enforcement trigger.

Draft — Convertible Note

MITGeneralFinance

Use when asked to draft a convertible promissory note — a debt instrument that converts into equity on a qualified financing event. Covers required inputs (principal, interest, maturity, valuation cap, discount), the conversion mechanics, change-of-control treatment, events of default, the note-vs-SAFE structural choice, and MENA-specific considerations including interest structuring under Sharia-compliant frameworks and jurisdiction availability of SAFEs.

Embedded Finance Partnership Agreement

MITGeneralFinance

Use when drafting an embedded finance partnership agreement between a regulated financial institution (FinTech or bank) and a non-financial platform that will offer financial services through its application. Covers API integration, revenue sharing, regulatory responsibilities, customer ownership, data sharing, and liability allocation. Relevant for fintech deals in UAE (CBUAE, DIFC, ADGM), KSA (SAMA), LB, EG, UK (FCA), and EU. Trigger when a platform and a licensed financial partner need to structure their embedded banking, lending, or payments arrangement.

E-Money License Application Memo

MITGeneralFinance

Use when preparing a compliance memo outlining the regulatory requirements for obtaining an electronic money institution (EMI) or e-money license in a target jurisdiction. Covers capital requirements, governance, AML/KYC obligations, safeguarding requirements, and application process timeline. Relevant for fintech companies seeking to operate in UAE (CBUAE), DIFC (DFSA), ADGM (FSRA), KSA (SAMA), LB (BdL), EG (CBE), UK (FCA), EU (national NCAs under EMD2), and other jurisdictions. Trigger when a payments or e-money startup needs to understand the licensing pathway.

Forensic Deposit Tracking

Apache-2.0GeneralFinance

Traces deposits from receipt through disbursement across bank statements and financial records, producing transaction matrices, fund-flow timelines, and evidentiary chains of custody. Flags structuring, commingling, trust account violations, and unexplained gaps. Use when tracking deposits, tracing funds, auditing trust accounts, or analyzing bank statements during discovery.

Guarantee Analyst

MITGeneralFinance

Analyses guarantee and indemnity scope, liability triggers, defences, release risks and enforcement. Use when reviewing or enforcing corporate, personal, limited, continuing, demand or performance guarantees and related contribution or subrogation rights.

Guarantee (Surety / Personal)

MITGeneralFinance

Use when drafting a guarantee (surety or personal) whereby a guarantor undertakes to satisfy the obligations of a principal debtor to a beneficiary. Covers the two main structures (demand guarantee vs. conditional surety), mandatory clauses, MENA-specific nuances (KSA Sharia kafala vs. commercial guarantee, UAE Commercial Code Federal Law 18/1993, DIFC/ADGM common-law demand guarantees, LB civil-law aval), independence from the underlying transaction, and the distinction between a guarantee and a standby letter of credit.

Intake — Loan Agreement

MITGeneralFinance

Use when a user wants to draft a loan agreement, facility agreement, or credit agreement and Claude must gather the financing, security, and structural inputs before generating the document. Triggers on requests to prepare a lending arrangement between any combination of individuals and corporate entities. Covers multi-jurisdictional MENA (UAE, KSA, LB, EG, DIFC) with Islamic finance carve-out for Sharia-compliant structures, and secondary coverage of UK, EU, and US.

Investment Agreement (Venture Capital)

MITGeneralFinance

Use when drafting a venture capital investment agreement for a Series A, B, or C round — covering investment terms, preferred share rights, anti-dilution protection, liquidation preference, board composition, investor veto rights, and protective provisions. Applicable for startups raising capital across MENA (UAE, DIFC, ADGM, KSA, LB, EG), UK, EU, and US. Trigger when a startup and its investors need to document a priced equity round and the full suite of investor protections.

Knowledge Pack — Shariah Finance and AAOIFI Standards

MITGeneralFinance

Use when a matter involves Sharia-compliant financial products, Islamic banking structures, sukuk issuance, takaful, or the use of AAOIFI standards. Covers the major Islamic finance structures (murabaha, ijara, mudaraba, musharaka, sukuk, tawarruq, wakala, salam, istisna), compliance markers for drafting, AAOIFI and IFSB standard-setting roles, Sharia Supervisory Board requirements, and the DIFC/ADGM Islamic finance overlay. Relevant for any transaction involving KSA or UAE onshore parties, Islamic banks, halal investment funds, or Sharia certification. Triggers on Islamic finance, sukuk, murabaha, AAOIFI, Sharia-compliant, takaful, halal investment, or Islamic banking questions.

KYC / Customer Due Diligence Procedure

MITGeneralFinance

Use when drafting or reviewing a Know Your Customer (KYC) procedure for a financial institution, fintech, law firm, or regulated business operating under AML/CFT obligations. Covers the full customer due diligence lifecycle — identification, verification, beneficial ownership, risk classification, sanctions screening, PEP checks, and periodic refresh — with specific attention to MENA regulatory frameworks (UAE CBUAE, KSA SAMA, Lebanon SIC, DIFC/ADGM, FATF). Triggers on "kyc", "customer due diligence", "cdd", "aml procedure", or "onboarding compliance" requests.

Lending Platform Terms

MITGeneralFinance

Use when drafting terms of service for a digital lending platform offering consumer or SME loans. Covers loan application process, credit assessment disclosure, interest rate transparency, repayment terms, default consequences, collection practices, and consumer protection compliance. MENA-first: addresses UAE Central Bank, SAMA (KSA), and Banque du Liban requirements, interest/Sharia compliance considerations, and DIFC/ADGM regulated lending frameworks.

Loan Agreement / Facility Agreement

MITGeneralFinance

Use when drafting a loan agreement or facility agreement between a lender and borrower for a commercial or corporate financing. Covers facility type, interest mechanics (including Sharia-compliant structures for KSA), covenants, events of default, security cross-references, and key lender/borrower negotiation points. Handles LMA-style common-law agreements (DIFC/ADGM) and civil-law structures (LB, UAE onshore). Triggers on "loan agreement", "facility agreement", "credit agreement", "term loan", "revolving credit", or Islamic finance equivalents (murabaha, ijara, tawarruq).

Open Banking API Terms

MITGeneralFinance

Use when drafting API terms of service for a bank or fintech offering open banking APIs to third-party providers (TPPs), developers, or payment initiation services. Covers access credentials, rate limits, data usage restrictions, security requirements, liability, SLA commitments, and compliance with applicable open banking regulations. MENA-focused: UAE Central Bank open finance framework, SAMA open banking framework (KSA), and EU PSD2 as a reference standard.

Payment Facilitator Agreement

MITGeneralFinance

Use when drafting an agreement between a payment facilitator (PayFac) and an acquiring bank (or sponsor bank) governing the PayFac's authority to onboard and manage sub-merchants, process card transactions, and bear acquiring liability. Covers sub-merchant underwriting standards, transaction monitoring, chargeback management, reserve requirements, PCI-DSS compliance, and liability allocation. MENA-relevant: UAE and KSA payment regulation context included.

Payment Services Agreement

MITGeneralFinance

Use when drafting an agreement between a payment service provider (PSP) and a merchant for processing card and digital payments. Covers transaction fees, settlement terms, chargebacks, rolling reserves, PCI-DSS compliance, data security, regulatory compliance, and liability allocation. MENA-focused: UAE CBUAE and KSA SAMA licensing requirements, local payment network rules (Mada, UAE NAPS), and regional AML obligations addressed.