Bundling E-Commerce Transactions: Consolidate Orders into Summary Accounting Entries

A growing online retailer can generate thousands of orders, payments, refunds and fees within a few days. If every event is exported as a separate journal entry, the accounting system receives extremely large posting batches. The volume makes review harder, increases import processing and produces general-ledger accounts filled with repetitive descriptions.

The solution is not to delete the underlying orders or invoices. It is to distinguish two layers:

Operational individual transactions remain available with order number, invoice number, VAT rate, marketplace, payment reference and all relevant detail.

Consolidated accounting entries combine compatible transactions for export to DATEV or another accounting system.

KudTax therefore does not merge several legally independent invoices into a new invoice. The accurate description is:

KudTax bundles compatible orders, sales and transactions into consolidated accounting entries for the accounting export.

The invoice remains the supporting document for the individual supply. The summary entry is a controlled representation of compatible transactions in the general ledger.

Why individual entries quickly become difficult to manage

In a conventional B2B company, 500 invoices may result in approximately 500 sales postings. An e-commerce order can generate several accounting events:

sale and output VAT,
shipping,
discount,
payment,
payment fee,
marketplace commission,
later partial refund,
return,
chargeback,
provider payout.

A merchant selling through Amazon Germany, Amazon France, Shopify and eBay multiplies the number of variants. Several VAT rates, warehouse countries, currencies and revenue accounts can also be involved.

Exporting every order as an individual posting can be correct, but large volumes create practical disadvantages:

very large DATEV posting batches,
long general-ledger reports,
higher import and processing effort,
limited visibility of period totals,
more effort reviewing identical entries,
technical file limits,
reports that are harder for clients and accountants to read.

DATEV states a maximum of 99,999 entries per posting-batch file. This does not mean every business must aggregate its data, but it demonstrates why controlled consolidation or period-based file separation can become relevant at scale.

What is a summary accounting entry?

A summary entry combines individual transactions that share the same accounting characteristics.

Assume 1,800 Amazon Germany orders between 1 and 15 January all use:

debit account 1800,
credit account 4400,
Amazon Germany marketplace,
EUR,
the same VAT treatment,
the same export period.

Instead of creating 1,800 export rows, the system can add the amounts and produce:

15 Jan – 4400 to 1800 – Amazon DE Orders

The 1,800 orders remain individually available in the source system. The summary posting must be expandable into the list of included transactions.

It is not a new order or invoice. It is a general-ledger posting based on documented source events.

Individual versus summary entries

Feature	Individual entry	Summary entry
Export rows	One per transaction or component	One for several compatible transactions
General-ledger detail	Very high	Consolidated
Source-system detail	Individual record available	Individual record must remain available
Account report	Many lines	Period or group totals
Open-item suitability	Useful for invoice-level clearing	Not suitable for every debtor model
Import volume	High	Reduced
Review	Direct individual review in accounting	Review through summary and drill-down report
Typical use	B2B invoices, special cases, open items	compatible B2C mass transactions

Both methods can be combined. Debtor invoices can remain individual while selected general-ledger movements are consolidated.

Is consolidation compatible with German GoBD requirements?

German GoBD principles generally require transactions to be complete, correct, timely, ordered and traceable. Individual records should allow the basis, content and significance of each transaction to be reviewed.

At the same time, consolidated records in the general ledger can be acceptable where they can be broken down into the individual positions in the journal or primary records.

A traceable summary process therefore requires:

every source transaction remains stored,
every transaction has an unambiguous summary-entry assignment,
the calculation can be reproduced,
filters, criteria and period are documented,
changes remain traceable,
invoices and supporting documents remain accessible,
individual data can be exported and analysed,
the process is included in procedural documentation.

Consolidation must not make the original record impossible to determine. Section 239 of the German Commercial Code requires the original content to remain identifiable when records are changed.

The specific model should be agreed with the responsible German tax adviser. Not every transaction is suitable for aggregation.

Which criteria can KudTax use for bundling?

During export, the user activates the bundling function and selects which transactions may enter the same accounting entry. The conditions are combined; only records meeting all selected criteria belong to the same bundle.

Period

The user can define separate date ranges, for example:

1 to 15 January,
16 to 31 January.

This creates two postings even where platform and accounts are identical.

Daily, weekly, semi-monthly and monthly groups can be appropriate. The process must also define which source date is used: order date, invoice date, service date, payment date or another transaction date.

