TabellenFaktura for Word · Manual
Special cases for Word invoices
Handle multiple pages, macros, advance payments, final invoices and other requirements in both the document and the structured data.
Macros, DOCM and Protected View
A normal DOCX invoice does not require VBA macros. Existing templates may nevertheless contain macros for calculation, numbering or document generation.
- Preserve macro-enabled documents as DOCM and templates in a suitable format such as DOTM. DOCX removes macros.
- Test existing macros in a copy. Do not run two competing numbering systems.
- Recheck fields, items, totals and printing after a macro changes the document.
- An ordinary PDF-export macro does not create a ZUGFeRD invoice.
Office may block downloaded macro files. Only consider file-specific unblocking after checking the origin and contents. Follow IT policies and do not enable all macros globally. Microsoft explains macro blocking.
Protected View and macro blocking are different states. Only enable editing for trusted files. Read-only documents prevent saving new mappings.
Multiple pages and long tables
- Build the complete invoice in one Word document.
- Repeat the table header on later pages if appropriate.
- Configure paragraph and table-row page-breaking rules and remove blank or clipped pages in Print Preview.
- Extend the mapped item range to the final real item. Page breaks do not extend it automatically.
- Map separate blocks explicitly and exclude headings, carried totals and summary rows.
- Check recognised items and every final PDF page.
The PDF follows the bound document's printed appearance, while structured items follow mappings. Attach additional evidence or timesheets separately through the agreed channel.
Continuation text and merged cells
Additional description columns and their separator form the electronic description. Explicitly choose whether text-only continuation rows belong to the preceding or following item. Check that long descriptions remain complete.
A merged letterhead cell may hold a single invoice value. Item data, however, needs a consistent column structure per row. Simplify merged item cells or nested tables in a copy before remapping.
Partial, advance and final invoices
Choose the invoice type that matches the transaction under Allgemein → Rechnungsart. Give every independent document its own number and show a clear service or project, date or period and tax treatment. Selecting a type alone does not produce a complete final settlement.
An advance invoice
Enter the services or agreed advance charged by that document. Match the visible title and recognised invoice type. An invoice issued earlier is not proof of a received payment.
Received payments in the final invoice
- Enter the full service and its tax.
- Record actually received payments to be credited in the amount schedule under Summen.
- For each payment, provide gross amount, tax amount or allocation and required invoice/payment references.
- Add preceding invoices under Rechnungsbezüge.
- Compare the schedule, VAT presentation and balance with the visible document.
At a uniform 19%, €10,000 net plus €1,900 VAT gives €11,900. A received €3,570 including €570 VAT leaves €8,330 due. Do not deduct that payment again as a negative service line.
The journal does not determine payments received. Allocate multiple tax groups correctly. The German Finance Ministry's e-invoice FAQ explains the tax principles for final invoices. Technical validation does not replace a complete business settlement.
Discounts, surcharges and text amount sources
Use Einzelbeträge under Summen to enter several amounts or select them from Word, including free text. Select the relevant amount only, specify tax allocation and check the total. Do not add the same source twice.
Allocate adjustments to the correct tax group. A discount already included in item prices must not be deducted again. Direct assistant entries must also be represented correctly in Word.
Cash discount and security retention
Enter agreed cash discount under Zahlung with percentage, deadline and optional basis. It is not a received payment. Enter retention in its dedicated totals field, not as a discount or payment. For example, €8,330 due less €595 retention leaves a current payout of €7,735. Map the correct Word control value.
Mixed tax, small-business exemption and reverse charge
Use item-level rates for mixed taxation. Category, rate and required exemption reason must agree. Small-business exemption, zero rate, general exemption, reverse charge, intra-community supply and out-of-scope transactions are different cases.
Provide required identifiers and notes in both document and mappings. Apply appropriate tax information to adjustments and payments as well. Resolve uncertain tax treatment before issuing the invoice.
XRechnung for public customers
- Confirm format, Leitweg-ID or buyer reference, electronic address and submission channel with the customer.
- Open XRechnung erstellen.
- Check buyer reference, process identifier, seller contact and electronic addresses.
- Create the invoice, wait for KoSIT validation and correct any reported error.
- Submit the XML through the agreed channel and check acknowledgment.
A Leitweg-ID is not an email address. Renaming a PDF to XML does not create an XRechnung. A supplementary PDF does not replace the structured file.
Corrections and previously used numbers
Do not replace a completed invoice under its existing number. Create the required correction with a new number and reference to the original. Check document type and signs together; a negative unit price is not a universal correction method.
For duplicates, find the number in the journal. An existing reservation may belong to the current process. A finalised process calls for its original file or an appropriate correction. Preserve both original and correction.
Rounding, zero quantities and Word formulas
Formatting and actual numeric values differ. Quantity multiplied by net unit price, line amount, VAT and totals must agree. Update Word formulas instead of relying on their previous displayed result.
The zero-quantity option deliberately omits zero lines. A missing quantity is not a valid zero. Correct actual values or formulas rather than removing control fields to bypass discrepancies.