The Invoice You Send Late

The company booking was three weeks ago. The invoice has not gone out, because invoicing happens when somebody has a quiet afternoon.

And a quiet afternoon is the thing this business has least of.

What the delay costs

Cash, obviously. Later out means later in, on top of whatever payment terms apply.

Credibility. ⚠️ A venue that invoices late is assumed to be casual about money generally — and the person receiving it is frequently the one who decides where the next booking goes.

Disputes you cannot win. Three weeks later, details are contested and nobody remembers. ⚠️ The longer the gap, the weaker your position, whatever actually happened.

Their process, not yours. Companies pay on cycles. Miss the cut-off and you wait for the next one — the delay is not the days you were late, it is a whole month.

Why it slips

No fixed time. ⚠️ The whole mechanism. Invoicing has no slot, so it happens when everything else has stopped, which is never.

Assembling takes longer than sending. What was ordered, what was agreed, who to send it to. The information is scattered and reconstruction is the work.

Nobody owns it. Or the owner is the busiest person.

It is not urgent until it is. No consequence today, and by the time there is one, the delay is already spent.

The twenty-minute routine

A fixed slot, weekly. ⚠️ Same day, same time. Not "when there is time."

Everything from the previous week goes out in it. No exceptions and no batching for later.

One person, by role. With cover for their absence.

Send to a named person, not an inbox. ⚠️ Invoices to a generic address take longest. Ask at booking who handles payment; it costs one question.

Making assembly fast

The reason it takes long is that the details were never captured in one place.

Capture at booking. ⚠️ Company name, invoice contact, purchase order reference if they use one, terms. Asked at booking, it is one minute; chased afterwards, it is three emails.

Note what was agreed. Inclusions, rate, anything discounted. This is the part that generates disputes.

Record on the night. ⚠️ What was actually taken, while the person who was there can still say.

The follow-up

Note when payment is due, at the moment you send.

⚠️ Then chase on the day — one short message. Not weeks later, when it is awkward, and not never, which is what mostly happens.

Most late payment is administrative, not refusal. The first chase resolves most of it, and the tone should assume exactly that.

Three to hold

Days from event to invoice sent. ⚠️ Measure it for a month. It is nearly always longer than believed.

Days from invoice to payment. The second half, and it tells you whether the terms or the chasing is the problem.

Invoices disputed. ⚠️ Correlated with delay — and the correlation is the argument for the weekly slot.

Where the record has to sit

An invoice is fast to produce when the booking already holds what it needs — who to bill, what was agreed, what was taken. If those live in three places and one person's memory, invoicing is reconstruction, and reconstruction gets postponed.

tasteck keeps bookings, orders and settlement on the same records, so what was taken and what was agreed sit together when it is time to bill.

Nobody is being slack. Invoicing was never given a time, and work without a time happens after everything that has one.