Fichaloto

Blog Billing

The July milestone that nobody invoiced until November

6 min read

Nothing is lost: it is billed late, which is a different thing and almost always worse than it looks. The arithmetic fits in a paragraph, and the reason it always happens in August fits in a sentence.

The July milestone

A fixed-fee engagement, €60,000, three milestones: 30 % on signature, 40 % on delivery of the pilot, 30 % at close. The pilot goes out on 18 July. The person who handles billing leaves on the 25th.

By September nobody remembers the pilot, because the project has moved on to another phase. The €24,000 milestone gets invoiced in November, when the client asks why nothing has arrived. On thirty-day terms, that money lands in December instead of August: four months on a payment that was agreed and delivered.

The arithmetic, which is less obvious than it looks

The first thing anybody works out is the financing cost, and it is the smallest of the three: €24,000 over four months, at a cost of capital of 8 %, is about €640. Annoying, not serious.

The expensive part comes next. An invoice that turns up four months late gets challenged: your contact has changed, the year's budget has closed, and somebody in procurement wants it justified — exactly what was delivered in July. That is hours of your own people digging through email, and sometimes a credit note «to sort it out».

And the third cost, which never gets counted: a late invoice tells the client you are not on top of the account. Somebody who gets a July invoice in November starts to wonder, reasonably, what else is not being watched.

Why it always happens in August

Because the billing calendar almost never exists anywhere except the contract and one person's head. The contract does not remind anybody. The person does, right up until they go on leave, change jobs or have a bad week.

Every system that depends on somebody remembering fails in August, over Christmas and in the week of a big delivery. It is not a discipline problem. It is a design problem.

Write it on the day you sign

The fix is not a reminder in somebody's calendar: it is the billing calendar living in the same place as the project, written on the day the contract is signed, while you still have it in front of you and know exactly what was agreed.

In Fichaloto that is the project billing plan: a monthly retainer, a single payment, or a milestone table with its dates and its percentages. From then on, «what are we invoicing this month?» is answered by looking at one screen instead of opening four contracts. How a billing plan is set up.

What we do not do — and we say it because half the sector says the opposite — is issue the invoice on its own when the date arrives. An invoice carries sequential numbering and tax consequences; having it appear by itself is convenient for eleven months and expensive in the twelfth. What you get is the invoice already drafted against the due date it belongs to, and a person who reviews it and presses issue.

The case that is not anywhere

There is a fourth gap, and it is the hardest one to find by hand: the project that reaches its delivery date with no billing plan and no invoice at all. It does not show up in outstanding invoices, because there are none. It does not show up in the due dates, because none were written. It is simply not there.

Those are the ones invoiced six months late, or not invoiced at all. Which is why the cash screen shows them in the same table as forecast, issued and collected: a gap is only visible if somebody draws it.

Frequently asked questions

Does a recurring invoice in the accounting package not solve this?

For a flat retainer, yes. For a milestone tied to a delivery, no: the accounting package has no idea whether the pilot went out. The billing calendar has to live where the project lives, and feed accounting from there.

What if the project slips and the milestones move?

You regenerate the plan, and regenerating only touches what has not been invoiced yet. Anything issued or cancelled stays as it is: a calendar that rewrites the past is no use to anybody.

Can I bill a flat retainer and the overrun hours on top?

You can bill it, but the extra lines you build yourself. Which overrun gets charged and which gets absorbed changes with every contract, and automating that badly is worse than not automating it.

How many due dates can one project hold?

A hundred and twenty, which is ten years of a monthly retainer. If you need more, what you have is not a project: it is an open-ended support contract, and it is worth treating as one.

All of this is built into Fichaloto. See how it works.

Keep reading