A government invoice's due date depends on the contract's payment clause, relevant dates, and any applicable shorter period.
Key takeaways
- Check the payment clause before calculating a due date.
- Record when the billing office received the invoice and when the government accepted the work.
- Keep progress-estimate approval dates separately.
Why one government invoice can have a different due date than the last one
Different contractual payment triggers can explain different due dates. Federal contract rules tie the payment clock to specific events, and the event that starts the clock depends on the kind of payment being requested.
This post explains three day counts that appear in federal prompt payment clauses. It describes what each count means in plain terms and gives your team a simple way to calculate and track due dates. It is written for operations leads and partners, not lawyers. The contract itself controls, and nothing here replaces reading it closely or asking your client's contracting staff when a term is unclear.
One caution up front. The specific numbers in this post come from the text of FAR clause 52.232-26, which applies to fixed-price architect-engineer contracts. Your client's contract may cite a different clause. The general clause for other contracts is 52.232-25, and we come back to the difference below.
The first count: 30 days after a proper invoice is received
The first count starts when the government's designated billing office receives a proper invoice from the contractor. Under FAR 52.232-26, the due date is "the 30th day after the designated billing office receives a proper invoice from the Contractor," subject to exceptions the clause describes.
Two words in that sentence deserve attention. The first is "designated." The clock starts at the billing office the contract names, not when your client emails a project manager or drops a PDF into a general inbox. The second is "proper." The clause points to sections 2.101, 32.001, and 32.902 of the Federal Acquisition Regulation for definitions of pertinent terms, so your team should read those definitions before assuming an invoice is complete.
In practice, the date your client prepared an invoice and the date the billing office received it can differ by days or weeks. If your firm calculates due dates from the date printed on the document, the calendar can be wrong. Ask for the date the billing office recorded receiving it whenever the contract or the client's process allows it, and store that date next to the invoice.
The second count: 30 days after government acceptance
The second count uses a different trigger. It is when the government accepted the finished work.
The date the invoice is received and the acceptance date may coincide, which can hide the difference. The clause lists these dates separately, so your firm should not assume they always match. Track both dates for each invoice, and confirm how the contract combines them to determine the payment's due date.
Acceptance is also easy to overlook because it happens on the government's side. Your client may know when the project manager signs off, but your firm may not see that information until a payment notice arrives. Ask the client to tell you the acceptance date in writing, and record it in your receivables file. Do not estimate it from the delivery date.
The third count: 30 days after approval of progress estimates
The third count applies to progress payments. The clause provides that "the due date for progress payments is the 30th day after Government approval of Contractor estimates of work or services accomplished." Its trigger is government approval of the contractor's estimate, not submission of an invoice or an accepted deliverable.
For firms that prepare progress billings, two earlier events matter: the contractor's estimate of work accomplished, and the government's approval of that estimate. The invoice itself does not start the clock. Approval may fall on a different day than the invoice, so keep the estimate and approval records separate from the invoice file. That way you can see which date controls each payment.
The three counts side by side
Use this table as a checklist. It summarizes the quoted language, omits the exceptions each clause describes, and does not replace the contract. Check how the contract relates the first two calculations before setting a due date.
| Date component | Trigger that starts the count | Calculation under the clause |
|---|---|---|
| Date invoice is received | Designated billing office receives a proper invoice | 30th day after the designated billing office receives a proper invoice |
| Acceptance date | Government accepts the work or services | 30th day after Government acceptance |
| Progress-estimate approval date | Government approves the contractor's estimate of work accomplished | 30th day after Government approval |
How to tell which count applies
Start by identifying the payment type on the invoice. Is it a request for payment on completed work or services, or a progress payment based on estimates of work accomplished? Then open the payment terms in the contract and find the clause it cites.
The quotes in this post come from the clause for fixed-price architect-engineer contracts. FAR 32.908 explains that the general Prompt Payment clause, 52.232-25, is inserted in other solicitations and contracts, with exceptions. Those exceptions include cases where the commercial products and services clause at 52.212-4 applies, or where payment terms and late payment penalties are set by other governmental authority, such as tariffs.
Do not assume another clause's day counts match the ones above. Read the clause in the contract, and if the contract is silent or unclear, ask the client's contracting staff to point you to the governing language.
Illustrative example: a progress payment
Suppose the client submits a progress estimate, and the government approves it on day 10 of an illustrative timeline. The third count places the due date on the 30th day after approval. Confirm the counting convention against the contract and your firm's standards. The invoice that follows may be dated earlier or later, so the approval date, not the invoice date, is the number to record. If any of these dates falls on a weekend or legal holiday, paragraph (a)(3) of the clause governs, as the next section explains.
Weekends and holidays can move the date
The 52.232-26 clause includes a note that reads "(However, see paragraph (a)(3) of this clause concerning payments due on Saturdays, Sundays, and legal holidays.)" A due date that lands on a weekend or holiday is therefore governed by that paragraph, not by a general assumption. Do not assume the date rolls forward or backward. Pull up paragraph (a)(3) in the clause and apply it to the specific date. The clause text is where to find it.
Agencies can set shorter periods
Thirty days is not always the number. The shorter period applies only to the paragraphs the agency amends, so check the contract and agency rules before you set a calendar entry.
The practical lesson is simple. Do not hard-code 30 days into a standard form for every government client. Put the due-date rule in each client record, and note the source next to it, whether that is the clause, the contract, or an agency adjustment.
Common mistakes
Check for these errors during monthly reviews.
- Calculating from the date printed on the invoice instead of the date the billing office received it.
- Failing to check how the contract uses both the date the invoice is received and the acceptance date.
- Applying the progress-payment trigger to a final invoice, or the reverse.
- Hard-coding 30 days into every government client's tracking form.
- Forgetting the weekend and holiday rule when a due date lands on a non-business day.
- Assuming that one clause governs every contract with the same client.
- Waiting for the client to raise a late payment before looking at the record.
Today, open one unpaid invoice's contract and record its payment clause and relevant dates. Add them to your client intake checklist.
Related guides: Form 9465 payment plan limits: 3 dollar tests · Late filing penalty rates: 4 agency figures on tax due · New-hire report due within 20 days in 4 states.
Questions to ask your client
Ask these at the start of an engagement, and again whenever a contract is modified or renewed.
Which billing office receives our invoices, and how do we confirm they arrived?
Use the designated billing office named in the contract and ask for its recorded date.
Who records government acceptance of completed work, and how will we learn the date?
Ask the client to identify the contact and provide the acceptance date in writing.
Which of our payments are progress payments, and who approves the estimates?
Identify payments based on estimates of work accomplished and confirm government approval.
Which clause does the contract cite for payment terms, and has any agency adjustment applied?
Read the contract's payment clause and check for an amended payment period.
How will we be notified when a payment is made, and does that notice show any interest included?
Agree how the client will share payment notices and interest details.
Who should we contact when a payment is late?
Ask the client to name the contact for payment-status questions.
When a payment is late
The clause says the designated payment office "will pay an interest penalty automatically, without request from the Contractor, if payment is not made by the due date and the conditions listed in paragraphs (a)(3)(i) through (a)(3)(iii) of this clause are met, if applicable." Two points follow. First, your firm does not have to request the penalty. Second, the penalty applies only when the stated conditions are met, so read those conditions before concluding that interest is owed. FAR 52.232-26 has the full text.
The clause also says the government computes the interest penalty under the Office of Management and Budget prompt payment regulations at 5 CFR Part 1315. Your firm does not need to calculate interest to track receivables, but it should check the payment record when a due date passes. Confirm whether the payment was made, whether any interest was included, and whether the conditions in the clause appear to be met.
When a due date passes without payment, start with the record. Confirm the trigger date, the clause, and any shorter period that applies. Then send your client a written question about the payment's status, and keep a dated log of every contact. Good records help the client's staff trace the payment, and they help your firm if the payment office asks for dates later.
Who does what inside your firm
Due-date tracking works best when roles are clear. Consider assigning operations leads the records of invoices received, acceptance, and approval, because they see the paperwork as it moves. Staff who prepare invoices should note the billing office and the clause on every file. Partners should review the aging report on a regular schedule and ask about any government invoice that is past due without a documented reason. If your firm handles several government clients, consider a single shared checklist so that each client's rules are recorded in the same format. A checklist can help preserve dates during hand-offs, so it should be the first thing a new owner reads.
A simple tracking routine
Here is a routine that works for most small firms. Adapt it to the clauses in each client's contract.
- Record when the billing office received every invoice, not just the invoice date.
- For completed work, record the government's acceptance date in writing when the client provides it.
- For progress billings, record the date the government approved the contractor's estimate.
- Note which clause the contract cites, and whether any agency period differs from 30 days.
- Calculate the due date from the correct trigger, and flag any date that falls on a weekend or holiday for review under paragraph (a)(3).
- Set reminders before the due date, not after it.
- When payment arrives, reconcile it against the due date and note any interest the payment office added.
For related payment-record checks, see client bank reconciliation.
Accurate due dates feed your aging report and your cash forecast. A forecast built on the invoice date instead of the right trigger will be off for the whole client, and that error can compound across several contracts. Keep the routine in writing, so a new staff member who inherits a government client can see the trigger, the clause, and the last few due dates without asking the previous owner.
Where to check the source text
Verify every date against the source before relying on it. The clause for fixed-price architect-engineer contracts is at FAR 52.232-26. The agency-period rule and the note on which clause applies in other contracts are at FAR 32.908. Check the contract for the clause it actually cites, and send questions about how a clause applies to your client's contracting staff or counsel.
Due dates are only as reliable as the trigger dates behind them. Record those carefully, and the calendar usually takes care of itself.