WooCommerce Finnish VAT Invoices: ALV / Y-tunnus Checklist

What a Finland-ready WooCommerce invoice plugin must store

Finnish invoice workflows break when checkout cannot capture company and Y-tunnus data, invoice numbers are tied to WooCommerce order IDs, invoice data only exists inside a PDF, reverse-charge evidence is missing, refunds overwrite originals, or accountant exports miss invoice document relationships.

Before buying an invoice plugin, confirm that every field below is structured order and invoice data that can move into PDFs, emails, My Account downloads, credit notes, tax reports, and accountant exports.

Finnish ALV invoice field checklist

✓Seller legal name, Finnish address, VAT/ALV registration details, invoice identity, and contact details that match bookkeeping records

✓Customer legal name, billing address, country, Y-tunnus business ID or EU VAT number, and optional purchase-order or cost-centre reference

✓Dedicated invoice number, invoice date, supply date, payment method, currency, net amount, ALV/VAT rate, VAT amount, and gross total

✓Reverse-charge wording and VAT-number evidence for eligible EU B2B invoices where VAT accounting shifts to the buyer

✓Retained invoice PDF, email attachment history, customer download access, and accountant-ready export fields

✓Credit-note relationship for refunds, cancellations, partial refunds, retained originals, and audit-ready correction trails

Where Finnish invoice workflows break

Scenario	Weak setup	Better invoice workflow
Finnish B2C ALV invoice	WooCommerce sends only a payment receipt and the finance team manually creates a Finnish VAT invoice when support receives a request.	Issue a final VAT invoice after payment with a dedicated invoice number, ALV breakdown, retained PDF, customer download access, and exportable invoice metadata.
Finnish B2B order with Y-tunnus	Company ID or business reference is captured in an order note, so it does not reliably appear on invoice PDFs, customer emails, or accountant exports.	Capture company and Y-tunnus fields as structured checkout metadata, print them on the invoice PDF, expose them on the order, and export them for bookkeeping.
EU reverse-charge sale	The store removes VAT but keeps no validation evidence, reverse-charge wording, or tax-treatment reason that explains why the invoice has zero VAT.	Store the buyer VAT number, retain validation evidence where possible, print reverse-charge wording, and include the tax-treatment reason in exports.
Refund or correction	Refunds overwrite the original invoice PDF or create manual credit notes with no link to the first invoice document.	Preserve the original invoice, issue a linked credit note with its own sequence, and keep both documents available for support and the accountant.

Questions to ask before choosing a plugin

1Can the plugin collect Finnish Y-tunnus, company names, and EU VAT numbers before checkout is completed?

2Can invoice numbers use a dedicated invoice sequence instead of WooCommerce order IDs?

3Can the PDF template show seller identity, customer identity, VAT totals, payment method, Y-tunnus/VAT identifiers, and reverse-charge wording?

4Can invoices, credit notes, and tax-treatment reasons be exported as structured bookkeeping fields instead of only PDF files?

5Can customers download invoices and credit notes from My Account without support manually resending PDFs?

6Can refunds create a linked credit note while preserving the original invoice PDF?

FAQ

Does a Finnish WooCommerce store need more than a payment receipt?

Usually yes when the store needs ALV/VAT invoice data, Y-tunnus capture, B2B VAT-number evidence, dedicated invoice numbers, reverse-charge wording, retained PDFs, customer downloads, credit notes, or accountant exports.

Should Finnish invoice numbers reuse WooCommerce order IDs?

A dedicated invoice sequence is safer because WooCommerce order IDs include pending, failed, cancelled, draft, and test orders. A sequence such as FI-2026-000184 is easier to audit and hand to an accountant.

What should a Finnish ALV invoice workflow do for EU B2B orders?

It should capture the buyer VAT number, store the tax-treatment reason, print reverse-charge wording when applicable, preserve validation evidence where possible, and expose those fields in accountant exports.

How does Lattice Invoices fit this Finnish VAT workflow?

Lattice Invoices is being shaped for EU WooCommerce stores that need structured tax fields, predictable invoice numbers, PDF delivery, credit notes, customer downloads, and accountant exports instead of a PDF-only receipt workflow.