WEBVTT

1
00:00:00.000 --> 00:00:18.826
German e-invoicing is not just a new file format. It changes the path from service delivery and invoice data into accounting, archiving, and increasingly digital VAT reporting. If the topic is treated only as a PDF problem, the real workflow work is usually missed.

2
00:00:18.826 --> 00:00:38.507
First, clarify the obligation. For many supplies between domestic German businesses, structured electronic invoices have been relevant since January first, twenty twenty-five. Transitional rules, exceptions, and concrete cases need tax review. Operationally, however, companies already need receiving, processing, and auditability to work.

3
00:00:38.507 --> 00:01:01.611
Then comes the format decision. XRechnung is especially important in German public-sector contexts. ZUGFeRD, also known as Factur-X, connects a readable PDF with embedded structured data. UBL, CII, and Peppol BIS matter in European and network contexts. The decisive question is not the label, but what the recipient, system, and process actually require.

4
00:01:01.611 --> 00:01:21.292
A reliable e-invoice starts with clean invoice data. That includes the delivered service, tax treatment, recipient, order references, payment terms, mandatory fields, and any customer-specific requirements. If these details are collected only at the end, the invoice may be created, but the workflow will not be reliably checkable.

5
00:01:21.292 --> 00:01:43.540
On the receiving side, the task is control. Companies need to make e-invoices readable, validate them technically, review them commercially, and archive them in an audit-proof way. The original file, a visual representation, attachments, validation status, and accounting treatment should remain traceable later.

6
00:01:43.540 --> 00:02:04.933
This becomes very visible in project and professional-services billing. Messy time bookings, weak service descriptions, missing approvals, and unclear recipient logic rarely produce good invoices. Time records, evidence, approvals, and accounting handoff have to fit together before they become professional e-invoices and reliable timesheets.

7
00:02:04.933 --> 00:02:22.047
The sensible next step is therefore not a rushed format choice, but a short workflow check. Which formats do you really need? Can you receive, validate, and archive? Do project data and accounting handoff line up? The Momentum Advisory e-invoicing check helps make these gaps visible.
