Staffing Agency Invoice Rejected? Log the Reasons, Then Fix the PO Upstream

What the strictest buyer calls a proper invoice

The federal government publishes its rule, which makes it a useful checklist even for firms with no federal work. Under the Prompt Payment rules, 5 CFR 1315.9(b) lists what a proper invoice contains.

• The vendor’s name and the invoice date.
• The government contract number, or other authorization for the goods or services.
• The vendor invoice number, account number or any other identifying number agreed to by contract.
• A description, including for example the contract line or subline number, with price and quantity of the services rendered.
• Shipping and payment terms, unless agreed to sit only in the contract.
• The taxpayer identifying number and banking information, unless agency procedures provide otherwise.
• A contact name, title and telephone number, and any other substantiating documentation or information required by the contract.

Two more lines in 5 CFR 1315.4 matter. When an agency finds an invoice improper, it returns it no later than 7 days after receipt and identifies all defects that prevent payment, with a request for a corrected invoice. If it notifies late, the days allowed for paying the corrected invoice are reduced accordingly. These rules govern federal agencies, and a staffing firm with federal contract work should read them with its contracts and its attorney. A commercial client’s VMS sets its own rules, usually in a supplier guide. The habit worth borrowing is the federal one: every rejection names every defect, in writing, once.

Keep a rejection log by client and program

For one quarter, every rejected or short-paid invoice gets a row. The columns are plain: invoice number, client, program or VMS, amount, date sent, date rejected, the reason in the client’s own words, date the firm noticed, date resubmitted, date accepted, who fixed it and a reason code. The gap between date rejected and date noticed can turn out to be its own problem, because VMS notices land in a shared inbox or in one person’s email.

Start with a short code list and let the quarter add to it.

• PO missing, wrong or expired. The invoice carries no PO, an old PO, or a PO whose end date has passed.
• PO funds exhausted. The PO is valid but the billed amount exceeds what remains on it.
• Hours not approved or not matching. The invoice carries hours the VMS does not show as approved, or a different number.
• Rate mismatch. The bill rate differs from the rate card loaded in the program.
• Overtime not pre-approved or coded wrong. The program requires overtime approval or a separate line, and the invoice did not follow it.
• Cost center or project code missing. The client needs a charge code the assignment record never captured.
• Worker or assignment not active in the program. The worker was never fully onboarded in the VMS, or worked past the assignment end date there.
• Expense not allowed or without backup. A reimbursable expense outside the program’s rules or missing its receipt.
• Duplicate or format. The invoice was already submitted, or the file layout did not match the program’s template.

At the end of the quarter, sort by code and by client, and add one column: days added, from the original send date to the date the corrected invoice was accepted. That column, multiplied by the dollars on each invoice, is the size of the problem.

Three upstream checks that prevent whole categories

Each code points upstream to a moment before the invoice existed. Three checks address the codes that repeat, and all three happen in the assignment record, not in billing.

• Every active assignment carries its PO number and PO end date before the first timesheet is entered, and a report lists every PO ending in the next four weeks.
• PO burn-down. For every PO, the dollars remaining against the hours still to bill before the assignment ends, checked weekly.
• The client’s entry rules recorded per program: overtime approval, cost center or project codes, expense rules and invoice format, in the client file where billing and the recruiter both see them.

The PO burn-down is the staffing version of a change order: work that will happen whether or not the paperwork caught up. Illustrative example: a PO of $60,000 covers a contractor billed at $75 an hour. After 640 hours billed ($48,000), $12,000 remains, which is 160 hours, or four 40-hour weeks. If the assignment is expected to run eight more weeks and nobody asks the client to extend the PO now, the fifth week’s invoice is likely to come back unpaid, and the firm will have paid the contractor for weeks five through eight before the client has a PO to pay against. Asking at week zero of the remaining four is a phone call; asking at week five is a collections problem. The numbers are hypothetical; the arithmetic is the check.

Measure one quarter, then give it an owner

Illustrative example: in one quarter a firm sends 600 invoices across its VMS programs and logs 45 rejections worth $90,000 in total. Twenty were PO-related, twelve were hours not matching the VMS, eight were rate mismatches and five were missing cost centers. The average rejection added 9 days before acceptance, of which 4 were days nobody had noticed the rejection. Ninety thousand dollars waiting an extra nine days is not a write-off, but it is cash the firm had already paid out in wages, and the four unnoticed days are the cheapest to recover. All of these figures are hypothetical; a firm’s own log will give its own.

The owner is one person, by name, who reads every rejection notice the day it arrives and either fixes it or assigns it with a due date. Program notices go to a single billing inbox, not to individual recruiters. The weekly review is short: rejections by code and client, last week against this week, and the PO list for the next four weeks. When the same code repeats at the same client, the fix belongs upstream, in the assignment record, and the recruiter or account manager who owns that client takes it.

Whether a firm may bill hours worked after a PO expired, or how a program’s dispute window interacts with the client agreement, are contract questions for the firm’s attorney. The operational answer stays the same either way: ask for the PO extension before the money runs out.

When not to hire anyone for this

A firm with few VMS programs, a short rejection log and every rejection noticed the same day does not need outside help here. The log above, kept for a quarter, will say so on its own, and the time is better spent on a different hand-off.

It is worth a second look when rejections repeat at the same clients, when the noticed-to-rejected gap is measured in days, or when the problem sits next to others: approved hours not yet invoiced, receivables past terms, programs whose fees and rejections together leave little spread. The page on staffing agency consulting lays out where a staffing firm’s cash waits. The Revenue Review is a read-only engagement that takes two weeks: we read the firm’s own invoice, rejection, PO and payment records, measure the days each program adds, and put a monthly dollar figure on each leak, with a written report and a 90-day plan. We do not contact clients, programs, candidates or contractors, and contract questions stay with the firm’s attorney. A free 20-minute call is enough to tell whether a Review fits.