Technical Training

Amazon → DATEV Conversion — Technical Training

How the e-VATAX conversion system works: Logic Bridge Key, Amazon Markets Logic, sales & expense ledgers, VAT treatment, routing tables and the EU VAT rates reference. For new trainees.

e-VATAX Team June 2026 30 min read
On This Page

1. System Overview

e-VATAX operates three in-house converters that transform raw Amazon reports into ready-to-import DATEV Buchungsstapel (format 125 / v700) files:

ConverterInputOutputPurpose
Settlement → DATEVAmazon settlement .txt files (tab-delimited, per marketplace)DATEV EXT / ASCII CSVBooks every money movement: sales, fees, refunds, payouts, reserves
VTR → DATEVAmazon VAT Transaction Report (.csv/.txt)DATEV EXT / ASCII CSVBooks revenue to the correct VAT ledger with BU-Schlüssel and EU-Land
Invoice PDFs → DATEVAmazon invoice PDFsDATEV EXT / ASCII CSVBooks Amazon fee invoices to the correct expense ledger

Every conversion is driven by lookup tables stored in our database, editable in the admin panel (Admin → Lookup Tables). No account number is hardcoded — if Amazon introduces a new transaction type, we add one row to a table and re-run. The tables can be exported/imported as JSON backups to sync environments.

The Golden Rule
The converters never guess. Every row is mapped through a lookup table. Anything unknown routes to account 9998 (UNMAPPED) and must be reviewed by a human before the DATEV export is delivered.

2. The Four Lookup Tables

TableRowsUsed byWhat it maps
Logic_Bridge_Key (LBK)~156Settlement Convertertransaction-type / amount-type / amount-description → routing key
Amazon Markets Logic (ML)14Settlement ConverterMarketplace → Debitor, Creditor, Transit and special accounts
VTR Routing Logic7+VTR ConverterRouting_Code → Konto, BU-Schlüssel, EU-Land type, S/H direction
Invoice Routing10Invoice ConverterAmazon invoice type → expense Konto + BU
Where to Edit
Admin → Lookup Tables. Each table supports inline editing, CSV upload, CSV export, and full JSON backup/restore. Always export a backup before making bulk changes.

3. Logic Bridge Key (LBK) — The Heart of the Settlement Converter

Every settlement row carries three identifying fields: transaction-type (Order, Refund, other-transaction…), amount-type (ItemPrice, ItemFees…) and amount-description (Principal, Tax, Commission…). The LBK table maps each combination to one routing key:

Order / ItemPrice / Principal          →  Debitor
Order / ItemPrice / Tax                →  Debitor
Order / ItemFees  / Commission         →  Creditor
Order / ItemFees  / FBAPerUnitFulfillmentFee → Creditor
other-transaction / FBA Inventory Reimbursement / WAREHOUSE_LOST → Adjustment_Reimbursement

Current distribution of our ~156 LBK rows by routing key (snapshot, June 2026):

Routing KeyLBK rowsMeaning
Creditor72Amazon fees → marketplace Creditor account
Debitor30Sales revenue → marketplace Debitor account
Adjustment_Reimbursement24Reimbursements / adjustments → 4760
Debt_Adjustment10Cross-marketplace debt transfers → 1592 (nets to zero)
WithheldTaxVAT7Marketplace Facilitator VAT → 1754
non_invoiced_Amazon_Fee_without_VAT5Non-invoiced fees, no VAT → 4765
non_invoiced_Amazon_Fee_with_VAT2Non-invoiced fees with Vorsteuer → 4766 + BU 9
Shipping_Label_Buy_Fee2Shipping label purchases → marketplace Creditor
Reserve_Amount2Amazon reserve balance → 1591
BANK-DEPOSIT1Settlement header row, positive payout → 1361
Case Sensitivity Trap
The LBK join is normalised with fnNorm() on both sides — but when you add new rows, keep the key spelling identical to the ML table column headers ("Debitor", not "DEBITOR"). A mismatch sends everything to Gegenkonto null / 9998.

Routing Key → Account Reference (SKR03 / SKR04)

