Native DATEV Interface & DATEVconnect online
One of the main reasons compact DACH wholesale and e-commerce businesses with 5 to 25 users choose weclapp is its built-in German financial logic. Unlike international ERP suites where DATEV often has to be bolted on afterward, weclapp handles SKR03/SKR04 charts of accounts, posting periods, GoBD posting locks, dunning, and receipt transfer straight in its core.
Alongside classic EXTF file exports, weclapp supports direct online transfer via official DATEV APIs (historically widely referred to as DATEVconnect online, and technically delivered today through the DATEV Accounting Data Service and DATEV Invoice Data Service 1.0). Outgoing invoices, supplier bills, credit notes, and payment entries—complete with matching PDF receipt images—transfer directly to your tax advisory firm without manual file exchange.
Comparing the Three Handoff Paths in weclapp
Which transfer mode fits best in weclapp depends on document volume and whether account pre-coding sits in-house or with your tax advisor:
| Handoff Path in weclapp | What Gets Transferred? | Advantage | What to Watch |
|---|---|---|---|
| EXTF File Export (CSV + receipt ZIP) | Pre-coded posting batches, sub-ledger master data & receipts | Usable immediately with no extra DATEV online services | Manual exchange creates risk of duplicate or incomplete exports under time pressure |
| DATEV Accounting Data Service (Online API) | Fully pre-coded EXTF batches + linked document images (BEDI-GUID) |
Delivered straight into the DATEV data center with zero manual receipt matching | Chart of accounts, tax keys, and sub-ledger accounts in weclapp must be 100% accurate |
| DATEV Invoice Data Service 1.0 (Unternehmen online) | Structured invoice metadata and document PDFs into Unternehmen online | Tax firm retains full control over account coding and booking proposals | Often slower than pre-coded batches at very high e-commerce order volumes |
Chart of Accounts, Tax Automation & EU OSS in Commerce
In B2B wholesale and multi-channel e-commerce, the real work is never flicking on the DATEV connection—it is clean account determination. weclapp derives revenue accounts and tax flags from a matrix combining sales channel, destination country, customer type (B2B/B2C), VAT ID verification, and item tax category.
Four scenarios must be defined cleanly before your first live export:
- Domestic 19% and 7% VAT (e.g., food / D2C): Separate revenue accounts per VAT rate plus proper ancillary-service treatment of shipping charges (proportional split on mixed-VAT shopping carts).
- Intra-EU B2B supplies: Zero-rated posting only when the recipient's VAT ID is validated and proof of delivery is archived; clean routing to the intra-EU revenue account for the EC Sales List (ZM).
- EU OSS (B2C above the delivery threshold): Once an online retailer crosses the EU-wide €10,000 threshold, destination-country VAT rates apply. weclapp must store the correct VAT rates per EU member state along with the OSS revenue accounts or DATEV tax keys agreed with your tax firm.
- Non-EU exports (e.g., Switzerland, UK, US): Zero-rated export deliveries cleanly separated from duty-paid (DDP) shipments, with verified export documentation attached.
Reconciling Shopify, Stripe & PayPal Payouts Cleanly
By far the biggest source of chaos in growing e-commerce accounting sits at the intersection of Shopify, weclapp, and payment service providers (PSPs) such as Shopify Payments, Stripe, PayPal, or Klarna. The reason is simple: the payout arriving in your business bank account almost never matches a single invoice total.
A typical Shopify Payments payout bundles dozens of individual orders, deducts processing fees immediately, nets out partial refunds or chargebacks, and frequently spans orders across two different calendar months. Posting that bank deposit straight against customer receivables destroys open-item visibility within weeks.
| Posting Step | Debit | Credit | Month-End Objective |
|---|---|---|---|
| 1. Invoice from weclapp | Debtor / channel collective account | Revenue account (domestic / OSS) + VAT | Complete gross revenue from the leading ERP |
| 2. PSP Payment Capture | PSP clearing account (e.g., 1361/1461) | Debtor / channel collective account | Individual invoice marked paid; open item cleared |
| 3. PSP Transaction Fees | Banking & payment processing fees | PSP clearing account | Fees appear transparently as operating expense, never as reduced revenue |
| 4. Bank Payout | Business bank account | PSP clearing account | Clearing account nets to zero; any balance equals payouts currently in transit |
This structure keeps every single order audit-ready, clears Shopify refunds and credit notes automatically against the same channel, and spares your tax firm from manually dissecting 400 PayPal statement lines every month.
Seven Common Pitfalls at Month-End Close
From our weclapp implementations and system audits, seven recurring issues hold up month-end closing most frequently:
- Missing or inconsistent debtor numbers: B2B accounts without fixed sub-ledger ranges—or switching arbitrarily between individual debtors and collective accounts—break open-item reconciliation (OPOS).
- Unlocked or backdated postings: If someone adds or modifies a document in a prior month after the DATEV export has already run, that entry is missing from the transmitted batch.
- Mismatched G/L digit lengths: If your tax firm uses 4-digit accounts while weclapp exports 5-digit accounts (or vice versa), DATEV immediately rejects the import with format errors.
- Credit notes and partial returns crossing month-end: When Shopify triggers a refund before the matching credit note is posted in weclapp, unallocated credit balances remain stranded.
- Supplier bills without PDF attachments: Recording vendor invoices as ledger rows without digital receipt images forces your tax firm to chase missing documents one by one.
- Duplicate invoicing in shop and ERP: Invoices must always be generated in exactly one place. In a clean Shopify–weclapp integration, weclapp owns invoice numbers, credit notes, and the DATEV handoff.
- Unclear ownership for advisor queries: Without a fixed monthly review checkpoint between internal finance and the tax firm, a misconfigured tax key often goes unnoticed for months.
Onboarding with Your Tax Firm: Go Live Only When Every Cent Matches
As a weclapp Certified Partner, we follow one strict principle on every implementation: never turn a DATEV export live blindly. Before the cutoff date, we transmit a complete set of real transactions—domestic invoice, EU B2B with VAT ID, EU OSS order, credit note, vendor bill, and PSP payout—as a trial batch to your tax firm. Regular operations start only once accounts, tax keys, receipt images, and the trial balance (SuSa) agree down to the exact cent.
Next Step
Read more about our end-to-end support covering setup, data migration, Shopify integration, and training on our weclapp Certified Partner platform page and our DATEV Interface module page. For general DATEV fundamentals on EXTF, BEDI-GUID, and GoBD, see our Master Guide: DATEV Integration for SMEs.
If you want to launch weclapp cleanly from day one—or finally eliminate friction from your monthly closing—book a free introductory call directly on our Contact page.
Frequently Asked Questions
Is the DATEV interface already built natively into weclapp?
Yes. As a German cloud ERP, weclapp ships with native DATEV export logic for EXTF posting batches, master data, and document images, and supports direct online transmission to DATEV through the official DATEV Accounting Data Service and Invoice Data Service 1.0.
How are Shopify Payments, Stripe, and PayPal reconciled cleanly against DATEV in weclapp?
Each payment service provider receives its own clearing account in weclapp. Customer invoices are settled against that clearing account during payment matching, while deducted transaction fees and the net lump-sum bank payout are posted separately. As a result, the clearing account reconciles cleanly to zero at month-end.
Does weclapp support EU OSS and automatic revenue account determination?
Yes. Using tax rules, destination countries, item tax categories, and validated customer VAT IDs, weclapp automatically assigns domestic, intra-EU, non-EU export, and EU OSS revenue accounts. The prerequisite is configuring all OSS destination accounts and tax keys jointly with your tax firm beforehand.
When should accounting entries be locked in weclapp?
As soon as an accounting month has been fully reviewed and transmitted to DATEV, exported postings should be locked for GoBD immutability. Any later corrections are then booked exclusively through clean reversal entries or credit notes in the open period so no silent discrepancies emerge between weclapp and the tax firm.
Do we still need an alignment project with our tax firm when using weclapp?
Absolutely. The native interface handles technical file and API generation, but it does not replace business-side configuration of SKR03/SKR04, sub-ledger numbering ranges, EU OSS accounts, and PSP clearing. Running one joint trial month with your tax firm before go-live eliminates almost all downstream rework.