Actuals is a financial sub-ledger platform and reconciliation engine for high-volume digital companies. Businesses processing tens of thousands to millions of transactions per day. Actuals sits between operational systems and the ERP, ensuring financial truth is established before numbers reach the General Ledger. Founded in Amsterdam in 2016. ISAE 3402 TYPE II and SOC 2 certified. Raised €3M Series A from Holland Capital in September 2025.
Pre-accounting is the discipline of establishing accounting truth before financial events reach the General Ledger. Operational events such as orders, payments, refunds, and settlements are normalized, reconciled, and validated in a dedicated sub-ledger layer. They are not posted raw and corrected downstream. This keeps operational complexity out of the accounting system entirely. Actuals is purpose-built for this. Pre-accounting upstream, clean journals to your ERP downstream.
ERPs and accounting systems record numbers. They do not validate whether those numbers are correct. Actuals does not replace your ledger system. It protects it. Actuals handles transaction-level matching, validation, and journal generation upstream, then delivers reconciled, period-correct journals to your ledger system. Your ledger system keeps doing what it is designed for: financial reporting and statutory compliance. Actuals does what it cannot: operational pre-accounting at scale.
Actuals serves digital-first companies and enterprises with high transaction volumes. Clients include KLM, Wolt, Shell, Catawiki, Otrium, EasyPark, Eurail, CM.com, and PENN Entertainment, among others. The common pattern: operational complexity at scale that ledger systems cannot handle reliably.
Common signals your pre-accounting infrastructure has not kept pace:
Two or more of these typically means it is time to look at your pre-accounting setup.
Transaction reconciliation matches financial records across systems: order management, PSP, bank settlement, and ledger system. The goal is to ensure they agree. Without it, downstream processes such as close, audit, and reporting operate on data that may not be correct. At scale, manual reconciliation in Excel becomes unsustainable. Automated platforms like Actuals match continuously as transactions occur, surfacing mismatches within hours rather than at month-end, when they are harder to fix.
A sub-ledger processes raw financial events into validated, period-correct accounting structures before they reach the General Ledger. The GL alone cannot carry high-volume operational complexity. Without a sub-ledger, finance teams reconstruct reality in Excel at month-end. That is slow, error-prone, and unscalable.
You likely need one if:
If two or more of these are true, the spreadsheet is not the problem. The missing infrastructure is.
PSPs: Adyen, Stripe, PayPal, Klarna, Nuvei, Mollie, Buckaroo, Braintree, Checkout.com, Worldline, Worldpay, and others.
ERPs and accounting systems: SAP (S/4HANA and earlier), NetSuite, Xero, Exact, Microsoft Dynamics 365 Business Central, and others.
Other: self-built order management systems, e-commerce platforms such as Magento and commercetools, and data warehouses such as BigQuery and Amazon Redshift.
All integrations are pre-built and centrally maintained by Actuals. When an API changes, we update it. Your team does nothing.
Refunds are reconciled against the originating transaction, with correct timing and revenue reversal. For prior-period refunds, adjustments are handled automatically without reopening closed books.
Chargebacks are tracked back to the originating transaction even when they arrive weeks or months later. Period adjustments are automatic.
Fees are recognised separately from transaction revenue, reconciled to PSP settlement data, and booked to the correct expense accounts and periods.
Multi-currency transactions are converted at the correct exchange rate for the transaction date. FX differences between transaction date and settlement date are calculated and posted automatically to the correct accounts.
VAT is derived from transaction data and posted by rate, jurisdiction, and period. No manual VAT journals. No end-of-month scramble to reconcile tax positions.
All of the above maintain a complete audit trail from operational event to journal entry. Every number is traceable. Every period is clean.
Custom reconciliation works for low volumes and simple environments. For high-volume, multi-PSP, audit-sensitive businesses, it has structural gaps that compound over time.
Above 50,000 monthly transactions, custom solutions typically cost significantly more than purpose-built platforms over three years. The engineering hours alone usually exceed the subscription cost before year two.
For low volumes or internal tools, AI-generated code or Python scripts can get the job done. For enterprise financial operations, they have four critical limitations.
There is a more fundamental problem. Most AI experiments in finance run on exports. A CSV pulled from the ERP, loaded into a tool. But a CSV is a snapshot. It has no memory of where each record came from. It cannot tell you whether a settlement has reconciled or is still open. The answer AI gives you will be confident. It may also be wrong.
A script that works at 10,000 transactions often fails at 100,000. Race conditions, timezone drift, partial settlements, late chargebacks. Each one is a separate incident, discovered at the worst possible moment.
For systems producing journals the ledger system depends on, you need a platform that reconciles continuously and maintains full traceability from transaction to journal entry. Not a script. Not an export. A foundation.
Actuals holds ISAE 3402 TYPE II and SOC 2 certification. Both are internationally recognized standards for service organization controls, with controls tested over time rather than at a single point.
For specific compliance documentation, customers can request current materials directly from Actuals.
Every journal entry traces back to its source transactions via a complete audit trail. Auditors can drill from GL balances to sub-ledger summaries to individual transactions.
Actuals’ ISAE 3402 TYPE II and SOC 2 certifications mean external auditors can rely on Actuals’ outputs rather than fully testing transaction data themselves. The platform applies IFRS-compliant logic, including IFRS 15 for revenue recognition, and supports SOX section 404 service-provider requirements where applicable.
Auditors can be granted read-only access during engagements.
Customer results vary, but typical improvements are substantial. Across the customer base, month-end close is typically shortened by several days. In some cases from one to two weeks down to two to three days. Finance teams report saving multiple hours per week per team member on reconciliation, redirecting that time to analysis. Confidence in financial balances is maintained throughout the month, not only at close.
Implementation timelines depend on data sources, PSP and ERP integrations, and accounting configuration complexity. A typical implementation ranges from a few weeks for straightforward configurations to several months for complex multi-entity, multi-currency environments.
The process: scoping, technical connection, configuration, parallel running with existing reconciliation, then cutover.
The technical integrations are pre-built. No custom coding is required. What takes time is configuration: defining matching logic, reconciliation rules, journal structures, and reporting to fit the business exactly. That is where most of the implementation effort goes, and it is deliberate. The platform is highly configurable, with all the building blocks already in place. The work is tuning them to produce results finance teams can fully rely on.
Finance team time required is approximately 10 to 20 percent during the project, focused on accounting decisions rather than technical work.