Debit and credit accounts or accounting codes

Only entries with compatible account mapping should be grouped. KudTax can use accounting codes or debit and credit accounts as bundling criteria.

For example, all records using credit account 4400 and debit account 1800 can be grouped within the selected period.

Transactions using another revenue, tax, fee or clearing account remain in a separate group. This prevents different economic events from disappearing into one unexplained total.

Platform

The platform is the main sales channel or system, such as Amazon, Shopify, eBay or Kaufland.

Grouping by platform prevents Amazon and Shopify from entering the same summary entry even where amounts are posted to similar accounts. The channels may use different data sources, payment processes and control reports.

Marketplace

One platform can contain several marketplaces. Amazon Germany, France, Italy and Spain should be distinguishable.

Marketplace-level grouping supports a clear separation of Amazon Germany, Amazon France and Amazon Italy. This is particularly important where VAT country, rate, account or currency differs.

Posting date of the summary entry

The user chooses the posting date assigned to the consolidated entry. A bundle covering 1 to 15 January can use 15 January.

The summary date does not replace the original invoice, service or transaction dates, which remain stored at source level. It controls the presentation and period assignment in the accounting export and must fit the approved accounting process.

Custom posting text

The posting description can be set individually or dynamically, for example:

Amazon DE Orders 01-15,
Shopify DE Sales January,
Amazon FR 20% VAT,
eBay Payments Week 03.

DATEV limits the booking-text field in a posting batch to 60 characters. Longer details should therefore remain in the drill-down report, additional information or source system.

Practical example: Amazon Germany sales from 1 to 15 January

The user selects:

Setting	Selection
Period	1 Jan–15 Jan
Accounts	4400 to 1800
Platform	Amazon EU
Marketplace	Germany
Posting date	15 Jan
Posting text	Amazon DE Orders

The period contains 2,400 matching orders with a combined amount of €142,800.00.

KudTax creates:

15 Jan – €142,800.00 – 4400 to 1800 – Amazon DE Orders

The system continues to retain:

all 2,400 order numbers,
invoice numbers,
individual values,
original dates,
item and VAT information,
marketplace assignment,
payment references,
assignment to the summary entry.

A second entry can be generated for 16 to 31 January.

Extended example with several groups

Period	Marketplace	VAT/account group	Export description
1–15 Jan	Amazon DE	German 19% / 4400 to 1800	Amazon DE 19% 01-15
1–15 Jan	Amazon DE	German 7% / separate revenue account	Amazon DE 7% 01-15
1–15 Jan	Amazon FR	French standard rate / separate account	Amazon FR STD 01-15
16–31 Jan	Amazon DE	German 19% / 4400 to 1800	Amazon DE 19% 16-31
16–31 Jan	Amazon FR	French standard rate / separate account	Amazon FR STD 16-31

The number of export lines is reduced without mixing rates, countries or accounts.

Which transactions should not be bundled together?

Transactions need to be economically and technically compatible. They should normally remain separate where they involve:

different debit or credit accounts,
different VAT rates,
different VAT countries,
different currencies,
taxable and exempt sales,
different B2B and B2C treatments,
sales and refunds where controls require separate presentation,
revenue and marketplace fees,
customer payments and bank payouts,
open chargebacks and final revenue corrections,
different accounting periods,
domestic and OSS sales,
different marketplace deemed-supplier status,
invoice-level debtors requiring open-item clearing.

The more criteria that genuinely match, the more reliable the summary entry.

Orders, invoices, transactions and journal entries are different

Order

The order records what the customer requested. It can later be cancelled, split or changed.

Invoice

The invoice is the legal and tax document. The bundling function does not merge independent invoices into one new invoice.

Transaction

A transaction is a financial or operational event such as payment, refund, fee, reserve or payout. One order can generate several transactions.

Accounting entry

The accounting entry transfers the financial effect to the ledger. An individual entry can represent one transaction; a consolidated entry can represent several compatible transactions.

KudTax consolidates the export accounting layer. It does not replace the source orders or invoice documents.

Benefits of consolidation

Fewer general-ledger entries

Thousands of compatible orders can be reduced to a few entries by period, accounts and marketplace.

Clearer account reports

Instead of repetitive lines, the ledger shows clearly described totals with drill-down available in the source system.

Faster processing

Smaller batches can be easier to transmit, import and validate, especially where transaction volumes approach technical file limits.

