How to Invoice a Government Agency: Getting Paid on Federal Contracts

Federal agencies do not pay invoices. They pay proper invoices. That distinction — a legal one rooted in FAR Subpart 32.9 — matters because a single missing data element does not result in a partial payment or a follow-up request from your contracting officer. It results in your invoice being rejected outright and returned to you, and your 30-day payment clock starting over from zero.

For a small business operating on thin margins or managing subcontractor payrolls, that delay is not a paperwork inconvenience — it is a cash-flow problem. The government spent $753 billion on contracts in FY2024 according to USASpending.gov. That money flows out through invoicing systems that have specific requirements most new contractors discover the hard way.

The good news: the system is learnable. There are two primary invoicing platforms — one for civilian agencies, one for DoD — and each has a defined process. Master them once and billing becomes a routine, not a headache.

One more thing worth knowing upfront: the government is legally required to pay you interest if it is late. The Prompt Payment Act is not optional guidance — it is statute. If your invoice is proper and the agency misses the deadline, interest accrues automatically at the Treasury rate. You do not even have to ask for it. The law is on your side. But you have to submit a compliant invoice first.

The federal government runs two separate electronic invoicing ecosystems. Which one you use depends entirely on who you are contracting with.

Your contract will specify which system to use. Look for the invoicing clause — FAR 52.232-25 will be present on civilian contracts and often references IPP. DoD contracts will include DFARS 252.232-7003 and 252.232-7006, which require WAWF. If you hold contracts with both civilian agencies and DoD, you will use both systems. They are not interchangeable.

One important nuance on IPP: some civilian agencies have agency-specific invoicing requirements layered on top of IPP. The EPA, for example, includes clause 1552.232-70 in its contracts, which adds additional required fields. Always read your contract's invoicing section — do not assume standard FAR language covers everything.

FAR 52.232-25 defines exactly what makes an invoice “proper.” Miss one element and the billing office must return the invoice within 7 days — with a written explanation of what is missing. Your payment clock restarts when you resubmit. These 10 elements are required on every invoice for federal contracts:

Your contract may require additional information beyond these 10 elements — evidence of delivery, acceptance documentation, certified cost breakdowns for cost-type contracts, or agency-specific forms. The contract's invoicing clause is the definitive list. Read it before your first billing cycle.

If you are on a GSA Schedule contract, your invoicing requirements are similar but task orders under the schedule will each have their own specific delivery instructions. Treat each task order as its own mini-contract for invoicing purposes.

The Prompt Payment Act (31 U.S.C. Chapter 39) requires federal agencies to pay contractors within specific deadlines. When they miss those deadlines, they owe you interest — automatically, without you asking for it. This is not a complaint process. It is a statutory right.

The interest clock starts the day after the payment was due. The rate is tied to the Treasury's Prompt Payment rate, which is reset every six months. For contracts where payment was late in 2026:

On a $50,000 invoice that runs 20 days late at the 4.75% rate, the government owes you roughly $130 in interest. That may not sound like much — but if you have multiple contracts and payments are routinely slow, this adds up. More importantly, the existence of the penalty mechanism incentivizes agencies to pay on time. Knowing the rule exists changes how you follow up on late payments.

There is one important catch: the 30-day clock does not start until the agency receives a proper invoice. An invoice returned for missing elements restarts the clock on the day you resubmit a corrected version. This is the real cost of invoice deficiencies — not rejection itself, but the weeks of delay that compound from it.

The Invoice Processing Platform (IPP) at ipp.gov is the Treasury's centralized invoicing hub for most civilian federal agencies. Registration is free and one-time. Once you are set up, billing through IPP is faster than paper by a significant margin.

IPP's helpdesk is reachable at IPPCustomerSupport@fiscal.treasury.gov or (866) 973-3131. If you are having registration issues or cannot locate your PO in the system, they can typically resolve it within one business day. Do not let an IPP access problem delay your billing — call the helpdesk immediately.

Important exception: a contracting officer can authorize invoicing outside of IPP if electronic submission would be “unduly burdensome.” This is rare, and you must get written confirmation from the contracting officer. Without that written authorization, paper invoices submitted to civilian agencies will be returned.

Wide Area Workflow (WAWF) is the Department of Defense's procure-to-pay platform. It is accessed through PIEE (Procurement Integrated Enterprise Environment) at piee.eb.mil. WAWF is not optional on DoD contracts — DFARS 252.232-7003 makes electronic submission mandatory, and DFARS 252.232-7006 defines the routing information your invoice must include.

The core concept in WAWF is the three-way match: before DoD pays, the system verifies that the contract, the receiving report (confirming the government received what you delivered), and your invoice all align. If any of the three disagree, payment halts until the discrepancy is resolved. Understanding this helps you anticipate where delays come from.

One practical advice for new DoD contractors: request a WAWF walkthrough from your contracting officer's representative at contract kickoff. Most CORs will spend 30 minutes helping you set up routing and submit a test invoice. This is standard — they want you billing correctly as much as you do.

What you invoice — and how you support it — depends on your contract type. The invoicing requirements are meaningfully different across the main types. Getting them confused is a fast path to rejection.

These are the actual reasons invoices get returned. Each one resets your Prompt Payment clock. A single billing cycle with two rounds of rejection can push payment back 45-60 days on what should have been a 30-day invoice.

If you experience repeated rejections on the same contract, ask for a meeting with the contracting officer or billing office. They will often walk through their internal checklist with you. One 20-minute call can prevent months of back-and-forth.

When you have one contract, manual invoicing is manageable. When you have three or five — each with different contract types, billing offices, systems, and submission schedules — an ad-hoc process breaks down. Build structure from your first contract.

Cash flow predictability on government contracts comes directly from billing discipline. The firms that struggle with government cash flow — despite having good contracts — are almost always the ones with inconsistent billing schedules, invoice errors that push payment back 2-3 weeks per cycle, and no visibility into where each invoice stands. These are process problems, not contract problems.

CapturePilot's pipeline management tracks your active contracts from award through closeout — including billing milestones, deliverable dates, and funded ceilings. Combined with the contract intelligence that shows you modification history and option exercise dates, you get a full picture of each contract's billing status without maintaining a separate spreadsheet for every award.