LBK KeySKR03SKR04What it represents
Debitor30005 (DE), 30006 (FR)…10005, 10006…Sales revenue — customer receivable
Creditor80005 (DE), 80006 (FR)…70005, 70006…Amazon fees — Amazon payable
TRANSIT1365 (DE, per marketplace)1465Always the Konto side for every booking
BANK-DEPOSIT13611461Bank payout — positive total-amount
BANK-CHARGE17301830Credit card charge — negative total-amount
Reserve_Amount15911691Amazon's reserve balance
Debt_Adjustment15921692Cross-marketplace debt transfers — always nets to zero
WithheldTaxVAT17541854Marketplace Facilitator VAT
Adjustment_Reimbursement47606760Reimbursements and adjustments
non_invoiced_Fee_without_VAT47656765Non-invoiced fees, no VAT
non_invoiced_Fee_with_VAT4766 + BU96766 + BU9Non-invoiced fees with VAT (Vorsteuer)
DPD_Hermes_DHL_Fee_with_VAT80100 + BU970100 + BU9Shipping label costs with VAT
UNMAPPED99989998Unknown — review needed

4. Amazon Markets Logic (ML) — Per-Marketplace Accounts

The marketplace is detected from the settlement file name. The ML table then supplies every account for that marketplace. Current snapshot:

MarketplaceCodeDebitorCreditorTransit
AMAZON.ITIT30003800031363
AMAZON.ESES30004800041364
AMAZON.DEDE30005800051365
AMAZON.FRFR30006800061366
AMAZON.NLNL30007800071367
AMAZON.COM.BEBE30007800071367
AMAZON.SESE30008800081368
AMAZON.PLPL30009800091369
AMAZON.IEIE30010800101590
AMAZON.COM.TRTR30011800111590
AMAZON.CO.UKUK30012800121368
AMAZON.COM.CZCZ30013800131369
AMAZON.AEAE30014800141369
NON-AMAZON DEDE30005800051365

Accounts shared by all marketplaces (same ML table, identical per row):

PurposeAccountNotes
Reserve Amount1591Amazon's security reserve hold-back
Withheld Tax VAT1754Marketplace Facilitator VAT
Bank Deposit1361Positive settlement payout
Bank Charge (credit card)1730Negative settlement — card charged
Commingling VAT1770Always cancels to zero
Adjustment / Reimbursement4760Lost/damaged inventory reimbursements
Debt Adjustment1592Cross-account transfers — nets to zero
Non-invoiced fee without VAT4765Storage, inbound transport, removals
Non-invoiced fee with VAT4766With Vorsteuer — BU 9
UNMAPPED9998Review required — never deliver with 9998 rows

5. Sales Ledgers & VAT Treatment

Revenue is booked by the VTR converter, never by the settlement converter. Which sales ledger a transaction hits depends on departure country, arrival country, tax scheme and whether the buyer has a VAT number:

Ledger (SKR03)NameVAT treatmentWhen used
8400Erlöse 19% MwSt19% German VAT — automatic accountDE→DE domestic; EU warehouse→DE regular (BU 290)
8300Erlöse 7% MwSt (Reduced Rate)7% German VAT — automatic accountDE domestic sales of reduced-rate products (food, books, certain takeaway items). For OSS sales of such products, always check the destination country's own reduced rates (see section 11)
8320Erlöse EU OSSDestination-country VAT via OSS — needs BU 240/241/285All B2C cross-border EU sales under UNION-OSS
8125Steuerfreie ig Lieferung0% — reverse charge, buyer declares VATB2B sale to EU business with valid VAT ID (ZM reportable)
8120Ausfuhr / Export0% — outside EU scopeExports outside EU; UK/CH where Amazon collects (VOEC)
DATEV Gets Gross — Always
All amounts delivered to DATEV are gross (VAT included). DATEV splits VAT itself using the account's automatic tax key or the BU-Schlüssel. Delivering net amounts understates VAT and is the single most expensive beginner mistake.

6. Expense & Fee Ledgers

Amazon fees split into invoiced (booked against the marketplace Creditor, cleared later by the invoice receipt) and non-invoiced (booked straight to expense). The Invoice Converter additionally routes invoice PDFs by document type:

Ledger (SKR03)Used forBU
80003–80014Marketplace Creditor — invoiced Amazon fees (Commission, FBA, storage, EPR)—
4760Non-invoiced fees without VAT; reimbursements; Merchant VAT invoices9 / 0
4765Non-invoiced Amazon fees without VAT (settlement path)—
4766Non-invoiced Amazon fees with Vorsteuer (settlement path)9
4761Fulfillment by Amazon tax invoices & credit notes; EPR Pay-On-Behalf9
4730Merchant Buy Shipping Label9
4600Product Ads (Amazon Advertising) VAT invoices & credit notes9

Invoice Routing Table (Invoice Converter) — Snapshot

Amazon Invoice TypeKontoBU
Fulfillment by Amazon Tax Invoice47619
Fulfillment by Amazon Tax Credit Note47619
Merchant VAT Invoice47609
Merchant VAT Credit Note47609
Merchant Buy Shipping Label47309
EPR Pay On Behalf Service Invoice47619
AGL Merchant Self Billing Invoice47609
Product Ads VAT Invoice46009
Product Ads VAT Credit Note46009
Merchant Consolidated B-XML VAT Invoice47600

