German Document Extraction PricingKMU Needs vs Enterprise Bundles

Candis starts at €199 a month. Spendesk at €99. Yokoy doesn't publish a price — you book a demo. These are the numbers a German Mittelstand finance manager runs into when they search for "Dokumentenextraktion Kosten" (document extraction costs). After 30 minutes of research, the conclusion writes itself: document extraction costs €200 a month minimum — double what the manual work it replaces is worth at 80 invoices. But that conclusion is only true if you accept the industry's assumption that extraction must arrive inside a procurement suite. It doesn't.

German KMU document extraction pricing comparison with business documents, invoices, and a laptop showing a cost analysis spreadsheet on a desk

Key Takeaways

  1. €199 a month is what AI document extraction costs in the German market — not because extraction is expensive, but because every vendor bundles it into an AP automation suite.
  2. At 80 documents a month, a €199 suite costs nearly as much as the manual labor it replaces — a 35-employee KMU is buying approval workflows and corporate card management for a procurement department that doesn't exist.
  3. ImageToTable.ai uses the same visual-language AI as the suites to extract the same fields at €17.50 a month — at 200 documents monthly, unbundling extraction from the suite saves €2,160 a year without losing a byte of accuracy.

The Real Document Mix in a German KMU

Most discussions about German document automation start with invoices — and stop there. The e-invoicing mandate under the Wachstumschancengesetz, the XRechnung standard, and the phased rollout to 2028 dominate the conversation for good reason: every German business must be able to receive structured e-invoices (XRechnung or ZUGFeRD 2.x formats compliant with EN 16931) since January 2025. But an invoice is one document type. A KMU (Kleines und mittleres Unternehmen, the German term for SME) processes a much messier mix.

A 45-person engineering firm in Baden-Württemberg with 80 active suppliers doesn't just receive Rechnungen. Their daily document flow includes Lieferscheine (delivery notes) from metal suppliers, Bestellungen (purchase orders) that need to be matched against incoming invoices, Kontoauszüge (bank statements) from Commerzbank and Sparkasse, and Verträge (contracts) from three equipment leasing companies. A 25-person food distributor in North Rhine-Westphalia handles invoices from Metro and Transgourmet alongside handwritten Lieferscheine from small regional producers, scanned Empfangsbestätigungen (goods receipt confirmations), and monthly Kontoauszüge from Volksbank.

Only about half the documents in a typical KMU workflow are invoices. The rest are documents that will never appear in a Peppol network, will never carry embedded XML, and won't be covered by any e-invoicing mandate. They arrive as PDFs, as scans, as photos taken with a phone, and occasionally as faxes. Each one needs the same thing: someone to read it, extract the key data points, and type them into a system — DATEV, lexoffice (Lexware Office), sevDesk, or a spreadsheet that feeds all three.

This is the extraction problem, and it's bigger than invoice processing. For a broader look at how this works across document types, AI-powered data extraction software reads by understanding what fields mean, not by locating coordinates on a template — which is why the same tool can handle a Lieferschein, a Rechnung, and a Kontoauszug without reconfiguration.

Document TypeTypical Monthly Volume (25-80 Employee KMU)Key Fields ExtractedCovered by E-Invoice Mandate?
Incoming Invoices (Eingangsrechnungen)60–180Rechnungsnummer (invoice number), Nettobetrag (net amount), USt-IdNr (VAT ID), Leistungszeitraum (service period)Partially (from 2027-2028)
Delivery Notes (Lieferscheine)40–120Lieferscheinnummer, Artikelnummern (item numbers), Mengen (quantities), Lieferdatum (delivery date)No
Purchase Orders (Bestellungen)30–100Bestellnummer (PO number), Lieferant (supplier), Positionspreise (line-item prices), Liefertermin (delivery deadline)No
Bank Statements (Kontoauszüge)1–5Buchungsdatum (posting date), Verwendungszweck (reference), Betrag (amount), Empfänger (recipient)No
Contracts / Agreements (Verträge)5–20Vertragspartner (contracting party), Laufzeit (term), Kündigungsfrist (notice period), monatliche Rate (monthly rate)No

