# Financial Audit Prover MCP for AI Agents AI Agent Connect

> Financial Audit Prover forces your AI client to ground every financial conclusion in actual US GAAP codification. It stops the AI from guessing numbers and forces it to trace every figure back to source documents like GL entries or invoices. It checks for statement reconciliation, materiality per SAB 99, and required SEC disclosures so your reports actually hold up under scrutiny.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_rpgCkQZYWEOQiO44h4nyvmCrKgcX1zKKq7sgLYCz/ai-agent-connect
- **Tags:** financial-audit, us-gaap, accounting, sec-compliance, structured-reasoning, decision-pivots, audit, sox

## Description

Financial Audit Prover fixes the problem of AI agents generating financial analysis that looks correct but fails professional scrutiny. AI often applies the wrong accounting standards, mixes up IFRS and US GAAP, or produces figures without a clear audit trail. It might skip materiality assessments entirely or reference "required disclosures" without naming a single ASC topic. This Connector acts as a hard gate for financial reasoning by forcing your AI client to follow five specific decision pivots. It verifies that the correct ASC topic is applied, ensures every number traces to source documents like bank statements or contracts, and confirms that the balance sheet equation actually balances. It also demands both the quantitative 5% pre-tax threshold and the qualitative factors required by SAB 99 for materiality. Connecting this via the Vinkius catalog means you can use this audit-grade tool alongside thousands of other Connectors from a single connection to your AI client. You get a defensible, audit-ready memo instead of a generic summary that ignores the FASB codification or PCAOB standards.

## Tools

### validate_financial_audit
Force your AI to cite specific ASC topics and provide a full audit trail for every material number. It checks for internal reconciliation and mandatory SEC disclosures.

## Prompt Examples

**Prompt:** 
```
The company recognized $5M in revenue from a multi-year software licensing deal. Is this correct under GAAP?
```

**Response:** 
```
Verdict: GAAP_VIOLATED. 'Under GAAP' is not a citation. Revenue recognition for software requires ASC 606 five-step analysis:

*   **Identify the contract** (ASC 606-10-25-1)
*   **Identify performance obligations** (distinct software license vs. ongoing services? — ASC 606-10-25-19)
*   **Determine transaction price** ($5M — is there variable consideration?)
*   **Allocate to performance obligations** (standalone selling prices)
*   **Recognize when satisfied** (point-in-time for license under ASC 606-10-25-27, or over-time for SaaS under ASC 606-10-25-31?)

Which step supports full upfront recognition?
```

**Prompt:** 
```
Issue: Whether $2.8M goodwill impairment is required. GAAP: ASC 350-20-35-1, qualitative election per 35-3A. Five factors assessed — stable industry, no customer loss, share price above book, no regulatory changes, CFO replaced in 60 days. Conclusion: fair value exceeds carrying. Audit: GL 1800, $2.8M from 2022 DataVault acquisition (WP-805-22). Cross-check: rollforward reconciles. Materiality: 7.2% of $38.9M pre-tax. Disclosures: ASC 350-20-50-1/50-2, Reg S-K Item 303.
```

**Response:** 
```
Verdict: AUDIT_PROVEN. 

*   **GAAP compliant** — ASC 350-20-35-1 through 35-19 correctly cited with qualitative election per 35-3A.
*   **Audit trail complete** — GL 1800 traced to 2022 acquisition, work paper WP-805-22 referenced.
*   **Cross-check passed** — intangible rollforward reconciles ($2.8M beginning = $2.8M ending).
*   **Materiality assessed** — both quantitative (7.2% > 5% threshold) and qualitative (strategic acquisition signaling).
*   **Disclosures identified** — ASC 350-20-50-1/50-2 footnotes, Reg S-K Item 303 MD&A discussion.

This analysis meets audit memo standard.
```

**Prompt:** 
```
The company has approximately $1.2M in accounts receivable. Based on financial data, this seems reasonable. Required disclosures have been made. The amount is immaterial.
```

**Response:** 
```
Multiple rejections.

1.  **TRAIL_BROKEN** — 'approximately $1.2M' is hedged language suggesting fabricated precision. What is the exact GL balance? Which invoices? What aging bucket? What confirmation results?
2.  **Source Missing** — 'Based on financial data' is not an audit trail — name the source documents.
3.  **MATERIALITY_IGNORED** — 'immaterial' without a threshold is not an assessment. What is 5% of pre-tax income? How does $1.2M compare?
4.  **DISCLOSURE_MISSING** — 'required disclosures have been made' names zero specific ASC topics. ASC 310-10-50 (receivables), ASC 326-20 (CECL allowance), ASC 820-10-50 (fair value hierarchy if measured at FV)? Which disclosures specifically?
```