7. Settlement → DATEV: The 10 Phases

The settlement converter processes every uploaded file through ten deterministic phases:

Phase 1–2

Load & parse: read every tab-delimited settlement file, detect marketplace from the file name, stack all files into one dataset.

Phase 3

Normalise & filter: trim whitespace, drop junk/empty rows, standardise column names.

Phase 4

Number conversion: parse German decimal commas ("5207,79") into numeric amounts — DATEV output later uses F2 format without thousand separators.

Phase 5

Bank row flag: the single header row with a filled total-amount becomes BANK-DEPOSIT (positive), BANK-CHARGE (negative) or no booking (zero).

Phase 6

LBK merge: join each row on transaction-type / amount-type / amount-description against the Logic_Bridge_Key table. No match → UNMAPPED.

Phase 7

MarketsLogic lookup: translate the routing key into the actual account number for this marketplace (Debitor 30005 for DE, 30006 for FR…).

Phase 8

DATEV text fields: build Buchungstext (ORDER-PRICE-302-xxx…), Belegfeld1 and Belegdatum per row.

Phase 9

Group & sum: aggregate rows per order-id and account pair (Principal + Tax become one booking); zero-sum groups (commingling, debt pairs) disappear.

Phase 10

S/H direction, amount formatting and final DATEV 125 column order. Export as DATEV EXT or ASCII CSV.

Net Check After Every Run
Sum of all bookings on the Transit account (1363–1369) must equal zero once the bank row is booked. If it does not, a row was dropped or double-mapped — check the unmapped report first.

8. VTR → DATEV: Routing Logic

The VTR converter classifies every transaction into a Routing_Code using this exact decision order (from our production code):

1. COMMINGLING_SELL / COMMINGLING_BUY → own codes by DE/EU direction
2. Marketplace collects VAT (UK, CH)            → MARKETPLACE_COLLECTS
3. EXPORT_OUTSIDE_EU = YES or scheme = CH_VOEC  → EXPORT_OUTSIDE_EU
4. B2B (BUYER_VAT_NUMBER filled), DE → EU       → DE_EU_B2B_RC
5. B2B, EU warehouse → other country            → EU1_EU2_B2B_RC
6. DE → DE                                      → DE_DOMESTIC
7. DE → EU, scheme UNION-OSS                    → DE_EU_OSS
8. DE → EU, scheme REGULAR                      → DE_EU_REGULAR
9. EU → DE, scheme UNION-OSS                    → EU1_DE_OSS
10. EU → DE (otherwise)                         → EU1_DE_REGULAR
11. EU1 → EU2, scheme UNION-OSS                 → EU1_EU2_OSS
12. EU1 → EU1 (local)                           → EU1_EU1_LOCAL
TRANSACTION_TYPE = REFUND → same code + "_REFUND" (S/H flipped)

The Routing_Code is then looked up in the VTR Routing Logic table — current snapshot:

Routing_CodeKontoBU-SchlüsselEU-Land TypeS/H
DE_DOMESTIC8400——S
DE_EU_OSS8320240Bestimmung (destination)S
DE_EU_B2B_RC8125—Bestimmung (full VAT ID)S
EU1_DE_OSS8320285—S
EU1_EU2_OSS8320241Bestimmung (destination)S
DE_DOMESTIC_REFUND8400——H
DE_EU_OSS_REFUND8320240Bestimmung (destination)H
Gross, Not Net
The VTR Umsatz field must use the VAT-inclusive amount (Gross_Amount). Using TOTAL_ACTIVITY_VALUE_AMT_VAT_EXCL makes every 19% booking exactly 19% too low — a classic error we test for after every table change.

9. Invoice PDF Converter

Amazon fee invoices arrive as PDFs. The converter extracts invoice type, number, date and gross amount from each PDF (pdfplumber), then routes it through the Invoice Routing table (section 6) to produce one DATEV booking per invoice against the marketplace Creditor or the mapped expense ledger. Unrecognised invoice types route to 9998 for review — add the new type to the Invoice Routing table and re-run.

10. BU-Schlüssel / VAT Key Reference