The volume range matters. An IfM Bonn definition pegs the German Mittelstand at up to 499 employees and €50 million in annual revenue, but the companies most affected by this pricing mismatch are the 2.6 million KMU with 5 to 150 employees — too large to handle documents manually, too small to amortize a €200/month AP automation platform. At 80 to 300 documents a month, the labor cost of manual entry sits somewhere between €250 and €900, depending on document complexity and employee hourly cost (German minimum wage in 2026 is €13.90, and fully loaded Buchhalter costs run €25–35 per hour). A tool that costs €199 doesn't eliminate the labor cost — it replaces half of it with a subscription and leaves the harder half on someone's desk.

The German Software Stack, Layer by Layer

The tool landscape in Germany isn't one market — it's four distinct price layers, and most KMU operate inside the first two while being marketed to from the third.

LayerPrice Range (Monthly)What It DoesWho It's ForExtraction Included?
1. Accounting Software€7–50Bookkeeping, VAT filing (Umsatzsteuervoranmeldung) via ELSTER, DATEV export, bank feed, basic receipt scanningFreelancers, micro-businesses, small GmbHBasic OCR for receipts; invoice data extraction is partial and layout-dependent
2. Document Collection€15–79Centralized invoice inbox, portal auto-fetch, some extraction, DATEV-format exportSmall businesses with multiple supplier sourcesModerate — works well for standard-format invoices, degrades on unusual layouts
3. AP Automation Suite€99–500+Approval workflows, PO matching, multi-entity support, corporate card management, full AP automationMid-size companies (50–500 employees) with dedicated finance teamsExcellent AI extraction — but only accessible inside the full suite
4. Enterprise IDP$500–$12,500+Custom document classification, high-volume processing (1M+ pages/year), deep ERP integration, on-premise deploymentEnterprise (1,000+ employees, dedicated IT)Industry-leading — with 3-year contracts and 6-month implementations

Layer 1 — Accounting Software. Lexware Office (formerly lexoffice) starts at €7.90/month for Plan S with VAT filing included; Plan L at €21.90 adds the Einnahmen-Überschuss-Rechnung (EÜR, the simplified income-expense statement for freelancers and sole traders). sevDesk starts at €12.90/month (annual billing) for the accounting tier with DATEV export. These tools handle basic receipt scanning well, but their built-in OCR was designed for single receipts and simple invoices — not for parsing a 6-page Rechnung from an industrial supplier with 40 line items and mixed VAT rates. The extraction works when the document matches the expected layout, and produces errors when it doesn't. For KMU receiving invoices from 50+ suppliers, each with their own layout, that means roughly 20–30% of invoices still need manual correction after scanning.

Layer 2 — Document Collection. GetMyInvoices is the standout here: €15/month (Basic, 50 docs), €35/month (Professional, 200 docs), €65/month (Business, 500 docs). It auto-fetches from 12,000+ portals and exports to DATEV format. But as EU E-Invoicing Hub notes in their 2026 review, it handles the document layer, not the accounting layer — you still need DATEV or lexoffice for GoBD-compliant bookkeeping. Its extraction quality is solid for standard-format invoices but varies significantly on documents that don't follow Deutsche Rechnungslegung conventions.

Layer 3 — AP Automation Suite. This is where the price jumps. Candis starts at €199/month and bundles AI extraction with approval workflows, PO matching, contract management, and expense reimbursement. Spendesk starts at €99/month with corporate cards, expense management, and AP automation in one platform. Yokoy offers invoice and expense modules as separate purchases with custom pricing. These are excellent products — if you have a finance team of three to five people processing 500+ invoices a month across multiple entities. For a 30-person KMU with one Buchhalter and 120 invoices a month, you're paying for infrastructure designed for a department you don't have.

Layer 4 — Enterprise IDP. ABBYY FlexiCapture, Kofax (now Tungsten Automation), and Rossum occupy a pricing tier where the annual contract starts at $15,000–$50,000 and routinely exceeds $100,000 for full deployments. As reported by Vendr's buyer data, ABBYY FlexiCapture for mid-sized deployments (500,000–2M pages annually) typically lands at $30,000–$80,000 per year. Implementation adds another $15,000–$200,000 for professional services. These tools are built for organizations processing hundreds of thousands of pages annually with dedicated IT teams — not for a German KMU that needs to extract data from 2,000 pages a month and feed them into DATEV.

The extraction layer is the only part of this stack that every KMU actually needs automated. But the tools that do extraction well at scale are either buried inside Layer 3 suites or locked behind Layer 4 enterprise contracts. The German market doesn't have a widely recognized standalone extraction layer — which is why many KMU conclude the problem is unsolvable at their budget.

What Enterprise Vendors Bundle That KMU Don't Need

