Mate iT – Digital Architects

April 23, 2026 4 min read

DATEV interface in weclapp — what it does well, where it falls short

weclapp has the most native DATEV interface among DACH cloud-ERPs — built in Karlsruhe with the German tax-advisor workflow in mind. What it can do, what it can't, and how we typically set it up.

  • datev
  • weclapp
  • accounting
  • mid-market

The simple case

weclapp has the most native DATEV interface in the DACH cloud-ERP segment. “Native” means: no third-party module, no custom implementation, no workarounds. The functionality is part of the license scope and reachable through the standard accounting configuration at setup.

In practice, this means: when you roll out weclapp in production, the DATEV integration is included in the standard rollout — typically 1–2 days additional to the ERP base setup. For a mid-market company with classic German business, an established tax advisor, and a tidy chart of accounts, this is a half-day session in configuration mode.

What the interface does technically

Chart-of-accounts mapping: weclapp ships SKR03 and SKR04 as templates. At setup, the relevant chart is selected, then individual accounts are added. Mapping to the DATEV client number is set up once, then the export runs automatically.

Tax keys: weclapp knows all common DATEV tax keys — standard rates (VAT 19 %, 7 %, 0 %), intra-community supplies, reverse-charge, third-country revenue, low-value invoices. The correct key is assigned per article or per account, then automatically applied at booking time.

Booking-stack export: Export typically runs monthly. In the accounting module, a stack is created for the reporting period, exported (DATEV ASCII or DATEV XML), and handed over to the tax advisor. With DATEV-Unternehmen-online setups, the handover runs automatically over the cloud interface.

Document-image attachment: Each booking can carry a document — incoming invoices as PDF, outgoing invoices auto-generated by weclapp. When the booking stack is exported, document images are included automatically, so the tax advisor has direct access in the DATEV document center.

Debtor/creditor sync: New customers and suppliers are created in weclapp; on the first booking, a DATEV client number is automatically assigned. Master-data changes are logged.

Where the interface falls short

Three areas where we typically do additional work during rollout:

1. Special tax keys: For very international business (e.g., third-country imports with customs handling, US business with special reverse-charge rules), the standard keys aren’t enough. We then configure additional keys and maintain the mapping per order type.

2. Multi-tenant setups: Holdings with multiple subsidiaries need a separate DATEV client number per subsidiary. weclapp supports this, but the setup isn’t trivial — we typically configure central accounting with separated export per tenant.

3. Cost-center logic: When the tax advisor wants to see bookings with cost centers (Marketing, Sales, Administration etc.), this must be set explicitly per booking in weclapp. We typically build a default logic based on the document type, which the bookkeeper only needs to override.

How we set up the interface

Typical Mate iT setup sequence:

  1. Tax-advisor workshop (½ day, before ERP setup): align chart of accounts, tax keys, booking-stack workflow, request DATEV client number.
  2. Configuration in weclapp (1 day): import chart of accounts, map tax keys, enter client number, set up booking-stack template.
  3. Test export (½ day): export sample bookings, tax advisor imports into DATEV Kanzlei-Rechnungswesen, checks for completeness. Corrections are fed back into weclapp.
  4. Hypercare phase (4–8 weeks): we actively accompany the first monthly closes, so edge cases (e.g., year-end-close bookings, VAT pre-filing) run cleanly.

More on weclapp: /en/plattformen/weclapp. Pillar overview DATEV: /en/blog/datev-anbindung-mittelstand.

When weclapp + DATEV is the right combination

  • DACH mid-market with established tax-advisor relationship
  • Classic trade, manufacturing, or e-commerce business
  • Chart of accounts fits SKR03/SKR04 (with individual adjustments)
  • DATEV integration is a high hygiene requirement, not a “nice to have”

If that fits — happy to set this up with you.

Pillar overview

More on DATEV integration in the mid-market as a whole: /en/blog/datev-anbindung-mittelstand. Comparison of platforms weclapp/Odoo/Zoho: /en/blog/weclapp-vs-odoo-vs-zoho. More on weclapp: /en/plattformen/weclapp.

Frequently asked questions

Which charts of accounts does weclapp support? +

weclapp supports SKR03 and SKR04 out of the box — both are German standard charts. Both are available as standard templates; one is selected at setup, then individual accounts are adjusted. Special charts (e.g., hospital, industry-specific) can be modeled but require Mate iT configuration.

How does the booking-stack export work technically? +

In the weclapp accounting module, an export stack is created (e.g., April 2026). It exports all bookings of the period in DATEV ASCII or XML format. The export is downloaded or transferred directly to a cloud destination (e.g., DATEV-Unternehmen-online), from where the tax advisor imports it. Document images are exported automatically.

Can weclapp also receive incoming supplier invoices via DATEV-Unternehmen-online? +

Yes — via the DATEV-Unternehmen-online integration. Supplier invoices captured digitally by the tax advisor flow back into weclapp as incoming invoices, linked to the document. This saves manual capture in weclapp and is especially useful for mid-market companies with high incoming-invoice volume.

What does the DATEV interface in weclapp cost? +

It's part of the standard weclapp license scope — no additional module, no add-on license. With the Mate iT rollout, configuration and tax-advisor alignment are included in the typical ERP setup — no separate pricing for the DATEV integration.

Cluster

Keep reading

Other articles in the same topic cluster.