When the work is finished but the invoice still cannot go out
A common cash flow problem has nothing to do with whether the work was done properly.
The job is complete. The customer is happy. The team expects the invoice to go out. Then accounts discovers a problem: the customer requires a purchase order number, specific line references, supporting documents, or a particular approval trail before they will accept the invoice.
At that point, invoicing stalls.
Sometimes the invoice is rejected outright. Sometimes it sits in draft while someone tries to work backwards through emails, job notes and spreadsheets to find the right information. In other cases, the invoice goes out with incomplete references and payment is delayed because the customer’s accounts payable team cannot match it to their internal procurement records.
This is often treated as an accounts issue, but it usually starts much earlier in the workflow.
If the business only discovers billing conditions at the point of invoicing, the process is already too late.
Why customer PO matching causes delays
The visible issue is simple: the invoice is missing something the customer needs.
The underlying issue is that the business has not designed a process to capture and carry billing conditions from the start of the job through to the end.
That can show up in several ways:
- the quote is accepted, but nobody records whether a customer PO is required before invoicing
- the job is created without the correct PO number or billing contact
- the customer issues a PO with multiple lines, but the work delivered is not linked to the correct line items
- technicians complete work, but the delivery evidence is stored separately from the billing reference
- variations or extras are done, but no one checks whether they need separate PO coverage
- accounts only finds out about customer invoicing rules once the invoice is being prepared
None of those are really invoicing problems in isolation. They are handover and data-flow problems.
The business completed the operational work, but it did not preserve the information needed to convert that work into a payable invoice.
The real problem is usually broken information flow
In many businesses, the customer purchase order is treated as an administrative detail rather than part of job execution.
That sounds minor, but it creates a gap between what operations delivers and what finance is allowed to bill.
For example:
- sales knows the customer always needs a PO, but that information stays in email
- the project or service team starts the work without seeing the billing conditions
- field staff complete the job and upload photos, but nothing ties those records back to the PO or PO line
- accounts receives a “job complete” signal, but not an “invoice-ready under customer rules” signal
The result is predictable. Work moves through the business, but invoice readiness does not move with it.
That is why businesses can be operationally finished but commercially stuck.
Capturing billing conditions early matters more than chasing them later
If a customer has billing requirements, they should be captured at quote stage or job setup, not at the end.
That does not mean every quote needs a complex procurement workflow. It means the business should know, before work progresses too far, whether invoicing depends on conditions such as:
- a customer PO number
- a specific PO line reference
- a site code or cost centre
- a named billing contact
- proof of delivery or completion documents
- signed timesheets
- approval from a customer-side manager
- separate billing rules for variations or additional works
These are not just finance fields. They affect whether completed work can actually turn into cash.
If the information is optional in the system, inconsistently recorded, or hidden in free-text notes, the team will end up reconstructing it later under pressure.
That usually means rework, delays and increased risk of billing errors.
Where this commonly breaks down
There are a few predictable failure points in the workflow.
Sales-to-operations handover
A quote may be won and converted into a job, but the billing conditions do not transfer cleanly.
The estimator or account manager might know the customer requires invoice references in a specific format, but the operations team only receives the scope and dates. By the time the work is complete, nobody is sure which PO applies, whether the PO covers all stages, or whether the customer needed separate references for different locations.
Job creation without mandatory billing fields
Some businesses create jobs quickly to keep work moving, but they do not require key billing information at setup.
That often leads to blank PO fields, unclear site references, or loose text like “PO to come”. Once the job is underway, people assume it will be sorted out later.
Later is usually when invoicing gets delayed.
Delivery evidence separated from billing references
The technician may finish the work and upload photos, service reports or signed dockets. But if those records sit in a different system or are not linked to the right job and PO context, accounts still cannot invoice confidently.
The evidence exists, but not in a usable billing workflow.
Variations and extras
This is a common problem in field service, projects and installation work.
The original PO might cover the initial scope only. Then additional labour, parts or call-outs are provided, but no one confirms whether the customer requires an updated PO or separate approval before those items can be billed.
When the invoice is raised, the commercial reality and the customer’s procurement rules no longer match.
Why larger customers often need line-level matching
For some customers, having a PO number alone is not enough.
They may require the invoice to match:
- a specific PO line
- a service period
- a site or branch
- a cost code
- a staged delivery milestone
- quantities approved under the PO
This matters particularly when a single customer PO covers multiple sites, multiple jobs, or multiple service lines.
If your internal job records do not preserve that level of detail, the invoice may be technically correct from your point of view but still unpayable from theirs.
That is where businesses often get caught out. They assume “we have the PO number” means billing is covered. In practice, the customer may be matching far more than that.
The more structured the customer’s procurement process, the less tolerance there is for vague invoice references.
What a better process looks like
The fix is not to ask accounts to chase harder at month end.
A better process starts by treating customer billing conditions as part of the operational workflow.
At a minimum, the business should define:
- what billing conditions need to be known before work starts
- where those conditions are captured
- which fields are mandatory
- which system holds the source of truth
- how those fields carry through to job execution
- what evidence must be collected before the job is invoice-ready
- what exceptions require human review
In practice, that often means a cleaner chain from quote to job setup to delivery to invoice generation.
For example:
- quote or order stage captures whether customer PO matching is required
- job setup records PO number, PO line, site code, billing contact and any approval rules
- field or delivery teams complete work against the correct job reference
- supporting documents are stored against that same job
- invoice readiness checks confirm all required billing fields and evidence are present
- only then does the invoice move to billing
That is a systems design decision, not just an accounts procedure.
Invoice readiness should include billing-condition checks
Many businesses treat a job as ready to invoice when the work status changes to complete.
That is often too simplistic.
Completion of work and readiness to bill are related, but they are not always the same thing.
A better invoice-readiness check might include questions such as:
- Is the correct customer PO recorded?
- If required, is the correct PO line or cost code recorded?
- Does the delivered work match what the PO approves?
- Are completion documents attached?
- Are variations covered by approval or updated PO information?
- Is the billing contact known?
- Are there any customer-specific invoice formatting rules?
If those checks are not built into the workflow, someone in accounts ends up doing manual detective work every time.
That does not scale well, and it introduces avoidable delays into cash collection.
Keep the PO reference linked to the work, not just the customer
One of the biggest mistakes is storing the customer PO only at an account level.
That may be enough for very simple billing, but it breaks down quickly when the same customer has:
- multiple sites
- repeat jobs
- staged works
- overlapping purchase orders
- multiple approvers
- separate departments or cost centres
The billing reference needs to stay connected to the specific work delivered.
That might mean linking PO details to:
- the quote or accepted order
- the project stage
- the service job
- the variation
- the invoice line
The right design depends on the business model, but the principle is the same: keep the billing condition attached to the operational record that generates the invoice.
If that link is missing, people will fill the gap manually. That usually means mistakes.
Don’t automate a messy billing workflow too early
Automation can help, but only after the process is clear.
If the business has not decided:
- when PO information must be captured
- which fields are mandatory
- who owns missing information
- how variations are handled
- what counts as invoice-ready
then automation will just move incomplete data faster.
A useful workflow might automatically prevent a job from progressing to invoice-ready status if required billing fields are missing. It might also carry PO references from accepted quote to job record to invoice draft, reducing rekeying.
But those automations only work when the underlying rules are explicit.
Without that, the team still ends up bypassing the process or correcting it manually later.
Exceptions still need human judgement
Not every situation should be forced into rigid automation.
There are legitimate exceptions, such as:
- the customer issues a revised PO after work has started
- one job needs to be split across multiple PO lines
- urgent work is performed before procurement paperwork is finalised
- part of the work is billable now and part later
- a variation is commercially agreed but awaiting formal PO update
These cases need clear ownership.
The system should make the exception visible rather than pretending it does not exist. For example, the job might be flagged as complete but “billing hold - PO clarification required”, with a named owner and next action.
That is far better than allowing the work to disappear into an unstructured queue where accounts has to guess what is wrong.
What good looks like operationally
A well-designed process is usually less dramatic than people expect.
Good looks like this:
- customer billing conditions are captured early
- mandatory billing fields are not left to memory
- operations can see the invoicing requirements, not just accounts
- delivery evidence stays linked to the correct job and billing reference
- variations are checked against customer approval rules before billing
- invoice-ready status means commercially ready to invoice, not just physically complete
- accounts is reviewing prepared information, not reconstructing it
That does not require a huge transformation project.
Often the biggest gains come from tightening a few key handovers and making sure the correct billing information survives the whole workflow.
The cash flow benefit is really a process benefit
Cleaner PO matching improves cash flow because invoices go out earlier, get rejected less often, and require less rework.
But the real improvement is operational.
The business stops relying on scattered emails, staff memory and month-end chasing to bridge a design flaw in the workflow.
Instead, it creates a more reliable path from sold work to completed work to billable work.
That matters most in businesses where jobs move across multiple teams or systems. If quoting, job delivery and invoicing all sit in different places, small gaps in billing information become expensive delays very quickly.
If customer PO compliance keeps slowing invoicing down, it is usually worth mapping the workflow end to end and deciding where billing conditions should be captured, stored and checked. That kind of process and systems design work is exactly where 5M Consulting can help.