-
01 Finance Close on the source row.
A bank line arrives for an open invoice. AI Builder proposes a match — bank line, invoice, customer, amount, confidence, and every row that would be touched. The CFO or controller reviews the diff and ratifies or rejects it. When ratified, one commit clears AR, posts the GL movement, updates the reconciliation state, and writes the audit trail. If the match is wrong, the transaction reverts as a governed platform action. The boundary: AI does not post to the GL on its own. It proposes. Finance ratifies.
-
One row, no bridge
AR debits, AP pays, and GL reads against the same row. Sub-ledger reconciliation collapses to a join.
Match on the PO
Three-way match — PO, goods receipt, invoice — enforced on the purchase order, not a workflow beside it.
One trial balance
FX revaluation, accruals, and intercompany eliminations all post against the trial balance the consolidator reads.
Cleared on post
Intercompany legs settle inside the transaction that opened them. No suspense account, no period-end clean-up.
SEF from the invoice
e‑Faktura submission writes back to the source invoice — not a nightly export to a localization partner.
Filing reads the close
The tax-authority pack runs the same query finance uses to close. No drift between posted and filed.
-
02 Compliance Audit-ready by default.
A customer emails dpo@ asking for everything you hold on them, plus deletion of marketing consent. The DPO opens the customer's Account record — one field, email or national ID, anchors the query. A single export runs across CRM accounts, orders, invoices, tickets, consents, and communications: same record key, same transaction. The pack lands in Approvals: anonymise marketing consent, retain invoice rows the tax authority requires, redact the ticket where another customer is named. One click ratifies; the platform writes the anonymisation, logs every change, generates the response PDF, and timestamps the close.
-
One query, one DSAR
Article 15 anchors on one identity — email or national ID — and returns Account, every Order, every Invoice, every Ticket, every Consent, every Communication in one transaction.
Erasure with retention guard
Erasure runs only when approved. Retention exceptions for ZZPL Art. 45 and tax law are first-class rules.
One write log
Each write captures actor, target row, before, after, and lawful basis. The auditor reads a config screen.
Compliance as data
Retention schedules, consent versions, and the lawful-basis register are queryable records — not policy PDFs in a shared folder.
AI writes traceable
Every AI-generated row carries an agent identifier and confidence. One query separates AI proposals from human writes.
-
03 Approvals Approve the record, not a copy.
A buyer raises a high-value PO for a new vendor. The approval rule routes on amount, vendor status, budget utilization, and department — the CFO and operations lead review the same underlying record, not screenshots or copies. If the AI pilot is enabled, the system proposes a route and flags the policy reasons. A controller still ratifies. Every state change writes back to the record itself — so the auditor never has to compare a workflow timestamp with an ERP timestamp.
-
One engine, every record
POs, expenses, vendors, journals, contracts — every record approves through the same engine, against the same row. The amount cannot drift between approval and posting.
SoD on the row
Segregation of duties is enforced at the record itself, not at a workflow layer the ERP can't see.
Policy as data
Amount, vendor risk, GL account, budget, project — every routing rule is a queryable, versioned expression.
AI proposes, you ratify
Bank matches, journal accruals, expense categorizations — every AI proposal enters the same Approvals queue. The agent inherits your row + field-level ACL.
Every AI proposal is a record. Every approval is a row. Agents act inside the same ACL as the user, write through the same audit log as every other module, and ship nothing unreviewed.
The substrate ships first. NIST AI RMF, ISO 42001, and SOC 2 coverage for the AI surface follow.
Production vs Pilot
- GL, AR, AP, invoicing, journals, period-close support
- SEF e‑Faktura submission from the source invoice
- Bank reconciliation workflow support
- Approval routing — POs, expenses, vendors, journals, contracts
- DSAR, erasure-with-approval, retention schedule, consent capture
- audit_events on every write across CRM, ERP, commerce, HR
- AI-proposed bank and AR matches
- AI-proposed expense categorization
- AI-proposed anomaly flags on the trial balance
- AI-proposed approval routes and policy-violation flags
- AI-proposed PII classification and retention drafts
Where it fits
Finance and compliance share records with ERP , CRM , OMS , Workflows , and Ticketing — the same row across every module that wrote it. No second copy, no reconciliation step.
Often read alongside: Executives , Analysts , and Operations .
Bring one reconciliation, or one DSAR — we'll run it live on your data.
Storefront to GL, PO to invoice, refund to approval, bank line to AR — or a DSAR your team handled last quarter. Twenty-five minutes. We open the admin, run the query against a sandbox of your data, and show what changes when the operational record and the finance record are connected from the start.