Menu

Blog — Vedron

Most accounting software picks one country's rules and treats everything else as an afterthought. Vedron's accounting is set up the other way: the chart of accounts, the e-invoicing format and the tax rules are resolved per company from a lookup, not hardcoded.

Four standards are live today. Three more are registered and in progress. The rest of this post is honest about which is which.

Chart of accounts — a lookup, not a fork

Every posting resolves its account through a three-tier lookup:

  1. Company-specific override (if your company has mapped this transaction type to a specific account).
  2. Tenant default (your organisation's preferred account for this transaction type).
  3. Code-level standard definition (the baseline mapping for whichever national standard this company runs on).

Keyed by tenant, company and account. That is what lets two companies on the same platform run different national standards side by side, without either one's logic leaking into the other.

Four standards are fully mapped and live today: SKR03 (Germany), UOR (Poland), SG_FRS (Singapore) and CZ_GAAP (Czech Republic). Three more — SKR04, UK GAAP and IFRS — are registered in the same lookup and in progress. Adding the next one is registry work, not a rebuild.

E-invoicing — one dispatcher, per-country handlers

One dispatcher resolves which structured format a given invoice needs based on the seller's country and whether the buyer is a government entity, then hands off to a format-specific handler that shares common line-item, tax and formatting logic.

Live today: Germany's XRechnung, Poland's KSeF, Italy's FatturaPA, and generic EN 16931 via Peppol. Each shares the same pre-submission validation, the same VAT-category mapping, and the same reference-number round-trip logic. Different countries, same pipeline, each with its country-specific adapter at the tail.

The practical result: a tenant selling into Germany and Poland uses one invoicing engine, with per-order format resolution based on where the invoice is going. No separate tool per country.

Tax rules — data-driven per company, not unified yet

Which VAT rate or code applies to a given transaction is resolved by priority order, from company and tenant data, not from hardcoded logic that would need a code change to adjust. Being direct: Germany's tax-rule table and Poland's tax schema are currently two separate country-specific structures, not one unified cross-country engine. Both are real and in use. Merging them is on the roadmap.

What that means in practice today: a company operating in both countries has correct tax handling in both, but if you look at the schema, you see two tables. The user experience is unified; the engine behind is not. The merge is a cleanliness goal, not a correctness one.

What ties it together — period locks and verified reconciliation

Closed periods are enforced at the database level. A trigger blocks edits to manual journal entries once a fiscal period is marked closed for that company — not a UI warning that can be clicked past. That means post-close corrections happen through reversal entries in the next open period, which is standard GAAP practice, not a hack.

The ledger has also been reconciled, not just assumed. A multi-phase check during the 2025 Q4 close confirmed zero discrepancy across all 241 posted accounts after each reconciliation step. That is a one-time snapshot, not an ongoing claim, but it establishes a baseline.

Where DATEV fits

Most German tax accountants work in DATEV. It is the tool their workflow assumes. DATEV expects a specific structure:

A generic export against a generic chart of accounts means your accountant spends time remapping before they can even start work.

Vedron's chart of accounts sits directly on SKR03 (with SKR04 in progress), so postings are already in DATEV's expected structure. Every invoice and receipt — including the ones captured by OCR — is reconciled against the ERP's own vendor and tax-rule data before being treated as final. The export is a direct DATEV import; your accountant imports the file and starts work on reconciliation and advice, not on reformatting.

Which countries are live, specifically

To be as concrete as possible:

If you operate in a country not on this list, the three-tier lookup falls back to the standard definition and a dedicated mapping can be added without restructuring your data. Talk to us about the specific country.

Frequently asked questions

Does this mean every accounting standard is supported today?

No. Four are live (SKR03, UOR, SG_FRS, CZ_GAAP). Three more are registered and in progress (SKR04, UK GAAP, IFRS). Adding another is registry work on the lookup table and chart-of-accounts definition — not a code change — but architected-to-support-X and already-supports-X are two different claims.

Is the tax-rule engine unified across countries?

Not yet. Germany and Poland currently have separate country-specific tax-rule schemas, both real and data-driven. Merging them into one cross-country engine is on the roadmap. Today it means a company operating in both countries has two sets of tax rules, correctly applied per transaction, but not merged into one lookup.

Does this replace my tax accountant?

No. It removes the reformatting and re-entry work so what reaches your accountant is already structured for their software. For most German accountants that means a DATEV export that imports cleanly, with chart-of-accounts mapping already done, line items already in the right fields, and documents already linked.

What if my company operates in a country without a fully mapped standard yet?

You can still use the platform's tenant and company-default fallback, and a dedicated mapping can be added without restructuring your data. Worth a direct conversation about your country — adding one is registry work, not a redesign.

How does DATEV import work in practice?

The export produces a CSV file in DATEV's own import schema (account number, counter-account, amount, date, document reference, VAT key, etc.). Your accountant imports it directly into their DATEV workstation. Documents linked to each posting are exported alongside with their file references, so DATEV's DMS can connect them.

What about SKR04 — is it live or not?

Registered, not fully live as of October 2026. The chart of accounts is defined in the same registry structure as SKR03, UOR, SG_FRS and CZ_GAAP; the remaining work is validation and specific mapping for edge cases. If you need SKR04 before the general release, tell us.

Can I run two companies on different standards under one account?

Yes. The three-tier lookup resolves per company, not per tenant. A tenant with one German company on SKR03 and one Polish company on UOR runs both correctly side-by-side, with chart-of-accounts, VAT rules and e-invoicing format each resolving per company.

How do period locks interact with corrections after a close?

Once a period is locked, manual journal edits are blocked at the database level by a trigger. A correction after close happens through a reversal entry in the next open period, which is standard GAAP practice. The audit trail shows both the original posting and the correction, with timestamps.

What validation runs on OCR-captured documents before they hit the ledger?

Each OCR-captured invoice is reconciled against the ERP's own vendor master and tax-rule data before being treated as final. A mismatched VAT rate, an unrecognised vendor, or an amount that doesn't match any known PO gets flagged for review rather than silently posted.

Does this interact with ELSTER for German VAT filings?

The accounting engine produces the figures that go into the VAT return; ELSTER submission itself is a separate step your accountant typically handles. If you file your own Umsatzsteuer-Voranmeldung, Vedron produces the pre-filled form with the amounts per BMF code, ready to transfer.

Talk to us about your setup

Every seller's mix of marketplaces, currencies and payment methods is a little different. Book a short call and we will walk through yours on your real data. Beta clients get the first two months of custom setup on us, and the standard trial can be extended on request.

All posts

DATEV and more — accounting that adapts to each country you sell in

April 14, 202611 min read
DATEV and more — accounting that adapts to each country you sell in

Most accounting software picks one country's rules and treats everything else as an afterthought. Vedron's accounting is set up the other way: the chart of accounts, the e-invoicing format and the tax rules are resolved per company from a lookup, not hardcoded.

Four standards are live today. Three more are registered and in progress. The rest of this post is honest about which is which.

Chart of accounts — a lookup, not a fork

Every posting resolves its account through a three-tier lookup:

  1. Company-specific override (if your company has mapped this transaction type to a specific account).
  2. Tenant default (your organisation's preferred account for this transaction type).
  3. Code-level standard definition (the baseline mapping for whichever national standard this company runs on).

Keyed by tenant, company and account. That is what lets two companies on the same platform run different national standards side by side, without either one's logic leaking into the other.

Four standards are fully mapped and live today: SKR03 (Germany), UOR (Poland), SG_FRS (Singapore) and CZ_GAAP (Czech Republic). Three more — SKR04, UK GAAP and IFRS — are registered in the same lookup and in progress. Adding the next one is registry work, not a rebuild.

E-invoicing — one dispatcher, per-country handlers

One dispatcher resolves which structured format a given invoice needs based on the seller's country and whether the buyer is a government entity, then hands off to a format-specific handler that shares common line-item, tax and formatting logic.

Live today: Germany's XRechnung, Poland's KSeF, Italy's FatturaPA, and generic EN 16931 via Peppol. Each shares the same pre-submission validation, the same VAT-category mapping, and the same reference-number round-trip logic. Different countries, same pipeline, each with its country-specific adapter at the tail.

The practical result: a tenant selling into Germany and Poland uses one invoicing engine, with per-order format resolution based on where the invoice is going. No separate tool per country.

Tax rules — data-driven per company, not unified yet

Which VAT rate or code applies to a given transaction is resolved by priority order, from company and tenant data, not from hardcoded logic that would need a code change to adjust. Being direct: Germany's tax-rule table and Poland's tax schema are currently two separate country-specific structures, not one unified cross-country engine. Both are real and in use. Merging them is on the roadmap.

What that means in practice today: a company operating in both countries has correct tax handling in both, but if you look at the schema, you see two tables. The user experience is unified; the engine behind is not. The merge is a cleanliness goal, not a correctness one.

What ties it together — period locks and verified reconciliation

Closed periods are enforced at the database level. A trigger blocks edits to manual journal entries once a fiscal period is marked closed for that company — not a UI warning that can be clicked past. That means post-close corrections happen through reversal entries in the next open period, which is standard GAAP practice, not a hack.

The ledger has also been reconciled, not just assumed. A multi-phase check during the 2025 Q4 close confirmed zero discrepancy across all 241 posted accounts after each reconciliation step. That is a one-time snapshot, not an ongoing claim, but it establishes a baseline.

Where DATEV fits

Most German tax accountants work in DATEV. It is the tool their workflow assumes. DATEV expects a specific structure:

  • A chart of accounts on SKR03 or SKR04.
  • Postings formatted to DATEV's own import specification: account number, counter-account, amount, date, document reference, VAT key.
  • Documents organised so DATEV's own document-management side (DATEV Unternehmen online / DMS) can connect them to postings.

A generic export against a generic chart of accounts means your accountant spends time remapping before they can even start work.

Vedron's chart of accounts sits directly on SKR03 (with SKR04 in progress), so postings are already in DATEV's expected structure. Every invoice and receipt — including the ones captured by OCR — is reconciled against the ERP's own vendor and tax-rule data before being treated as final. The export is a direct DATEV import; your accountant imports the file and starts work on reconciliation and advice, not on reformatting.

Which countries are live, specifically

To be as concrete as possible:

  • Germany, SKR03: Live. DATEV export working. Istbesteuerung bank matching live.
  • Germany, SKR04: Registered, in progress. Target: Q1 2027.
  • Poland, UOR: Live. KSeF submission live. metoda kasowa on roadmap.
  • Singapore, SG_FRS: Live.
  • Czech Republic, CZ_GAAP: Live.
  • UK, UK GAAP: Registered, in progress. No live export yet.
  • IFRS: Registered, in progress.

If you operate in a country not on this list, the three-tier lookup falls back to the standard definition and a dedicated mapping can be added without restructuring your data. Talk to us about the specific country.

Frequently asked questions

Does this mean every accounting standard is supported today?

No. Four are live (SKR03, UOR, SG_FRS, CZ_GAAP). Three more are registered and in progress (SKR04, UK GAAP, IFRS). Adding another is registry work on the lookup table and chart-of-accounts definition — not a code change — but architected-to-support-X and already-supports-X are two different claims.

Is the tax-rule engine unified across countries?

Not yet. Germany and Poland currently have separate country-specific tax-rule schemas, both real and data-driven. Merging them into one cross-country engine is on the roadmap. Today it means a company operating in both countries has two sets of tax rules, correctly applied per transaction, but not merged into one lookup.

Does this replace my tax accountant?

No. It removes the reformatting and re-entry work so what reaches your accountant is already structured for their software. For most German accountants that means a DATEV export that imports cleanly, with chart-of-accounts mapping already done, line items already in the right fields, and documents already linked.

What if my company operates in a country without a fully mapped standard yet?

You can still use the platform's tenant and company-default fallback, and a dedicated mapping can be added without restructuring your data. Worth a direct conversation about your country — adding one is registry work, not a redesign.

How does DATEV import work in practice?

The export produces a CSV file in DATEV's own import schema (account number, counter-account, amount, date, document reference, VAT key, etc.). Your accountant imports it directly into their DATEV workstation. Documents linked to each posting are exported alongside with their file references, so DATEV's DMS can connect them.

What about SKR04 — is it live or not?

Registered, not fully live as of October 2026. The chart of accounts is defined in the same registry structure as SKR03, UOR, SG_FRS and CZ_GAAP; the remaining work is validation and specific mapping for edge cases. If you need SKR04 before the general release, tell us.

Can I run two companies on different standards under one account?

Yes. The three-tier lookup resolves per company, not per tenant. A tenant with one German company on SKR03 and one Polish company on UOR runs both correctly side-by-side, with chart-of-accounts, VAT rules and e-invoicing format each resolving per company.

How do period locks interact with corrections after a close?

Once a period is locked, manual journal edits are blocked at the database level by a trigger. A correction after close happens through a reversal entry in the next open period, which is standard GAAP practice. The audit trail shows both the original posting and the correction, with timestamps.

What validation runs on OCR-captured documents before they hit the ledger?

Each OCR-captured invoice is reconciled against the ERP's own vendor master and tax-rule data before being treated as final. A mismatched VAT rate, an unrecognised vendor, or an amount that doesn't match any known PO gets flagged for review rather than silently posted.

Does this interact with ELSTER for German VAT filings?

The accounting engine produces the figures that go into the VAT return; ELSTER submission itself is a separate step your accountant typically handles. If you file your own Umsatzsteuer-Voranmeldung, Vedron produces the pre-filled form with the amounts per BMF code, ready to transfer.

Talk to us about your setup

Every seller's mix of marketplaces, currencies and payment methods is a little different. Book a short call and we will walk through yours on your real data. Beta clients get the first two months of custom setup on us, and the standard trial can be extended on request.

Did you enjoy this article?