Summary

  • Trove is credit control software for growing UK finance teams. Its sending schedule sets the days of the week and working hours reminders and statements go out, so chasers land on days your customers’ finance teams are working.
  • Three dates decide whether you’re paid before the winter holidays: each key customer’s last payment run of the year, your last chase date before that run, and the day your own office closes.
  • An invoice that’s been sent isn’t an invoice that will be paid. It has to be matched, approved and free of holds in the customer’s system before their last run’s cut-off, or it waits until January.
  • Start six weeks before the break. Clear queries, deductions and missing POs first, send statements and pre-due reminders four weeks out, and use the last fortnight for calls on key accounts.
  • Over the break, pause chasers and keep the safe things running. Thank-you emails, promised payment dates and your out-of-office can carry on. Reminders to customers whose finance team is closed shouldn’t.
  • Trove has no date-range pause for the holidays. To stop chasers over the break, switch your workflows to manual, so Trove drafts reminders but sends nothing until you approve it from the Outbox.

Why December payments slip for suppliers to big customers

December payments slip because big customers pay in scheduled runs, and the last run of the year comes early. A supermarket or wholesaler doesn’t pay invoices the day they fall due. It pays the ones that are matched, approved and released in time for a payment run, and anything that misses the last December run waits for the first run in January.

Four things make December worse than any other month:

  • Earlier cut-offs. The customer’s accounts payable team brings its last run forward to clear the books before it closes, so the cut-off for approvals comes earlier too.
  • Approval queues. An invoice can sit waiting for a buyer or a depot to approve it. In December the approver is often busy with the peak or already on leave.
  • Holds you don’t know about. A missing PO, a price mismatch or a quantity query puts an invoice on hold. Nobody tells you until you ask, and by then the run has gone.
  • Short staffing on both sides. Your own credit controller wants time off too, and your customer’s AP team runs on a skeleton crew over the winter holidays.

For a food and drink supplier, this lands at the worst time. Q4 is your busiest quarter, so the December invoices are the biggest of the year, and agreed terms with big retailers already run long. Here’s how long UK supermarkets take to pay on average, from their own payment practices reports.

Find each key customer’s last payment run

Ask each key customer now for the date of their last payment run in December and the cut-off for invoices to be approved in time. Don’t guess from last year, and don’t rely on a date someone mentioned on a call.

  1. Email the accounts payable contact for each key account with two questions: what’s the date of your last payment run before the winter holidays, and by when does an invoice need to be approved to be in it?
  2. Record the answers against each account, with the date you asked and who replied.
  3. Work back from the cut-off. Your last chase date for that customer is a few working days before their approval cut-off, so there’s time to fix anything they tell you is on hold.
  4. Note when they reopen. The first January run tells you when to expect anything that misses December.

If a customer invoices through a group head office but approves at site level, ask both. Here’s how to chase a customer group with many sites, and Trove’s parents and sub-customers let you chase the head office about the whole group or each site about its own invoices.

Worked example: Example Foods Ltd’s December plan

Example Foods Ltd supplies chilled desserts to three retailers and a wholesaler. Priya runs credit control, Tom and Sam are the account managers, and Helen is the finance manager. Example Foods closes at noon on Thursday 24 December and reopens on Monday 4 January.

In the week of 16 November, Priya emailed each customer’s accounts payable team. These are the dates they gave her.

Customer Account manager Approval cut-off Last December payment run Priya's last chase date First January run
Example Grocers plc (retailer) Tom Fri 11 Dec Thu 17 Dec Tue 8 Dec Thu 7 Jan
Example Supermarkets Ltd (retailer) Tom Tue 15 Dec Tue 22 Dec Thu 10 Dec Tue 12 Jan
Example Market Stores plc (retailer) Sam Mon 14 Dec Fri 18 Dec Wed 9 Dec Fri 8 Jan
Example Wholesale Ltd (wholesaler) Sam Fri 18 Dec Wed 23 Dec Tue 15 Dec Wed 6 Jan