## Capabilities

### Verify US GAAP compliance
The AI must cite specific ASC topics and paragraphs instead of using vague generalities.

### Trace numbers to source documents
Every material number is forced to link back to a GL entry, invoice, or bank confirmation.

### Check internal statement reconciliation
The tool ensures your balance sheet, income statement, and cash flow statements actually balance.

### Assess materiality per SAB 99
The AI must state a quantitative threshold and evaluate qualitative factors like trend masking.

### Identify required SEC and SOX disclosures
The tool flags missing Reg S-K items, Reg X rules, and SOX certifications in your analysis.

## Use Cases

### Revenue Recognition Check
Verify if a $5M software deal meets ASC 606 point-in-time criteria for revenue recognition.

### Goodwill Impairment Assessment
Verify if a $2.8M impairment follows the qualitative elections in ASC 350-20-35-1.

### Accounts Receivable Audit
Ensure a $1.2M balance is tied to specific invoices and aging buckets rather than a general estimate.

### SEC Filing Review
Scan a draft MD&A to ensure Reg S-K Item 303 and Reg S-X requirements are met before submission.

## Benefits

- Stop IFRS leakage in your reports by forcing the AI to stick to US GAAP codification using validate_financial_audit.
- Remove hallucinated figures by requiring the AI to name specific GL accounts and invoice numbers for every value.
- Ensure your balance sheet actually balances by forcing the AI to cross-check net income against the equity rollforward.
- Get accurate materiality assessments that include both the SAB 99 quantitative threshold and qualitative factors.
- Avoid SEC non-compliance by automatically identifying missing Reg S-K items and SOX certifications.

## How It Works

The bottom line is you get a financial analysis that actually stands up to a professional audit.

1. Input your financial analysis or specific audit issue to your AI client.
2. The Connector runs the validation logic against US accounting standards and PCAOB rules.
3. You get a verdict identifying specific structural deficiencies or a proven audit-grade memo.

## Frequently Asked Questions

**How does Financial Audit Prover help with SEC compliance?**
It identifies specific disclosure requirements like Reg S-K and Reg S-X items, ensuring your filings meet SEC standards.

**Can I use Financial Audit Prover to check for IFRS leakage?**
Yes, it detects international standard terminology in US GAAP analysis to ensure you aren't accidentally using IFRS rules.

**What is an audit trail in the context of this Connector?**
It requires the AI to link every number to a specific source document, such as a GL entry, invoice number, or bank confirmation.

**Does Financial Audit Prover handle materiality assessments?**
It ensures the AI evaluates both the 5% pre-tax quantitative threshold and the qualitative factors required by SAB 99.

**Can I use Financial Audit Prover to verify revenue recognition?**
It forces the AI to apply the specific ASC 606 five-step analysis for every revenue recognition scenario it evaluates.

**Will Financial Audit Prover catch mistakes in my balance sheet reconciliation?**
Yes, it checks that the balance sheet equation balances and that net income flows correctly to the equity rollforward.

**Does it perform calculations or generate financial statements?**
No. Financial Audit Prover generates zero content and performs zero calculations. It validates the REASONING behind financial conclusions — whether the correct GAAP standard is applied, whether numbers trace to source documents, whether statements reconcile, whether materiality is properly assessed, and whether required disclosures are identified. The agent does the financial analysis; the tool proves whether that analysis meets audit-grade standards.

**Does it support IFRS or only US GAAP?**
US GAAP only. The engine actively detects IFRS terminology leakage (IAS references, 'revaluation model', 'true and fair view') and rejects it. US GAAP and IFRS differ materially on inventory (LIFO), development costs, leases, and revenue recognition implementation. Mixing frameworks produces unreliable analysis. If you need IFRS validation, a separate tool would be required — this one validates ASC codification exclusively.

**What types of entities does it cover?**
Any US entity reporting under GAAP: SEC registrants (10-K/10-Q filers), private companies (including private company alternatives under ASC), nonprofits (ASC 958), and tax-reporting entities (IRC Title 26). The tool adapts — SEC registrants trigger Reg S-K and SOX validation; private companies focus on ASC compliance and footnote completeness; nonprofits require net asset classification checks. Specify the entity type in the 'regulatoryContext' field.