The short answer
Public sector clients have a reputation for paying slowly, and it is mostly wrong. The delay is in getting onto their system, not in getting paid once you are on it. In several places they are held to shorter statutory deadlines than private companies.
Budget weeks for registration, supplier setup and a purchase order before anything can be invoiced.
Get the invoice format exactly right, because it is checked mechanically.
Expect the terms to be fixed, and stop trying to negotiate them.
Invoice the day a stage completes, since the clock usually runs from receipt.
Keep the exposure small until the first invoice has been paid once.
Treated as a cash flow problem at the start rather than a collection problem at the end, public work is among the more predictable revenue a small agency can hold.
The part that surprises people
Across the markets most agencies work in, public bodies are subject to payment rules that do not apply to ordinary companies.
Market | Public sector standard | Private sector |
|---|---|---|
US federal | Payment due on the 30th day after a proper invoice | No general statutory limit |
EU | 30 days, or 60 in exceptional cases | 60 days unless expressly agreed |
UK | 30 days implied into public contracts | Contract, plus reporting duties |
In the US, the Federal Acquisition Regulation sets the due date as the 30th day after the designated billing office receives a proper invoice, or after acceptance of the work, whichever is later. In the EU, the European Commission's guidance on the Late Payment Directive is that public authorities have to pay within 30 days, or 60 in exceptional circumstances, against 60 days for businesses. In the UK, the Procurement Act implies a 30-day term into public contracts, running from receipt rather than approval.
So a government client is frequently obliged to pay you faster than a corporate one, and has an auditable process for doing it. The reputation for slowness comes from the other end of the engagement.
Where the time actually goes
4 stages sit between winning the work and being able to invoice, and all of them happen before you do anything billable:
Supplier registration. Tax forms, bank verification, insurance certificates, sometimes a code of conduct. Weeks rather than days, as in the cross-border setup.
A framework or contract vehicle. Some bodies can only buy through an existing arrangement, which you may need to join before they can contract with you at all.
The purchase order. Non-negotiable in practice. No purchase order, no payment, for the reasons in the PO piece.
A portal. Often the only accepted route for invoices, with email submissions simply ignored.
Start all 4 the day the work is agreed rather than when the first invoice is due. An agency that leaves registration until it has something to bill will wait 6 weeks for a payment that was legally due in 30 days, and will blame the client for it.
Get the invoice format exactly right
Public buyers check invoices against a defined standard, which is published, and a defective invoice is returned rather than queried informally.
The federal definition is a useful model even outside the US. A proper invoice must carry the contractor's name and address, the invoice date and number, the contract number including order and line item numbers, a description with quantity, unit of measure, unit price and extended price, the payee's name and address, and a contact for questions.
The same rule contains something genuinely in your favour. Where an invoice is not proper, the billing office has to return it, with reasons, within 7 days, and where that notice is not given the due date is adjusted. Private clients are under no such obligation and can hold a defective invoice indefinitely without telling you, which is why silence from a corporate client usually means a formatting problem and silence from a public one usually does not.
What is different, operationally
The terms are the terms. There is no useful version of asking for shorter terms here, so spend the effort on invoicing promptly instead.
Your contact cannot help with payment. The person you work with and the people who pay you are in different functions with no overlap. Find the finance contact at the start.
Nothing is informal. A verbal approval to do extra work is worth nothing against a purchase order, which makes pricing extra work in advance more important rather than less.
Records are expected. Keep timesheets, delivery notes and acceptance confirmations as a matter of routine, because they may be asked for long after the project ends.
Changes take a cycle. Amending a purchase order is a process with its own timetable, so ask early when a budget looks like it will be exceeded.
Plan the cash, not the collection
Because the risk sits at the start, the planning does too. Assume a long gap between starting work and receiving the first payment, and size the engagement so that gap is survivable.
Put the registration period into your forecast as a block with no inflow, which is exactly the kind of trough a 13-week forecast exists to show. Where the body allows staged payments, use them. Where it allows an advance, which some do for small suppliers, ask.
Then watch the first invoice closely. Once 1 invoice has travelled the whole route and been paid, the remaining ones usually follow the same path at the same speed, and the account becomes genuinely low maintenance.
When something does stall
The causes are narrower than in the private sector, which makes diagnosis faster. In rough order of likelihood: the invoice never reached the portal, the purchase order has no remaining value, the goods receipt or acceptance was never entered, or a required field is wrong.
Ask the finance team to confirm which of those it is, naming them, rather than asking when payment is expected. A specific question gets a specific answer, and the same approach works in any organisation large enough to have a payment run.
Where an invoice has genuinely passed the statutory period and the work is accepted, say so plainly and in writing. Public bodies are measured on payment performance and a factual, dated note usually moves things without any escalation at all.
Is it worth it for a small agency
It depends almost entirely on the size and length of the engagement. The setup cost is close to fixed, so a single short project rarely justifies it, while a framework place or a multi-year contract amortises it comfortably.
The honest summary: slow to start, awkward to join, and then unusually reliable. For an agency whose other clients pay unpredictably, a public body paying on a fixed cycle is worth a great deal, and it is the kind of client whose behaviour shows up well in the weekly numbers.
FAQ
Do public sector clients pay slowly?
Usually not, once you are set up. US federal payment is due on the 30th day after a proper invoice, EU public authorities have 30 days, and UK public contracts carry an implied 30-day term. The delay is in registration, framework access and purchase orders at the start.
How long does it take to get set up as a public supplier?
Weeks rather than days. Expect tax forms, bank verification, insurance evidence and portal registration, and start all of it the day the work is agreed rather than when you want to invoice.
Can I negotiate payment terms with a public body?
Rarely. Terms are usually set by statute or policy and your contact has no authority to vary them. Put the effort into invoicing on the day a stage completes instead, since the clock typically runs from receipt.
What makes a public sector invoice get rejected?
A missing purchase order number, a contract or line item reference that does not match, submission by email where a portal is required, or an amount exceeding the remaining purchase order value. The required elements are usually published.
What happens if a public body pays late?
Statutory interest usually applies automatically, and these bodies are measured on payment performance. A factual, dated note that the invoice is accepted and past the statutory period generally resolves it without escalation.
Is public sector work worth it for a small agency?
For a one-off small project, often not, because the setup cost is close to fixed. For a framework place or a longer contract it usually is, and the predictability is valuable alongside less reliable private clients.
Not legal advice. Public procurement rules, payment deadlines and interest entitlements differ by country, by level of government and by contract, and the provisions mentioned here have their own scope. Check the terms you have actually signed.