Agentic

The invoicing and accounts receivable agent: money coming in faster

How many days pass between the moment the work is completed and the moment the invoice is sent out? Not between the invoice and payment, but between completion and the invoice.

How many days pass in your company between the signature on the order form and the first invoice? Not between invoice and payment. Between closed-won and invoice.

How many days sit between unloading and the invoice in your business? Not between invoice and payment. Between the moment the trailer stands empty at the consignee and the moment the shipper receives your bill.

How many days pass in your agency between an accepted sprint demo and the invoice for that milestone? Not between invoice and payment. Between client sign-off and invoice.

How many days pass between the signature on the factory acceptance test in your own hall and the milestone invoice that goes with it? Not between invoice and payment. Between passed test and invoice.

The second figure is in your report. The first one isn’t mentioned anywhere, and that’s exactly why it’s increasing.

Your DSO sits in the board deck. The gap before the invoice sits nowhere, so it grows with every AE you hire.

Your DSO appears in every monthly report. The days between unloading and invoice appear nowhere, so they grow quietly.

Your DSO sits in the monthly report. Work accepted but not yet billed sits nowhere, which is why it grows.

Your DSO appears in the monthly report. The days before the milestone invoice appear in no ERP report, and that is why they grow.

I would like to carry out a baseline assessment of my invoicing process

30 mins · senior consultant · no slide deck

Your accounts receivable report starts from the invoice date

Your DSO clock only starts on the invoice date

Your DSO starts counting on the invoice date, not at unloading

Your debtor report starts counting at the invoice, not the go-live

Your debtor ledger only starts counting at the milestone invoice

Outside the measurement

This means that half of your cash conversion has become invisible to the only tool you have at your disposal.

The mechanism

The completion record is stored in the ERP system or the project management system. The invoice is stored in the accounting software. There is no system linking the two; instead, there is a person who is not paid to do this.

The deal lives in HubSpot or Salesforce. The invoice lives in Chargebee, Stripe or Xero. Between them sits no integration, only a finance colleague retyping signed deals alongside month-end close.

The trip lives in your TMS. The invoice lives in the accounting package. Between them sits no link, only a planner with a pile of CMRs he works through after his shift.

The hours live in Jira and the timesheet tool. The invoice is built in the accounting package. Between them sits no link, only a project manager lining up exports on a Friday afternoon.

Extra work during commissioning lives in the ERP as hours on the order number. The invoice lives in the accounting package. Between them sits the project manager's spreadsheet, and invoicing is not his job.

The project manager is already with the next client. The finance department is waiting for the timesheet, the handover document or the signed receipt. Nobody realises that a completed order hasn’t been invoiced this month, because no alarm is raised when something doesn’t happen.

The AE has already celebrated the upsell from 40 to 65 seats in Slack and is chasing the next deal. Finance waits for the signed amendment and the right start date. Nobody sees that those extra seats went unbilled this month, because an invoice that does not exist sends no alert.

The driver is already heading to Duisburg for the next load. Finance waits for the signed CMR and the log of three waiting hours at the distribution centre. Nobody notices those waiting hours never get billed, because no alarm sounds for something that does not happen.

The project manager is already in the kick-off for the next engagement. Finance is waiting for the client's product owner to sign the acceptance. Nobody notices that forty hours of change-request work went unbilled this month, because nothing sounds an alarm for something that did not happen.

Your service engineer is already driving to the next breakdown near Stuttgart. The signed job sheet with his travel hours and the replaced bearing is still in his van. Finance sees nothing, because an uninvoiced service visit leaves no trace in the monthly figures.

Technical blueprint with dimension lines and cross-sections on blue paper

Work out the cost using your own figures

365Divide your annual turnover by 365. The denominator is 365 calendar days, not working days, and this remains the denominator throughout the calculation.

With an annual turnover of four million euros, that works out at around 10,960 euros in turnover per day. If there is an average of nine days between completion and invoicing, then nine times 10,960 is approximately 98,600 euros that is permanently held by your customers rather than by you. That amount simply carries over.

At €6 million ARR you bill roughly €16,440 a day on average. If twelve days sit between closed-won or renewal and the invoice, twelve times €16,440, around €197,000, stays permanently with your customers. At a burn of €250,000 a month, that is over three weeks of runway that only rolls forward.

A haulier with forty tractor units and six million euros in annual revenue books about 16,440 euros of freight a day. With an average of twelve days between unloading and invoice, twelve times 16,440, roughly 197,000 euros, sits permanently with your shippers instead of in your account. That amount only moves along.

An agency of 60 people turning over six million euros a year books roughly 16,440 euros a day. With twelve days on average between acceptance and invoice, twelve times 16,440, about 197,000 euros, sits permanently with your clients. That sum only moves with your growth.

