TaxRouter Logo
BlogIntegrationsPricingAboutContact
Log inStart now
All articles
Bookkeeping2 November 20265 min read

How to correct a past DATEV booking without importing it twice

If you need to correct a past marketplace or payment booking, the key question is whether you can amend the existing DATEV record or need a separate correction. The practical difference matters because copied or moved postings are exported and then imported again when they are inserted once more, so a second pass through the interface can create a duplicate import if you treat the correction like a new transaction.

TaxRouter editorial team

A finance lead reviewing booking records on a laptop beside printed receipts and a notepad at a desk

Start with the booking record you already have

For a past correction, first check whether the original transaction is already captured as a complete booking record in DATEV. The Buchungsdatenservice transfers complete booking records, including booking data, master data, and related receipt images. That matters because a correction to a historical booking is not the same thing as creating a fresh import from the source system.

In DATEV’s data-services setup, structured data and digital receipts are transferred into DATEV programs, and in some cases the flow can also run in the reverse direction. For your decision, the important point is that you are dealing with a structured booking record rather than a free-form note or a standalone receipt image. If the booking already exists, the question is whether the correction changes that record or creates another one alongside it.

  • A booking record can already contain booking data, master data, and receipt images.
  • A historical correction should be assessed against the existing record, not treated automatically as a new transaction.
  • The transfer flow can involve structured data in both directions depending on the setup.

Sources: [1], [2]

Why duplicate imports happen

DATEV’s help center says that copied or moved postings are exported and then imported again when they are inserted once more. That is the direct reason a historical correction can turn into a second import if you duplicate the posting instead of adjusting the existing one. The system behavior described there is about reposting the entry, not about changing the accounting substance of the original record.

For an ecommerce finance lead, the practical takeaway is simple: if your correction method creates another posting object, you should expect it to go through the import process again. If your goal is only to amend the history of the original booking, a copied or moved posting is not the same thing as a correction in place.

  • Copied or moved postings are exported and imported again when inserted once more.
  • A duplicate import risk appears when the correction is handled as a new posting object.
  • Changing the existing record is different from inserting a second posting.

Sources: [4]

Separate the chart of accounts from the receipt assignment

DATEV distinguishes the chart of accounts from the concrete account assignment of individual receipts. That distinction is useful when you are deciding where a historical correction belongs. The chart of accounts is the structure; the receipt assignment is the specific booking of a particular document or transaction.

If the problem is that a transaction was assigned to the wrong account, the correction concerns the concrete account assignment, not the existence of the chart of accounts itself. In other words, you are not redesigning the bookkeeping structure just because one marketplace or payment booking was entered incorrectly. That makes it easier to keep the correction tied to the original booking record instead of recreating the import.

  • The chart of accounts is not the same as the individual account assignment of one receipt.
  • A wrong booking usually points to the specific assignment, not the overall account structure.
  • Keeping the correction at the booking level helps avoid turning one item into two imports.

Sources: [3]

When a historical change needs its own correction

Not every historical change belongs inside the original booking record. § 17 UStG requires correction when the tax base changes, and the correction is made for the assessment period in which the change occurred. That means a later change can require a separate correction step rather than a silent edit to the earlier booking. The tax-law point here is about the period in which the change is recognized, not about how the software interface should be used.

A separate correction is relevant when the original record no longer matches the changed basis for the booking. In that case, you are not trying to make the old entry disappear; you are documenting the change in the period to which it belongs. The accounting decision is therefore between preserving the original booking and recording the later adjustment as its own event.

  • A change in the tax base can require correction in the assessment period when the change occurred.
  • A later adjustment may need its own correction entry rather than a replacement of the original booking.
  • The timing of the change matters for the correction period.

Sources: [5]

Keep the evidence chain intact

If you correct a past booking, the underlying evidence still has to remain traceable. § 257 HGB requires retention of bookkeeping evidence and sets the start of the retention period at the year-end in which the document arose. For historical corrections, that means the receipt and the booking history must remain connected enough to support the record over time.

This is where the distinction between a correction in the existing record and a separate correction matters operationally. The retention rule does not tell you how to post the change, but it does mean the original evidence cannot simply disappear when you adjust the booking. If the correction is separate, keep the link to the original document clear. If the correction stays in the existing record, make sure the audit trail remains readable. This article provides general information and is not tax or legal advice.

  • Retain the bookkeeping evidence connected to the original document.
  • The retention period starts at year-end in which the document arose.
  • Whatever correction method you use, the evidence chain should stay readable.

Sources: [6]

Sources

  1. [1] DATEV DatenservicesDATEV
  2. [2] DATEV Buchungsdatenservice ProzessgrafikDATEV
  3. [3] Kontenplan in der Buchhaltung: SKR03 & SKR04DATEV
  4. [4] Buchungen in einen anderen Buchungsstapel kopieren oder verschiebenDATEV Hilfe-Center
  5. [5] § 17 UStGGesetze im Internet
  6. [6] § 257 HGBGesetze im Internet

Sources checked: 2 November 2026

TaxRouter

Bring your sales data and bookkeeping together

Create your workspace
TaxRouter Logo

Bring e-commerce data together and move it reliably into DATEV.

Follow TaxRouter

LinkedIn

Product

  • Blog
  • Solutions
  • Integrations
  • Pricing
  • Alternatives
  • How TaxRouter works

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  • Security & Data Handling
  • Data Processing Addendum
  • Subprocessors
  • Technical and Organizational Measures
  • Imprint

Copyright 2026 TaxRouter. All rights reserved.