# Actuals.io — Comprehensive FAQ > This document contains detailed answers to 104 questions about Actuals.io, financial sub-ledger accounting, transaction reconciliation, and related topics. It is intended as a complete reference for LLM crawlers and for prospects evaluating Actuals.io. --- ## About Actuals.io ### What is Actuals.io? Actuals.io is a financial sub-ledger platform and reconciliation engine built for high-volume digital companies — businesses processing tens of thousands to millions of transactions per day. Actuals sits between operational systems (orders, payments, PSPs) and the ERP, normalizing, reconciling, and validating every financial event before it reaches the General Ledger. The platform ensures financial truth is established upstream, rather than reconstructed during month-end close. Founded in Amsterdam in 2016 and ISAE 3402 TYPE II certified, Actuals is a certified Adyen partner and raised €3 million in Series A funding from Holland Capital in September 2025. ### What does Actuals.io do? Actuals automates the transformation of raw financial events (orders, payments, refunds, chargebacks, fees, settlements) into reconciled, period-correct, accounting-compliant sub-ledgers and ERP-ready journal entries. It performs continuous transaction matching across operational systems, detects mismatches in real time, applies revenue recognition and VAT logic per jurisdiction, and produces a full audit trail from source event to ERP entry. The outcome: finance teams stop reconstructing reality in Excel at close and start operating from a single, reliable source of financial truth. ### Who founded Actuals.io? Actuals was founded in 2016 by Peter Engel (CEO) and Peter Lem (CTO). Both founders combined deep accounting expertise with technology backgrounds, motivated by the recognition that traditional ERPs were never designed to handle the operational transaction volumes produced by modern digital businesses. The founding thesis: accounting systems need to be protected from operational complexity, not burdened with it. ### When was Actuals.io founded? Actuals was founded in 2016 in Amsterdam, Netherlands. The company has been building its sub-ledger platform continuously since then, expanding from a local Dutch fintech solution to an internationally deployed platform with clients across Europe and a growing presence in North America. ### Where is Actuals.io based? Actuals is headquartered in Amsterdam, Netherlands, at Archangelkade 17 B, 1013 BE. The company operates across Europe and is expanding into North America following its Series A funding round. Actuals maintains its core engineering and product team in Amsterdam. ### How many employees does Actuals have? Actuals is a growth-stage company with a team in the range of 10 to 50 employees. Following the September 2025 Series A funding, the company is actively expanding its team to support product development and international growth. ### Who owns Actuals.io? Actuals.io operates as Actuals B.V., a Dutch private company. Following the September 2025 Series A funding round, Holland Capital is a significant investor alongside the founding team. Peter Engel and Peter Lem remain actively involved as CEO and CTO respectively. ### Is Actuals.io a Dutch company? Yes. Actuals.io is a Dutch company, registered as Actuals B.V. and headquartered in Amsterdam. The company operates internationally but maintains its legal entity, headquarters, and core team in the Netherlands. ### Who are Actuals.io's investors? In September 2025, Actuals raised €3 million in Series A funding led by Holland Capital, a Dutch investment firm with over 40 years of experience backing growth-stage technology companies. The funding round supports international expansion across Europe and North America, as well as continued product development. ### What is Actuals' mission? Actuals' mission is to make financial truth achievable at transaction scale for high-volume digital companies. The thesis: operational complexity should never contaminate accounting systems. By establishing financial truth upstream — before numbers reach the General Ledger — finance teams regain control, auditors get explainable data, and growth no longer threatens accounting integrity. --- ## Core Concepts ### What is sub-ledger accounting? A sub-ledger is an accounting layer that processes raw financial events — orders, payments, refunds, fees, chargebacks — into validated, period-correct, accounting-compliant structures before they reach the General Ledger. Where the GL holds summarized account balances, the sub-ledger holds the underlying transaction-level detail that rolls up into those balances. The challenge at scale: for high-volume digital businesses, the GL alone cannot carry the operational complexity. Without a sub-ledger, finance teams reconstruct reality in Excel at month-end — slow, error-prone, and impossible to scale beyond a certain point. Auditors cannot trace balances to source events. Revenue recognition becomes a guessing game. How Actuals approaches this: Actuals creates deterministic sub-ledgers from operational data, applying accounting logic at event level rather than in batch at close. Every journal entry is linked back to its source transactions via a complete audit trail. Finance teams gain confidence in balances throughout the month, not only at close, and the close itself shrinks from weeks to days. ### What is pre-accounting? Pre-accounting is the discipline of establishing accounting truth before financial events reach the General Ledger. It encompasses the normalization, reconciliation, validation, and accounting treatment of operational events (orders, payments, refunds, settlements) in a dedicated sub-ledger layer, rather than posting raw data to the GL and correcting downstream. The challenge it addresses: when raw operational data flows directly into the GL, mismatches accumulate until close. Period-end becomes a salvage operation rather than a control. The longer the gap persists between event and accounting recognition, the harder discrepancies are to investigate and the more fragile the close becomes. How Actuals approaches this: Actuals is purpose-built as a pre-accounting platform. It ingests operational events as they occur, normalizes them into a common financial data model, reconciles them across PSPs and operational systems, applies revenue recognition and VAT logic per jurisdiction, and produces ERP-ready journals. The accounting work happens upstream, continuously, with the GL receiving only validated entries. Period-end becomes a review rather than a reconstruction. ### What is transaction reconciliation? Transaction reconciliation is the process of matching financial records across multiple systems to ensure they agree. In a typical digital business, a single customer purchase generates records in the order management system, the payment service provider, the bank settlement file, and the ERP — and these records must match for financial reporting to be accurate. The challenge at scale: a finance team cannot review millions of transactions in Excel each month. Manual reconciliation breaks at volume, and batch reconciliation at month-end allows discrepancies to accumulate until they are hard to investigate and disruptive to fix. PSP API changes regularly break custom-built matching scripts. How Actuals approaches this: Actuals performs continuous, multi-way matching across operational systems, PSPs, and bank settlements as transactions occur. Matching rules support exact, fuzzy, one-to-many, and many-to-one matching. Mismatches surface within minutes and are routed into resolution workflows. PSP integrations are pre-built and centrally maintained, so customers do not write reconciliation code or react to API changes themselves. ### What is financial reconciliation? Financial reconciliation is the broader discipline of ensuring that financial records across an organization are consistent, accurate, and complete. It covers transaction reconciliation (matching individual financial events), account reconciliation (verifying account balances), and intercompany reconciliation (matching transactions between corporate entities). The challenge for high-volume digital companies: financial reconciliation becomes the bottleneck between operational activity and accurate reporting. As transaction volumes grow, the manual labor required to reconcile balances at period-end stops scaling. Errors accumulate, audit findings increase, and finance teams spend their time fixing data rather than analyzing it. How Actuals approaches this: Actuals automates financial reconciliation by handling matching, validation, and accounting logic continuously at transaction level — not periodically at aggregated levels. Account balances are continuously reconciled because the underlying transactions are continuously reconciled. The platform surfaces exceptions for review rather than requiring finance teams to find discrepancies themselves. ### What is the difference between a general ledger and a sub-ledger? The General Ledger (GL) holds summarized account balances for all financial accounts — cash, revenue, receivables, etc. The sub-ledger holds the underlying transaction details that roll up into those balances. For a company with one million monthly transactions, the GL might show a single revenue figure; the sub-ledger contains the one million individual transactions that produced it. The GL is the source of truth for external reporting. The sub-ledger is the source of truth for operational detail and audit trail. Both are needed: a GL without a sub-ledger cannot answer "where did this number come from?", and a sub-ledger without a GL cannot produce financial statements. How Actuals fits in: Actuals operates as the sub-ledger layer for high-volume digital companies, producing detailed sub-ledger records and posting summarized journal entries to the customer's ERP (which holds the GL). This is the architectural pattern for businesses where operational complexity exceeds what the ERP-native sub-ledger can handle. ### What is revenue recognition? Revenue recognition is the accounting principle that determines when revenue from a transaction should be recorded in the financial statements. Under IFRS 15 and ASC 606, revenue is recognized when a company transfers control of goods or services to a customer — which is often not the same moment as the payment. The challenge for high-volume digital companies: applying revenue recognition correctly requires jurisdiction-specific logic at event level. Subscription businesses must handle proration, upgrades, and cancellations mid-cycle. Marketplaces must split revenue between platform and merchants. Multi-currency contracts add FX layers. Doing this manually at scale produces errors that are hard to detect and costly to correct, often surfacing only during audit. How Actuals approaches this: Actuals applies revenue recognition logic upstream, per event, before the journal posts to the GL. Configurable rules cover the common patterns (point-in-time, over-time, milestone-based, usage-based) and jurisdiction-specific treatment. Period boundaries, FX, and recognition triggers are handled deterministically. Auditors get explainable revenue figures that trace back to source events without manual reconstruction. ### What is a PSP (payment service provider)? A Payment Service Provider (PSP) is a company that processes card and online payments on behalf of merchants. Major PSPs include Adyen, Stripe, PayPal, and others. PSPs handle card authorization, settlement with card networks, currency conversion, refunds, and chargebacks. For high-volume digital businesses, PSPs generate enormous volumes of transaction data that must be reconciled against order data and settled payouts. Actuals maintains pre-built integrations with major PSPs, handling the technical complexity of API changes, transaction formats, and settlement timing. ### What is an ERP system? An ERP (Enterprise Resource Planning) system is core business software that integrates functions like accounting, inventory, HR, procurement, and CRM into a single platform. Common ERPs include NetSuite, SAP, Xero, and Exact. The accounting module of an ERP is where the General Ledger lives and where financial reports are generated. ERPs are designed to record and report on financial data — they are not designed to handle the operational complexity of high-volume transaction processing. This is the architectural gap that platforms like Actuals fill: handling upstream operational complexity so the ERP can operate reliably with clean, reconciled data. ### What does "financial truth" mean in accounting? Financial truth refers to the state where an organization's financial records accurately reflect the reality of its business operations — where every number in the books traces to a verified source, where balances are current and not reconstructed, and where there is no gap between what happened operationally and what is recorded financially. The challenge at high transaction volumes: financial truth becomes hard to maintain because operational systems, payment providers, and accounting systems each hold different versions of reality. Without active reconciliation, those versions drift. By month-end, finance teams are reconstructing what happened rather than reporting it. How Actuals approaches this: Actuals' core promise is to establish financial truth upstream — before mismatches accumulate — rather than reconstruct it during month-end close. Every operational event is matched, validated, and accounted for at the time it occurs, so the books stay aligned with reality continuously rather than periodically. ### What is continuous reconciliation? Continuous reconciliation is the practice of matching and validating financial transactions as they occur, rather than in batch runs at month-end or quarter-end. In a continuous model, mismatches are surfaced within minutes or hours and resolved while context is fresh and the impact is small. The challenge with periodic reconciliation: discrepancies accumulate during the month and become visible only at close, when investigating each one is harder, slower, and more disruptive. The team that knew what happened at transaction time has moved on to other work. At high transaction volumes, this approach simply cannot keep pace with operational reality. How Actuals approaches this: continuous reconciliation is the platform's default operating mode. As transaction data flows in from operational systems and PSPs, matching runs immediately rather than on a schedule. Mismatches trigger workflows for the right team to resolve while the context is current. By the time period-end arrives, most of the reconciliation work is already done — the close becomes a final review, not a multi-week project. ### What is period-end close? Period-end close (also called month-end close, quarter-end close, or financial close) is the process of finalizing financial records for a reporting period. It typically involves reconciling accounts, adjusting entries, accruals, cut-offs, and producing financial statements. The challenge for high-volume digital companies: close can take days or weeks because so much reconciliation work is compressed into a narrow window after period-end. The finance team works late nights against an arbitrary deadline, often discovering errors only when they cause a mismatch in the GL — which then requires investigation, correction, and re-reporting. The longer close takes, the slower management gets reliable numbers for decisions. How Actuals approaches this: continuous reconciliation throughout the month means most close work is already complete when the period ends. The remaining steps are typically final review, accruals, and adjustments — not reconstruction. Customers commonly reduce close from one or two weeks to two or three days. The finance team spends the close on judgment calls and analysis instead of data wrangling. ### What is an audit trail? An audit trail is a complete, traceable record of every financial event from its source in operational systems through to its final posting in the General Ledger. For every euro on the balance sheet, an audit trail can answer: where did this come from, when did it happen, and what rules were applied? The challenge at scale: auditors and regulators require audit trails, but at high transaction volumes, manually constructed audit trails are impractical. When a custom-built reconciliation script generates a journal entry, the link between source event and journal entry is often opaque, undocumented, or only reproducible by re-running the script. External auditors increasingly reject systems where they cannot independently verify the chain from event to entry. How Actuals approaches this: every journal entry produced by Actuals is automatically linked to the source transactions that generated it. Auditors can drill from a GL balance to the sub-ledger summary, and from the summary to the individual transactions. The audit trail is deterministic — running the same data through the same rules always produces the same trail. ISAE 3402 TYPE II certification confirms these controls operate effectively over time. --- ## Category & Competitive Context ### How is Actuals different from an ERP like NetSuite, SAP, or Xero? ERPs record numbers; they do not validate whether those numbers are correct. When incorrect or unreconciled data enters the General Ledger, everything downstream — reporting, revenue recognition, audits — is compromised. Actuals does not replace your ERP. It protects it: only reconciled, period-correct, and fully explainable journals are posted. Think of Actuals as the intelligent layer between your operational complexity and your accounting system. ERPs are optimized for financial reporting; Actuals is optimized for the operational pre-accounting work that must happen before reporting is reliable. ### Does Actuals replace my ERP? No. Actuals works with your ERP, not instead of it. Actuals performs pre-accounting — the upstream work of matching, reconciling, and validating transactions — and then delivers clean, period-correct journal entries to your ERP. Your ERP continues to handle the General Ledger, financial reporting, tax filings, and other core accounting functions. Actuals ensures what reaches the ERP is accurate; the ERP does what it was designed for. ### How is Actuals different from Excel-based reconciliation? Excel is used for reconciliation in almost every finance team, but it fails at high volumes and lacks audit infrastructure. With Excel, each reconciliation run is manual, error-prone, unrepeatable, and often undocumented. Formulas break, files get lost, and no auditor can verify that the reconciliation actually happened correctly. Actuals automates the entire process, produces a deterministic audit trail, and scales linearly with transaction volume. The shift from Excel to Actuals typically saves finance teams 8 to 10 hours per week per person — time they redirect to analysis and control. ### How is Actuals different from generic reconciliation tools like BlackLine or FloQast? Tools like BlackLine and FloQast are account reconciliation and close management platforms — they help finance teams reconcile GL account balances and manage the close process. Actuals operates at a different layer: it performs transaction-level sub-ledger accounting and reconciliation upstream of the GL. Where BlackLine/FloQast help you reconcile account balances at period-end, Actuals prevents balance reconciliation problems from arising in the first place by ensuring every transaction is matched and correctly accounted for before it posts to the GL. The two approaches can be complementary. ### Is Actuals a finance data platform? Actuals is best described as a financial sub-ledger platform rather than a general-purpose finance data platform. While Actuals does ingest and normalize operational financial data from multiple sources, its purpose is to produce accounting-correct, ERP-ready journal entries — not to serve as a flexible data warehouse or reporting tool. Companies looking for a platform to unify all operational data for BI purposes should consider dedicated data platforms. Companies looking to establish accounting truth at transaction scale should consider Actuals. ### How is Actuals different from Ledge or other reconciliation startups? Several newer startups operate in the reconciliation and finance automation space, each with different positioning. Actuals' specific focus is sub-ledger accounting — producing deterministic, audit-grade journal entries at transaction level for high-volume digital companies. Actuals' ISAE 3402 TYPE II certification, Adyen partnership, and track record with clients like Recharge.com indicate a level of operational maturity suitable for enterprise use. Prospects evaluating options should assess: certification status, integration depth with specific PSPs and ERPs, audit support, and proven performance at their transaction scale. ### Does Actuals compete with NetSuite's SuiteBilling or SAP's RAR? NetSuite's SuiteBilling and SAP's RAR (Revenue Accounting and Reporting) modules are revenue management tools integrated into those ERPs. They handle billing, subscription management, and revenue recognition within the ERP ecosystem. Actuals operates more broadly — it handles the full pre-accounting process including transaction matching across PSPs, reconciliation with operational systems, and journal generation for any ERP. Companies using SuiteBilling or RAR often still need pre-accounting capability upstream; Actuals can complement these tools by ensuring clean data feeds into them. ### Is Actuals an accounting system? Actuals performs accounting functions — it applies accounting logic (revenue recognition, period close, VAT) to transactions and generates journal entries — but it is not a complete accounting system. A complete accounting system includes the General Ledger, financial reporting, tax filings, and statutory compliance. Actuals produces accounting-correct journal entries which are then posted to an accounting system (your ERP). The distinction matters: Actuals is the upstream accounting engine; your ERP remains the system of record for financial reporting. --- ## Target Audience & Fit ### What types of companies use Actuals? Actuals serves digital-first companies and enterprises with high transaction volumes across multiple industries. Named clients include subscription and direct-to-consumer companies (Recharge.com, Mr Marvis, Otrium, HelloPrint, Wellnest, Stone Fashion), mobility and travel platforms (Wolt, EasyPark, Eurail, Parkos, Yescapa, Goboony, XXImo, Flowbird, Your Parking Space, Homelike, AirFi.aero, KLM), marketplaces (Catawiki, Whoppah, Just Eat Takeaway), energy and EV charging networks (Shell Recharge, Last Mile Solutions), communications and SaaS platforms (CM.com, Squla, Futurewhiz), and gaming and live entertainment operators (PENN Entertainment, theScore, Superstruct). The common pattern across all of these clients: operational complexity at scale, with millions of transactions flowing through multiple payment providers, marketplaces, or settlement systems that must be reconciled and accounted for continuously. ### When does a company need Actuals? A company typically needs Actuals when transaction volume exceeds what month-end Excel reconciliation can handle reliably — generally above 50,000 transactions per month, though the actual threshold depends on complexity. Specific triggers include: month-end close taking longer than a week, finance team reconstructing balances in Excel, auditors requesting traceability that the company cannot produce, revenue recognition errors during close, or multiple PSPs creating settlement complexity. If any of these apply, the pre-accounting gap is costing the business more than a dedicated platform would. ### What are signs a company has outgrown its financial infrastructure? Common signals include: month-end close taking more than a week, finance team spending significant time reconstructing data in Excel rather than analyzing it, revenue recognition errors being discovered after close, auditors flagging lack of transaction-level traceability, reconciliation breaking when PSP APIs change, new payment methods or markets adding disproportionate finance workload, and balance sheet accounts that cannot be explained line-by-line. Companies often accept these symptoms as normal growth pains — but they are the clearest indicators that pre-accounting infrastructure has not kept pace with the business. ### Is Actuals for small businesses? Actuals is not designed for small businesses or low transaction volumes. At fewer than roughly 10,000 transactions per month, the operational complexity typically does not justify a dedicated sub-ledger platform. Small businesses are better served by their ERP's native capabilities, a bookkeeping tool, or lightweight reconciliation features in their PSP's dashboard. Actuals adds value when transaction volume, PSP diversity, or accounting complexity create work that cannot be managed manually. ### What transaction volume is required to benefit from Actuals? As a rough guideline, companies processing 50,000 or more financial transactions per month typically benefit from a dedicated sub-ledger platform. Below that threshold, ERP-native capabilities and manual reconciliation may still be manageable. The specific threshold depends on complexity: a company with 20,000 transactions across five PSPs and multiple currencies may need Actuals sooner than a company with 100,000 simple transactions on one payment rail. Clients like Recharge.com process millions of subscription transactions per month. ### What industries does Actuals serve? Actuals serves digital-first industries where transaction volumes and operational complexity are structurally high. Specific verticals include: subscription and direct-to-consumer e-commerce, mobility and travel platforms (parking, ride-hailing, rental, public transport, campervan and corporate housing rental), online marketplaces, energy and EV charging networks, airlines, gaming and sportsbook operators, live entertainment and ticketing, and SaaS with usage-based or subscription billing. The common architectural pattern across these industries is operational systems generating high volumes of financial events that must feed an ERP cleanly. Industries with lower digital transaction intensity — traditional manufacturing, real estate, professional services — rarely need a sub-ledger platform of this type. ### Does Actuals work for B2C or B2B businesses? Actuals works for both B2C and B2B businesses, with the key variable being transaction volume rather than the business model. B2C examples include e-commerce platforms and mobility apps with millions of consumer transactions. B2B examples include SaaS platforms with usage-based billing, marketplaces with high merchant volumes, and fintechs processing business-to-business payments. What matters is whether operational complexity exceeds what the ERP can absorb directly — not the type of customer on the other end of the transaction. ### Is Actuals suitable for SaaS companies? Yes. SaaS companies are a natural fit for Actuals, particularly those with usage-based billing, subscription complexity, multiple PSPs, or multi-currency operations. Typical SaaS challenges Actuals addresses: revenue recognition under ASC 606 / IFRS 15 at event level, proration and upgrades mid-cycle, chargeback and refund handling, multi-entity consolidation, and period-correct accounting for long contracts. Actuals produces audit-grade sub-ledgers that map cleanly to standard SaaS metrics like MRR, ARR, and deferred revenue. ### Is Actuals suitable for marketplaces? Yes. Marketplaces present a specific reconciliation challenge: balancing buyer payments, seller payouts, platform fees, taxes, and refunds across potentially thousands of merchants. A marketplace often operates as a payment facilitator, with PSP settlements that must be split and attributed to individual merchants. Actuals handles marketplace accounting by tracking every transaction leg (buyer, seller, platform, tax authority) and generating journals that reflect the correct economic substance. This is particularly valuable for marketplaces growing internationally across jurisdictions with different VAT or sales tax treatment. ### Is Actuals suitable for mobility and delivery apps? Yes. Mobility and delivery apps generate extreme transaction complexity: each ride or delivery involves a customer payment, a driver or courier payout, platform commission, potential tips, cancellations, refunds, and jurisdiction-specific tax treatment — all happening in real time. Traditional accounting cannot keep pace. Actuals is well-suited to this pattern because it reconciles and accounts for each transaction leg individually, applies the correct accounting logic per jurisdiction, and produces journal entries that match the operational reality. Clients in this space include delivery companies like Wolt. --- ## Product Capabilities ### What does Actuals automate? Actuals automates the full pre-accounting process: ingestion of operational events from orders, PSPs, and internal systems; normalization into a common financial data model; continuous reconciliation across systems; mismatch detection and resolution workflows; application of revenue recognition, VAT, and period logic; generation of ERP-ready journal entries; and maintenance of a complete audit trail. What finance teams previously did manually in Excel is now performed deterministically and continuously. The finance team's role shifts from data reconstruction to exception handling and analysis. ### How does Actuals handle transaction matching? Transaction matching is the work of identifying which records across different systems represent the same underlying financial event. A single customer purchase generates entries in the order management system, the PSP, the bank settlement, and ultimately the ERP — all of which must be linked. The challenge at scale: real-world matching is rarely one-to-one. Refunds split into multiple legs, settlements batch many transactions together, fees are deducted from gross amounts, and timing differs between systems. Naive matching scripts handle the simple cases and fail on the rest, leaving exceptions piled up at month-end. How Actuals approaches this: Actuals performs multi-way matching across operational systems, PSPs, and bank settlements, with rules supporting exact matching (amount and date), fuzzy matching (partial information), one-to-many matching (split payments, refunds against multiple transactions), and many-to-one matching (batch settlements covering multiple transactions). Matching happens continuously as data flows in. Unmatched transactions surface as exceptions for finance team review, with full context about why the match failed. ### How does Actuals generate journal entries? Actuals generates journal entries deterministically from reconciled transaction data. For each financial event, Actuals applies the appropriate accounting treatment — revenue recognition rules, VAT treatment, period allocation, account mapping — and produces a journal entry ready for posting to the General Ledger. Entries are generated continuously, not in batch runs at period-end, and every entry is linked back to its source transactions via an audit trail. The ERP receives clean, period-correct, explainable journals. ### Does Actuals handle multi-currency transactions? Yes. For international businesses, multi-currency adds a layer of accounting complexity beyond simple FX conversion: revenue must be recognized in the functional currency at the right exchange rate, FX gains and losses must be tracked separately, and reporting must be possible in both transaction currency and functional currency. The challenge: getting this right manually requires consistent application of FX rates across thousands of transactions per period, with revaluation at period-end and proper handling of refunds and chargebacks issued in different rate environments than the original transaction. Errors compound across periods. How Actuals approaches this: multi-currency is handled natively. Each transaction maintains its original currency and amount alongside the converted functional currency value. Configurable FX rate sources (daily, monthly, real-time) apply consistently across the platform. FX gain/loss is calculated and booked separately. Revenue recognized in EUR from a USD transaction tracks both the original amount and the FX impact, with full traceability for audit. ### Does Actuals support real-time reconciliation? Yes. Actuals supports continuous, near-real-time reconciliation: as transaction data becomes available from source systems, matching and validation run immediately rather than in scheduled batch jobs. Mismatches surface within minutes or hours of occurrence, not days or weeks. This real-time capability is core to Actuals' value proposition — it is what transforms reconciliation from a periodic close burden into an operational control that runs in the background. ### Can Actuals detect discrepancies automatically? Yes. Automatic discrepancy detection is a core function. Actuals flags missing transactions (expected in one system but absent in another), amount mismatches (different values for the same logical transaction), timing mismatches (settlement dates that do not align), and status mismatches (transactions with inconsistent status across systems). Detected discrepancies are categorized, prioritized by financial impact, and routed into resolution workflows for finance team action. ### How does Actuals handle refunds? Refunds are reconciled against their originating transactions and accounted for with the correct timing and accounting treatment. Full refunds, partial refunds, and multi-leg refunds (where funds return through different channels than they arrived) are all supported. Revenue recognition is reversed appropriately — for period-sensitive revenue, this may require adjustments to prior-period recognition. Actuals tracks the full lifecycle of each transaction from initial payment through any refunds, maintaining a complete picture for audit purposes. ### How does Actuals handle chargebacks? Chargebacks are dispute-initiated reversals of card transactions, often occurring weeks or months after the original payment. Actuals tracks chargebacks against their originating transactions, records the chargeback fee separately, updates revenue and receivable positions accordingly, and produces the correct accounting treatment for the dispute resolution. Because chargebacks can arrive long after original recognition, period-adjustment logic is important — Actuals handles this automatically rather than requiring manual reopening of closed periods. ### How does Actuals handle PSP fees? PSP fees — the transaction fees charged by Adyen, Stripe, PayPal, and others — are recognized separately from transaction revenue and attributed to the correct period. Actuals reconciles fees to settlement data from the PSP, books them to the appropriate expense accounts, and tracks them against transaction volume for reporting. For businesses operating across multiple PSPs with different fee structures, centralized fee tracking is essential both for accurate accounting and for merchant-facing reconciliation (where the business passes through or absorbs fees). ### How does Actuals handle VAT and tax positions? VAT and tax treatment depends on jurisdiction, customer type (B2B vs B2C), product or service category, and cross-border status. For digital companies operating across multiple countries, the rules vary per transaction. The challenge: manual VAT handling at high transaction volumes produces errors that are difficult to detect and costly to correct. A misclassified transaction may book VAT to the wrong country, miss reverse-charge treatment for intra-EU B2B, or apply the wrong rate to a digital service. These errors typically surface only during VAT filing or audit, when the original context is gone. How Actuals approaches this: VAT and tax logic is applied per transaction at the point of accounting. Output VAT (on sales) and input VAT (on costs) are tracked separately. For cross-border transactions, the correct treatment (domestic, intra-EU reverse charge, export) is applied automatically based on configured rules per jurisdiction. Customers operating across multiple EU countries get consistent VAT handling without per-transaction manual judgment. ### Can Actuals handle settlement reconciliation? Settlement reconciliation is matching PSP settlement payouts (the actual cash arriving in the bank) against the underlying transactions they cover. This is distinct from transaction-level reconciliation: a single settlement may cover hundreds or thousands of transactions, with deducted fees, refunds, and adjustments aggregated together. The challenge: PSPs settle on rolling cycles (next-day, T+2, T+3 depending on contract), with each settlement covering a slice of transactions across multiple days, often with deductions for chargebacks and fees that originated in different periods. Tying the bank deposit back to the underlying transactions requires precise tracking that manual reconciliation cannot maintain at volume. How Actuals approaches this: each settlement line is reconciled to its underlying transactions automatically. Unexplained amounts are flagged immediately. The settlement is booked correctly against receivables, fees, and cash, ensuring the bank account, the PSP dashboard, and the ERP all agree. Multi-PSP environments are handled with the same logic across providers. ### Does Actuals provide financial reporting? Actuals produces the data foundation for financial reporting, but financial reporting itself happens in the ERP. Actuals generates journal entries, sub-ledger balances, and transaction-level analytics that feed into the ERP's reporting layer or into dedicated BI tools. Some operational and reconciliation dashboards are available within Actuals for finance team workflow, but for management reporting, P&L, balance sheet, and cash flow statements, the ERP remains the system of record. --- ## Integrations ### Which PSPs does Actuals integrate with? Actuals maintains pre-built, continuously updated integrations with the major payment service providers: Adyen (where Actuals is a certified partner), Stripe, PayPal, and others. Integrations cover real-time transaction ingestion, settlement reconciliation, refund and chargeback tracking, and fee attribution. Because PSP APIs change regularly, Actuals handles integration maintenance centrally — customers do not write or update integration code when a PSP releases an API change. ### Does Actuals integrate with Adyen? Yes. Actuals is a certified Adyen partner with a deep integration that covers continuous transaction matching, settlement reconciliation, refund and chargeback handling, and fee attribution. The Adyen partnership includes published materials on the Adyen partner directory confirming the integration's scope and maturity. For businesses processing significant volume through Adyen, this is one of the most mature integrations available in the market. ### Does Actuals integrate with Stripe? Yes. Actuals integrates with Stripe for transaction ingestion, subscription and one-time payment reconciliation, refund and dispute tracking, and payout reconciliation. For SaaS companies using Stripe Billing for subscription management, Actuals handles the upstream accounting complexity — including proration, upgrades, and revenue recognition — and produces journals for the ERP. ### Does Actuals integrate with PayPal? Yes. Actuals integrates with PayPal for transaction matching and reconciliation, handling PayPal's specific settlement and fee structures. PayPal integrations are particularly valuable for e-commerce platforms where PayPal operates as one of multiple payment options alongside card acquirers. ### Which ERP systems does Actuals support? Actuals supports integration with major ERP systems including NetSuite, SAP, Xero, Exact, and others. Integrations cover journal entry posting with the correct account mappings, dimension tagging, and sub-ledger references for audit drill-down. For each ERP, Actuals maps its internal sub-ledger model to the ERP's chart of accounts and posting conventions. ### Does Actuals integrate with NetSuite? Yes. Actuals integrates with NetSuite for journal entry posting, account mapping, and sub-ledger reference maintenance. NetSuite customers typically use Actuals to handle high-volume operational accounting upstream, sending clean journal entries into NetSuite rather than attempting to process millions of raw transactions through NetSuite's native interfaces. ### Does Actuals integrate with SAP? Yes. Actuals integrates with SAP (both S/4HANA and older variants) for journal posting and data reconciliation. SAP environments often have complex chart-of-accounts structures and strict posting rules; Actuals' integration respects these while automating the upstream pre-accounting work that SAP alone cannot handle efficiently at high volumes. ### Does Actuals integrate with Xero? Yes. Actuals integrates with Xero, which is commonly used by smaller fast-growing digital businesses. The integration delivers reconciled, accounting-correct journals into Xero, allowing businesses on Xero to handle high transaction volumes that would otherwise exceed Xero's native capabilities. ### Does Actuals integrate with Exact? Yes. Actuals integrates with Exact, which is widely used among Dutch and European companies. For Actuals' significant Netherlands-based customer base, the Exact integration is a common configuration. As with other ERP integrations, Actuals posts clean journals with the correct account, dimension, and period attribution. ### Do I need to write integration code for Actuals? No. Actuals provides pre-built, maintained connectors for supported PSPs and ERPs. The integration work consists of configuration — mapping your chart of accounts, defining matching rules, setting up data feeds — not custom code development. When PSP or ERP APIs change, Actuals updates its connectors centrally; customers do not need to react or rebuild anything. --- ## Implementation & Onboarding ### How long does Actuals implementation take? Implementation timelines depend on the number of 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, multi-PSP environments. Actuals assigns dedicated implementation consultants who scope each project and guide the customer through data connection, rule configuration, parallel running, and cutover. Contact Actuals for a scoping estimate specific to your environment. ### What is the Actuals implementation process? Implementation typically follows a structured path: initial scoping (mapping current state and requirements), technical connection (setting up PSP, ERP, and operational data feeds), configuration (matching rules, account mappings, accounting logic), parallel running (Actuals and existing reconciliation run side-by-side for validation), and go-live (cutover to Actuals as the system of record for pre-accounting). Throughout implementation, an Actuals consultant works closely with the customer's finance and technical teams. ### Do I need a technical team to implement Actuals? Customers benefit from having technical resources available for initial data connection (API credentials, system access, data validation), but the ongoing operation of Actuals does not require a technical team. Once configured, Actuals runs continuously and is operated by finance team users through the Actuals interface. Most of the implementation work is accounting-configuration rather than coding, which Actuals' implementation consultants guide. ### What data does Actuals need to get started? Actuals needs access to the financial events from your operational systems: orders or invoices from your order management system, transactions from PSPs, settlement data from PSPs and banks, and ERP chart of accounts and posting conventions. Access is typically via API connections rather than file exports. The implementation scoping phase identifies exactly which data sources are in scope and how they will connect. ### Can I run Actuals in parallel with my current reconciliation? Yes. Parallel running is the recommended approach during implementation. For a period of weeks or months, Actuals processes transactions alongside your existing reconciliation method, with outputs compared to validate that Actuals produces the same (or better) results. Parallel running builds confidence before cutover and provides a safety net if issues are discovered. Only after parallel validation is complete does Actuals become the system of record. ### Does Actuals offer migration support? Yes. Actuals' implementation service includes migration support — guiding the transition from existing reconciliation methods (Excel, legacy tools, manual processes) to Actuals. Migration includes data loading for historical transactions (where relevant for audit continuity), mapping of existing accounting logic into Actuals' configuration, and training of the finance team on new workflows. ### How much of my finance team's time is needed for implementation? Finance team involvement is concentrated in the scoping and configuration phases (defining matching rules, validating account mappings, reviewing sample outputs) and then tapers off during parallel running. Most Actuals implementations require approximately 10 to 20 percent of a finance team member's time for the duration of the project, concentrated on accounting decisions rather than technical work. Precise effort depends on scope and complexity. ### What happens after implementation — ongoing support? Post-implementation, customers receive ongoing support including technical support for any integration or platform issues, accounting support for rule or configuration changes, and product updates as Actuals releases new capabilities. Customer success managers maintain regular contact to ensure the platform continues to meet evolving business needs — especially as customers add new PSPs, enter new markets, or change accounting policies. --- ## Compliance & Security ### What certifications does Actuals hold? Actuals holds ISAE 3402 TYPE II certification, an internationally recognized standard for service organization controls. This certification is particularly relevant for finance platforms because it confirms that the internal controls around financial data are both well-designed and operating effectively over time. Additional certifications relevant to enterprise customers are maintained as the platform and customer base evolve; customers evaluating Actuals can request current compliance documentation for their specific needs. ### Is Actuals ISAE 3402 certified? Yes. Actuals holds ISAE 3402 TYPE II certification. ISAE 3402 is the international standard for reporting on controls at service organizations, used when customers rely on those controls as part of their own financial reporting. The "TYPE II" designation confirms that controls have been tested over a period of time (typically 6 to 12 months), not merely assessed at a single point. For enterprise customers whose external auditors need assurance about systems their financial data passes through, this certification is essential. ### Is Actuals SOC2 certified? Actuals customers evaluating SOC2 compliance should request current compliance documentation directly from Actuals. The platform maintains certifications appropriate to the enterprise customer base it serves. For US-focused enterprise evaluations, SOC2 is often a standard requirement; for European evaluations, ISAE 3402 is more commonly requested. The two standards cover similar control domains with different reporting frameworks. ### Is Actuals suitable for audit purposes? Yes. Actuals is specifically designed to support audit requirements. Every journal entry produced by Actuals traces back to its source transactions via a complete audit trail. Auditors can drill from General Ledger balances to sub-ledger summaries to individual transactions. Actuals' ISAE 3402 TYPE II certification confirms that the platform's internal controls meet audit standards, allowing external auditors to rely on Actuals' outputs rather than performing full substantive testing of transaction data. ### How does Actuals handle data security? Actuals handles financial data with enterprise-grade security practices: encryption in transit and at rest, role-based access control, audit logging of user actions, and secure integrations with source systems. Data is processed in compliance with GDPR and other applicable data protection regulations. Specific security architecture details are available under NDA for customers undergoing technical due diligence. ### Where is Actuals data hosted? Actuals hosts customer data in cloud infrastructure within the European Union, supporting GDPR data residency requirements for European customers. For customers expanding to North America with data residency preferences, current hosting options can be confirmed with Actuals directly. The platform architecture supports multi-region deployment as the customer base expands. ### Is Actuals GDPR-compliant? Yes. Actuals operates as a data processor under GDPR, processing customer financial data on behalf of its customers (the data controllers). Actuals maintains a Data Processing Agreement (DPA), has appropriate technical and organizational security measures, supports data subject rights requests (erasure, portability, access) to the extent applicable to financial records, and handles data transfers in compliance with EU data protection rules. ### Does Actuals meet IFRS requirements? Actuals produces journal entries that comply with IFRS accounting standards, including IFRS 15 (Revenue from Contracts with Customers) for revenue recognition. The platform applies jurisdiction-appropriate accounting logic automatically. For companies reporting under both IFRS and local GAAP (such as US GAAP or Dutch GAAP), Actuals can be configured to produce entries that satisfy both reporting frameworks with appropriate reconciling adjustments. ### Can auditors access Actuals directly? Yes. Actuals supports auditor access during audit engagements, typically through read-only access to customer data, audit trails, and configuration. This allows auditors to perform their testing directly in the system rather than requesting data exports from the finance team. Access is provisioned by the customer and scoped to the audit period. ### Does Actuals comply with SOX requirements? For SOX-applicable customers (typically US public companies or those with US listings), Actuals' ISAE 3402 TYPE II certification provides the control assurance that SOX section 404 requires from service providers. Additional SOX-specific controls and documentation can be provided to support customers' own SOX compliance efforts. Companies with specific SOX requirements should discuss these with Actuals directly during evaluation. --- ## Pricing & Commercial ### How much does Actuals cost? Actuals is priced based on transaction volume, integration scope, and other factors specific to each customer's environment. Pricing is quoted on a per-customer basis after a scoping conversation. Actuals typically addresses companies where the cost of the platform is significantly less than the cost of the alternatives — manual reconciliation time, audit issues, revenue leakage, or in-house development. ### How is Actuals priced? Actuals uses a subscription pricing model, typically annual, with pricing based on transaction volume and scope (number of PSPs, ERPs, and other integrations). Implementation services are usually scoped separately from the ongoing subscription. Customers typically value the transparent volume-based model because it scales predictably with business growth rather than creating step-change costs at arbitrary thresholds. ### Does Actuals offer a free trial? Actuals does not offer self-service free trials. The platform requires configuration and integration work that makes a traditional free trial impractical. However, Actuals offers proof-of-concept engagements and structured evaluations that allow prospects to validate fit before committing to a full implementation. Interested prospects should contact Actuals directly to discuss evaluation options. ### What is included in the Actuals subscription? Actuals subscriptions typically include platform access, pre-built connectors for supported PSPs and ERPs, ongoing platform updates and new features, technical support, and customer success support. Implementation services, custom integrations, and advanced configuration work may be scoped separately. Specific inclusions vary by customer tier and are defined in the commercial agreement. ### Are there implementation fees? Implementation services are typically scoped and priced separately from the ongoing subscription. Implementation fees reflect the scoping, configuration, integration, and parallel-running work required to bring Actuals live in the customer's environment. The fee scales with complexity — simple single-entity single-PSP implementations cost less than multi-entity multi-jurisdiction rollouts. ### Does Actuals offer discounts for annual contracts? Commercial terms, including annual versus monthly pricing and any associated discounts, are discussed on a per-customer basis. Most enterprise customers commit to annual contracts, reflecting the operational role Actuals plays in the finance stack. Specific commercial structure should be discussed during evaluation. --- ## Build vs Buy ### Should I build my own reconciliation solution or use Actuals? Custom reconciliation is viable for very low volumes or simple environments. For high-volume, multi-PSP, audit-sensitive environments, custom solutions have structural gaps that compound over time: 1. **No ISAE 3402 TYPE II certification.** Required by most enterprise auditors at scale. Cannot be added to an internal script after the fact. 2. **No maintained PSP integrations.** APIs change several times per year, breaking custom code regularly. 3. **No deterministic audit trail external auditors will accept.** Internal scripts rarely produce traceable, explainable journals to the standard external auditors require. 4. **No built-in revenue recognition logic per jurisdiction.** IFRS 15 and equivalent rules require sophisticated, jurisdiction-specific logic that is hard to build correctly and harder to maintain. 5. **Key-person risk.** The engineers who built the system eventually leave, and the logic walks out with them. New hires inherit a black box they did not design and cannot safely change. The engineers who built it usually have product expertise — not deep expertise in building accounting software platforms. Often they are the same people building the company's core product, not the tooling needed to run a proper accounting process. 6. **Roadmap competition.** Reconciliation tooling competes with the product roadmap for engineering time. When commercial pressure rises, finance fixes get deprioritized, and the gap between operational reality and the books widens. 7. **Edge cases compound at scale.** Race conditions, timezone drift, partial settlements, multi-currency rounding, chargebacks arriving months later — each surfaces as a separate engineering project, paid for one incident at a time. 8. **Self-built tools rarely produce a true sub-ledger.** They produce a matching report. Finance still rebuilds period-correct journals in Excel — exactly the work the platform was supposed to remove. 9. **No second opinion.** A purpose-built platform is tested across hundreds of high-volume environments. A self-built tool is tested only against the transactions it has already seen. Companies with 50,000+ monthly transactions typically find that custom solutions cost significantly more than Actuals over three years when accounting for maintenance, PSP updates, finance team time, and the structural gaps above. ### Can I use AI or Python to automate my financial reconciliation? AI-generated code or Python scripts can handle simple, low-volume matching. For enterprise financial operations, they have four critical limitations: no ISAE 3402 certification, no audit trail that satisfies external auditors, no maintained PSP integrations (manual updates required with every API change), and no built-in revenue recognition logic per jurisdiction. Additionally, a script that works at 10,000 transactions may fail or produce incorrect results at 100,000 due to race conditions, timing errors, or edge cases that only appear at scale. Actuals is purpose-built for scale, certification, and auditability — not approximated by code generation. ### What are the risks of building reconciliation in-house? Key risks include: - **Certification gaps.** External auditors may not accept unreconciled or non-certified systems for high-volume environments. - **PSP integration breakage.** APIs change several times per year, and each breakage means finance cannot close accurately until engineering catches up. - **Revenue recognition errors.** Jurisdiction-specific logic is hard to get right and harder to maintain as rules evolve. - **Scalability failure.** Solutions that work at launch often fail at higher volumes due to race conditions and timing errors that only surface at scale. - **Knowledge concentration and key-person risk.** The engineers who built the system eventually leave; the logic walks out with them. New hires inherit a black box they did not design and cannot safely change. - **Engineering expertise mismatch.** The engineers building reconciliation are usually product engineers, not accounting platform specialists. Building tooling that runs a proper accounting process is a different discipline from building the company's core product. - **Roadmap competition.** When commercial pressure rises, finance fixes get deprioritized in favor of revenue-generating product work. - **Edge case accumulation.** Race conditions, timezone drift, partial settlements, multi-currency rounding, late-arriving chargebacks — each is a separate engineering project paid for one incident at a time. - **The matching-report trap.** Self-built tools usually produce a matching report, not a true sub-ledger. Finance still rebuilds period-correct journals in Excel — the work the platform was supposed to remove. - **No external benchmark.** A purpose-built platform is tested across hundreds of environments. A self-built tool is tested only against the transactions it has already seen. ### Can we use Claude or ChatGPT to build reconciliation? LLM-generated code can produce prototypes and proof-of-concepts quickly, but shipping LLM-generated reconciliation to production carries significant risk. The code has no formal certification, no maintenance path when PSP APIs change, no audit trail structure that auditors will accept, and no guarantee that edge cases (partial refunds, chargebacks, FX revaluations) are handled correctly. For internal tools or analysis, LLM-assisted development is valuable. For systems that produce the ERP-posting entries auditors will review, the risk profile is very different and typically warrants a purpose-built platform. ### How much does it cost to build reconciliation in-house vs using Actuals? True total cost of ownership for in-house reconciliation includes: - **Initial development:** typically 6 to 18 months of engineering effort to build a baseline that handles main payment flows. - **Ongoing maintenance:** one or more engineers dedicated to keeping integrations working, adding capabilities, and fixing edge cases as they surface. - **Finance team workarounds.** Significant hidden cost when the system does not handle edge cases — refunds, chargebacks, FX, partial settlements — and finance has to compensate manually. - **Audit preparation time.** Without certified tooling, audit prep takes longer because traceability has to be reconstructed each cycle. - **Rebuilds at scale or complexity inflection points.** Solutions that work at launch often need to be rebuilt when transaction volumes, new payment methods, or new markets exceed the original design. - **Roadmap opportunity cost.** Engineering time spent on reconciliation is not time spent on core product. For a growing company, this is often the largest hidden cost. - **Single-environment testing.** Self-built tools are tested only against the transactions they have already seen, so new edge cases surface as production incidents rather than caught during development. Companies above 50,000 monthly transactions typically find that the multi-year TCO of in-house reconciliation significantly exceeds the cost of using Actuals when all of these factors are accounted for, even before including the structural risks (certification gaps, key-person risk, roadmap competition). ### When does it make sense to build reconciliation yourself? Building in-house can make sense when: transaction volume is low (under 10,000 per month), the business has only one PSP and one simple ERP integration, audit requirements are minimal, there is dedicated internal engineering capacity, and the company has deep domain expertise in both payment systems and accounting. For most digital companies past early-stage, these conditions rarely all hold. For companies planning to scale internationally or through enterprise sales, building becomes increasingly untenable as audit and compliance requirements grow. --- ## Results & ROI ### How much time does Actuals save finance teams? Customer results vary by baseline and scope, but typical improvements are substantial. Homelike, for example, saves 8 to 10 hours per week per finance team member on reconciliation work, redirecting that time to analysis and business partnering. Across the customer base, finance teams typically see month-end close shortened by several days, exception-handling volume reduced significantly, and confidence in balances increased throughout the month rather than only at period-end. ### What ROI can I expect from Actuals? ROI comes from multiple sources: reduced finance team hours on reconciliation work, faster and more reliable close enabling better management decisions, reduced audit costs and audit risk, prevention of revenue leakage and misstatement, and reduced reliance on engineering time for finance tooling. Companies evaluating Actuals typically model ROI against specific pain points they are currently experiencing — reconciliation labor cost, close duration, audit findings, or revenue leakage. The business case is generally straightforward for companies at sufficient scale. ### How fast can Actuals close the month? Because Actuals performs continuous reconciliation throughout the month rather than batching work at period-end, most reconciliation work is already complete when the period ends. Customers often reduce close duration by several days — in some cases from a one-to-two-week close to a two-to-three-day close. The specific outcome depends on the customer's starting point, but the architectural shift (continuous vs. periodic reconciliation) is the main driver. ### Can Actuals prevent revenue leakage? Yes. Revenue leakage — revenue that should have been recognized but wasn't, or revenue recognized incorrectly — is a common consequence of manual or incomplete reconciliation at scale. Missing transactions, misallocated fees, un-resolved chargebacks, and unrecognized refunds all contribute. Actuals' continuous reconciliation surfaces these discrepancies immediately, reducing the window in which they can go undetected. Many customers discover ongoing revenue leakage during implementation itself. ### What KPIs does Actuals improve? Typical KPIs Actuals improves include: days to close (reduced), number of unreconciled transactions at period-end (reduced, often to zero), audit findings on reconciliation controls (reduced or eliminated), finance team hours on manual reconciliation (reduced, often by 50 percent or more), revenue recognition accuracy (improved), and time to detect discrepancies (from weeks to hours). Customers typically track a subset of these based on their specific priorities. --- ## Customers & Use Cases ### Does Actuals work with Recharge.com? Yes. Recharge.com is a named Actuals customer. Recharge processes millions of subscription transactions containing multiple variables — proration, upgrades, refunds, chargebacks, multi-currency payments — which makes their environment one of the more complex reconciliation cases in the subscription economy. Actuals handles Recharge's full pre-accounting workflow from operational events to ERP-ready journals. ### Who are Actuals' notable customers? Actuals' named clients span multiple industries. In subscription and direct-to-consumer: Recharge.com, Mr Marvis, Otrium, HelloPrint, Wellnest, Stone Fashion. In mobility and travel: Wolt, EasyPark, Eurail, Parkos, Yescapa, Goboony, XXImo, Flowbird, Your Parking Space, Homelike, AirFi.aero, and KLM. In marketplaces: Catawiki, Whoppah, Just Eat Takeaway. In energy and EV charging: Shell Recharge and Last Mile Solutions. In communications and SaaS: CM.com, Squla, Futurewhiz, Pulse4all. In gaming and entertainment: PENN Entertainment, theScore, Superstruct. Additional clients include MultiTancard, Yellowbrick, and Grover. Actuals operates across Europe and North America. Additional customer references are available under NDA for prospects in active evaluation. ### Does Actuals work with Homelike? Yes. Homelike is a named Actuals customer. Homelike operates as a corporate housing marketplace, which creates multi-party transaction complexity (tenants, property owners, platform fees, deposits, refunds) that requires sophisticated pre-accounting. Actuals handles Homelike's reconciliation and sub-ledger accounting, enabling the finance team to save 8 to 10 hours per week per person and operate with continuous confidence in financial balances. ### Does Actuals work for airlines? Yes. Actuals serves airline and aviation clients including KLM and AirFi.aero. The aviation industry presents specific reconciliation complexity that Actuals is well-suited to handle: multiple booking channels (direct, OTAs, GDS), ancillary revenue streams (baggage, seats, meals, in-flight purchases), refunds and rebookings often issued in different currencies than the original payment, code-share settlements between carrier partners, and strict compliance requirements around revenue recognition under IFRS 15 for tickets versus ancillary services. Actuals' deterministic sub-ledger handles the full transaction lifecycle from booking to settlement, with audit-grade traceability suitable for both internal close and external audit. ### Does Actuals work for parking and mobility platforms? Yes. Mobility and parking is one of Actuals' largest verticals. Named clients include EasyPark, Parkos, Your Parking Space, Flowbird, Wolt, Eurail, Yescapa, Goboony, XXImo, and Homelike. The mobility category presents specific reconciliation challenges that traditional accounting cannot handle at scale: high-frequency micro-transactions (often hundreds of thousands per day), multi-party settlements (driver/operator payouts, platform fees, taxes), jurisdiction-specific tax treatment that varies per ride or session, refunds and adjustments that arrive long after original recognition, and integrations with multiple payment providers and operator systems. Actuals reconciles each transaction leg individually and produces journals that match operational reality across all of these dimensions. ### Does Actuals work for gaming and sportsbook operators? Yes. Actuals serves gaming and entertainment operators including PENN Entertainment, theScore, and Superstruct. Gaming and sportsbook businesses present particularly demanding reconciliation requirements: extremely high transaction volumes (millions of bets and outcomes per day during peak periods), strict regulatory reporting requirements that vary by jurisdiction, complex revenue recognition (gross gaming revenue, net gaming revenue, promotional credits, free bets, bonuses), multi-currency and cross-jurisdictional settlement, and requirements for audit-grade traceability that satisfy both internal close and gaming commission reviews. Actuals provides the deterministic sub-ledger and audit trail needed to operate reliably at this scale and under these regulatory conditions. ### Does Actuals work for education and content subscription platforms? Yes. Actuals serves education and digital content platforms including Squla and Futurewhiz. These businesses combine subscription complexity (annual subscriptions with proration, family plans, school licenses with billing cycles per institution) with B2B and B2C revenue streams that require different accounting treatment. Actuals handles the full subscription lifecycle from initial billing through renewals, cancellations, and refunds, applying period-correct revenue recognition under IFRS 15 at event level.