AIP Framework.
A composable, ERP-agnostic intelligence layer built on three engines. AIP sits above any ERP, transforming transactional data into obligation intelligence.
AIP operates above all ERP systems — ERP-agnostic by design
Definition Engine
What is owed and why
The Definition Engine is the classification layer of AIP. It uses the 780 taxonomy to identify and categorize every financial obligation. Every accrual type is assigned a code, mapped to a value stream, and linked to a trigger event.
Maps To
Policy Layer
Establishes the accrual policy framework — materiality thresholds, recognition criteria, and governance rules that determine which obligations require accrual.
BPML Layer
Maps each accrual type to its Business Process Model — identifying the upstream process (e.g., PO issuance, goods receipt) that creates the obligation.
Analytics Layer
Provides catalog analytics — coverage gaps, policy compliance rates, and accrual type distribution across value streams.
Core Components
780 Taxonomy Mapping
Assign every obligation to a 780 code
Trigger Catalog
Define the event that creates each obligation
Source System Registry
Map ERP tables and API sources to each accrual
Policy Framework
Materiality, recognition criteria, governance
Value Stream Anchoring
Link each accrual to its enterprise value stream
ERP Compatibility
AIP Philosophy
"Accrual is eternal. Tools are temporary. ERPs are execution systems. Intelligence sits above ERP."
Composable
Each engine operates independently or in combination. Deploy what you need.
ERP-Agnostic
AIP connects to any ERP via API. SAP, Oracle, NetSuite, or custom systems.
Audit-Ready
Every calculation produces a full audit trail — amount, logic, source, timestamp.