At annual revenue of 24 million euros, that is roughly 65,750 euros a day. If an average of fifteen days passes between accepted machine and milestone invoice, fifteen times 65,750 is roughly 986,000 euros sitting permanently with your customers. You pre-finance that amount, month after month.

Second-order costs

Tied-up working capital is working capital that you do not invest in stock, in an engineer or in a market opportunity. And the pattern persists because it is not part of anyone’s job description. Major customers unilaterally extend their payment terms, and you only realise this during the payment reconciliation process, weeks later.

That money does not go into another AE, your launch in Germany or a longer runway to your Series B. The pattern persists because it falls exactly between RevOps and finance. Enterprise customers quietly move you from 30 to 60 days through their procurement terms, and you spot it only at month-end close, weeks later.

Money stuck with shippers is money you do not put into the deposit on a new tractor unit or into hiring two drivers. The pattern persists because it is in nobody's job description. And a large retailer's distribution centre moves its payment terms from thirty to sixty days on its own. You spot it only at reconciliation, weeks later.

Working capital that is locked up is capital you cannot put into another senior developer or a sharp fixed-price bid. The pattern stays because it sits in nobody's role. And your largest account quietly moves its payment term to sixty days through procurement. You only see it at reconciliation, weeks later.

That money cannot go into the deposit on a servo drive with a six-month lead time, or into a second engineer for the next project. It sits in nobody's job description, so it stays. And when a German group's purchasing department quietly moves the payment term from thirty to ninety days, you only notice at reconciliation, weeks later.

The calculation example uses fictitious input figures to illustrate the method. This is our estimate, not a measured standard.

[ Four questions ]

Four questions

  1. On average, how many days are there between the completion date and the invoice date for your last fifty invoices, and do you know that figure off the top of your head, or do you need to look it up?

  2. What proportion of your outstanding balance is owed by three customers, and do those happen to be your three biggest customers in terms of turnover?

  3. How many customers consistently pay later than the deadline specified in their own contract, and what actually happens at your company on day 31?

  4. Who in your organisation is currently alerted if a completed order has not yet been invoiced by the end of the month?

The agent runs the PRAL loop on your invoice stream

Perceive, Reason, Act, Learn

Perceive retrieves completed orders or project milestones from the ERP system or project management system, outstanding items from the accounting software, and the entries on the bank statements.

Reason: it determines what should have been invoiced, matches credit entries against outstanding items and identifies any discrepancies.

Act: he prepares draft invoices, sets up the series of reminders for the contract term and draws up a reconciliation report containing only the exceptions.

Learn, your corrections are reflected in the rules – for example, that one customer requires a PO number on the invoice, whilst another only accepts invoices via their own portal.

Learn, your corrections flow back into the rules, for example that a German customer only accepts an XRechnung, or that an enterprise account pays each seat expansion only against a new PO number.

Learn, your corrections flow back into the rules, for example that one shipper demands the CMR scan with every invoice line, or that a German customer accepts the Maut surcharge only on a separate line.

Learn: your corrections flow back into the rules, for instance that one client wants hours itemised per epic, or pays for extra work only with the signed change request attached.

Learn: your corrections flow back into the rules. One German customer pays the final instalment only with the signed acceptance certificate attached; another wants spare-parts invoices via SAP Ariba.

Two people sitting at a laptop; one is explaining something to the other; on the screen is a field of blue data points

The autonomy ladder

Money doesn’t change hands here without a signature. Capgemini’s autonomy ladder includes preparations for Level 3 – semi-autonomous – involving multiple steps across multiple systems, with a human supervising the process and handling exceptions.

The payment transaction itself reverts to L2. Sending an invoice and reconciling a transaction are Request-Approval processes; a person signs off on the batch. Credit notes, debits and initiating a direct debit process are Mandatory Halt processes; the agent cannot proceed beyond this point. Capgemini estimated in 2025 that around 15 per cent of processes would run at L3 or higher. This workflow is not one of the exceptions that fall into that category.

Two hard borders

The agent never determines the VAT rate or the treatment of intra-Community supplies, including reverse charge, themselves. They apply the set of rules you have defined and stop at any deviation. And every action is logged with its source, rationale and timestamp, as that log serves as your evidence for your accountant and the regulatory authority.

Week one: what you, as the person with overall responsibility, need to do

You take a baseline measurement of your invoicing discrepancy across fifty invoices. You set three figures: the acceptable margin of error on a draft invoice, the percentage of drafts you approve without amendment, and the threshold below which you revert to a fully manual check. And you appoint a sign-off authoriser. Gartner predicts that more than 40 per cent of agentic projects will fail by 2027 due to unclear business value. Those three figures are your safeguard against that.

Capgemini, 2025. Gartner, 2025.

[ By sector ]

The same workflow, three different diagnoses

SaaS scale-up