The pricing gap between a €79/month document collection tool and a €199/month AP suite isn't about better extraction. It's about everything else in the box.

Candis at €199/month includes: custom approval workflows requiring multiple sign-offs, purchase requisition capture with budget controls, automated three-way PO matching, contract management with deadline reminders, travel expense reimbursement with per-diem calculations, and corporate credit card integration with real-time transaction syncing. These features solve real problems — for a 150-employee company with procurement spending across five departments and a finance team that needs an audit trail for every transaction. For a 35-employee KMU where the Geschäftsführer (managing director) approves invoices by walking over to the Buchhalter's desk, approval workflow software is overhead dressed as automation.

Spendesk at €99/month+ adds: physical and virtual corporate cards with spend controls, multi-currency international payments (30+ currencies via Wise Platform), and a procurement module that routes purchase requests through budget owners. These features assume a distributed spending environment — employees across departments making purchases, managers approving them, finance reconciling everything at month-end. A manufacturing KMU with 40 employees where the Einkauf (purchasing) is handled by one person doesn't have this problem architecture.

Yokoy, acquired by TravelPerk with a $200 million funding round in 2025, further compounds the bundle: expense management with automated per-diem calculations, corporate card matching, invoice capture, and supplier payment processing — all integrated into a single spend management platform. It's an elegant solution for companies with 200+ employees and multi-country operations. For a German KMU that needs to extract 100 Lieferscheine and 80 Rechnungen a month into DATEV, it's buying a cruise ship to cross a river.

The bundle problem isn't unique to Germany. For a broader analysis of how this pricing architecture affects buyers across all markets, see the enterprise vs SMB divide in document extraction pricing and the full breakdown of pricing tiers from budget to enterprise.

The Modular Alternative: Extraction as a Standalone Layer

There is a middle path that the German software market didn't build. It works by separating the extraction step from the accounting suite that receives the data — the same architectural insight that GetMyInvoices applied to the document collection layer, taken one step deeper into the data extraction layer itself.

The logic is straightforward: an AI reads each document — regardless of whether it's a Rechnung, a Lieferschein, a Kontoauszug, or a Vertrag — identifies the data points you specify by semantic meaning rather than template position, and outputs structured data (Excel, CSV, or JSON) that feeds into whatever downstream system you already use. DATEV, lexoffice, sevDesk, Sage 50, or a spreadsheet that you import into any of the above — the extraction layer doesn't care. It produces clean, structured data and lets your existing workflow consume it.

This approach is called Custom Column Extraction: instead of training a template for each supplier's invoice layout, you define the field names you want — "Rechnungsnummer", "Nettobetrag", "USt-IdNr", "Leistungszeitraum" — and the AI locates each value by understanding what it means semantically, not where it sits spatially on the page. A Rechnung from supplier A with the invoice number in the top-right corner and a Rechnung from supplier B with it in a table header row produce the same structured output because the system identifies "the string that looks like an invoice number" rather than "the text in pixel coordinates (820, 145)." This is the same underlying technology that powers the extraction inside Candis and Spendesk — without the approval workflow, PO matching, and corporate card management layered on top.

For a deeper dive into how this works specifically for German invoices, see our detailed analysis of affordable invoice extraction for the German Mittelstand — which covers the invoice-side economics at 80, 150, and 300 invoices per month in granular detail.

JPG/PNG/PDF AI Extraction

Files are processed securely and not stored.

Three Cost Scenarios at Real KMU Volumes

The following scenarios model a German KMU with an existing accounting setup — DATEV Unternehmen Online with their Steuerberater (tax advisor) or lexoffice/sevDesk — looking to reduce the manual labor of document data entry. The "manual cost" estimates assume 5–7 minutes per document for a full cycle: opening the document, reading it, keying fields into the accounting system, verifying against source, and filing. At a fully loaded Buchhalter cost of €28/hour, that's roughly €2.30–3.30 per document in labor alone. This is consistent with findings from the Journal of Small Business Strategy's 2025 study on digital transformation ROI in German SMEs, which documented a company saving 2 hours/day on mail scanning alone with a tool costing €400/month, yielding an ROI of 4.0.

