Every payable you export from Spendesk, and every payment, arrives in DATEV Rechnungswesen as its own batch. You don't have to process them one by one. Select all the batches of a month, process them in one go, and DATEV puts them into a single booking batch. It takes about six clicks, whether the month has 5 invoices or 500.
Why there is one batch per payable
Spendesk sends each payable to DATEV separately, so that one payable with an error doesn't block the others. DATEV turns each one into a batch in Stapelverarbeitung (batch processing), named after the journal and the month:
Eingangsrechnung - 10-2026 (incoming invoices) for the invoices, card purchases and expense claims of October 2026;
Bank … - 10-2026 for their payments.
Process the batches of a month in one go
In DATEV Rechnungswesen, open the client and go to Buchführung › Vorbereitende Tätigkeiten › Stapelverarbeitung (Bookkeeping › Preparatory tasks › Batch processing).
Click the Bezeichnung (name) column header: the batches are now grouped by journal and month.
Click the first batch of the month, then hold Shift and click the last one (1). Select one journal and one month at a time, for example all the Eingangsrechnung - 10-2026 batches.
Tick Stapel bei der Verarbeitung zusammenfassen (merge batches when processing) (2). DATEV doesn't remember this box: tick it each time.
Click Verarbeiten (process) (3).
The first time, DATEV explains the next window. Tick Meldung nicht mehr anzeigen (don't show this message again) so it doesn't come back, then click OK.
In Stapel anhängen (append to batch), select the booking batch (Buchungsstapel) of that month, for example 10-2026/0001 Eingangsrechnung - 10-2026 (4), and click OK (5). If the month has no booking batch yet, click Neuen Buchungsstapel anlegen (create a new booking batch).
DATEV confirms: Der/die Stapel wurden verarbeitet (the batch(es) were processed). Click OK.
Then do the same for the payment batches (Bank … - 10-2026, bank journal), into the bank journal's booking batch for that month.
If some entries have a warning (for example a tax key DATEV doesn't accept), DATEV first shows an import log (Importprotokoll). Close it. DATEV then asks what to do: keep Auch Buchungssätze mit Fehlern oder Hinweisen übernehmen (also take entries with errors or warnings) to take all entries, and correct the flagged ones in the Primanota (posting journal) afterwards.
The result in the Primanota (posting journal)
All the entries of the month are in one booking batch (6), each with its own date, accounts, cost centres and document number (7). Your accountant reviews them and makes them final (Festschreibung, locking the entries) as usual.
Why tick "Stapel bei der Verarbeitung zusammenfassen" (merge batches when processing)? Without it, DATEV still processes all the selected batches with one click, but makes one booking batch per Spendesk batch. With it, they all go into the month's booking batch.
DATEV terms used here
DATEV (German) | English |
Stapelverarbeitung | Batch processing |
Stapel | Batch |
Buchungsstapel | Booking batch |
Bezeichnung | Name |
Eingangsrechnung | Incoming invoices (purchase journal) |
Periode | Period |
Stapel bei der Verarbeitung zusammenfassen | Merge batches when processing |
Verarbeiten | Process |
Stapel anhängen | Append to batch |
Neuen Buchungsstapel anlegen | Create a new booking batch |
Meldung nicht mehr anzeigen | Don't show this message again |
Der/die Stapel wurden verarbeitet | The batch(es) were processed |
Importprotokoll | Import log |
Auch Buchungssätze mit Fehlern oder Hinweisen übernehmen | Also take entries with errors or warnings |
Primanota | Posting journal |
Festschreibung | Finalisation (locks the entries) |
Good to know: if you export the same payable twice (for example after a failed export), you'll see two batches for it. Delete the extra one in Stapelverarbeitung before you process, so the entry isn't booked twice.







