Transaction Processing

Transaction processing is the core of your accounting system. AI-native ERP uses a unified ledger architecture where every transaction -- AP invoices, AR invoices, payments, journal entries, bank transactions, payroll entries, and more -- flows through a single posting engine. One workflow, one table, one set of rules. This eliminates the complexity of managing separate subsystems for each transaction type.

40+ Transaction Types

The system supports a comprehensive set of transaction types organized by domain. Accounts payable covers vendor invoices, credit memos, debit memos, and payments. Accounts receivable handles customer invoices, credit memos, debit memos, payments, and recurring billing. Banking includes deposits, withdrawals, transfers, fees, and interest. Journal entries cover manual adjustments, opening balances, closing entries, and reclassifications.

Specialized types handle Stripe payment processing (charges, refunds, payouts, fees), expense reports, payroll entries, fixed asset transactions (depreciation, disposal, impairment), and intercompany transfers. Each type has its own posting rules defined by posting profiles, but they all flow through the same unified posting engine.

Automatic GL Posting

When you post a transaction, the system automatically generates the correct double-entry journal lines based on the transaction type's posting profile. Debits always equal credits -- the system validates this before any transaction is committed. If a transaction would create an imbalance, it is rejected with a clear explanation of the discrepancy.

Each transaction line can carry dimension tags (department, project, cost center, location) that enable multi-dimensional reporting and analysis. Dimensions are validated against your configured dimension values, preventing invalid categorization.

Transaction Lifecycle

Every transaction can be updated, reversed, or deleted after posting. Updates modify header fields or GL lines on the existing transaction. Reversals create a new transaction with opposite debit-credit entries, effectively canceling the original while preserving the audit trail. Deletions permanently remove the transaction but capture a snapshot for audit purposes.

Risk-Based Approval

Transactions are routed through approval workflows based on their risk level. Small, routine transactions from trusted users may be auto-approved and posted immediately (green lane). Moderate transactions require single-level manager approval (yellow lane). Large or unusual transactions require multi-level authorization (red lane). The thresholds and routing rules are configurable per transaction type and organization.