Federal Invoice Payment: Check Receipt, Acceptance and Disputes
Check a federal invoice’s receipt and acceptance dates, work through a complete due-date example, and prepare a focused payment-status request.
Estimated reading time: 6 minutes
A federal customer’s unpaid invoice raises more than one question: did the right office receive a proper invoice, has the government accepted the work, and is anyone disputing the amount or performance? An aging report alone can’t answer them.
This guide is for reviewing ordinary goods-and-services invoices under a federal prime contract. Start with that contract’s payment clause, applicable agency deviations and exceptions. It doesn’t cover subcontractor payments, construction, special food rules, fast-payment procedures, cost-reimbursement interim payments or contract financing.
Read the payment clause before counting days
Under the standard FAR 52.232-25 clause, the general invoice-payment date is the later of 30 days after designated billing office receipt of a proper invoice and 30 days after government acceptance, subject to the clause’s exceptions. It isn’t a universal deadline measured from the invoice’s printed date.
For potential interest computation only, the clause generally uses constructive acceptance on day seven after compliant delivery or performance, unless the contract specifies otherwise or there’s a qualifying disagreement. Earlier actual acceptance is used instead. Constructive acceptance doesn’t compel officials to accept the work or pay before fulfilling their responsibilities.
Keep those two concepts separate on your review sheet: actual acceptance and the acceptance treatment used for any interest calculation. An empty acceptance field isn’t permission to fill in a guessed date.
Check what made the invoice proper—or defective
FAR 32.905 ties payment to a proper invoice and satisfactory performance. Invoice requirements include contract identifiers, billed items and prices, payment terms and any contract-required support. Check the actual requirements rather than assuming a familiar commercial invoice is sufficient.
TIN or banking information belongs on the invoice only when required. Correct EFT information may instead need to have been supplied under the applicable contract procedures, unless EFT was waived. This isn’t a reason to email sensitive information to an unverified contact.
Keep any defect notice, its date and the stated reason. Untimely notice of an improper invoice affects the applicable interest calculation; don’t assume every correction starts a completely untouched payment period.
Try a four-record review without inventing a deadline
Original hypothetical exercise: A supplier’s folder contains these records for one ordinary federal invoice. The dates are invented, and the folder is deliberately incomplete.
| Record | What is known | Question left open |
|---|---|---|
| Invoice copy | Dated October 2 | Which version reached the designated office? |
| Acknowledgment | Receipt recorded October 5 | What document and office does the acknowledgment identify? |
| Delivery record | Delivery recorded October 6 | Where is the separate acceptance or review record? |
| Later email | Questions one line item’s quantity | What exactly remains disputed, and what response has been recorded? |
The useful output is an unresolved-question list, not a due date or interest figure. Attach each question to its source document. Preserve the original email rather than replacing it with a summary such as “payment delayed.” That summary loses the difference between an administrative status question and a disagreement about the billed work.
When the answer arrives, retain both the question and response. A new document may resolve one uncertainty without resolving the others.
Complete example: turn confirmed records into a due date
Use a new fictional invoice, separate from the incomplete folder above. Assume the ordinary FAR 52.232-25 payment clause applies without a different contractual or agency rule. The designated billing office confirms receiving a proper invoice on October 5, 2026. The government receives and actually accepts the compliant work on October 6, 2026. There’s no disagreement, defect, special-payment category or final-settlement issue.
| Confirmed event | Thirty days later |
|---|---|
| Proper invoice received October 5 | November 4, 2026 |
| Work actually accepted October 6 | November 5, 2026 |
The later date is November 5. It’s a Thursday, so this example doesn’t need the weekend or federal-holiday adjustment. The printed invoice date isn’t used as a substitute for the confirmed receipt date. The example’s immediate actual acceptance also avoids substituting a later constructive-acceptance date.
This establishes the modeled ordinary due date, not an interest award. Whether interest is payable still requires the conditions described below and the relevant payment record. If the acceptance evidence is absent, return to the unresolved-question list rather than copying this result.
A focused payment-status request
“Please confirm the designated billing office’s receipt date for invoice ___ under contract ___. Is the invoice considered proper? Please identify any defect or disagreement, the recorded acceptance date, and the payment office handling it. Our records show receipt ___ and acceptance ___. Please explain any difference and confirm the payment status.”
Send the request through the contact route in the contract and keep its response with the original acknowledgment. A status request is an information-gathering step; it doesn’t replace a contract claim or its deadlines.
A rejection doesn’t always erase the first receipt
FAR 32.906 addresses an invoice determined to have been proper but erroneously rejected. Upon resubmission, the payment office uses the original designated billing office receipt date to calculate the correct due date and any interest due. That’s narrower than saying every corrected invoice keeps its first date.
The same section permits payment on the following working day without late-payment interest when the due date falls on a Saturday, Sunday or legal holiday when government offices are closed.
Keeping the original acknowledgment, rejection explanation and later resolution together helps prevent a revised copy from becoming the only surviving record. It doesn’t itself establish which legal treatment applies.
Automatic interest still has conditions
FAR 32.907 provides automatic late-payment interest when its applicable conditions are met. These include a proper invoice, government documentation authorizing payment, no quantity, quality or contract-compliance disagreement, and payment after the due date. A final invoice must also be free of further contract-settlement actions affecting its amount.
Prompt-payment interest isn’t paid for delays caused by disagreements over payment amount or compliance, or on amounts properly withheld or retained under the contract. Contract disputes and any associated interest follow the Disputes clause instead. “Automatic” therefore doesn’t mean every unpaid invoice earns interest.
This guide doesn’t calculate an award, establish a claim or cover the separate procedures for seeking an additional penalty. For a substantive dispute, obtain qualified government-contract advice rather than treating a payment-status inquiry as a substitute.
Leave the review with specific questions
- Which contract clause and version did you review?
- Which existing record supports each date or status?
- What fact remains unconfirmed, and which contact named in the contract can address it?
- Who will retain the response and update the unresolved-question list?
These are practical recordkeeping suggestions, not a prescribed claims process. Don’t assume an inquiry pauses contractual or legal deadlines. Keep the receivable’s review separate from a promise that cash will arrive on a particular day.
For the separate financing decision, see invoice financing versus factoring. Funding an invoice and establishing the government’s payment obligations are different tasks.
Sources checked October 28, 2026 UTC. General U.S. business-finance education, not an individualized legal determination. Actual contract terms, applicable rules and documented facts control.