From those dates, Helen signed off this plan. Every step has one owner.

Week Weeks before the break Task Owner
w/c 16 Nov 6 Ask each customer for its last payment run and approval cut-off. Record them per account Priya
w/c 16 Nov 6 List every open query, deduction, missing PO and on-hold invoice for the four accounts Priya
w/c 23 Nov 5 Resolve the commercial queries with each buyer: promotions, pricing, missing POs Tom (Grocers, Supermarkets), Sam (Market Stores, Wholesale)
w/c 23 Nov 5 Dispute shortages and unexplained deductions with accounts payable, evidence attached Priya
w/c 30 Nov 4 Send statements to all four accounts, and pre-due reminders for invoices falling due between 24 Dec and 8 Jan Priya
w/c 7 Dec 3 Chase every invoice due in each customer's last run, up to Priya's last chase date for that account Priya
w/c 7 Dec 3 Confirm with each retailer's buyer that the invoices in the last run are approved and nothing is on hold Tom, Sam
w/c 14 Dec 2 Phone accounts payable at each customer before its run, key accounts first, to confirm what's being paid Priya
w/c 14 Dec 2 Match each December remittance to invoices the day it arrives, and log anything paid short Priya
w/c 21 Dec 1 Switch Trove workflows to manual, set the out-of-office, and write the January restart list Priya, signed off by Helen
w/c 4 Jan After Work through the restart list, then switch workflows back to automatic Priya

The plan works because each customer’s chasing ends on its own date, not one date for everyone. Example Grocers’ last chase falls a week before Example Wholesale’s, because its approval cut-off comes a week earlier.

Six weeks out: clear queries, disputes and deductions

Six weeks before the break, find everything that could stop an invoice being paid and start clearing it. An invoice with an open query won’t be approved in time, however many reminders you send.

Put every open item where the whole team can see it. On Trove’s Kanban board, you can add columns such as “On hold” and “Confirmed for last run”, give each account an owner and keep notes with the account, so nobody chases a customer who’s waiting on you for a credit note.

Four weeks out: statements and pre-due reminders

Four weeks before the break, send a statement to every key account and a pre-due reminder for any invoice falling due over the break. Both give the customer’s AP team time to spot a missing invoice while there’s still time to approve it.

A statement shows the customer every open invoice in one place. If something on it isn’t in their system, you’ll hear now rather than in January. Here’s how to automate statement sending.

A pre-due reminder goes before the due date. For an invoice due on 30 December, a reminder in early December says, “This falls due while we’re both closed. Can you check it’s approved for your last run?” Here’s how to send a reminder before the due date.

Don’t add extra reminders to make up for the break. One clear pre-due reminder and one follow-up before the last chase date do more than four reminders in a fortnight. Here’s how many invoice reminders to send.

The last fortnight: who calls which customer

In the last fortnight, the credit controller and the account managers split the calls, key accounts first. Priya phones accounts payable before each customer’s run to confirm which invoices are being paid. The account managers deal with the buyers.

Before each retailer’s last December run, the account manager confirms with the buyer that every invoice due in that run is approved and nothing is on hold. Priya sends Tom and Sam the list of invoices for each run. They know the buyers, and she knows what’s owed. That way Priya isn’t finding a blocked invoice on 4 January.

Order the calls by the run date, not by balance. Example Grocers’ run on 17 December comes before the wholesaler’s on 23 December, so Example Grocers gets the first call even if the wholesaler owes more.

When a customer pays or replies, the right person needs to hear the same day. Trove’s Slack and Teams alerts can go to a shared finance channel or as a direct message to the person who owns the customer, so Tom hears when Example Grocers replies without checking the shared inbox.

Over the break: what to pause and what to keep running

Over the break, pause the chasers and keep the things that can’t go wrong. A reminder landing on 29 December in an AP inbox nobody’s reading does nothing, and it can be the email that gets buried when they come back.