ScenarioDocuments / MonthManual Cost (Labor)Mid-Tier AP Suite (Candis €199)Standalone AI Extraction ($19/mo Pro)
Small KMU80€200–260€199 — costs nearly as much as the labor it replaces€17.50 — extraction cost drops to €0.22/doc
Mid-Size KMU200€460–660€199 — reasonable, but paying for approval workflows unused€17.50 — extraction cost drops to €0.09/doc
Growing KMU400€920–1,320€199–500 — may need higher tier, features finally relevant€54 (Max plan) — extraction cost drops to €0.14/doc

The numbers reveal the pattern. At 80 documents per month, Candis costs roughly the same as the manual labor — the business case collapses. At 200 documents per month, Candis at €199 costs less than the labor but you're still paying for approval workflows, PO matching, and contract management that a 35-employee KMU simply doesn't use. At 400 documents per month, AP automation suites begin to make operational sense because the volume justifies multi-user workflows.

But across all three scenarios, standalone AI extraction paired with your existing accounting tool produces the same extracted data at roughly 10–15% of the cost of a full AP suite. The trade-off is that you don't get approval routing, PO matching, or corporate card management — but the data shows most KMU weren't going to use those anyway. For a broader market comparison of extraction-only pricing, see the full 2026 AI document extraction pricing breakdown and a comparison of the most affordable tools across all tiers.

At 200 documents per month — a realistic volume for a 30–50 employee KMU — a €17.50/month extraction tool saves roughly €440–640 per month in bookkeeper time, paying for itself 25 times over each month. A €199/month AP suite saves €260–460 and requires you to change how your company approves invoices.

E-Invoicing Won't Replace Extraction

Germany's B2B e-invoicing mandate is the most significant structural change to German invoicing in decades. As of January 2025, every business must be able to receive structured electronic invoices in EN 16931-compliant formats (XRechnung or ZUGFeRD 2.x). From January 2027, businesses with over €800,000 annual revenue must issue e-invoices for domestic B2B transactions. By January 2028, every business must.

These deadlines are real, and the transition will eliminate a meaningful chunk of manual data entry for the invoice portion of a KMU's document mix. A ZUGFeRD hybrid PDF carries embedded XML that a compliant accounting system can ingest directly — no extraction needed. An XRechnung file is pure structured data from the start. A KMU receiving 60% of its invoices as structured e-invoices by 2028 will see a proportional reduction in manual extraction labor.

But the e-invoicing mandate has a hard boundary: it covers domestic B2B invoices and nothing else. The other half of the document mix — Lieferscheine, Bestellungen, Kontoauszüge, Verträge, handgeschriebene Quittungen (handwritten receipts), international supplier invoices outside the German mandate, and all documents arriving as paper or unstructured PDF scans — remains exactly where it is today. The mandate also doesn't cover B2C transactions, and cross-border EU invoices fall under each country's separate regime.

More importantly, the transition is gradual. During the 2025–2028 rollout, most KMU operate in a mixed environment: some invoices arrive as XRechnung XML, some as ZUGFeRD PDFs, some as unstructured PDFs from suppliers who haven't switched yet, and some as paper that gets scanned. The extraction problem doesn't disappear in 2028 — it shrinks proportionally to e-invoice adoption, and the remaining documents are the ones with the most variable formats.

For KMU that also handle invoice data extraction to Excel as part of monthly reporting or supplier analysis, even fully structured e-invoices often need data pulled out and consolidated for purposes beyond the accounting entry — spend analysis, budget tracking, or supplier performance reviews that accounting software doesn't natively produce.

How to Decide What You Actually Need

The framework that cuts through the pricing noise is simple: separate the extraction decision from the software suite decision. Your accounting software (DATEV, lexoffice, sevDesk, Sage) is doing its job. The question is whether you need to replace the layer around it or just fill the gap between document arrival and data entry.

Three questions determine which approach fits:

1. What is your actual monthly document volume, and what types? Count for a month — not just invoices. If 80% of your documents are invoices and your suppliers are already sending ZUGFeRD or XRechnung formats, your extraction gap is smaller than you think. If 50% are Lieferscheine, Bestellungen, and Kontoauszüge, your extraction gap is larger than most tools' marketing suggests.

2. Do you have multiple people who need to approve documents before they're booked? If the answer is yes and involves three or more approvers across departments, an AP automation suite with workflow routing (Candis, Spendesk) may justify its cost. If the answer is "the Geschäftsführer glances at invoices during Kaffee" (coffee), you don't need approval software — you need extraction software.

