Lattice Plugins

Romanian TVA invoices

WooCommerce Romanian VAT invoices need CUI fields, retained PDFs, and correction trails — not just an order receipt.

If your WooCommerce store sells to Romanian customers or EU B2B buyers, invoice setup has to cover CUI capture, TVA totals, reverse charge, invoice numbering, credit notes, customer downloads, and accountant export before launch.

Request Romanian invoice reviewView Lattice Invoices offer

What a Romania-ready WooCommerce invoice plugin must store

Romanian invoice workflows break when checkout cannot capture company and CUI 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.

Romanian TVA invoice field checklist

✓Seller legal name, Romanian address, CUI/VAT registration details, invoice identity, bank details, and contact details that match accounting records
✓Customer legal name, billing address, country, CUI or EU VAT number, and optional company, purchase-order, or cost-centre reference
✓Dedicated invoice number, invoice date, supply date, payment method, currency, net amount, TVA/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
✓Linked credit-note relationship for refunds, cancellations, partial refunds, retained originals, and audit-ready correction trails

Where Romanian invoice workflows break

ScenarioWeak setupBetter invoice workflow
Romanian B2C TVA invoiceWooCommerce sends only an order confirmation while staff manually generate VAT invoices when customers or accountants ask for them.Issue a final VAT invoice after payment with a dedicated invoice number, TVA breakdown, retained PDF, customer download access, and exportable invoice metadata.
Romanian B2B order with CUICompany and CUI values are stored as free-text order notes, so the data is missing from invoice PDFs, email attachments, customer downloads, or accounting exports.Capture company and VAT fields as structured checkout metadata, print them on invoice PDFs, expose them on orders, and export them for bookkeeping cleanup.
EU reverse-charge saleThe store removes VAT without keeping validation evidence, reverse-charge wording, or a 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 invoice exports.
Refund or correction documentRefunds overwrite the first invoice PDF or create manual correction notes that are not linked to the original invoice number.Preserve the original invoice, issue a linked credit note with its own sequence, and keep both documents available for support, customers, and the accountant.

Questions to ask before choosing a plugin

1Can the plugin collect Romanian CUI, 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, TVA/VAT totals, payment method, VAT identifiers, bank details, 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 Romanian WooCommerce store need more than a payment receipt?

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

Should Romanian 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 RO-2026-000184 is easier to audit and hand to an accountant.

What should a Romanian VAT 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 Romanian 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.