Education Hub
Foundation RWA and Deal Types

Revenue advances on government contracts: lending against the most reliable payer


Revenue advances on government contracts: lending against the most reliable payer

Companies that sell to government agencies have an odd problem. Their customer is about as likely to pay as any customer in the world. But it pays slowly, on its own schedule, through its own systems. A small contractor that has delivered the work may wait 30, 60, or 90 days for the cash, while payroll and suppliers are due now.

A receivables advance closes that gap. A lender pays the contractor most of the invoice value up front and is repaid when the government pays the invoice.

How it actually works

  1. The contractor performs work under a government contract and submits an invoice.
  2. The invoice is accepted through the government's electronic invoicing and payment systems.
  3. The lender advances a percentage of the invoice, the advance rate, to the contractor.
  4. When the government pays, the payment is routed to an account the lender controls.
  5. The lender takes its advance plus a fee and releases the rest to the contractor.

It's a textbook example of self-liquidating credit. The loan exists because of a specific invoice, and it's repaid by the payment of that invoice.

Where the risk actually sits

The government paying is rarely the risk. The risks are elsewhere.

Invoice validity. Was the work actually performed and accepted? An invoice that's rejected or disputed won't be paid on schedule, or at all.

Payment routing. Government payments go to the bank account registered for the contractor. If that account isn't controlled by the lender, the contractor can receive the cash and not pass it on. In the US, assigning payments on federal contracts is governed by the Assignment of Claims Act, which sets formal steps for redirecting payment to a lender.

Offsets. A government payer can sometimes reduce a payment to recover money the contractor owes it elsewhere, such as unpaid taxes or overpayments on another contract.

Timing. Budget disputes, shutdowns, and processing backlogs can delay payment. A delay doesn't mean a loss, but it extends the advance and ties up capital.

Contractor performance. If the contractor fails to deliver, future invoices won't be accepted, and the relationship ends.

Why it matters

This is a form of credit where the repayment source is unusually strong and the risks are unusually specific. That makes it a good fit for verification. Each invoice can be checked against the payer's own acceptance records. Each payment can be checked against the controlled account. The question "did this invoice exist and was it paid?" has a clear yes or no answer.

It also shows a general lesson. A strong payer doesn't make a loan safe by itself. What makes the loan safe is confirming the invoice is real, making sure the cash reaches the lender, and keeping the exposure short. See The security package for the legal tools that control where the cash goes.