Why Fiscalization Matters for Multi-Country Delivery Chains
Fiscalization — the electronic reporting of sales data to tax authorities in real time or near-real time — is mandatory in several European countries. For food delivery chains operating across borders, getting this wrong means fines, audits, and potential loss of operating licenses. Getting it right is a non-trivial technical challenge, because each country has its own protocols, certificate requirements, and reporting formats.
Ukraine: Checkbox Fiscalization
Ukraine uses the Checkbox system for fiscal receipt generation. Every delivery order must generate a fiscal receipt through the Checkbox API, which registers the receipt with the State Tax Service in real time. The receipt must include the operator's fiscal number, item names and prices, VAT breakdown, and a QR code linking to the State Tax Service verification page.
Failure to issue fiscal receipts in Ukraine carries fines of up to 200% of the unregistered transaction value. Ukraine has been aggressively enforcing fiscal requirements since 2021, with inspectors actively checking that delivered orders come with valid fiscal receipts.
Poland: KSeF (National e-Invoice System)
Poland is transitioning to the mandatory KSeF (Krajowy System e-Faktur) for B2B transactions, with mandatory rollout for all businesses. For food delivery, the key requirement is generating structured XML invoices for corporate customers and ensuring VAT reporting aligns with KSeF data. Consumer (B2C) receipts don't require KSeF but must still comply with Polish receipt regulations.
Czech Republic: EET (Electronic Sales Registration)
The Czech Republic requires electronic registration of sales (EET) for food delivery operations. Sales data must be reported to the Czech Tax and Customs Administration in real time, with each transaction receiving a confirmation code that must appear on the customer receipt. The EET system uses a certificate-based authentication system — operators must obtain a certificate from the tax authority before going live.
Germany: Fiskaly / TSE
Germany requires all point-of-sale systems to use a certified Technical Security Equipment (TSE) module. For cloud-based delivery systems, this is typically implemented through providers like Fiskaly, which offer a cloud TSE API. Every transaction must be signed by the TSE, and the signature must appear on the receipt. Receipts are required to be offered to all customers.
Spain: VeriFacTu
Spain is rolling out VeriFacTu, a voluntary-transitioning-to-mandatory system for verifiable tax records. Delivery operations in Spain need to generate VeriFacTu-compliant invoices for B2B sales and be prepared to report directly to the AEAT (Agencia Estatal de Administración Tributaria) as the system becomes mandatory.
United States: Stripe Tax
While not a fiscalization system in the European sense, US delivery operations must correctly calculate and remit sales tax, which varies by state and sometimes by city. Stripe Tax integrates with payment processing to calculate the correct tax automatically and generate the documentation needed for tax remittance.
The Technical Integration Challenge
Each country's system uses different APIs, different certificate formats, different receipt requirements, and different error handling requirements. A delivery chain going live in a new country needs to budget 4–8 weeks of development time to implement compliant fiscalization, or use a platform that has these integrations pre-built.
The most important thing to get right: receipts must be issued at the time of payment, not at delivery. If your system generates receipts at delivery, you're already non-compliant in countries with real-time fiscal requirements.