Help for owners
I want invoices to be created automatically when an order comes in
Short answer
Automatic invoicing copies an order into your accounting system as an invoice. It goes wrong in predictable places: the same order sent twice, tax calculated differently in the shop and the books, customers that do not match, and refunds or edits that are never passed on. Fix those rules on paper first, then automate.
Does this sound like your situation?
- I retype every order into my accounting software.
- Some orders never get an invoice and I find out at month end.
- A few customers received two invoices for one order.
- The invoice total differs from what the customer paid.
- Refunds and cancelled orders still sit as open invoices.
Why does this happen?
There is no single order identifier
If the invoice does not carry the order's own ID, a retry or a second trigger cannot tell that the invoice already exists. The result is two invoices for one sale.
Tax and totals are calculated in two places
The shop and the accounting system each work out tax, rounding, shipping and discounts. When their rules differ by even a cent, totals do not match and reconciliation turns manual.
Customers are matched by name
Matching by name or by a typed email creates a new customer for every small difference, or attaches an invoice to the wrong person. A stable customer ID or a rule for unknown customers is needed.
Only the first event is handled
A flow built for new orders often ignores edits, partial shipments, refunds and cancellations. The books then drift away from the shop.
A failed step leaves no trace
When the accounting system rejects an invoice, for example because a product code does not exist, and nobody is told, the order is simply never invoiced.
What can I do about it today?
- Write down your current invoicing rulesWhen is an invoice raised, on payment or on shipping, who counts as a new customer, how tax and shipping appear. Write it as plain sentences.
- Collect ten real orders of different kindsInclude a discount, a refund, a foreign customer and a partial shipment. These become the test cases.
- Ask your accountant what must appear on an invoiceNumbering, tax lines and customer details are their call. I do not give tax or legal advice.
- Do not switch on any automation against live books yetA new connection on live books can create invoices that are hard to remove. Ask for a test company or a sandbox first.
- Decide who is told when an order fails to invoiceName one person and one channel. A failure nobody sees is the most expensive kind.
When should I bring someone in?
- You already see doubled or missing invoices from a connection that is running.
- Your orders come from more than one place, such as a website and a marketplace.
- Tax rules differ by country or product.
How do I handle it?
- Write the rules with youI turn your invoicing habits into a one-page rule sheet, with the cases you collected, before building anything.
- Read the vendor's current API documentationI check what the accounting system accepts, its limits and its duplicate protection, from its official documentation, not from memory.
- Make every step safe to repeatThe order ID is stored with the invoice, and the flow looks for it first, so a retry cannot create a second invoice.
- Test with the real cases on a copyThe ten sample orders run through a test company, and the totals are compared line by line.
- Report failures to a personOrders that cannot be invoiced go to a short daily list with the reason, and a count of orders against invoices is compared each day.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Should the invoice be created on order or on payment?
That is a business and accounting decision, so ask your accountant. Either is possible, and the flow follows the rule you choose.
Can this work with the accounting software I already use?
Most accounting systems have an API. I confirm what yours allows from its official documentation before promising any detail.
What happens to refunds?
They need their own rule, usually a credit note linked to the original invoice. I treat them as a separate case, not an afterthought.
Do I need custom code, or is a no-code tool enough?
For simple one-to-one orders a no-code tool can be enough. Custom logic matters once there are bundles, multiple tax rules or several sales channels.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.