Invoice automation the whole cycle, from order to posting
The billing cycle has six stages: the order, the counterparty check, issuing the invoice and sending it as a structured document, then matching the payment, chasing what is late and posting it to the ledger. We wire them into one flow, recurring invoices and foreign currency sales included. We start with the single stage where you lose the most days today.
- 6 stagesthat is how many points the billing cycle has from order to posting, and each one can be taken over on its own
- 200 invoicesroughly the monthly count at which moving numbers from one window into another becomes somebody's whole job
- 14 daysthe usual gap between the workshop and the first stage running in production, on your own invoices
The problem
Why does the money arrive later than the invoice says?
An order comes in on Friday. The invoice is issued by the person who gets back from holiday on Wednesday, so a fourteen day payment term starts five days later than it should. The client pays late, but nobody sees it until someone puts together a spreadsheet of arrears. The transfer lands with no invoice number in the reference, so accounting matches it by hand next month. The subscription invoice for March never went out at all, because it sat on a list that someone ticks off from memory.
None of these stages is hard on its own. The problem is that there are six of them, each one lives in a different system, and between them stands a person copying data across. At 50 invoices a month that is a few hours of work and a few mistakes. At 200 it is a separate desk whose only job is moving numbers from one window into another. Then there is currency: the rate from the day before the sale, the exchange difference on payment, the conversion used for VAT.
Part of this work is no longer a matter of convenience. Countries across the EU are phasing in mandatory e-invoicing on their own timetables, and the direction is the same in all of them: the invoice stops being a PDF and becomes a structured document that one system sends and another receives, with a confirmation coming back. Whatever your invoicing tool is today, it has to be able to produce that format and record the confirmation. An invoice assembled in a spreadsheet and emailed as an attachment needs an extra manual step to get there, and that is exactly the kind of step that gets skipped in a busy week.
- The payment term starts days after the sale, because the invoice waited on a person
- Arrears show up at month end, not on the day the term was missed
- Transfers with no invoice number in the reference sit unmatched for weeks
- One month of a recurring invoice never went out and nobody noticed
- The credit note and the original invoice live in two places, so the client balance is often stale
- Everyone works out the exchange rate their own way, and the differences surface at quarter end
Why now
What changed, so that the billing cycle can be wired up in weeks?
The first change is the format. Invoicing is moving from PDF attachments to structured documents that systems exchange through an interface. That reads like a compliance burden, and in practice it is the first time every invoice in circulation carries the same fields and its own identifier. Matching payments, catching duplicates and posting to the ledger all get easier on structured data than on scans, so the work you do to meet the requirement pays back inside your own finance team.
The second change is on the tooling side. Xero, QuickBooks, sevDesk and Fakturownia all expose APIs that let you issue an invoice, read its status and pull the PDF. Comarch Optima, Symfonia and SAP Business One sit on your own infrastructure, so the same thing runs through a connector inside your network or straight against the database. Shopify, WooCommerce, PrestaShop and BaseLinker can report a paid order the same second it happens, and the HubSpot API reports a closed deal the same way. The cycle logic goes into n8n, Make or a custom integration, and your systems stay where they are, doing what they already did.
This cycle is made of specific scenarios that we describe separately: automatic invoicing from CRM, VAT number verification before issuing, automatic payment reminders once a term is missed, and the automatic financial report at the end. This page is about the whole thing: how the stages sit one behind the other and what happens at the joins, because the joins are where the days go.
The third change is the AI agent. A workflow will issue the invoice, but it will not answer the question how many payments are unmatched today and which client owes the most. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, from the data in your invoicing system and your bank statements, with nobody logging in and nobody compiling a report.
What changes
What does a company get when the billing cycle runs itself?
The invoice goes out the same day as the sale
A deal closed in the CRM or a paid order in the shop triggers the invoice with no data retyped. The payment term starts from the day of sale, not from the day somebody had time for it.
The road from order to issued invoice drops from several days to several minutes
Structured e-invoicing handled in the same flow
The invoice goes out in the structured format at the moment it is issued, and the identifier and status come back into the CRM and onto the drive. A rejection does not disappear: the workflow reports it to accounting with the error text and the document number.
Every issued document has a recorded status, sent, confirmed or rejected, with a reason
Recurring invoices with no list to tick off
A schedule issues subscription invoices on the agreed day of the month and takes account of mid period changes: an amendment, a suspension, a different number of users. A skipped month stops being possible.
One schedule instead of a contract spreadsheet that someone walks through once a month
The payment finds its own invoice
The workflow reads the bank statement and matches payments to invoices on amount, transfer reference and document number. A partial or bulk payment goes into a manual queue with a suggested match, instead of being left with no description.
Three matching criteria instead of reading transfer references one by one
Currency converted by one written rule
The rate for the invoice and for VAT comes from one source agreed in the workshop, and it is stored with its date next to the document. Exchange differences are worked out when the payment is matched, not at quarter end.
Rate, date and conversion recorded against every foreign currency invoice
Questions about receivables in a plain sentence
How many invoices are overdue. Who is more than 30 days late. How many payments are waiting to be matched. The AI agent answers from the invoicing system, with no login and no report put together by hand.
An answer in 5 to 10 seconds, the same one for the owner and for accounting
And in your company
What if our invoices are issued by an external accountant?
Four sentences we hear most often, and what we say back to them. If your sentence is a different one, say it on the consultation: that is the faster way to find out whether there is anything here worth talking about.
Our accounting firm issues the invoices, we only send them the data.
Then we automate your side of that handover: the sales summary for the accountant builds itself, in the format they accept, and goes out on the same day every month. Payment matching and reminders stay with you, because that is your money and those are your clients. We agree the split with the accountant during the workshop, so nobody does the same work twice.
We issue 20 invoices a month, that is no trouble at all.
At 20 invoices, issuing them really is not the problem, and we will tell you so. What is worth a look is the stages after it: whether anyone watches the payment terms, whether payments get matched as they arrive, whether the recurring invoices go out every month. Quite often the sensible first automation is chasing, not issuing.
Our invoicing system already sends structured e-invoices by itself.
Good, and there is no reason to duplicate that. The e-invoicing requirement covers one stage out of six, and the days usually go missing before it and after it: while the data for the invoice is being collected, and while the payment is being matched. In the workshop we find where your bottleneck actually sits, and if it falls outside e-invoicing, that is where we start.
We sell in euro and in pounds, our accountant works out the rates.
The exchange rule is one of the things we write down in the workshop: which source the rate comes from, which date, how VAT is converted and what happens to the exchange difference on payment. A written rule gives the same answer every time, including in the weeks when the accountant is away. The substantive decision belongs to your accounting team, we only carry it out without deviation.
- Invoicing systems and ERP
- Xero, QuickBooks, sevDesk, Fakturownia, Comarch Optima, Symfonia, SAP Business One
- E-invoicing and archive
- structured e-invoice formats, PEPPOL, Google Drive, Google Workspace, Microsoft 365
- CRM and proposals
- HubSpot, Pipedrive, Salesforce, Zoho
- Sales and orders
- Shopify, WooCommerce, PrestaShop, BaseLinker, Amazon
- Payments and statements
- bank statements in MT940, camt.053 or CSV, confirmations from payment gateways
- Data, automation layer and alerts
- Google Sheets, BigQuery, SQL databases, n8n, Make, Zapier, custom API integrations, Slack
Six stages of the billing cycle and what the automation takes over
We break the cycle into stages, because almost nobody automates all of them at once. In the workshop we pick one for the first rollout, usually the stage that loses the most days or the most money.
| Stage of the cycle | What happens without a person | What we wire it with |
|---|---|---|
| 01. Order or closed deal | the workflow collects counterparty details, line items, amounts and payment terms | HubSpot, Pipedrive, Shopify, BaseLinker, a spreadsheet |
| 02. Counterparty check | VAT number, VAT status and bank account checked before issuing, result stored with a date | VIES, the national VAT register, bank account registers |
| 03. Issuing and e-invoicing | the invoice is created in the invoicing system and sent in the structured format, the identifier returns to the CRM | Xero, sevDesk, Comarch Optima, PEPPOL |
| 04. Delivery and archive | PDF to the client from the right template, a copy in their folder on the drive | email, Google Drive |
| 05. Payment matching | the payment from the statement matches its invoice on amount, reference and document number | MT940, camt.053 or CSV statements, the invoicing system |
| 06. Chasing and posting | a reminder sequence after the due date, escalation, a summary for accounting | n8n or Make, the ERP, the accounting firm |
| Outside the numbering: recurring invoices | a schedule issues subscriptions on the agreed day and knows about mid period changes | CRM, invoicing system, contract register |
The order is the natural one, but the rollout order does not have to follow it. For most clients the first rollout covers one or two stages, and the rest goes in after the measurement.
How we work
Five steps from six people in the cycle to one flow
Process first, tools second. Every step ends with something you can judge before you decide on the next one.
Process workshop
We take your cycle apart into stages and measure them in days: how long from sale to invoice, from invoice to payment, from payment to it being matched. We write down the rules that currently exist only in people's heads: who issues, which term for which client, which rate, what happens to a recurring invoice when the contract is amended.
Picking the first stage and designing it
Out of six stages we choose one, the stage with the biggest loss of days or the biggest risk of error. We settle the tool, the data needed for each decision, how edge cases are handled and what stays with a person. The rest of the cycle waits, in an agreed order.
Pilot on real data
The workflow runs alongside the current way of working, on your invoices from the last month. We test the hard documents rather than the easy ones: credit notes, foreign currency invoices, partial payments, counterparties with incomplete details, subscriptions changed mid period.
Production and handover
Once the results check out we switch the stage to production, with error monitoring and an alert when a document does not go through. The person who owns invoicing learns to change the rules alone: a new template, a different payment term, a new counterparty, taking a client out of the reminder sequence.
Measurement at 30 and 90 days
We go back to the numbers from the workshop and measure the same gaps in days. Only then do we decide on the next stage of the cycle, because without a measurement every further rollout is guesswork.
Before and after
How the month changes for the person who owns invoicing
Before
- Monday goes on issuing invoices for last week's orders
- Arrears come from a spreadsheet she fills in herself once a month
- Payments with no invoice number in the reference get matched by amount, in the bank window
- Recurring invoices get ticked off a list, and once a quarter one of them does not
After
- Invoices for the weekend are issued and delivered before Monday morning
- She hears about an overdue invoice on the day the term is missed, from an alert, not a spreadsheet
- She only handles partial and bulk payments, the workflow matches the rest
- Subscriptions go out from a schedule, and she checks the exceptions rather than the whole list
The first stage is visible in production 14 days after the workshop. The effect in days, meaning the shorter road from sale to payment, is judged at 30 and at 90 days.
For the person signing this off
What an owner or a finance director gets out of it
The billing cycle turns into numbers you can manage. You know how many days pass from sale to invoice and from invoice to payment, how much money is standing overdue and with whom. That is the data you need for a conversation about working capital, about credit limits, and about whether you need financing at all or just faster invoicing.
The second thing is about the risk that sits on your signature. Rules written down in the workshop behave the same way when the person who owns invoicing is on holiday and when they leave the company. Meeting the e-invoicing requirement stops depending on whether somebody remembered an extra step, and every invoice carries a record of when and on what basis it was issued. You start with one stage, so the first decision is small and reversible.
- The road from sale to payment counted in days, before the rollout and after it
- Invoicing and exchange rules written down, independent of any one person
- A pilot alongside the current way of working, so the old way runs until testing ends
- Scope by stage: you decide on one stage, not on rebuilding your finance function
What it costs
The workshop has a published price, the rollout is quoted after it
The process workshop costs EUR 3,500 net per week and runs from 1 to 7 weeks. With a billing cycle one or two weeks is usually enough, because the process is narrow but carries a lot of exceptions to write down: credit notes, currencies, subscriptions, the handover to your accounting firm. We quote the rollout after the workshop, once it is clear how many stages are in scope and what state the systems are in.
You pay the running cost of the workflow directly to the tool provider, n8n or Make for example, or you pay nothing at all when it sits on your own infrastructure. The same goes for the invoicing system and for model usage with the AI agent, where a single query costs the provider roughly EUR 0.005 to 0.07. No margin from us and no reselling of licences. There is more about the workshop itself on the process workshop page.
Process workshop
EUR 3,500 net
per week, and with a billing cycle that is usually one to two weeks
A self-contained piece of work. It ends with a measured cycle, written rules and an order of stages you could roll out without us.
- The billing cycle broken into stages and measured in days
- Written rules: terms, templates, exchange rates, recurring invoices, credit notes
- A tool recommendation and the first stage to roll out
- The handover to your accounting firm and the scope of e-invoicing agreed
- Most popular
Workshop and cycle rollout
Quoted after the workshop
scope follows from the number of stages and the state of the systems
The option most companies choose. The first stage in production 14 days after the workshop, each further one in 2 to 4 weeks.
- Everything in the workshop
- A workflow in n8n, Make or through the API, wired to the invoicing system and the CRM
- Structured e-invoicing, credit notes, currencies and recurring invoices handled
- Payment matching from the bank statement and a reminder sequence after the due date
- Pilot alongside the current way of working, switchover with error monitoring
- Training so the invoicing owner can change the rules alone
Billing cycle and an AI agent
Quoted after the workshop
for companies that ask about receivables several times a day
Everything in the rollout plus BOND, the company AI agent that answers questions about invoices and payments in a plain sentence.
- Everything in the cycle rollout
- An AI agent wired to the invoicing system, the CRM and the bank statements
- An answer in 5 to 10 seconds: who is late, how much is overdue, what is unmatched
- Alerts on overdue invoices and on documents rejected by the e-invoicing network
- Agent rollout takes around 2 months, regardless of how many stages are in scope
The workshop ends with a document that stands up without us: a measured cycle, written rules and an order of stages. You can carry it out with your own hands, hand it to another firm, or shelve it. If the workshop shows that your invoicing system already does what you are asking about, we say so and show you where to switch it on, instead of selling you a rollout.
Frequently asked questions
What is invoice automation?
It is a workflow taking over the whole billing cycle, not just the act of creating a document. An order or a closed deal triggers the data collection, the counterparty check, issuing the invoice, sending it in the structured format, delivering it to the client, matching the payment and chasing it once the term is missed. People handle the exceptions that no rule covers.
Does invoice automation cover structured e-invoicing?
Yes, it is one of the six stages of the cycle. The invoice goes out in the structured format at the moment it is issued, and the identifier and status come back into the CRM and into the archive. Requirements differ by country and are being phased in on different timetables, so in the workshop we check what your markets demand and what your current system already does. If it handles this already, we do not duplicate it.
How long does an invoice automation rollout take?
The first stage usually 14 days after the workshop, each further one 2 to 4 weeks. The workshop itself is 1 to 2 weeks for this process. We do not roll out six stages at once, because then the first value arrives after a quarter rather than after two weeks, and there is nothing to measure along the way.
Will this work when our books are kept by an external accounting firm?
Yes, the boundary just sits somewhere else. We automate your side: collecting the data, issuing and delivering the invoice, matching payments, chasing. The summary for the accountant builds itself, in the format they accept, on the same day every month. We agree the scope together with the firm during the workshop.
How do you issue recurring subscription invoices?
From a schedule built on the contract register, not from a list ticked off by hand. The workflow knows the issue date, the billing period and mid period changes: an amendment, a suspension, a different number of users. A change halfway through the month produces a pro rata invoice under the rule written down in the workshop, the same rule every time.
How does the automation match payments to invoices?
On amount, transfer reference and invoice number, or the e-invoice identifier where the counterparty quoted it. An unambiguous match closes the invoice and takes it off the reminder sequence. A partial payment, a bulk one covering several invoices, or one with a reference and no number goes into a manual queue with a suggested match, so it never sits there with no description.
What about invoices in euro and in pounds?
The exchange rule gets written down in the workshop: the source of the rate, the date, the conversion used for VAT and how the exchange difference on payment is worked out. The rate and the date are stored with the document, so six months later you can reconstruct where the amount came from. The substantive decision belongs to your accounting team, we carry it out without deviation.
How many invoices a month do we need for this to pay off?
The invoice count on its own is a weak criterion. At 20 invoices, issuing them is rarely the problem, but chasing and payment matching often are. At 200, issuing is already a separate desk. On the consultation we count the days in your cycle, and those are what say whether there is anything here to automate. If there is not, we say so plainly.
Let us count how many days pass from your sale to the payment
The free consultation takes 30 minutes. You tell us how many invoices you issue, who issues them and what happens once a payment term is missed. You leave the call with the road from sale to payment counted in days, and with a view on which stage is worth starting from. You do not have to give us access to any system at this stage.
We run at most two rollouts at a time, so that someone is genuinely sitting on each of them.
Book a free consultationPS. If somebody in your company spent this month staring at the bank looking for the invoice a payment belongs to, that is exactly this problem. The money is in the account and the company does not know about it, because the billing cycle ends at issuing the document. Wire the whole thing up and the road from sale to payment gets shorter by days, not by minutes. You write directly to Pawel.