The December Payment Diary: A One-Page Cut-Off Check for Project Teams

December has a habit of making sensible project teams look disorganised. Not because the work is bad, but because the normal rhythm disappears. Approvers take leave, suppliers chase earlier, finance runs a tighter timetable and someone discovers on 22 December that a key invoice is still sitting in a shared inbox with the subject line “for info”.

A missed payment run is not usually a catastrophe. But it creates January noise: awkward calls, repeated explanations and a supplier who suddenly wants to revisit terms. The fix does not need to be a full finance review. It needs a single page, agreed early, that answers one question: what has to happen, and by when, for December’s invoices to be paid without a scramble?

That is the December payment diary. It is less glamorous than a project plan and far more useful than a hopeful email saying “please chase anything outstanding”.

Start with the days people actually work

The first mistake is treating December as a normal month with tinsel. It is not. The last genuinely useful approval window is often a week before the office goes quiet, and the first week of January is rarely a fast payment week either. So build the diary around people, not just bank holidays.

For 2026, look at the week beginning 21 December with a realistic eye. Who is in? Who is covering? Which finance colleague is on leave but still copied into every approval email? If the answer is “I think Sarah is around”, that is not a plan. It is a rumour.

Work backwards from the supplier’s payment terms. If an invoice needs 30 days, and the approval only lands on 24 December, the payment date is not a finance problem — it is a diary problem. The one-page sheet should show the last practical date for an invoice to be received, approved and passed to finance. Anything after that date goes into January, and everyone should know it.

The four boxes worth filling in

A useful cut-off check does not need forty rows. Four boxes will do.

Invoice date and receipt date. When was the invoice actually issued, and when did your team actually receive it? Those are often different. A supplier may have dated an invoice in November but sent it to an old project inbox in December. Both dates matter because they affect approval and payment expectations.

Approval owner and cover. Name the person who can approve. Then name the person who can approve when the first person is away. A delegated authority is worth more than a cheerful “I’ll keep an eye on it”. If the approval sits with a client, make that explicit too. A project team cannot pay what it cannot approve.

Payment method and bank cut-off. BACS, Faster Payments, CHAPS and international transfers do not behave the same way. Cut-offs also shift around bank holidays. Do not rely on last year’s note in the shared drive. Ask your bank or finance team for the 2026 holiday processing timetable and put the key dates on the sheet.

Supplier expectation. Has anyone told the supplier what to expect? A short note saying “approved, scheduled for the December run” prevents a lot of chasing. A shorter note saying “this will now be January” prevents a lot of resentment.

The approval cover question

Most December payment delays I see are not caused by finance refusing to pay. They are caused by an approval that nobody owns for ten days. The invoice is valid, the work is done, but the only person who can sign it is on a train to somewhere with poor signal.

So the diary should include an approval cover column. Not a vague deputy, but a named person with the authority to say yes. If that authority does not exist, fix it before December rather than discovering it on the 23rd. A one-line email confirming delegated approval is enough, provided it is written down and sent to finance.

It also helps to separate “approval” from “queries”. A query can wait for someone to return. An approval should not. If the invoice needs a technical sign-off, get that done early and keep the commercial approval moving separately.

Bank cut-offs are not a guess

Every December, someone says “the bank is closed, so we’re fine” and then discovers that the payment file needed to be with finance two days earlier. The bank may be closed, but the processing timetable is not simply the office calendar.

Put the cut-off dates on the sheet and assign someone to confirm them. For UK payments, that usually means checking the finance team’s BACS submission timetable, same-day payment limits and any international cut-offs. For suppliers paid from overseas, add a line for currency and correspondent bank timing. None of this needs to be complicated. It just needs to be checked rather than assumed.

Tell suppliers before they chase

A short supplier note is one of the cheapest project controls available. It does not need to be formal. Something like: “We have received the invoice, it is approved, and it is scheduled for the December payment run. If anything changes, I will let you know by Friday.” That single message reduces the chance of a supplier ringing three people on 30 December.

If a payment is going to slip, say so early. Suppliers can plan around a known January date far more easily than a silent December inbox. It also protects the relationship when the new year starts.

Keep the sheet small enough to use

The temptation is to turn this into a spreadsheet with twelve tabs and a colour key. Resist it. One page, one owner, one review date. The project lead should be able to look at it on 18 December and know exactly which invoices are safe, which are waiting on approval and which have been pushed into January.

That is the whole point. December is not the month for a finance overhaul. It is the month for a short, honest cut-off check that stops small admin gaps becoming January relationship problems. Get the diary right and the payment run mostly takes care of itself.