library · field guide

Hope is not a payment method.

A nursery can grow beautifully and still run out of cash, because the money it is owed sits in other people’s inboxes. Getting paid is a system that starts the moment you raise the invoice and runs until the payment clears.

the shift

Cash is a process, not an event.

The money you are owed doesn’t arrive because you hoped, or because you sent one stern email. It arrives because every step between the sale and the settlement is written down, watched, and chased on a cadence.

the quiet leak

The sale you already made and still haven’t been paid for.

The hardest money to collect is money you have already earned. The plants left the nursery weeks ago, the customer is happy, and somewhere in the gap between "delivered" and "paid" a chunk of your working capital is quietly sitting still. It doesn’t show up as a loss. It shows up as a nursery that is busy, profitable on paper, and always a little short of cash.

Most growers manage this the hard way — a spreadsheet that’s out of date by Tuesday, a shoebox of invoices, a monthly panic where someone digs through the accounts and starts phoning the worst offenders. It works, roughly, but it depends entirely on a person remembering to do it, and it always finds the problem late: when the debt is 90 days old instead of 30, and when the money is hardest to recover.

The alternative is to make the chase a workflow: a handful of steps that run the same way every time, so being paid on time is the default state of the business rather than a monthly scramble.

step one · the request

Nothing gets collected until you ask.

Nothing gets collected until a clear request goes out. An invoice is exactly that, a request for payment raised from an order, and it helps enormously to give it a visible lifecycle: Draft → Sent → Paid, with Partially Paid, Overdue, Refunded or Cancelled along the way.

That status is the backbone of the whole workflow. A large order can be billed across several invoices as work proceeds, invoicing each shipment separately, and billing is worth keeping independent of delivery, so three deliveries and two invoices for the same order is perfectly normal. What matters is that every request has a state you can read at a glance: what has been sent, what has been paid, and what has quietly slipped past its due date.

step two · the money lands

Money lands on the account first.

When a payment arrives, it rarely drops neatly onto one invoice. The cleaner model is to let it land first on the customer’s account, their overall position with you, and then work it downwards: account → order → invoice.

With settlement automated, a payment flows down to the orders that still owe money, and each order down to its own invoices, following an allocation rule you choose: oldest first (the usual choice), newest first, or by hand. Anything a payment doesn’t cover stays on the account as unallocated credit, ready for the next order. Keep settlement scoped to the one customer, so money from one buyer can never pay off another’s debt, and "how much does this customer actually owe" becomes a number the system keeps honest for you.

the discipline

You can’t chase what you can’t see.

A chase list you rebuild by hand every month is a chase list that’s wrong every month. The whole point of a workflow is that the system already knows who owes what, and how late they are, before you go looking.

The difference between a nursery that gets paid and one that’s always waiting is rarely effort — it’s visibility. When the overdue list lives in one person’s head or a stale spreadsheet, the chase is reactive: you notice a problem when the customer goes quiet, or when the bank balance gets uncomfortable.

A workflow flips that. The unpaid invoices, the days each one is overdue, the customers who are drifting from slow to risky — these are facts the system already holds, updated live as payments land. Chasing stops being an investigation and becomes a routine: open the list, work the top of it, done. The energy goes into the conversation with the customer rather than into assembling the list.

step three · the chase list

The aging report writes your chase list.

An invoice aging report is the workflow made visible: every invoice still owing, its days overdue, and its aging band as of any date you pick — Current (0–30), 31–60, 61–90, 91–120, and over 120 days. Roll it up by customer to see who owes the most, or by payment terms to separate your 30-day accounts from your 60-day ones, and export the lot for the accountant.

Each customer’s payment terms should shape the report honestly: longer terms push an invoice’s due date out, so it only starts aging when it is genuinely late rather than the day after you sent it. A good report tells you who to ring today, and hands you the oldest, most fragile debts first.

step four · the early warning

The number that warns you before the write-off.

Bad debt is almost never a surprise in hindsight. The customer was slowing down for months, a few days later each time, a part-payment here, a promise there, and nobody joined the dots until the invoice was 120 days old.

The antidote is a single running score for each customer’s payment behaviour, covering whether they pay on time and how much credit risk they carry, kept as a history rather than a snapshot. Watch it and you can see a relationship slip before it breaks: a score drifting down from strong to merely adequate is the signal to tighten terms, ask for payment up front, or simply have the conversation now — while the debt is still small and the customer still remembers the order.

atlas core

How Atlas Core runs credit control as a workflow

Atlas Core turns the habits above into a working system:

Invoices with a real lifecycle: Draft → Sent → Paid, with Partially Paid, Overdue and Cancelled states, raised from orders, billed per shipment where you need it, and kept independent of deliveries.
Three-tier settlement — payments land on the Customer Account and flow down through orders to invoices on an allocation strategy you set (oldest first, newest first or manual), with leftover money held as unallocated credit.
The Invoice Aging Report — every outstanding invoice, its days overdue and aging bucket as of any date, grouped by customer, payment terms or bucket, with an Excel export and terms-aware due dates so nothing ages before it’s truly late.
The Customer Rating — a 0–100 health score tracked over time, with on-time payment and credit risk among its ingredients, so a slipping account warns you before it becomes a bad debt.

Read further

Field guide · 2026

Which shop does the website ship from?

Most webshops rest on a comfortable fiction: that one warehouse behind the checkout holds everything. A nursery group has tunnels, a yard and three shop floors in different towns - and the plant just sold is standing in exactly one of them.

8 min read · Jul 2026 Read →

Field guide · 2026

Your plants are stuck at the border

A lorry in an inspection bay is rarely held because of the plants. It's held because a commodity code was wrong, a weight didn't tie back, or the certificate and the invoice disagree - and with living goods, a two-day hold is damage with a delayed invoice.

8 min read · Jul 2026 Read →

Field guide · 2026

Every bench is money

An empty bench earns nothing yet costs the same to heat, light and rent as a full one; a bench crammed past its limit grows weaker plants and more loss. The margin lives in the space between those two failures - and you can only manage it if you can see it.

7 min read · Jul 2026 Read →

See how Atlas Core gets you paid on time.

Invoicing, settlement, the aging report and a customer rating that warns you early — see how it fits your nursery.

Talk to us