Government receivables: why they are often ineligible

It sounds backwards. The US government is the strongest credit on earth, and yet its invoices are often the first thing struck from a borrowing base. The problem is not whether the government pays. It is whether the lender can make the government pay them. A receivables lender's whole position rests on being able to redirect collections if the borrower fails, and with government obligors that redirection is legally harder.

For US federal receivables, the Assignment of Claims Act sets out a specific process for assigning payment rights under a federal contract, including notice to the contracting officer and the disbursing office, and it generally limits assignments to financing institutions on contracts above a threshold. This is context, not legal advice, but the practical effect is that a blanket security agreement does not by itself give the lender a perfected, enforceable claim on federal receivables. Many lenders exclude them unless the assignment process has actually been completed contract by contract. State and municipal obligors raise similar questions under a patchwork of state laws, plus slow payment cycles and sovereign immunity concerns.

The test is an obligor classification: tag each customer as federal, state, municipal, or commercial, then apply the facility's treatment for each level. Here is a pool where the agreement excludes federal and state receivables outright and allows municipal balances within a basket of 5 percent of eligible receivables.

The exclusions total $2,490,000. At an 85 percent advance rate that is about $2,116,500 of availability the borrower does not get, on receivables that will almost certainly be paid. That is why government heavy businesses negotiate this rule hard, and why completing the Assignment of Claims process on a few large federal contracts can be worth real money.

You need obligor id, an obligor type classification, open amount, and for federal carve outs, evidence of which contracts have completed assignments. Classification is the weak point. Nothing in a standard ERP customer master says government. The receivable is owed by GSA, or by a prime contractor passing through federal work, or by a public university that may or may not count as a state entity under the agreement's definition. Resellers and primes are a common trap in both directions: selling to a commercial prime on a federal program is usually a commercial receivable, and treating it as government understates availability.

The other breakage is carve out tracking. If the agreement allows federal receivables where the assignment is perfected, someone has to maintain the contract level list of completed assignments and tie invoices to it. That list lives in a legal folder, not the ERP, and certificates quietly drift out of sync with it.

• Obligors are classified by government level once, and the classification is applied deterministically on every certificate rather than re decided by hand each month.
• Treatment is configured per facility: full exclusion, baskets by level, or carve outs for contracts with completed assignments, matching your agreement's language.
• Carve out lists are maintained as facility configuration, so an invoice is only treated as eligible federal paper when its contract is actually on the list.
• Every excluded government receivable traces to the obligor, its classification, and the rule applied, so the deduction is documented rather than folklore.