BUMeaningVAT effect in DATEVWhere we use it
— (blank)Automatic account tax keyAccount splits VAT itself (8400 → 19%)DE domestic sales
9Vorsteuer 19% (input VAT)DATEV extracts 19% input VAT from grossFee invoices, shipping labels, ads invoices
0No VATNo VAT extractedConsolidated B-XML invoices
240OSS — departure DERoutes to OSS declaration, destination-country rateDE warehouse → EU customer
241OSS — EU cross-borderRoutes to OSS declarationEU warehouse → other EU country (and local EU1=EU1)
285OSS — back to GermanyRoutes to OSS declarationEU warehouse → DE customer
290Regular — EU warehouse → DEGerman 19% on 8400Non-OSS FBA configuration

11. EU VAT Rates Table (Standard + Reduced)

OSS bookings collect VAT at the destination country's standard rate (unless the product qualifies for a reduced rate). Snapshot as of 2026 — verify against the EU TEDB database before relying on it for a filing:

CountryStandardReduced ratesSuper-reduced
Austria (AT)20%10%, 13%—
Belgium (BE)21%6%, 12%—
Bulgaria (BG)20%9%—
Croatia (HR)25%5%, 13%—
Cyprus (CY)19%5%, 9%3%
Czech Republic (CZ)21%12%—
Denmark (DK)25%——
Estonia (EE)24%9%, 13%—
Finland (FI)25.5%10%, 13.5%—
France (FR)20%5.5%, 10%2.1%
Germany (DE)19%7%—
Greece (GR)24%6%, 13%—
Hungary (HU)27%5%, 18%—
Ireland (IE)23%9%, 13.5%4.8%
Italy (IT)22%5%, 10%4%
Latvia (LV)21%5%, 12%—
Lithuania (LT)21%5%, 12%—
Luxembourg (LU)17%8%, 14%3%
Malta (MT)18%5%, 7%—
Netherlands (NL)21%9%—
Poland (PL)23%5%, 8%—
Portugal (PT)23%6%, 13%—
Romania (RO)21%11%—
Slovakia (SK)23%5%, 19%—
Slovenia (SI)22%5%, 9.5%—
Spain (ES)21%10%4%
Sweden (SE)25%6%, 12%—

12. Trainee Workflow & QA Checklist

Step 1

Collect the period's settlement files (per marketplace), VTR file and invoice PDFs from Amazon Seller Central.

Step 2

Run the Settlement Converter (Admin → Settlement to DATEV). Check the stats panel: row counts, unmapped count, empty Gegenkonto warnings.

Step 3

If unmapped rows exist: download the unmapped report, identify the new transaction combination, add it to the LBK table, re-run.

Step 4

Run the VTR Converter. Verify OSS amounts per destination country look plausible against last period.

Step 5

Run the Invoice Converter on the PDF batch. Any unknown invoice type → add to Invoice Routing table.

Step 6

Download DATEV EXT exports and import into DATEV Unternehmen Online.

QA Checklist Before Delivering an Export

  • Zero rows on account 9998 (UNMAPPED)
  • Transit account nets to zero after the bank row
  • Account 1592 (debt adjustments) nets to zero
  • Every BU 240/241/285 booking has a filled EU-Land (else DATEV error REW00287/00283)
  • Amounts have no thousand separators (else REW01155)
  • Refund bookings carry flipped S/H direction vs. their sale counterpart
  • VTR amounts are gross (VAT-inclusive)

Common System Errors (Converter Internals)

Accounting-level DATEV errors (REW codes, open Creditor balances, reconciliation) are covered in the PAN-EU Accounting Guide, section 12. The errors below originate inside our conversion tooling:

SymptomCauseFix
Konto 9998 rows in the outputNew Amazon transaction combination not in the LBK tableRead the Zusatz 7/8/9 columns → add the row to the LBK table → re-run
EPR rows land on 9998Period date inside amount-type not stripped before the joinVerify fnStripPeriod is applied to both raw data and the LBK table
Gegenkonto null for all rowsCase mismatch in the LBK join ("Debitor" ≠ "DEBITOR")Verify fnNorm() is applied to the Logic_Bridge_Key column on both sides
Triple amount on 1730"Payable to Amazon" and "Successful charge" also routed to BANK-CHARGEMap them to Debt_Adjustment (1592) in the LBK table
Wrong S/H on the bank rowBank_Type mapping invertedBANK-DEPOSIT → H, BANK-CHARGE → S
VTR amounts ~19% too lowUmsatz built from TOTAL_ACTIVITY_VALUE_AMT_VAT_EXCL (net)Use the Gross_Amount (VAT_INCL) field
Document Information: Internal technical training — e-VATAX DATEV Converter suite. Table snapshots taken June 2026 from the live Lookup Tables; the admin panel always holds the current version. Companion reading: Amazon PAN-EU Accounting Guide.

Questions About the Conversion System?

Talk to the team or book a session to walk through a live conversion end-to-end.