Inspiration
Every year, trillions of dollars move through mergers, acquisitions, and private investments. Yet the systems protecting these transactions remain surprisingly manual. Analysts rely on spreadsheets, static reports, and human review to detect financial inconsistencies before capital is deployed.
In cybersecurity, abnormal network behavior triggers intrusion detection systems in real time. In finance, abnormal financial behavior — earnings manipulation, working capital distortion, liquidity masking — often goes undetected until after capital has already moved.
We were inspired by a simple question:
If digital infrastructure has intrusion detection, why doesn’t financial infrastructure?
That gap between capital deployment and structural integrity enforcement led us to build TAM.
What It Does
TAM is a financial intrusion detection engine that secures high-stakes transactions before capital moves.
It:
Securely ingests financial documents (PDF, Excel, CSV)
Extracts structured financial data using AI
Builds a structural financial fingerprint for each entity
Runs multi-layer anomaly detection
Enforces accounting integrity constraints
Generates integrity-verified intelligence reports
Instead of automating diligence workflows, TAM protects capital by detecting structural financial anomalies early.
How We Built It
We designed TAM as a zero-trust financial processing pipeline with four core layers.
- Secure Extraction
We ingest raw financial documents into isolated processing environments.
LLM-guided extraction converts unstructured financial data into structured representations. Each extracted value is mapped back to its source location, preserving lineage and traceability.
This creates a clean financial dataset ready for validation and modeling.
- Structural Financial Fingerprint
We construct a multi-dimensional profile of a company’s financial behavior across:
Revenue and margin structure
Cash flow conversion
Working capital cycles
Leverage ratios
Cross-statement consistency
This fingerprint models how the company’s financial system behaves — not just individual numbers, but their relationships and structural dependencies.
- Multi-Layer Anomaly Detection
We treat abnormal financial behavior the same way intrusion detection systems treat abnormal network activity.
Our detection stack includes:
Deterministic Integrity Enforcement
We enforce accounting invariants such as:
Assets
Liabilities + Equity Assets=Liabilities+Equity EBITDA ≤ Revenue EBITDA≤Revenue Operating Cash Flow ≈ Net Income + Non-Cash Adjustments − Δ Working Capital Operating Cash Flow≈Net Income+Non-Cash Adjustments−ΔWorking Capital
If these constraints are violated, TAM flags structural integrity breaches.
Statistical Deviation Detection
We compute standardized deviation scores:
𝑧
𝑥 − 𝜇 𝜎 z= σ x−μ
to detect outliers relative to expected financial behavior.
This helps flag abnormal margin spikes, unusual leverage shifts, or extreme working capital movements.
Multivariate Anomaly Detection
We use Isolation Forest models to detect abnormal combinations of financial metrics. Even if individual metrics fall within acceptable ranges, their joint distribution may be inconsistent.
Formally, we model the financial feature vector:
𝑥
( 𝑥 1 , 𝑥 2 , . . . , 𝑥 𝑛 ) x=(x 1
,x 2
,...,x n
)
and identify observations that require fewer splits to isolate in random partitioning trees — indicating structural abnormality.
Temporal Drift Detection
We analyze time-series behavior across reporting periods to detect:
Earnings smoothing
Volatility suppression
Short-term liquidity window dressing
Drift is detected when:
∣ 𝜇 𝑡 − 𝜇 𝑡 − 1 ∣
𝛿 ∣μ t
−μ t−1
∣>δ
where 𝛿 δ represents acceptable structural change thresholds.
- Privacy & Security Architecture
Financial documents contain highly sensitive information, including customer data, revenue breakdowns, supplier pricing, and debt structures.
We implemented a privacy-first architecture:
Deal-level compute isolation
Encrypted data storage at rest
Role-based access control
Ephemeral LLM sessions with no cross-deal memory
Immutable audit logs
Traceable cell-level lineage for every reported metric
TAM protects both the transaction and the confidential financial data powering it.
Challenges We Ran Into
One major challenge was integrating deterministic accounting logic with probabilistic machine learning models in a coherent pipeline. Financial integrity requires both hard constraints and statistical modeling.
Another challenge was explainability. Black-box anomaly detection is not sufficient for high-stakes financial decisions. We needed to ensure every flagged anomaly was traceable and defensible.
We also had to carefully design isolation boundaries to prevent cross-entity data leakage while still enabling efficient AI processing.
Accomplishments We’re Proud Of
We built more than a document summarization tool.
We created:
A structured financial modeling engine
A multi-layer anomaly detection stack
An accounting integrity enforcement system
A privacy-preserving processing pipeline
Integrity-verified report generation
Most importantly, we reframed financial due diligence as a security problem — and built a system around that philosophy.
What We Learned
We learned that financial systems behave like infrastructure.
Just as networks require intrusion detection, financial systems require structural validation and anomaly detection before irreversible decisions are made.
We also learned that security and explainability must coexist. Detection without justification is not actionable in financial environments.
Finally, privacy cannot be layered on afterward — it must be embedded at the architectural level.
What’s Next for TAM
Next, we plan to:
Expand industry-specific anomaly baselines
Integrate real-time benchmarking datasets
Enhance temporal modeling using longer historical sequences
Implement stronger cryptographic guarantees for isolation
Deploy TAM as a scalable financial integrity layer in cloud environments
Our vision is simple:
Cybersecurity protects digital systems.
TAM protects financial systems.
We are building the integrity layer for capital markets.
Log in or sign up for Devpost to join the conversation.