Guide · As of

Zusammenfassende Meldung with AI: check sales and enter them in ELSTER

First check which sales actually belong in your Zusammenfassende Meldung (ZM). The assistant can read authorised sources through MCP, prepare a verifiable schedule and enter confirmed values using an additional browser function. VAT ID, transaction type and reporting period must be clarified.1

Who is it for? Managing directors doing their own bookkeeping for a German GmbH/UG, with deliberately authorised data access; the case assumptions apply only to the respective example.3

Not every EU document belongs in the ZM

This work plan covers a limited case of other B2B services supplied by a German business to a business in another EU member state. Under the confirmed case assumption, the recipient owes the tax there; exceptions to the place-of-supply rules are excluded.

Intra-Community supplies of goods, triangular transactions, corrections and other special cases need their own assessment. A foreign SaaS purchase invoice is not, merely because of reverse charge, a separate reportable sale in this example.

Basics: UStG § 18a · UStG § 3a

Bring individual details together before completing the form

Read sales documents and their related postings and revenue accounts. A VAT report alone does not automatically contain all recipient, service and verification details needed for the ZM.

The company ID, your own VAT ID, the recipient's actual VAT ID, service type, service date, currency, tax base and correct reporting period belong in the schedule. A number that looks formally plausible does not replace actual VAT ID verification.

On narrow screens, you can scroll the table sideways. With a keyboard, focus the table first.

Data needed before the ZM
DetailSource and reviewIf information is missing
Your own identity and VAT IDCompany master data and actual allocationStop and have the specific number confirmed
Recipient and VAT IDOriginal document/contract, partner details, separate verification evidenceDo not generate a number; do not infer verification from its format
Transaction type and service periodService description and tax assessmentNot a summary of all EU transactions
Tax base and signsSales documents, revenue accounts, adjustments and currencyClarify the difference; do not replace a missing value with 0

Fictional case: two services supplied, one separate purchase invoice2

Muster-Service GmbH (synthetic) supplies two consulting services classified accordingly to the same French business in the third quarter of 2026: 1,200 EUR on 20 July and 800 EUR on 15 August. All amounts and facts are explicitly invented; VAT ID placeholders are not entered into a real form.

This example groups separately by company, reporting period, recipient and transaction type: 1,200 + 800 = 2,000 EUR. The additional Irish software purchase invoice for 450 EUR stays outside this sales group.

The example amounts are whole EUR amounts and are unaffected by rounding. For actual amounts with cents, check the specific form instructions first; this example does not establish a general rounding rule.

On narrow screens, you can scroll the table sideways. With a keyboard, focus the table first.

Fictional sales schedule – 2026-Q3, ZM version 5-v3
Supporting documentDirection / caseExample amountResult
SYNTH-OUT-2026-071B2B consulting service supplied to the same EU recipient1,200 EURPart of the confirmed service group
SYNTH-OUT-2026-081Another corresponding service supplied800 EURTotal 2,000 EUR
SYNTH-IN-2026-091SaaS purchase invoice450 EURNot a sale in this group

Specify the form and period explicitly

At the time of this guide, the public ZM selection uses form version 5-v3. The report is still tied to its actual reporting period. Here, this is explicitly the third quarter of 2026 for the service case described.

Separate recipients and transaction types as grouping keys. Reconcile sales documents with revenue accounts and tax reports and explain differences in cut-off or reporting frequency; do not claim universal one-to-one equality with a VAT advance return code.

On narrow screens, you can scroll the table sideways. With a keyboard, focus the table first.

Mapping before the browser write step
Target field / contextDerivation in the exampleRequired confirmation
Your own VAT IDCompany master dataActual assigned number
Reporting periodService case 2026-Q3Reporting obligation and choice of period
Recipient VAT IDSame recipient on both sales documentsActual number and corresponding verification evidence
Type of serviceOther intra-Community service in this caseFacts and recipient's VAT liability
Tax bases1,200 + 800 = 2,000 EURSource reconciliation, signs, currency and form instructions

Basics: Zusammenfassende Meldung (ZM, EC sales list) – form selection · UStG § 18a · UStG § 18b

Enter confirmed ZM values in the browser

Log in to Mein ELSTER yourself and open the Zusammenfassende Meldung (ZM) for the correct period. Your authorised browser-capable assistant compares the identity and enters the individual recipient/service group only after your confirmation.

Have the recipient, transaction type, period and amount read back. Compare the display with your schedule. Run form validation and clarify its notices; a report without technical errors is still not proof of correct tax classification.

  1. Confirm your own login and the correct company.
  2. Check the reporting period and the form version actually displayed.
  3. Enter approved values and read them back.
  4. Compare sources and totals again; resolve outstanding errors.
  5. Stop before submission with the verifiable summary.

A limited task for this case

Replace the placeholders with explicitly confirmed details. Without a suitable browser function, no claim that form values have been entered is possible.

Handle corrections and changes to sources separately

If sales documents or mappings change after your review, retrieve the affected sources again and review the approval. The correction link and original reporting period must be preserved.

If you later discover that a submitted ZM is incorrect or incomplete, you must correct the original report within one month under § 18a(10) UStG. Do not rely on conflicting older help texts without checking them. This work plan does not provide a universal correction solution.

Basics: UStG § 18a

Sources and information date

  • Zusammenfassende Meldung (ZM, EC sales list) – form selection

    Publisher: ELSTER / Finanzverwaltung. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

  • ZM – publicly accessible form guidance

    Publisher: ELSTER / Finanzverwaltung. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

  • UStG § 18a

    Publisher: BMJ / Bundesamt für Justiz. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

  • UStG § 18b

    Publisher: BMJ / Bundesamt für Justiz. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

  • UStG § 18e

    Publisher: BMJ / Bundesamt für Justiz. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

  • UStG § 3a

    Publisher: BMJ / Bundesamt für Justiz. Information as of: 3 November 2026; specific scope stated in the text. Retrieval / comparison: 2026-11-03.

Notes and requirements

  1. This article provides general information and does not constitute individual tax advice. You remain responsible for reviewing your bookkeeping, annual financial statements and tax returns. You review the tax classification, sources, values and approvals and take responsibility. Passing form validation does not confirm complete substantive tax correctness. You can seek targeted advice on individual technical questions.

  2. Examples use explicitly synthetic data. VAT identification and tax identity placeholders must not be copied into actual tax returns. Example assumptions and figures do not replace a review of your own circumstances.

  3. MCP data access, browser actions and actual submission are separate capabilities. The assistant needs appropriate, deliberately granted permissions; in a cloud client, authorised data may reach that client's provider. You enter credentials and confirmations yourself.