Payment follows the invoice, not the work
A team can deliver excellent work for three months and still wait on its money, because the federal payment process does not look at the work. It looks at the invoice. An invoice that matches the order, carries the required content and arrives through the right system gets paid on a clock set by law. An invoice that misses any of those comes back, and the clock starts over when the corrected one arrives.
For most civilian agencies, the system is the Invoice Processing Platform, a free web-based service run by the Bureau of the Fiscal Service at the Department of the Treasury. Vendors submit invoices and supporting documents there, agencies review and approve them there, and both sides can see the status of each invoice as it moves. This guide covers the path from award to payment on a civilian order, what makes an invoice proper, how the Prompt Payment Act clock works and why invoices get rejected.
One point before anything else: not every agency uses the platform, and defense agencies use a different system entirely. The contract tells you which one to use, usually in an invoicing instructions clause or a section of the order labeled for payment. Read that before you read anything else about invoicing.
From Award to Payment on a Civilian Order
Before the first invoice: registration and enrollment
Two registrations have to be in order. The first is SAM.gov. Federal payments go to the bank account in your SAM.gov registration, so an expired registration or outdated banking information stops payment no matter how perfect the invoice is. Check the expiration date the day the order arrives and put the renewal on the calendar well ahead of it.
The second is the invoicing platform. Enrollment is generally started by the agency that uses it, and the person your company designates then receives instructions to set up access. If your order names the platform and nothing has arrived within the first week or two, ask the contracting officer or the agency's invoicing contact rather than waiting. If your company already has access from an earlier order, confirm the new order is visible to you.
Decide who on your side submits invoices and who can see payment status. A small number of trained people who submit every invoice the same way produces far fewer rejections than whoever happens to be free that week.
Find the order in the system and check it against the PDF
When an agency transmits its orders to the platform, your purchase order appears there with its line items as the agency's financial system recorded them. This is the moment to compare it against the signed order, line by line. Check line item numbers, descriptions, quantities, units, unit prices and amounts.
If anything differs, stop and tell the contracting officer before you invoice. A difference means the order was entered into the financial system differently from the document you signed, and invoices built against the signed order will not match the obligation the payment office sees. Fixing it may take a modification or a correction in the agency's system. Either way, it is far cheaper to fix in week two than after three rejected invoices.
Also check the funding. An order can be partially funded, with only some of the total obligated now and more added later. You can invoice only against what is obligated. Keep a running total of billed amounts against each line's obligated amount, and warn the contracting officer and the COR well before you reach the limit.
Invoice line by line against the order
Every charge on a federal invoice belongs to a specific contract line item, and the invoice should use the same line item numbers, descriptions and units the order uses. Do not combine lines, rename them or add your own. An invoice that says "consulting services, September" against an order with four line items is asking the reviewer to guess, and reviewers do not guess. They return the invoice.
How you bill each line depends on its pricing arrangement:
- Firm fixed price, deliverable based. Bill the line after the deliverable is delivered and, where the order requires it, accepted. Attach or reference the delivery and acceptance record.
- Firm fixed price, periodic. Some fixed-price lines are billed in equal monthly amounts or another schedule the order states. Bill exactly that amount on exactly that schedule.
- Labor hour. Bill hours worked by labor category at the contract's fixed hourly rates. Support with hours by person and category for the period.
- Time and materials. Labor as above, plus materials at cost as the contract allows, each supported with its own documentation.
- Travel and other direct costs. Bill only when the order includes a line for them, only within its ceiling, and with receipts and approvals attached.
Invoice for the period the order sets, which is commonly monthly for labor-hour and time-and-materials work. Use one invoice per period per order unless the agency asks otherwise, and give every invoice a unique number your accounting system can trace.
Supporting documents the reviewer will look for
The reviewer, usually the COR on a services order, is asked to confirm that what you billed matches what happened. Support makes that a five-minute task instead of an email exchange.
Labor. For labor-hour and time-and-materials lines, attach a summary of hours by person, by labor category and by day or week, matched exactly to the invoice totals. Many contracting officers also require the underlying timesheets. Each person billed should be qualified for the category billed under the contract's labor category descriptions, and if the contract names key personnel, the names on the timesheets should match. Hours for a person the government has never heard of draw questions.
Travel. Travel is reimbursable only when the order provides for it, usually with prior approval from the COR or contracting officer for each trip. Contracts commonly limit allowable travel costs to the rates in the Federal Travel Regulation. Attach the approval, an itemized expense summary, and receipts for lodging, airfare and other expenses as the contract and the travel rules require. Keep per diem calculations visible so the reviewer can check them against the published rates for the location and dates.
Deliverables. For fixed-price deliverables, reference the transmittal email or the acceptance record. A one-line note such as "Deliverable 3, final analysis report, delivered August 28, accepted by the COR September 4" saves a round of questions.
What makes an invoice proper
The Prompt Payment rules define the content of a proper invoice, and the contract's payment clause repeats it. An invoice missing any required element can be returned as defective, which resets the payment clock. Treat the list below as the pre-submission check for every invoice.
- Your company name and address, matching the order and your SAM.gov registration
- Invoice date and a unique invoice number
- Contract or order number, and any other identifiers the order requires
- Line item numbers, descriptions, quantities, units, unit prices and extended amounts, matching the order
- The period of performance or delivery covered by the invoice
- Payment terms, and shipping or delivery information where the work involved delivery
- Name, title and phone number of the person to notify about a defective invoice
- Taxpayer identification number and electronic funds transfer information, where the contract requires them on the invoice
- Supporting documents: hours by person and category, receipts, approvals and acceptance records
- Any other information or documentation the contract specifically requires
That last item is the one that catches people. Agencies add their own requirements, such as a cumulative billing summary, a specific cover sheet or a certification statement. The order's invoicing instructions will say. Build a template per order that includes every agency-specific element, and reuse it every month.
How the Prompt Payment clock works
The Prompt Payment Act sets the government's payment timing. For most services contracts, payment is due 30 days after the designated billing office receives a proper invoice, or 30 days after the government accepts the work, whichever is later. If the government pays late, it owes interest automatically, at a rate the Treasury sets every six months, without the vendor having to ask.
Three rules that decide when you get paid
First, the clock runs from receipt of a proper invoice, so a defective invoice does not start it. Second, when an invoice is defective the agency is expected to return it with the reasons within seven days of receipt; when it takes longer, the delay counts against the government in computing any interest due. Third, contracts usually treat acceptance as occurring a set number of days after delivery for the purpose of the payment clock, unless the contract states a different acceptance period. Read the payment clause in your order for the exact terms, because contracts can vary these rules within what the regulation allows.
The practical consequence is simple. A proper invoice submitted on the first day of the month is generally paid by the end of the month. An invoice returned on day six for a missing timesheet and corrected on day twelve restarts on day twelve. Two rejections in a row can push a month of labor into the following quarter, and on a services contract with salaried staff that is a real cash problem.
Why invoices come back, and how to fix each one
Rejections fall into a short list of patterns, and nearly all of them are preventable with a template and a checklist.
| Rejection reason | What happened | Fix |
|---|---|---|
| Line items do not match the order | Charges combined, renamed or placed on the wrong line, or the order was entered differently in the agency system | Invoice with the order's exact line numbers and descriptions; ask the contracting officer to correct any system mismatch |
| Amount exceeds funding | Cumulative billing passed the obligated amount on a line | Track billed against obligated per line; request incremental funding before you reach the limit |
| Missing or inconsistent support | Hours summary does not add to the invoice, timesheets missing, or receipts absent | Generate support from the same source as the invoice and reconcile before submitting |
| Billing before acceptance | A fixed-price deliverable was invoiced before the government accepted it, where the order requires acceptance | Wait for acceptance, or confirm the billing trigger at the kickoff and record it |
| Unapproved travel or other costs | A trip or purchase was billed without the prior approval the order requires, or above allowable rates | Get written approval before each trip; keep costs within the travel rules the contract cites |
| Period or rate errors | Wrong billing period, overlapping periods, or a rate that does not match the labor category or option year | Lock rates by category and option period in the template; one invoice per period |
When an invoice is rejected, read the stated reason, fix that issue and every similar issue in the same invoice, and resubmit promptly. Do not argue the rejection inside the invoicing system. If you think the rejection is wrong, send a short, specific note to the COR or the contracting officer with the clause or order section that supports your reading.
Defense agencies use a different system
If your customer is a Department of Defense component, invoicing generally runs through the Procurement Integrated Enterprise Environment, known as PIEE, and its invoicing module, rather than the Treasury platform. The defense supplement to the federal acquisition rules requires electronic submission of payment requests through that system, and the contract will name the specific document types and routing codes to use.
The principles in this guide carry over: invoice line by line against the order, attach support, keep registration current and check every element of a proper invoice. The mechanics, roles and terminology differ, so treat a first defense invoice as its own setup task, and read the defense invoicing clause in the contract before you start.
Make invoicing a monthly routine
Invoicing goes smoothly when it is boring. The teams that get paid on time run the same steps every month in the same order, and none of the steps depend on memory.
Close timekeeping on the last business day of the period and approve it within two days. Build the invoice from the order template, pulling hours from the timekeeping system and travel from the expense system, so the numbers on the invoice and the support come from the same source. Have a second person compare the invoice against the order and the checklist. Submit within the first week of the new month. Log the submission date, the invoice number and the amount, and check status weekly until payment arrives.
Reconcile every payment against the invoice it pays. Payments can be short for reasons that are not obvious in the remittance, such as a disallowed charge or a line paid on a different date. Catching a short payment in the month it happens is easy. Finding it at closeout, months later, is not.
Frequently asked questions
Under the Prompt Payment Act, payment on most contracts is due 30 days after the designated billing office receives a proper invoice, or 30 days after acceptance of the work if that is later, unless the contract sets a different date. Late payments carry interest at a rate set by the Treasury, paid automatically.
An invoice that contains every element the payment clause and the contract require: your name and address, invoice date and number, contract number, line item details matching the order, the period covered, a contact for defective invoices, payment information where required and any agency-specific documentation. Missing any element can make the invoice defective, and a defective invoice does not start the payment clock.
Usually the COR reviews it against the work performed, and the contracting officer or the payment office approves it for payment. The order and the agency's procedures set the exact routing. Clean support that matches the invoice line by line is what gets it through review quickly.
Generally no. Defense contracts require electronic invoicing through the Procurement Integrated Enterprise Environment, known as PIEE. The contract names the system and the document types to use, so check the invoicing clause on every order.