An advance payment invoice at year end is a typical December question in a B2B shop: the business customer wants to pay in 2026 because the budget expires otherwise, but the goods only arrive in January. Three things then need to be settled: when VAT arises, which invoices the shop issues and in which format. Since the letter of the German Federal Ministry of Finance (BMF) of October 15, 2026, the format question for the advance payment has been answered, and there is a time-limited relief for the final invoice as an e-invoice. The article sorts out the legal situation and shows how a B2B shop handles advance payment and final invoice cleanly.
The case: budget in December, goods in January
In business-to-business sales, the pattern is familiar: a department has to commit funds by December 31, but the ordered goods are still being manufactured or will be delivered later. Purchasing therefore asks whether the shop can invoice the order now.
For VAT purposes this is not a special case but an advance payment: the consideration is paid before the delivery takes place. Whether the customer pays the full price or only part of it does not change that, but it does change the documents. With a partial payment, December brings an advance payment invoice and January a final invoice that deducts the advance payment. With full prepayment, a single invoice can be enough. Partial deliveries are not meant here.
According to the German VAT Application Decree, advance payments give rise to tax if they are made for a specific supply of goods or services (UStAE). If there is no specific agreement on the supply when the payment is received, it has to be checked whether the payment is merely a loan; the circumstances of the individual case, for example an ongoing business relationship with regularly recurring orders, can still make it an advance payment (UStAE). Collecting a "credit" in December for later orders that are still open is therefore usually not an advance payment. In the shop this means: first the specific order, then the advance payment invoice.
VAT arises on payment, not on delivery
A business that pays VAT on agreed consideration normally owes the tax at the end of the advance return period in which it delivers. Advance payments are an exception, known in Germany as minimum actual taxation. The law puts it this way:
If the consideration or part of it is received before the supply or partial supply has been carried out, the tax arises to that extent at the end of the advance return period in which the consideration or partial consideration was received.
German VAT Act (UStG), Sec. 13(1) no. 1(a) sentence 4 (own translation)
For the December case this means: if the payment is received in December, the tax on that amount belongs in the December advance return, or in the one for the fourth quarter for quarterly filers, even if the goods only leave the warehouse in January (Sec. 13(1) no. 1(a) sentence 4 UStG). What counts is receipt, not the transfer order: for bank transfers, the time of receipt is generally the credit to the bank account (UStAE). A payment that the customer releases on December 30 and that arrives on January 4 is a January payment.
A second rule matters to the customer. It may deduct input VAT from an advance payment before delivery, but only under two conditions: the invoice must be available and the payment must have been made (Sec. 15(1) no. 1 UStG). A customer who pays in December but only receives an invoice in January cannot claim the input VAT for December. That is why purchasing departments explicitly ask for an invoice in the old year when they pay from a budget.
What goes into the advance payment invoice
An advance payment invoice is a full invoice. If a business receives consideration for a supply that has not yet been carried out, the general invoicing rules apply accordingly (Sec. 14(5) sentence 1 UStG). The VAT Application Decree spells out what that means for the advance payment. The invoice must show that an advance or down payment is being invoiced (UStAE), for example through the expected delivery date. Instead of the time of supply, the invoice states the expected time or the calendar month of the supply (UStAE).
- Mandatory details as on any invoice: name and address of both parties, tax number or VAT ID, date of issue and a separate invoice number (Sec. 14(4) UStG)
- Exact supply: items and quantities of the order, because the goods must be precisely determined at the time of the advance payment (UStAE)
- Expected delivery month: for example "delivery expected in January 2027", so it is clear that invoicing takes place before the supply (UStAE)
- Partial consideration and tax: the consideration received in advance takes the place of the consideration, plus the tax amount on it (UStAE)
- Time of receipt: if it is known and differs from the date of issue (Sec. 14(4) no. 6 UStG)
- Clear label: "advance payment invoice" in the header and an order number that the final invoice will refer to later
Two details make practice easier. The invoice may be issued before the payment is received, and if the customer pays less than invoiced, tax only arises on the amount actually received (UStAE). The shop can therefore send the advance payment invoice together with the order. The invoice number may come from a separate number range: the law requires a sequential number with one or more series of numbers that is assigned only once (Sec. 14(4) UStG).
The business can issue an invoice for the supply in advance that shows the entire consideration and the tax; additional invoices for advance payments are then not needed (UStAE). The downside: if quantity or price change in January, this invoice is corrected. If the shop is obliged to issue e-invoices at that point, the correction must also be an e-invoice (BMF letter of October 15, 2026). What cancellation, credit note and correction look like in the format is shown in our article on ZUGFeRD cancellation invoices and credit notes.
Format: the December advance invoice may be a PDF
In 2025 and 2026, all invoice issuers can still opt for an "other invoice", meaning paper or, with the recipient's consent, a PDF (BMF). The transitional rule in the law, however, is tied to the time of supply: it applies to supplies carried out before January 1, 2027 (Sec. 27(38) no. 1 UStG). A delivery in January 2027 is no longer covered. Until the fall, it was therefore unclear whether a December advance invoice for a January delivery already had to be issued as an e-invoice.
The letter of the Federal Ministry of Finance of October 15, 2026 answers the question in paragraph 2 (BMF letter of October 15, 2026):
Advance, prepayment and down payment invoices that a business issues, taking into account the transitional rules under Sec. 27(38) UStG, before it is obliged to issue an e-invoice do not have to be transmitted as e-invoices, even if the supply and payment only take place after this point in time.
Federal Ministry of Finance, letter of October 15, 2026, para. 2 (own translation)
For the December case this is clear: the advance payment invoice a shop issues in December 2026 does not have to be an e-invoice. A PDF is sufficient if the customer has agreed to electronic delivery; transmitting an "other invoice" in an electronic format requires the consent of the recipient (Sec. 14(1) UStG). Shops that already create e-invoices may do so for the advance payment as well. Our article on e-invoicing requirements for online shops gives an overview of formats and deadlines.
For supplies carried out in 2027, the previous year's total revenue decides. If it was no more than €800,000 in 2026, the shop may still transmit invoices for such supplies on paper or, with consent, as a PDF until December 31, 2027 (Sec. 27(38) no. 2 UStG). If it was higher, January deliveries to domestic businesses require e-invoices. Regardless of revenue, another electronic format remains permissible until the end of 2027 if the recipient consents and the invoice is transmitted via EDI (Sec. 27(38) no. 3 UStG). Your tax advisor handles the classification in the individual case.
The January final invoice: deduct the advance payment
With the delivery in January, the supply has been carried out and the shop invoices it. If it issues a final invoice for the entire order, the law prescribes what it must contain:
If a final invoice is issued, the partial consideration received before the supply was carried out and the tax amounts attributable to it must be deducted in it, if invoices within the meaning of subsections 1 to 4 have been issued for the partial consideration.
German VAT Act (UStG), Sec. 14(5) sentence 2 (own translation)
Deducted are the partial consideration and the tax on it. The tax authorities allow several ways of presenting this (UStAE):
| Presentation | What the final invoice shows | Reference |
|---|---|---|
| Deduct individually | Total price, below it each advance payment with date, consideration and tax as a deduction, the remaining payment at the end | Section 14.8(7) UStAE |
| Deduct the sum | Total price minus the sum of all partial consideration and the sum of the tax amounts | Section 14.8(7) UStAE |
| State additionally | Total price without deduction, the advance payments with consideration and tax listed in addition | Section 14.8(8) no. 1 UStAE |
| Attachment | Advance payments in an attachment that the final invoice explicitly refers to | Section 14.8(8) no. 2 UStAE |
| Remainder invoice | Instead of a final invoice only the remaining consideration; the advance payments are not stated | Section 14.8(11) UStAE |
A worked example shows how the amounts fit together. A business customer orders goods for €50,000 net. At the standard rate of 19 percent (Sec. 12(1) UStG), the tax amounts to €9,500 and the total price to €59,500. In December, the customer pays €20,000 net plus €3,800 tax, €23,800 in total, against an advance payment invoice. The January final invoice shows €59,500, deducts €23,800 including the €3,800 tax it contains and requests the remaining €35,700, including €5,700 tax.
An expensive mistake happens when the shop automatically creates a regular invoice for the full amount in January. If a final invoice does not deduct the partial consideration received and the tax on it, the business must pay the entire tax amount shown to the tax office (UStAE). The excess part is owed additionally under Sec. 14c(1) UStG, while the customer may only deduct the tax on the remainder as input VAT (UStAE). In the example, €3,800 of tax would appear twice in the documents. A corrected final invoice remedies this.
Final invoice as an e-invoice: BT-113 and BT-22
If the previous year's revenue is above the threshold, the January final invoice is an e-invoice under the standard EN 16931, for example in XRechnung or ZUGFeRD format. Here a technical gap shows. The mapping table of the German Coordination Office for IT Standards and the Forum for Electronic Invoicing Germany states for advance and final invoices that a detailed representation in the core model of EN 16931-1:2019 is not yet possible (KoSIT/FeRD). For the deduction it lists field BT-113 for the paid amount and BT-115 for the amount due (KoSIT/FeRD).
This is exactly where the letter of October 15, 2026 comes in. Until June 30, 2030, the tax authorities will not object if the partial consideration already received is deducted in the structured part as a sum in BT-113 ("Paid amount") and the required details on the partial consideration are given in the free text field BT-22 ("Invoice note") (BMF letter of October 15, 2026). Alternatively, the deduction may be made in an embedded, unstructured attachment if the structured part explicitly refers to it. The attachment rule was already part of the October 2024 letter, where it applied until December 31, 2027; it has now been extended to June 30, 2030 (BMF letter of October 15, 2026).
BT-113: paid amount
The sum of the advance payments as a gross amount. In the worked example this is €23,800, which is deducted from the total (KoSIT/FeRD).
BT-22: invoice note
The details under Section 14.8(7) and (8) UStAE in free text: number and date of the advance invoice, partial consideration and tax amount (BMF letter of October 15, 2026).
BT-115: amount due
What remains to be paid after the deduction, €35,700 in the example. With full prepayment this is zero (KoSIT/FeRD).
BG-24: attachment
The route via an embedded attachment listing the advance payments, which the structured part explicitly refers to (BMF letter of October 15, 2026).
The relief ends when the shop's own obligation begins. Paragraph 2 only exempts advance invoices issued before that point; when the obligation begins depends on prior-year revenue. If a shop with more than €800,000 in prior-year revenue invoices a new advance payment in February 2027, that advance invoice is also an e-invoice. As the invoice type, the mapping table provides code 386 ("Prepayment invoice") for advance payment invoices (KoSIT/FeRD). By then at the latest, the shop needs both in structured form: the advance invoice and the final invoice.
The customer pays attention to the format as well. If the invoice issuer is obliged to issue an e-invoice and sends a PDF anyway, the tax authorities take the view that it is not a proper invoice, and the invoice then does not in principle entitle the customer to deduct input VAT (BMF). The tax authorities allow ways out such as a subsequent correction by an e-invoice (BMF).
What the Shopware standard covers and what it does not
According to its documentation, Shopware provides global templates for delivery note, invoice, credit note and cancellation invoice (Shopware). In ZUGFeRD format, the core creates invoice, credit note and cancellation invoice, each as a separate XML or embedded in the PDF (Shopware source code). There is no document type for advance payments, and none of the templates invoices only part of the order value. How the standard invoice works as ZUGFeRD and which data it uses is described in our article on ZUGFeRD invoices from the Shopware standard.
It is worth looking at how the standard handles paid orders. If the payment status is "Paid", Shopware enters the total of the order as the paid amount in the XML (Shopware source code); the embedded ZUGFeRD library writes this value to BT-113 (ZUGFeRD library). The amount due is then zero. With any other status, the paid amount stays at zero, including "Partially paid", which order management knows as a separate payment status (Shopware). The standard does not write any text to BT-22 (Shopware source code). We checked this against the source code of version 6.7.15.1.
| Situation in the shop | What the standard creates | What is missing |
|---|---|---|
| Prepayment, invoice only on shipment in January | Invoice with the total in BT-113, zero due | An invoice in December so the customer can deduct input VAT |
| Advance payment invoice in December | No suitable document type | Document type, number range, partial amount, expected delivery month |
| Final invoice after partial payment | Invoice for the total without a paid amount | Deduction of partial consideration and tax, sum in BT-113, details in BT-22 |
| Final invoice after full prepayment with advance invoice | Total in BT-113, zero due | Details of the advance invoice in BT-22 |
Order management itself offers a stopgap. The "Custom document" option lets you upload a PDF created outside Shopware (Shopware), such as an advance payment invoice from accounting. That solves the December problem for individual cases, but not the January problem: if a flow automatically creates an invoice on shipment, a second invoice for the full amount is created. For these orders the automatic process has to pause, for example via a condition in the Flow Builder.
In many B2B shops the ERP or accounting software issues the invoice. The advance payment logic then belongs there, and the shop supplies the order, payment receipt and delivery date. What matters is that exactly one system assigns invoice numbers. Our article on the DATEV integration in e-commerce shows what the handover to accounting can look like.
Custom development: advance payment and final invoice in the shop
If the shop is to do the invoicing itself, a lean extension closes the gap. The building blocks follow the flow of an order:
- Define the advance payment: store the advance amount in the order or quote
- Advance invoice document type: a separate document type with number range, partial consideration, tax and delivery month, as an e-invoice with code 386 once the obligation applies
- Trigger in the flow: advance invoice on order or payment receipt, suppress the regular invoice for these orders
- Final invoice with deduction: sum of the advance payments in BT-113, number, date, partial consideration and tax of each advance invoice as text in BT-22, remainder in BT-115
- Validation: validate every XML against the EN 16931 rules and compare it with the PDF view
- Handover: pass both invoices, linked to each other, to accounting or the ERP
Technically, the extension hooks into the same event that our article on the ZUGFeRD standard invoice uses for the routing ID. Shopware dispatches it before the totals of the XML are calculated and validated (Shopware source code); a paid amount set there therefore flows into BT-113 and BT-115. The following sketch shows the heart of the final invoice: it sets the paid amount to the sum of the advance payments and writes the details into the invoice note.
public function onZugferdGenerated(ZugferdInvoiceGeneratedEvent $event): void
{
// Advance invoices of this order from the custom table
$prepayments = $this->prepaymentRepository->forOrder($event->order, $event->context);
if ($prepayments->count() === 0) {
return;
}
// BT-113: sum of the advance payments (gross), BT-115 follows as the remainder
$event->document->withPaidAmount($prepayments->amountTotal());
// BT-22: number, date, partial consideration and tax per advance invoice
$event->document->getBuilder()->addDocumentNote($prepayments->noteText());
} Repository and text template are part of the extension. In the source code, the event carries the note that it is to be replaced by a reworked document generation with version 6.9.0 (Shopware source code); extensions at this point should therefore stay small and be covered by tests. As a Shopware agency, we develop this individually, aligned with payment methods and accounting.
The schedule up to the turn of the year
For orders now coming in with budget payment in December and delivery in January, this sequence is advisable:
- Make the order specific: record items, quantities, prices and delivery month.
- Clarify the revenue threshold: estimate with your tax advisor whether total revenue in 2026 exceeds €800,000 (Sec. 27(38) UStG).
- Issue the advance invoice in December: as a PDF with the customer's consent or as an e-invoice.
- Watch incoming payments: credits up to December 31 belong in the December advance return or the one for the fourth quarter, later ones in the new year.
- Stop the automation: do not let the shop create a second full invoice on shipment for these orders.
- Final invoice in January: deduct the advance payment and tax, as an e-invoice with BT-113 and BT-22 if the obligation applies.
- Retain: keep advance and final invoices for eight years (Sec. 14b UStG), and for e-invoices at least the XML, intact and in its original form (BMF).
Our article on failed payments in the shop describes how a shop catches failed and open payments. If you prefer to supply business customers on account, you will find control via credit limits in the article on purchase on account in B2B.
The non-objection rule for BT-113 and BT-22 applies until June 30, 2030 (BMF letter of October 15, 2026); it is a bridge, not a permanent solution. Anyone developing now should therefore store the advance payments as separate records and not just as text, so the presentation can be switched later.
How we support B2B shops at year end
We review your shop and develop the missing building blocks individually, from the advance invoice document type to the final invoice with BT-113 and BT-22. You can find more about our approach to electronic invoices on the page ZUGFeRD and XRechnung; if invoicing runs through the ERP, we start at the interface to the ERP.
Inventory
Document types, number ranges, flows and payment methods as well as the role of the ERP.
Development
Advance invoice as a separate document type and final invoice with deduction, covered by tests.
Validation
Test orders per payment method and validation of the XML under EN 16931 before going live.
This article draws on Sections 12, 13, 14, 14b, 14c, 15 and 27(38) of the German VAT Act (gesetze-im-internet.de), the letter of the German Federal Ministry of Finance of October 15, 2026 on mandatory e-invoicing (ref. III C 5 – S 7287-a/00019/021/017), the BMF questions and answers on e-invoicing, Sections 13.5, 13.6 and 14.8 of the VAT Application Decree, the KoSIT and FeRD mapping table of mandatory details under the VAT Act (as of July 25, 2025), the Shopware documentation on documents and orders, the Shopware 6.7.15.1 source code on GitHub and the ZUGFeRD library horstoeko/zugferd embedded there. Retrieved on October 30, 2026. The article does not replace tax advice in the individual case.
As a rule, yes. According to the BMF letter of October 15, 2026, advance invoices issued before the start of the business's own e-invoicing obligation do not have to be transmitted as e-invoices, even if delivery and payment follow later (BMF letter of October 15, 2026). Sending it as a PDF requires the customer's consent (Sec. 14(1) UStG).
At the end of the advance return period in which the payment is received, so for monthly filers and a December payment with the December advance return (Sec. 13(1) no. 1(a) sentence 4 UStG). For bank transfers, the credit to the account generally counts (UStAE).
That depends on total revenue in 2026. If it was no more than €800,000, the invoice may still be sent on paper or, with consent, as a PDF until the end of 2027 (Sec. 27(38) no. 2 UStG). If it was higher, an e-invoice must be used for deliveries to domestic businesses, unless the invoice is transmitted via EDI with consent. Your tax advisor handles the classification in the individual case.
Then the shop owes the entire tax shown, and the part attributable to the advance payment is owed additionally (UStAE). The customer can only deduct the tax on the remaining amount as input VAT. A corrected final invoice usually resolves the error.
According to our review, no. Shopware provides templates for delivery note, invoice, credit note and cancellation invoice (Shopware), but no document type for advance payments. The standard only sets the paid amount in the XML for fully paid orders (Shopware source code).
That is possible. The business can issue an invoice for the entire consideration in advance, and additional advance invoices are then not needed (UStAE). If something changes later, this invoice is corrected, and if there is an obligation to issue e-invoices, the correction is an e-invoice as well (BMF letter of October 15, 2026).