All Collections
Add-On for DATEV Self Bookers
Functionalities in Candis & Import into DATEV
How does the core data export work with the add-on for DATEV self-bookers?
How does the core data export work with the add-on for DATEV self-bookers?

How the import of core data and payment conditions into DATEV Rechnungswesen works and what needs to be considered in the process

Pascale Bastian avatar
Written by Pascale Bastian
Updated over a week ago

Part of the add-on for DATEV self-bookers is the seamless export of core data and payment conditions to DATEV Rechnungswesen.

In the current version of the export, all business partners and payment conditions created in Candis are exported with each export.

Before the first export

Before exporting core data and payment conditions for the first time, you should make sure that the existing data in Candis is also up-to-date and matches the data in DATEV Rechnungswesen.

The easiest way to do this is via the contact import. By importing business partner data from DATEV Rechnungswesen, you can supplement (not overwrite) missing data in Candis.

The system uses the account number, VAT ID number, tax number, and/or exact business partner name to determine whether the business partner already exists and then adds any missing data.

You can find out how this works in this article.

How is the core data imported into DATEV Rechnungswesen?

  1. Click on 'Mandant ergänzen' in the menu on the left.
    A screen opens, select 'Beleg-/Buchungsstapel und Stammdaten (RZ)' and click on 'Daten holen' to fetch the data from the data center.

  2. Then click on 'Stapelverarbeitung' in the menu on the left.

    You can now see three batches: one for the invoices, one for the business partners and one for the payment conditions. Select the 'Business partner' batch and click on 'Verarbeiten'.

Only now is data imported from Candis to DATEV Rechnungswesen and the core data is updated. Matching works via the account number.

If business partner core data is not to be imported to DATEV Rechnungswesen, for example because there were no updates, the batch can be deleted (without processing).

How does the updating of fields in DATEV Rechnungswesen work during import?


DATEV Rechnungswesen

Import Logic

Field exists

Field exists

Data is overwritten

Field exists, but is empty

Field exists

Field is skipped

Field does not exist

Field exists

Field is skipped


Business partner A has a new IBAN and you update the IBAN in the contact field in Candis. With the next export, the updated core data is exported to DATEV Rechnungswesen and imported via batch processing.

With this import of the data, the IBAN is updated (overwritten) for Business Partner A in DATEV Rechnungswesen. All other fields and data at business partner A remain unaffected.

How are payment conditions imported into DATEV Rechnungswesen?

The import of payment conditions works exactly like the import of core data, except that, during batch processing, the batch 'Zahlungsbedingungen' is selected and processed.

The imported payment conditions are displayed under Stammdaten > Kreditoren > Zahlungsbedingungen.

Payment conditions stored with business partners can be viewed via Kreditor > OPOS Allgemein.

To learn how to use payment conditions in Candis to define fixed discount periods for your business partners, click here.

Did this answer your question?