Exact Online is the dominant bookkeeping platform among Dutch SMBs. If your general ledger is in Exact Online, your receipt workflow needs to end there: structured journal entries with matched source documents, not image files that an accountant processes at month-end.
This article covers what the workflow from receipt capture to Exact Online ledger entry should look like, where most Dutch SMBs have gaps today, and what to verify when evaluating a receipt management tool.
The receipt-to-ledger workflow
A complete receipt management workflow for an Exact Online user has four steps.
- Capture — a cardholder or finance team member submits a receipt at or near the point of purchase. Structured metadata — date, amount, currency, VAT amount, supplier, cost-centre — is recorded at this step, not inferred later from an image.
- Match — the receipt is matched to the corresponding card transaction or payment record. Where a card feed is available, this match can be automated by comparing amounts, dates, and merchant identifiers. Manual review handles exceptions.
- Code — the matched entry is assigned an Exact Online account code, VAT code, and cost-centre division based on cost-centre defaults or a finance review step.
- Post — the coded entry is pushed to the relevant Exact Online division as a journal entry, with the receipt image or structured record attached as the source document.
Each step depends on structured data from the previous one. If capture produces a raw image without extracted metadata, the match step becomes a manual search. If the match step produces no cost-centre assignment, the code step requires a finance review for every entry. If coding produces no structured output, the post step becomes a manual journal entry. The workflow is only as fast as its weakest link.
Where Dutch SMBs typically have gaps
Four gaps appear consistently in SMB receipt workflows that connect to Exact Online.
Manual re-entry at the export step
Most Dutch SMBs capture receipts in one tool and enter the resulting data into Exact Online by hand — or send an image file to an accountant who does it. This breaks the chain between the source document and the ledger entry. When the Belastingdienst queries a specific transaction, the match between receipt and journal entry depends on whether someone keyed the data in correctly, not on a structured audit trail.
Non-EU processing in the capture pipeline
Many expense tools use OCR and parsing services to extract data from receipt images. If those services are operated by non-EU providers without Standard Contractual Clauses, the processing chain includes a transfer to a third country without an adequate basis. Most Dutch SMBs have not mapped the sub-processor chain on their receipt tools, let alone verified the transfer basis for each step.
No structured VAT field at capture
Exact Online journal entries require a VAT amount and a VAT code. Receipt capture tools that store receipts as images — without structured metadata — require someone to read the VAT line and enter it into Exact Online separately. For high-volume expense environments, this is the step that causes the most errors and the most delay before month-end close.
No cost-centre mapping at point of submission
Exact Online organises transactions by division and cost centre. Receipt management tools that do not capture cost-centre at submission create a reconciliation step where finance must manually assign divisions before entries can be posted. Cardholder-level cost-centre defaults eliminate most of this work, but they require the receipt tool to carry that mapping.
GDPR and the Exact Online integration chain
The path from receipt capture to Exact Online journal entry involves multiple processors. Each one must operate under an adequate GDPR transfer basis. GDPR Art. 28 requires that your receipt management vendor names all sub-processors in a signed DPA, and that sub-processors outside the EU or EEA operate under Standard Contractual Clauses or an adequacy decision.
In practice, the compliance chain for a typical Dutch SMB receipt workflow looks like this:
- Receipt submitted via a mobile app or web upload — data enters the receipt management platform
- Image sent to an OCR or parsing service — this is typically the first sub-processor, and often a non-EU provider
- Structured metadata stored in the platform database — must be EU-hosted under a signed DPA for Dutch companies managing EU-resident employee data
- Coded entry pushed to Exact Online via API — Exact Online is an EU-incorporated entity; this step is generally inside the EU
The gap is typically at step 2. Most Dutch SMBs do not know which OCR provider their receipt tool uses, where that provider is incorporated, or whether SCCs are in place. The DPA review step before onboarding should surface this — but many SMBs skip the DPA review entirely.
What to verify before choosing a receipt tool
Six questions to ask any receipt management vendor before connecting their tool to your Exact Online environment.
- What fields does the tool capture at receipt submission — date, amount, currency, VAT amount, VAT code, supplier, cost-centre?
- Does the tool write structured metadata to a database, or does it store the raw image without extraction?
- What is the transfer mechanism for any non-EU sub-processors used in OCR or data extraction?
- What is the format of the Exact Online export — a structured API call, a CSV, or an image file?
- Does the integration handle division-level posting, or does it push to a single default division?
- Is the DPA in place before upload begins, and does it name all sub-processors in the parsing pipeline?
How Rexa approaches the Exact Online integration
Rexa is designed to integrate with Exact Online. The current prototype includes an onboarding step for connecting an Exact Online account; the full integration — OAuth token exchange, division discovery, and structured journal entry creation against your Exact Online general ledger — is on the product roadmap.
The design goal is to handle the four workflow steps above — capture, match, code, post — with structured metadata preserved through each transition, and EU-hosted processing throughout the chain. Rexa stores account data in the EU under Standard Contractual Clauses for US-headquartered sub-processors. The sub-processor list is available on request via the DPA.
The integration is not live today. If your evaluation timeline requires a live Exact Online connection, Rexa is not yet the right fit. If you are evaluating tooling for a workflow you are building now and want EU-first receipt management with a structured Exact Online integration on the roadmap, the waitlist is the right next step.
Related
Rexa is in pre-launch. If you are evaluating GDPR-compliant receipt management with an Exact Online integration on the roadmap, join the waitlist for early access.
Join the Rexa waitlist