Clear marketplace and account separation

Grouping rules prevent uncontrolled mixing of channels and account groups.

Flexible period logic

Users can form weekly, semi-monthly or monthly bundles and choose the posting date.

Reduced manual review

The accounting firm reviews criteria, totals and drill-down reports rather than reading thousands of identical lines.

Repeatable exports

Approved settings can be reused for recurring exports while accounting and VAT logic remains unchanged.

Risks and disadvantages

Over-aggregation can hide relevant information. Risks include:

no direct individual line in the general ledger,
difficult open-item clearing,
mixed VAT cases,
undocumented calculations,
incorrect period assignment,
duplicate exports,
differences between source and DATEV,
weak procedural documentation,
lost order or document references,
difficult tax audits without drill-down reports.

Controlled grouping requires fixed rules, version history, export IDs and complete traceability.

How KudTax bundles e-commerce accounting data

Select the data: The user chooses the export period and sources.
Apply accounting rules: Each order or transaction receives approved accounts, tax treatment and other attributes.
Activate bundling: The user groups by period, accounting codes, platform and marketplace.
Set posting date and text: Each group receives its export date and description.
Sum compatible values: Only transactions meeting all criteria are consolidated.
Create the export: KudTax produces the summary entries for DATEV or another supported system.
Retain the assignment: Every source record remains stored and connected to its bundle.

Control report for each bundle

A strong drill-down report should contain:

unique bundle or export ID,
creation date,
source period,
date type used,
platform and marketplace,
debit and credit account,
tax or booking key,
currency,
number of source records,
net, tax and gross totals where relevant,
posting date,
posting text,
list or export of included transactions,
rule version,
user and approval status,
later corrections or reversals.

This allows an accountant to move from a summary posting to its source transactions and from an order to the bundle containing it.

Returns and later changes

E-commerce data can change after export. A February return can relate to an order included in a January bundle. The January export should not be silently changed.

The return is processed as a new correction in the appropriate period and remains linked to the original order and invoice.

The system should identify:

whether the original transaction was exported,
which bundle contains it,
which correction is required,
whether a separate correction bundle should be formed,
whether a controlled reversal and re-export is permitted.

Finalised accounting records should not be overwritten without a traceable process.

Can a summary entry replace open-item accounting?

Not in every case. Open-item processes often require invoice, customer or order-level allocation. Consolidating debtor entries can remove the required detail from DATEV.

Possible models include:

Individual debtor entries with consolidated general-ledger components: Invoices and payments remain detailed in the subledger while selected ledger movements are grouped.

Platform or collective debtor: High-volume B2C transactions use a controlled collective process while transaction detail remains in the source system.

Full individual posting: Important B2B invoices, disputed receivables and special cases remain separate.

The appropriate method depends on invoicing, payment reconciliation, chart of accounts and the tax firm’s workflow.

Export to DATEV and other accounting systems

The DATEV format is a CSV-based interface for structured accounting data. DATEV recommends a separate file for each posting period. Consolidation can support this period concept by creating clearly separated monthly or semi-monthly entries.

DATEV posting batches can contain:

amount and debit/credit indicator,
account and contra account,
booking key,
document date and fields,
posting text,
order number,
service date,
currency,
additional information,
booking GUID.

Consolidation takes place before export. DATEV receives the final summary entry, while individual transactions and the drill-down report remain in the source and archive environment.

KudTax can also prepare exports for other accounting systems, where supported fields and aggregation rules may differ.

Simplified DATEV export example

Date	Amount	Account	Contra account	Posting text
15 Jan	€142,800.00	4400	1800	Amazon DE Orders 01-15
31 Jan	€151,420.00	4400	1800	Amazon DE Orders 16-31
15 Jan	€48,900.00	4125	1800	Amazon FR Sales 01-15
31 Jan	€52,760.00	4125	1800	Amazon FR Sales 16-31

The first line can represent 2,400 individual orders, the second 2,610 and the French entries additional transactions. The DATEV file remains concise while the drill-down contains every source record.

Controls for the tax firm

Before approval, the firm should confirm:

All expected platforms and marketplaces are included.
Periods are complete and do not overlap.
Previously exported transactions are excluded.
Accounts and tax keys match approved mappings.
Countries, VAT rates and currencies remain separate.
Every summary entry can be expanded into source records.
Bundle, control report and DATEV totals agree.
Invoices and documents remain accessible.
The posting date is appropriate.
Returns and corrections are traceable.
The rule version is documented.
New or unusual event types were reviewed or excluded.