Over the break Pause or keep running Why
Overdue reminders and statements Pause The customer's AP team is closed or short-staffed, and nobody at your end can answer the replies
Thank-you emails for payments Keep running They only go when a payment is reconciled, so they can't reach the wrong customer
Promised payment dates Keep running Chasing stays paused until the date, and a follow-up is ready if the money doesn't arrive
Your out-of-office Keep running It tells customers when you're back and who to contact if a payment is urgent
Escalations and final notices Pause Don't send a final notice nobody can follow up on

How to pause chasing over the break in Trove

Trove’s sending schedule sets which days of the week and which hours reminders and statements go out. It doesn’t pause a date range, such as 24 December to 4 January. To stop chasers for the break:

  1. Switch each workflow to manual before you close. Trove keeps drafting reminders but sends nothing until you approve it, and tells you the day before emails are due. Here’s how workflows work.
  2. Leave thank-you emails alone. They don’t follow sending days. Trove sends them an hour after a payment is reconciled, and holds them until working hours if that falls outside them.
  3. Exclude any single customer you want to leave alone for longer, by opening them from Customers and switching “Enrolled in” to Excluded. Write them on the restart list, because they stay excluded until someone includes them again.
  4. Log promised dates before you go. When a customer says they’ll pay on 7 January, Trove’s AI Reply Agent picks the date out of the reply and suggests logging it. Once the date is logged, Trove pauses chasing on that invoice and schedules a follow-up in case the payment doesn’t arrive.

You can also use the sending schedule to chase only on the days your customers’ AP teams are most likely to be in, such as Tuesday to Thursday, through December. Trove gives you a heads-up a set number of hours before anything sends, so you see what’s going out before it reaches a customer.

The first week of January: the restart list

In the first week back, work through the restart list before you switch workflows back to automatic. Anything that missed December needs a date, not just another reminder.

  1. Reconcile what came in over the break, so nobody is chased for an invoice that’s already been paid.
  2. Check the Outbox. Review the reminders Trove drafted while workflows were manual, against what’s been paid and promised, before you send any of them.
  3. Check each key account against its last run. Which invoices were meant to be paid in December and weren’t? Ask accounts payable which January run they’re now in. Here’s what to do when a customer doesn’t pay when they said they would.
  4. Re-include any excluded customers, and switch workflows back to automatic.
  5. Match the December remittances that arrived over the break, and log any deductions while the evidence is fresh.

For the wider picture on remittances, many-site groups and deductions, see credit control for food and drink suppliers.

FAQs about credit control over the winter holidays

Should I send payment reminders over the winter holidays?

Not to customers whose finance team is closed. Send your last reminders before each customer’s approval cut-off, pause chasers over the break, and restart in the first week of January with a check of what was paid.

When do supermarkets do their last payment run before the winter holidays?

Each retailer sets its own dates, and they can change year to year, so ask each one’s accounts payable team in November. Ask for two dates: the last payment run, and the cut-off for invoices to be approved in time for it.

Is it rude to chase invoices in December?

No. Most customers would rather hear in early December that an invoice is stuck than find out in January. Keep it specific: name the invoice, the customer’s last run and what needs approving. Holding back is what costs you, because an invoice that misses the last run waits weeks.

Should we pause automated reminders over the winter holidays?

Yes, for the days your customers are closed. In Trove, switch workflows to manual so reminders wait for your approval in the Outbox, and leave thank-you emails and promised payment dates running. Read more about how Trove’s AI Reply Agent logs promised payment dates.

What should I do with invoices falling due over the break?

Send a pre-due reminder in early December asking the customer to approve them for their last run. If that isn’t possible, ask which January run they’ll be in and log that date against the invoice.

Trove runs a free 30-day trial, so there’s time to set up your sending schedule and workflows before the December runs. You can start a free trial here or book a demo if you’d like to see it first.