Here you'll find descriptions of the individual fields of the DATEV export as well as a description of typical journal entries and accounts.
Description of the fields of a DATEV export
Field name | Description |
Umsatz (ohne Soll/Haben-Kz) | Amount of the payment |
Soll/Haben-Kennzeichen | S for payments, H for refunds |
WKZ Umsatz | We currently do not import any data into this field. |
Kurs | We currently do not import any data into this field. |
Basis-Umsatz | We currently do not import any data into this field. |
WKZ Basis-Umsatz | We currently do not import any data into this field. |
Konto | Clearing account of the payment method, or for cash deposits and withdrawals according to the configuration |
Gegenkonto (ohne BU-Schlüssel) | Collective debtor account of the payment method, or for cash deposits and withdrawals according to the configuration |
BU-Schlüssel | We currently do not import any data into this field. |
Belegdatum | Payment date (format: DDMM) |
Belegfeld 1 | If set accordingly in the configuration, the order number is exported here, otherwise the field remains empty. |
Belegfeld 2 | We currently do not import any data into this field. |
Skonto | We currently do not import any data into this field. |
Buchungstext | Order number, customer number |
Postensperre | We currently do not import any data into this field. |
Diverse Adressnummer | We currently do not import any data into this field. |
Geschäftspartnerbank | We currently do not import any data into this field. |
Sachverhalt | We currently do not import any data into this field. |
Zinssperre | We currently do not import any data into this field. |
Beleglink | The document link connects journal entries with document images. |
Beleginfo - Art 1 / Inhalt 1 | Sales Channel / Name of the Sales Channel in which the order was placed |
Beleginfo - Art 2 / Inhalt 2 | Export comment / The export comment for the payment stored in the order details |
Beleginfo - Art 3 / Inhalt 3 | Store / Name of the respective POS store. These fields are used for all journal entries created as a result of a DATEV export for a POS Sales Channel (receivables, chargebacks, payments, refunds, and cash deposits/withdrawals). For this, Pickware POS must be installed and activated. |
Beleginfo - Art 4 / Inhalt 4 | Transaction reference, if available |
Beleginfo - Art 5-8 / Inhalt 5-8 | We currently do not import any data into this field. |
KOST1 - Kostenstelle | Depending on the configuration, either the cost center of the Sales Channel or (if available) the cost center of the product is imported here. |
KOST2 - Kostenstelle | Depending on the configuration, either the cost center of the Sales Channel or (if available) the cost center of the product is imported here. |
Kost-Menge | We currently do not import any data into this field. |
EU-Land u. UStID (Bestimmung) | Country and VAT ID of the recipient. This field is only exported for line items with a delivery country in Europe (including Germany). |
EU-Steuersatz (Bestimmung) | Tax rate of the journal entry. This field is only exported for line items with a delivery country in Europe (not Germany). |
Abw. Versteuerungsart | We currently do not import any data into this field. |
Sachverhalt L+L | We currently do not import any data into this field. |
Funktionsergänzung L+L | We currently do not import any data into this field. |
BU 49 Hauptfunktionstyp | We currently do not import any data into this field. |
BU 49 Hauptfunktionsnummer | We currently do not import any data into this field. |
BU 49 Funktionsergänzung | We currently do not import any data into this field. |
Zusatzinformation - Art 1 / Inhalt 1 | Company |
Zusatzinformation - Art 2 / Inhalt 2 | Title |
Zusatzinformation - Art 3 / Inhalt 3 | First name |
Zusatzinformation - Art 4 / Inhalt 4 | Last name |
Zusatzinformation - Art 5-20 / Inhalt 5-20 | We currently do not import any data into this field. |
Stück | We currently do not import any data into this field. |
Gewicht | We currently do not import any data into this field. |
Zahlweise | We currently do not import any data into this field. |
Forderungsart | We currently do not import any data into this field. |
Veranlagungsjahr | We currently do not import any data into this field. |
Zugeordnete Fälligkeit | We currently do not import any data into this field. |
Skontotyp | We currently do not import any data into this field. |
Auftragsnummer | Order number |
Buchungstyp (Anzahlungen) | We currently do not import any data into this field. |
Ust-Schlüssel (Anzahlungen) | We currently do not import any data into this field. |
EU-Land (Anzahlungen) | We currently do not import any data into this field. |
Sachverhalt L+L (Anzahlungen) | We currently do not import any data into this field. |
EU-Steuersatz (Anzahlungen) | We currently do not import any data into this field. |
Erlöskonto (Anzahlungen) | We currently do not import any data into this field. |
Herkunft-Kz | We currently do not import any data into this field. |
Buchungs GUID | We currently do not import any data into this field. |
KOST-Datum | We currently do not import any data into this field. |
SEPA-Mandatsreferenz | We currently do not import any data into this field. |
Skontosperre | We currently do not import any data into this field. |
Gesellschaftername | We currently do not import any data into this field. |
Beteiligtennummer | We currently do not import any data into this field. |
Identifikationsnummer | We currently do not import any data into this field. |
Zeichnernummer | We currently do not import any data into this field. |
Postensperre bis | We currently do not import any data into this field. |
Bezeichnung SoBil-Sachverhalt | We currently do not import any data into this field. |
Kennzeichen SoBil-Buchung | We currently do not import any data into this field. |
Festschreibung | 0 – The journal entries will not be finalized in DATEV after import. Finalization is carried out by your tax advisor. |
Leistungsdatum | We currently do not import any data into this field. |
Datum Zuord.Steuerperiode | We currently do not import any data into this field. |
Fälligkeit | We currently do not import any data into this field. |
Generalumkehr (GU) | We currently do not import any data into this field. |
Steuersatz | We currently do not import any data into this field. |
Land | We currently do not import any data into this field. |
Abrechnungsreferenz | We currently do not import any data into this field. |
BVV-Position | We currently do not import any data into this field. |
EU-Land u. UStID (Ursprung) | We currently do not import any data into this field. |
EU-Steuersatz (Ursprung) | We currently do not import any data into this field. |
Configuring the "Auftragsnummer" field
The Auftragsnummer is an additional field on the order that by default contains the order number. Depending on the configuration in Pickware, one of the following values can be exported here, for example if you want to store transaction references or marketplace order numbers:
Order number
External order number
External order number, order number if empty
Under Settings → Extensions → DATEV → journal entry section, you can use the Auftragsnummer option to determine which value is exported to this field for receivables and payments.
When using Shopify, a corresponding metafield "Externe Auftragsnummer (Pickware)" is available for this purpose. It can be filled either manually or via Shopify Flow (e.g. through marketplace integrations such as magnalister or Shopify Marketplace Connect). The content of the metafield is automatically transferred to the additional field in Pickware.
DATEV allows a maximum of 30 characters for the Auftragsnummer. If the value is longer, an error is output per line in the export and the order number is used instead.
Automatic recording of Shopify payments
If you use Shopify as a Sales Channel, payment transactions from Shopify can be automatically created in Pickware as DATEV payments and flagged for export. To do this, enable the checkbox Automatic recording of Zahlungen und Rückerstattungen in the DATEV configuration.
Excluding specific payment methods
In the DATEV configuration, under "Ausgeschlossene Zahlungsarten", you can specify which payment methods should not be recorded automatically.
Shopify POS orders are not supported by the current DATEV export and are therefore automatically excluded as a payment method. You can also recognize this in the corresponding orders by this note:
Supported Shopify payment transactions
Only payment transactions of type SALE (incoming payment), REFUND (refund), and CAPTURE (subsequently captured payment) are automatically taken into account. Only payment transactions with the status SUCCESS are imported. Exactly one DATEV payment is created for each transaction, including payment amount, payment date, and payment reference. The payment reference corresponds to the Shopify paymentId of the respective payment transaction.
Retroactively recording payments
If you initially disabled automatic recording of payments, you may want to retroactively record payments for your orders. To do this, you can simply trigger a (re-)import of the affected orders, for example by adding a tag in Shopify or by using the In Pickware öffnen button on the order in Shopify. Missing DATEV payments are created automatically during the import.
Shopify POS orders
Shopify POS orders cannot be invoiced via Pickware. Accordingly, receivables or payments are not part of the DATEV export. As a result, no automatic DATEV payments are created for these orders either. You can find out more about handling Shopify POS orders here.
Description of typical journal entries and accounts
The following two types of accounts are commonly used:
Revenue accounts:
A revenue account can be described as a sub-account of equity and is used to determine profit. For example, when goods are sold, the incoming payment represents sales revenue, which is posted through the revenue account and closed via the profit and loss account.
Debtor accounts:
Debtor accounts record receivables, invoice corrections, and open items from a company's deliveries and services. This means that as soon as a customer completes an order, a receivable arises against the company, which is represented by a debtor account. For collective debtor accounts, the accounts are managed and named depending on the payment method.
The DATEV export contains individual journal entries in DATEV format. Each journal entry represents either a receivable or a payment. The following examples show which journal entries the plugin creates for the respective business processes.
Business processes:
1.) A payment transaction of €50
2.) A refund of €50
Corresponding journal entries:
1.) Clearing account €50 to debtor account €50
2.) Debtor account €50 to clearing account €50
Account representation for the business processes:
Debtor account | Debtor account |
2.) €50 | 1.) €50 |
Clearing account | Clearing account |
1.) €50 | 2.) €50 |