Why Klarna stores still need a WooCommerce invoice layer
A Klarna event can prove authorization, capture, refund, or dispute activity. It does not prove that the WooCommerce order has the correct VAT/BTW number, that the final invoice number was issued at the right moment, or that partial captures and refunds created accountant-ready correction records.
For EU WooCommerce stores, the payment gateway and invoice workflow should meet at the order record. The order should show customer VAT metadata, invoice PDF state, Klarna references, credit-note links, resend/download history, and export status without spreadsheet reconciliation.
Klarna invoice readiness checklist
1. Capture invoice-ready VAT/BTW data before Klarna authorization
Klarna can handle payment authorization and consumer financing, but your EU invoice still depends on WooCommerce order data: business name, VAT/BTW number, billing country, invoice email, customer reference, and reverse-charge status before the payment session begins.
Buyer question: Does checkout validate B2B invoice fields before the Klarna payment step?
2. Decide whether authorization, capture, or paid status creates the invoice
Pay-later and pay-now flows can create different timing events. Final VAT invoice numbers should be issued at the moment your finance team treats the order as paid or capturable, not merely when a customer starts Klarna checkout.
Buyer question: Which exact Klarna/WooCommerce event triggers final invoice numbering?
3. Keep Klarna references with the invoice record
Support and accounting should not reconcile three systems by hand. The WooCommerce order should show invoice number, Klarna order ID, authorization/capture state, VAT totals, payment date, refund references, PDF status, and customer download availability.
Buyer question: Can exports include invoice number, Klarna order ID, VAT totals, and refund references in one row?
4. Treat partial captures and refunds as invoice events
Klarna flows often include partial capture, delayed shipment, partial refund, full refund, or dispute handling. Your invoice workflow needs retained originals, linked credit notes, and correction evidence that matches the financial event.
Buyer question: How does the plugin handle partial capture, partial refund, and dispute correction evidence?
5. Provide customer self-service invoice downloads
B2B buyers who paid with Klarna still need a VAT invoice later for finance teams. My Account downloads and resend controls reduce support load and make repeat purchasing easier.
Buyer question: Can customers download invoices and credit notes without emailing support?
Three Klarna invoice scenarios to test before buying
Klarna order is authorized but not captured yet
Trigger: The customer passes Klarna checkout, but fulfillment or capture happens later.
Workflow: Store invoice-ready VAT metadata and Klarna order ID, keep the document as proforma/payment evidence if needed, and wait for the configured capture/paid status before issuing the final invoice number.
Pay-now order reaches a reliable paid status
Trigger: WooCommerce receives confirmation that the Klarna payment is paid or captured.
Workflow: Generate the final invoice number, attach the PDF to the customer email, expose the invoice in My Account, and export payment reference plus VAT totals for the accountant.
Partial refund or dispute happens after invoicing
Trigger: A Klarna refund, adjustment, or dispute changes the financial value of a paid order.
Workflow: Retain the original invoice, create a linked credit note for the corrected amount, store Klarna refund/dispute references, and include both documents in accounting export.
Manual workaround vs invoice-ready workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| Klarna dashboard shows the payment, WooCommerce shows the order, and invoice PDFs are created manually after fulfillment. | WooCommerce order links invoice number, PDF state, Klarna authorization/capture/refund references, VAT fields, and customer download access. |
| Final invoice numbers are issued when the buyer starts Klarna checkout, creating gaps for abandoned or failed flows. | Final invoice numbering waits for the configured paid/captured status, while earlier steps can remain proforma/payment-request evidence. |
| Partial captures and refunds are adjusted in Klarna but not reflected as retained correction evidence in WooCommerce. | Capture/refund workflows create traceable invoice or credit-note records linked to the original order and Klarna event IDs. |
| B2B customers email support for VAT invoices because Klarna receipt data is not enough for accounting. | VAT/BTW metadata is captured before payment, invoice PDFs are attached, and protected customer downloads remain available after purchase. |
FAQ
Does Klarna automatically create EU VAT invoices for WooCommerce?
No. Klarna handles payment authorization, capture, refunds, and buyer communication. EU VAT invoices still need WooCommerce order metadata, invoice numbers, VAT/BTW fields, PDF delivery, credit notes, and accounting exports.
When should a Klarna WooCommerce invoice be created?
Usually when the order reaches the configured paid or captured state. Creating final invoice numbers at checkout-start can create gaps, especially in authorization, delayed capture, or failed payment flows.
What makes Klarna invoice workflows different from card payments?
Klarna can involve authorization before capture, pay-later timing, partial captures, disputes, and refund adjustments. Those states should map to proforma, final invoice, credit-note, and export rules instead of a single manual PDF step.
Where does Lattice fit if I already use Klarna?
Klarna remains the payment method. The Lattice Invoices early-access workflow focuses on VAT/BTW checkout evidence, invoice PDFs, credit notes, customer downloads, and accountant-ready handoff around the WooCommerce order.