Common bundling errors

Error 1: Saying that invoices are merged

The function consolidates accounting entries, not legally independent invoice documents.

Error 2: Mixing VAT rates

Different VAT rates generally require separate tax or account groups.

Error 3: Combining Amazon Germany and France

Marketplace, tax country and potentially currency must remain separate.

Error 4: Netting sales and fees

Revenue and marketplace expenses must not be hidden in one net entry.

Error 5: Deleting source transactions after export

Consolidation is auditable only where primary records and documents remain available.

Error 6: Replacing the service date with the bundle date

The export date must not overwrite tax-relevant source dates.

Error 7: Silently changing old bundles after returns

Corrections need a new documented event or a controlled reversal and replacement.

Error 8: Providing no drill-down report

Without the transaction list, the total cannot be reviewed efficiently.

Error 9: Ignoring open-item requirements

Not every debtor and payment process can be consolidated.

Error 10: Changing grouping rules without version history

The same source data can otherwise produce different totals without explanation.

When is bundling particularly useful?

It is particularly suitable where:

large numbers of compatible B2C orders exist,
account mappings are stable,
invoice-level open-item tracking is not required in the general ledger,
all source transactions remain stored,
platform, marketplace, currency and VAT are clearly separated,
a control report is available,
the tax adviser has approved the process.

It is less suitable for a small number of material individual invoices, individual B2B debtors, disputed receivables, new transaction types, uncertain VAT cases or transactions without complete documents.

Frequently asked questions

What does bundling e-commerce transactions mean?

Compatible orders or transactions are added together into one consolidated accounting entry for export. The individual source transactions remain available.

Does KudTax merge several invoices into one invoice?

No. Invoices remain independent documents. KudTax consolidates the compatible accounting entries derived from them.

Which bundling criteria are available?

Transactions can be grouped by period, accounting codes or debit and credit accounts, platform and marketplace. Users can also define the posting date and text.

Can I group 1–15 and 16–end of month separately?

Yes. Both ranges can be configured as separate groups with their own totals, dates and descriptions.

Can Amazon Germany and France be combined?

They should remain separate where country, VAT or account treatment differs, which is common in cross-border commerce.

Can 7% and 19% German VAT sales be grouped together?

Not in the same tax posting. Different VAT rates and the relevant revenue accounts or keys should form separate groups.

Do individual Amazon orders remain traceable?

Yes. Source orders and transaction details remain stored in KudTax and are assigned to the relevant bundle.

Is a summary posting compliant with GoBD?

Consolidated general-ledger records can be acceptable when they can be fully expanded into the primary records and traceability, immutability, document access and procedural documentation are ensured. The specific workflow should be agreed with the tax adviser.

Does consolidation reduce the number of invoices?

No. It only reduces the number of export posting lines.

Can Shopify orders be bundled for DATEV?

Yes, where the selected records have compatible accounts, VAT, currency and period attributes and the accounting workflow allows consolidation.

What happens when an order is returned later?

The return is processed as a correction in the relevant period and linked to the original order. An already exported bundle should not be changed silently.

Is a report required for every bundle?

A drill-down and control report is strongly recommended. It explains the period, criteria, accounts, transaction count and calculation of the total.

Conclusion: Thousands of orders can become a small number of auditable entries

A high number of e-commerce orders does not have to create an unreadable general ledger. Compatible transactions can be consolidated by period, accounts, platform and marketplace.

The quality of the process is not measured only by how many lines it removes. The decisive factor is the connection between the summary entry and each operational transaction. Every total must be reproducible. Every order must remain searchable. VAT treatments, countries, currencies and accounts must not be mixed without control.

KudTax allows users to configure bundling during export. Periods, accounting codes, platform, marketplace, posting date and text can be adapted to the client’s accounting workflow. The result is a clearer DATEV or accounting export while the original orders and transaction details remain traceable.

Create a free KudTax account and consolidate high-volume e-commerce data into controlled accounting exports.

Official and further sources

This article provides general information and does not constitute tax, legal or GoBD advice. The suitability and scope of summary postings should be agreed with the responsible tax firm based on the company’s invoicing, open-item, VAT and control processes.

Bundling E-Commerce Transactions: Consolidate Orders into Summary Accounting Entries by Period, Account and Marketplace