3. Are you currently maintaining a GoBD-compliant digital archive? GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern) requires that electronically received documents be stored in a system that guarantees immutability, completeness, and traceability for 8–10 years depending on document type. If your current process is "PDFs in a shared folder," a document management layer is more urgent than an extraction layer. But these are separate purchasing decisions — bundling them into one tool may look convenient but usually means you're overpaying for one function to get the other.

FAQ

Can AI extraction handle documents that aren't invoices — like delivery notes (Lieferscheine) or contracts?

Yes. AI extraction that works on semantic understanding rather than template matching reads any document type the same way: it identifies fields by what they mean, not where they are. The same tool that extracts "Rechnungsnummer, Nettobetrag, USt-IdNr" from an invoice can extract "Lieferscheinnummer, Artikel, Menge" from a delivery note. You define the column names you want, and the AI finds the matching values on each document. Templates fail when a new supplier uses a different layout; semantic extraction doesn't care about the layout. This is covered in more detail in the full pricing guide.

Does a €17.50/month extraction tool produce the same quality as Candis at €199?

The extraction accuracy is comparable because both use visual language models to read documents semantically. The €181.50 difference buys approval workflows, PO matching, budget controls, corporate card integration, and multi-entity management — not better extraction quality. If your workflow is "extract data, feed it into DATEV, done," the extraction quality is equivalent at 8% of the cost. If you need line-item-level extraction with GL code assignment and three-way matching, the AP suite's additional features become relevant.

Will the German e-invoicing mandate (XRechnung/ZUGFeRD) make extraction tools obsolete?

No, for two reasons. First, the mandate covers only invoices — delivery notes, purchase orders, bank statements, contracts, and handwritten documents remain outside its scope. Second, even when fully implemented in 2028, small suppliers, international vendors, and one-off transactions will continue producing unstructured documents for years. KMU operating in mixed-format environments will need extraction capability long after the mandate's final deadline. The mandate also requires GoBD-compliant archiving, which is a separate requirement from extraction.

Does ImageToTable.ai export to DATEV format?

ImageToTable.ai exports structured data as Excel (XLSX), CSV, or JSON. You can format the output to match the DATEV import template structure — mapping extracted fields to the correct columns for DATEV CSV import. The tool doesn't produce native DATEV format files, but Excel output mapped to the DATEV import schema achieves the same result with one extra import step. For KMU using lexoffice or sevDesk, the Excel output can be imported directly or used for reporting and analysis alongside the accounting system.

Is GoBD compliance an issue if I use an extraction tool instead of a German-certified accounting suite?

GoBD compliance applies to the storage and archival of original documents and accounting records, not to the extraction step. The extraction tool reads documents and produces structured data; your GoBD-compliant accounting system (DATEV, lexoffice, sevDesk) stores the original documents and transaction records. As long as incoming documents are properly archived in a GoBD-compliant system after extraction, using an intermediate extraction tool doesn't create a compliance gap. The relevant GoBD principles — Unveränderbarkeit (immutability), Vollständigkeit (completeness), Nachvollziehbarkeit (traceability) — are satisfied by the archiving system, not the extraction tool.

At what document volume does it make sense to switch from standalone extraction to a full AP suite?

The threshold is less about volume and more about organizational complexity. A KMU processing 500 invoices a month with one Buchhalter still benefits from standalone extraction if the workflow is "extract, verify, book." The switch to an AP suite becomes justified when: (a) documents require approval from three or more people in different departments, (b) the company operates multiple legal entities that need separate accounting treatment, or (c) the finance team spends more time chasing approvals and matching POs than on actual booking. These conditions typically emerge around 50–100 employees, but the trigger is process complexity, not headcount.

The Bottom Line

German KMU have been sold a false choice: use the basic OCR built into your accounting software and accept 20–30% manual correction rates, or buy a €199/month AP automation suite built for companies with procurement departments. The missing middle — standalone AI extraction that reads any document type, outputs structured data, and feeds your existing accounting stack — is the layer that makes the economics work at Mittelstand volumes.

The data is clear: at 200 documents a month, the price difference between the bundled and modular approaches is roughly €180 per month — or €2,160 per year. Over three years, that's €6,480 that could have gone to something your KMU actually needs — or simply stayed in the bank. The extraction quality is the same in both cases. What's different is everything else in the box, and whether you were going to use it.

See what extraction at your actual volume and document mix looks like. Test on your own Rechnungen, Lieferscheine, and Kontoauszüge — the same tool, the same output, without the suite you don't need.

📮 contact email: [email protected]