Skip to main content

πŸ‡ͺπŸ‡Ί EU store migration: please clarify the current invoice document and numbering model

We are considering migrating an existing European store to FluentCart, but first we need to understand the current invoicing model.

As we understand it:

  • order_receipt is the PDF customers download after a paid purchase.
  • proforma_invoice is the template labelled β€œInvoice”, apparently used for pending/offline orders.
  • receipt_number is the sequential number generated when an order is paid.
  • invoice_no is the prefix combined with that receipt_number.

Could you please confirm whether this is correct? Should European stores therefore treat order_receipt as the final tax invoice and invoice_no as its official invoice number, while treating proforma_invoice only as a proforma?

We also need confirmation that test and live purchases can use separate sequences, so testing does not affect the official invoice numbering. Currently, this appears not to be possible, so a clarification on future ideas of improvement will be needed.

Related Receipt vs Invoice discussion:
https://community.wpmanageninja.com/portal/space/fluent-cart/post/receipt-vs-invoice-is-confusing-please

Can we safely begin migrating now, knowing that this model will be clarified or improved soon?

The new releases are fantastic, but the coming months are critical for EU merchants (this last quarter, basically) and we need certainty around these invoicing fundamentals.

Otherwise, I guess, many EU merchants may have to postpone their FluentCart migration for another year πŸ˜… (not because the product lacks great features, but because software and integration decisions for the coming regulatory changes are being made now).

Our inbox is already on fire with compliance-related messages, to be honest.

Connecting a store to accounting and invoicing systems requires considerable work. Without a clear invoicing model or roadmap, it becomes difficult to justify choosing a flexible native solution like FluentCart (that we definitely love) over a SaaS that is already prepared for requirements such as VERI*FACTU and electronic invoicing in the EU. πŸ˜…

AndrΓ© Daus

You can change the numbering to your liking with some PHP code. I needed specific invoice numbers that are not just the last number +1. I added it to my FluentCart Add-on which I sunset already before it even reached live status. But there might me bigger obstacles than just the numbering...