The unit is the contract, the clock is the monthly billing cycle, and the tool is the transaction list.

  1. 01 Determine which of your contract changes – upgrades, seat extensions and interim renewals – were not invoiced in the same batch.
  2. 02 Have the agent compare the contract balance with the invoiced balance for each run and report only the difference.
  3. 03 Ask him to calculate the pro rata amount as a draft, using the transaction date as the source, and submit it to Finance for approval.
  4. 04 Set a single figure: the percentage of changes that are included in the same month’s run.
SaaS scale-up

Logistics

The unit is the journey or consignment, the time frame is daily, and the tool is the surcharge record.

  1. 01 Work out how many euros’ worth of waiting time, extra stops and fuel surcharge you did not pass on to customers last month, per hundred journeys.
  2. 02 Ask the agent to match the journeys carried out each day in the TMS with the invoice lines created.
  3. 03 Ask him to provide the missing allowance rules, together with the supporting evidence, a timestamp or a scan.
  4. 04 Set a strict cut-off: any journey that still hasn’t generated an invoice line item after ten days goes to the planner rather than to finance.
  5. 05 Focus on revenue leakage per hundred journeys, not on invoice processing time.
Logistics

Mechanical Engineering

The unit is the timeframe within the project, the clock is the milestone, and the tool is the handover protocol.

  1. 01 For each ongoing project, calculate the number of days between the signed acceptance and the instalment invoice.
  2. 02 Ask the agent to link the acceptance documents to the payment schedules in the contract and to identify any missing signatures.
  3. 03 Once full acceptance has been given, have him prepare the instalment invoice, including the correct VAT treatment for exports, and submit it to the project manager and the finance department.
  4. 04 Report on the number of days between acceptance and invoicing for each project, not on the total accounts receivable balance.
Mechanical Engineering
A portrait composed of shards of mirror, each shard representing a separate fragment
Please bring

The result is your baseline measurement

Without it, you’re just buying a solution to the most obvious part of the problem.

Before you use this

Please read this first, as the instructions below involve both personal data and financial data. Carry this out using a business subscription, never a consumer account, and enter into a data processing agreement with your data provider before pasting any real data. Make sure you know in which region the processing takes place. Anonymise the data before pasting it; remove customer names, IBANs, contact details and addresses, and replace them with ‘Customer A’ and ‘Customer B’. Dates and amounts are sufficient. Your GDPR obligation here coincides with something you already do: the seven-year statutory retention period for your records. That retention period applies to your accounts, not to a chat history with a data model provider. So, set out how long this exchange will be retained and who is authorised to access it. And decide now who will halt the conversation and take over if an outcome arises that you cannot explain.

Je bent mijn financieel analist. Ik plak hieronder 30 recente facturen als tabel met vier kolommen: opleverdatum, factuurdatum, vervaldatum, betaaldatum. Alle klantnamen zijn vervangen door Klant A tot Klant Z. Doe exact dit, in deze volgorde.

1. Bereken per factuur twee vertragingen: (a) oplevering naar factuur, in dagen, (b) vervaldatum naar betaling, in dagen. Toon de mediaan en het hoogste kwartiel van beide.
2. Vertel me welke van de twee het grootste deel van de totale doorlooptijd verklaart. Geef het percentage.
3. Groepeer per klant en noem de drie klanten met de hoogste som van (bedrag maal dagen te laat). Noem dat bedrag in euro-dagen.
4. Geef per bevinding aan of ze wijst op een intern proces of op klantgedrag. Onderbouw dat met de data, niet met een aanname.
5. Sluit af met de drie meetpunten die ik maandelijks moet volgen om te zien of dit verbetert. Maximaal een regel per meetpunt.

Vraag geen aanvullende gegevens en verzin geen getallen. Als een datum ontbreekt, sluit die factuur uit en meld hoeveel je hebt uitgesloten.

Where this ends

This agent doesn’t apply everywhere. Our rule of thumb – not a measured standard – is that if you have fewer than about fifty invoices a month, you won’t recoup the set-up costs, and a clear agreement within the team works out cheaper. Nor does it apply if every invoice is negotiated, because then you’re not invoicing for a process but for a relationship. It certainly has no place if the handover date isn’t recorded anywhere; in that case, the agent has no ‘Perceive’ step and you’re building a machine for nothing. And if you let customers pay because they dispute the quality, an agent who dutifully sends reminders will only exacerbate the conflict. That’s not a debt collection problem.

Read more

I’d be happy to work with you to work out where your money is going.

I would like to measure how much runway your billing holds.

Let us measure together where your freight money stalls.

Let me measure where your accepted work gets stuck.

Let's measure how much cash your delivered machines hold.

Book an appointment and bring your last fifty invoices with you.

Book a call and bring your last fifty closed-won deals from the CRM.

Book a call and bring your last fifty trips with their CMRs and invoices.

Book a call and bring your timesheet export from the last quarter.

Book a call and bring twenty SAT reports with their invoices.

I would like to carry out a baseline assessment of my invoicing process

30 mins · senior consultant · no slide deck