A remittance that does not add up
The trust's payment arrives, and it is short. Somewhere in their accounts payable system, a handful of your invoice lines have been rejected: two because the booking reference was missing, one because the hours did not match the ward's record, one because the cost centre was for the wrong ward. You find out from the remittance, or from an email weeks later, or from a portal you check occasionally.
Each rejected line means a credit note, a corrected invoice, and a wait for the next payment run. Meanwhile, the nurses were paid weeks ago.
Some rejections never arrive as a clear message at all. A line simply goes unpaid, and it is only when someone reconciles the aged debt at month end that the gap appears, by which time the booking details are hard to reconstruct.
Why invoices bounce
Trusts process large volumes of agency invoices and use strict matching. Anything that does not match their booking record, PO and approved hours is rejected automatically or sent back. Each trust has its own rules, and they change.
- Booking references from the trust's system are not carried from booking to invoice.
- PO numbers and cost centres change, and your records hold the old ones.
- Hours on the invoice come from your timesheet, which differs from the ward's record.
- Rates do not match the framework or trust schedule for that shift.
- Invoices are grouped differently from how the trust wants them, such as by week, ward or booking.
What rejections cost
Cash flow is the obvious cost. Agencies pay nurses weekly and are paid by trusts much later, so every rejection stretches the gap. Credit notes and reissues take admin time. Unresolved lines age into write-offs. And a trust that sees repeated errors may start treating your invoices with extra suspicion.
| Rejection reason | Where it starts | Check we build |
|---|---|---|
| Missing booking reference | Not captured at booking | Required at booking, carried to invoice |
| Wrong PO or cost centre | Stale client data | Current PO and cost centre checked per line |
| Hours mismatch | Timesheet not approved on the ward | Only approved timesheets invoiced |
| Rate mismatch | Rate worked out by hand | Rate from the booking's rate tables |
| Wrong grouping | One template for all clients | Grouping and format per trust |
How we build invoicing that passes first time
- Each trust's invoicing rules are recorded: required references, PO and cost centre rules, grouping, format and submission route.
- Booking references from the trust are captured when the shift is booked and carried through to the invoice line.
- Only timesheets approved by an authorised signatory reach invoicing, with the approval attached.
- Each line is checked against the trust's rules before the invoice is created. Lines that fail wait in an exceptions list with the reason.
- Invoices are created in your accounting system, such as Xero or Sage, or the trust's required format, and submitted by the route the trust uses.
- Remittances are read and matched to invoice lines, and any short payment is linked to its rejection reason.
- A rejection report by trust and reason shows where errors start, so the upstream step can be fixed.
After the fix
Most invoices pass first time because problems are caught before sending. The exceptions list is short and specific. Short payments are matched to reasons automatically instead of being discovered in a remittance. And the rejection report shows where the errors start, often at booking, so you fix the cause rather than the symptom.
Your credit control conversations change as well. Instead of a trust and your finance team each holding different lists of what is outstanding, you can show every open line with its booking reference, approved timesheet and rate, which tends to close queries on the first reply.
Is this happening to you?
- Trust remittances regularly include rejected lines.
- Booking references are added to invoices after the fact.
- Credit notes and reissues are a weekly job.
- Invoices are built the same way for every trust.
- You cannot say which rejection reasons are most common.