A conventional accounting engagement can often be organised around bank transactions, sales invoices, supplier invoices and a limited number of subledgers. A growing online retailer creates a very different data environment. Orders originate in Amazon, Shopify, eBay, Kaufland, Etsy and other marketplaces. Payments are processed by PayPal, Stripe, Klarna, Mollie, Shopify Payments or Amazon. Invoices may be generated by the store, an ERP platform or a separate billing application. The process also includes fee statements, returns, chargebacks, reserves, foreign currencies, OSS sales and potentially inventory in several countries.

For German tax firms (Steuerkanzleien), taking on e-commerce clients without automated workflows frequently leads to severe operational bottlenecks. Processing thousands of transaction rows manually in Excel destroys profit margins, frustrates staff and creates compliance risks under GoBD auditing standards.

Conversely, e-commerce represents one of the fastest-growing and most profitable sectors for tax firms equipped with specialized digital automation.

This guide details a standardised e-commerce accounting workflow for tax firms, showing how to handle high-volume transaction data, structure clearing accounts, maintain open items, automate DATEV imports and establish traceable GoBD processes.

Why Traditional Tax Firm Workflows Fail in E-Commerce

When a tax firm attempts to process an e-commerce client using traditional bookkeeping methods, three main failure modes occur:

1. Data Volume Explosion

A merchant generating €100,000 in monthly sales across Amazon and Shopify can easily produce 20,000 to 50,000 individual data rows per month across orders, payouts, fees, refunds and tax records. Manual posting or simple CSV imports overload standard accounting software.

2. Broken Audit Trail & Unreconciled Clearing Accounts

Posting net bank payouts directly to revenue without reconciling underlying orders creates massive open-item backlogs. Unmatched receivables accumulate on payment provider clearing accounts (e.g. 1360/1361 in SKR03), leading to delayed year-end financial statements.

3. Cross-Border Tax Complexity

Intra-Community distance sales (OSS), foreign FBA inventory transfers (Poland, Czech Republic), reverse-charge service fees (§ 13b UStG) and local foreign VAT registrations require automated, rule-based tax rate determination.

The Standardised Kanzlei E-Commerce Workflow

To process e-commerce clients profitably and securely, leading tax firms establish a standardized 5-stage automated pipeline:

[Sales Channels & Gateways] ➔ [E-Commerce Interface (KudTax)] ➔ [Validation & Matching Engine] ➔ [DATEV EXTF Batch] ➔ [DATEV Kanzlei-Rechnungswesen]

Stage 1: Central System Onboarding

Map the client's complete system landscape during onboarding:

Sales Channels: Shopify, Amazon (DE/UK/US/EU), eBay, Kaufland, Etsy, WooCommerce.
Payment Service Providers: PayPal, Stripe, Klarna, Mollie, Shopify Payments, Amazon Pay.
Invoicing & ERP: Billbee, PlentyMarkets, Xentral, JTL, Shopify Invoicing.
Logistics & Warehouses: Own warehouse, Amazon FBA (DE/PL/CZ), 3PL fulfillment centres.

Stage 2: Data intake and tax case groups

Depending on the source, data is taken over via a connection or a file import and assigned to tax case groups. Which treatment applies to which case is decided by the accounting firm. Typical case groups are:

Domestic B2C/B2B: Standard 19% or 7% German VAT.
EU B2C Distance Sales: OSS destination VAT rate based on delivery country.
EU B2B Supplies: Zero-rated intra-Community supply with VIES VAT ID validation.
FBA Inventory Transfer: Intra-Community transfer reporting for stock moved between DE, PL, and CZ.

Stage 3: Reconciling open items and clearing accounts

Order invoices are matched against payment provider settlement reports:

Orders are posted to debtor clearing accounts using unique references (Belegfeld 1 = Order ID).
Payout reports clear debtor receivables, post provider processing fees to expense accounts, and record net transfers against bank clearing accounts.

Stage 4: Documents and document references

Every journal entry needs a traceable source document, such as the PDF invoice or the settlement report. The DATEV export contains document references; whether the document file can be opened in DATEV with one click is a separate question and should be checked during the test month.

Stage 5: DATEV EXTF Export & Kanzlei Import

The posting batch is exported as a DATEV EXTF file. Review the data and validation results before importing the file into DATEV Kanzlei-Rechnungswesen.

Recommended Chart of Accounts Setup (SKR03 / SKR04)

Tax firms should implement dedicated subledgers and clearing accounts for e-commerce clients:

Payment Provider Clearing Accounts (Verrechnungskonten)

SKR03 1361 / SKR04 1461: PayPal Clearing Account
SKR03 1362 / SKR04 1462: Stripe Clearing Account
SKR03 1363 / SKR04 1463: Klarna Clearing Account
SKR03 1360 / SKR04 1460: Amazon Settlement Clearing Account
SKR03 1364 / SKR04 1464: Shopify Payments Clearing Account

Dedicated Revenue Accounts for OSS Sales

SKR03 8400 / SKR04 4400: Domestic Sales 19% VAT
SKR03 8315 / SKR04 4315: EU OSS Distance Sales (Destination VAT)
SKR03 8125 / SKR04 4125: Tax-exempt intra-Community supplies B2B

Kanzlei Quality Controls & Month-End Checkpoints

To ensure zero-error accounting, tax staff should execute four key monthly checkpoints:

Clearing Account Zero-Balance Check: Verify that provider clearing accounts balance to zero or match known uncollected reserves at month-end.
OSS Reconciliation: Cross-check revenue posted to OSS accounts against the quarterly BZSt OSS return summary.
Amazon VCS Reconciliation: Verify that Amazon sales data matches the VAT Calculation Service (VCS) tax reports.
Bank Transfer Matching: Ensure net payouts received on the main bank account (1200) clear the corresponding provider clearing entries.

Onboarding E-Commerce Clients: A Kanzlei Checklist

When taking on a new online retail client, request the following documents and access credentials:

Complete list of active storefronts, marketplaces, and payment providers.
API read-only credentials or OAuth authorization for shop and payment portals.
Confirmation of Amazon FBA warehouse locations (DE, PL, CZ, etc.).
Historical OSS returns and foreign VAT registration certificates.
Chart of accounts preference (SKR03 vs SKR04) and client number in DATEV.

How KudTax supports accounting firms in e-commerce

KudTax reconciles your e-commerce data with AI assistance, creates journal entries based on SKR03 or SKR04 and hands them over in DATEV EXTF format. The relevant questions are which data your sources provide and which settings have been agreed for the destination system.

For eBay, the confirmed scope includes orders, fees, refunds and payouts. WooCommerce data is imported through CSV or XLSX files. PayPal and Stripe are confirmed payment-provider examples. Check other sources against their currently supported scope in the integrations overview.

Choose a test month with your accountant. Compare the source records, transactions already booked, document references and import results. A reference in a record does not automatically mean the underlying document file is available in the destination system. Resolve open questions before recurring exports begin.

For firms with several e-commerce clients, a conversation is usually the better first step: book a demo. Merchants can use KudTax free for up to 25 orders a month and try larger plans free for one month (create an account).

Official and further sources

This article provides general information for tax professionals and businesses and does not constitute formal legal or tax advice.

E-Commerce Accounting for Tax Firms: High-Volume Data