Federal progress payments have two clocks: conditional approval on day 7 and payment due on day 14, subject to documented extensions. The contractor reports work performed, submits a request, and waits for payment. In practice, federal progress payments run on two separate clocks. Accounting staff who watch only one of them end up chasing payments that are not yet late, or missing ones that are. This post walks through both clocks using the payment rules in the Federal Acquisition Regulation (FAR), and shows how to track them in a billing log.
This is general guidance, not legal advice. Your client's contract and the instructions from its contracting officer control the details of each award.
Why progress billings run on two clocks
For accounting staff, this work is mostly about dates and documents. You do not need to judge whether the work was performed well. Your job is to know which date governs, when it arrived, and what the record shows.
The first clock is about approval. Before the government pays a progress payment based on estimated work, someone on the government side has to approve the estimate. In some cases the FAR treats that approval as happening automatically once a set period passes, so the first clock can run out without anyone signing anything.
The second clock is about payment. Once a request is in the government's hands, a due date applies to the payment itself. That date is counted from when the designated billing office receives the request, not from when the estimate was approved.
Both clocks are set out in FAR 32.904, Determining payment due dates. Read it next to your client's contract. The clauses in a specific award decide which payment terms apply, and the FAR sets the default rules that those terms work from.
The first clock: constructive approval in 7 days
The FAR says that government approval of a progress estimate is deemed to occur constructively on the 7th day after the designated billing office receives the contractor's estimates ( FAR 32.904). "Constructively" means the approval is treated as given even though nobody signed off. For a billing clerk, this is the point where silence starts to count.
The rule has conditions. Constructive approval depends on two things: the payment request must be proper, and there must be no disagreement over quantity, quality, contractor compliance with contract requirements, or the requested progress payment amount ( FAR 32.904). If the government raises any of those disagreements, the automatic approval does not apply in the normal way. You then need to find out what the disagreement is and whether it has been resolved.
The FAR also lets the contracting officer extend the approval period beyond 7 days, but only with a record. The contracting officer must document in the contract file the justification for extending the constructive acceptance or approval period beyond 7 days ( FAR 32.904). A request for that justification is a fair, specific question to put to the contracting officer.
The second clock: payment due 14 days after arrival
The FAR sets a due date for progress payments based on contracting officer approval of the estimated amount and value of work performed. That date includes payments for reaching milestones in any project. The due date is 14 days after the designated billing office receives a proper payment request ( FAR 32.904).
Notice what starts this clock. It is the arrival of a proper payment request at the billing office. If your team counts from the day the work was finished, the contractor's sending date outside the fallback below, or the day someone in the program office first saw the numbers, your count will not match the rule.
The contracting officer can also extend this due date, again only with a record. The contracting officer must document in the contract file the justification for extending the due date beyond 14 days ( FAR 32.904). If a payment passes day 14 without a documented extension, first confirm the date received and check for any disagreement on file, then raise it with the contracting officer.
What makes a request "proper"
Both clocks depend on a proper payment request. Your client's contract and the billing instructions attached to it are the place to check what the government expects to see in a request.
In practice, this means a request that does not meet the contract's requirements may not start the clock. Before you assume a clock is running, compare the request against the contract's billing requirements and confirm it meets them. If the government sends back a request as improper, record the reason and the date it went back. Record when the billing office receives any corrected request, because the clocks depend on a proper payment request.
The disagreement conditions matter as much as the form of the request. For the payment due date, the FAR's fallback rule lists quantity, quality, and contractor compliance, and leaves out the payment amount ( FAR 32.904). The lists are close but not identical, so do not copy one into the other. When a disagreement appears, write down which category it falls into, because the category decides which clock it affects.
When the billing office does not record the arrival date
The second clock depends on the date the billing office receives the request. Sometimes that date is not recorded when the request arrives. The FAR covers this case. If the designated billing office fails to annotate the payment request with the actual date received when it arrives, the payment due date is 14 days after the date of the contractor's payment request. That applies provided the billing office receives a proper payment request and there is no disagreement over quantity, quality, or contractor compliance with contract requirements ( FAR 32.904).
This fallback is useful, and it is also a reason to protect your own records. The contractor's payment request date becomes the starting point, so the date on the request and the date you sent it need to be accurate and easy to prove. Keep the transmittal email, the submission confirmation, or whatever record your client's systems produce. If the billing office stamps or logs the arrival later, compare its date with yours and note any gap.
Ask for the documented extension when a payment runs past the fallback date (FAR 32.904).
Why you need to track both clocks
It is tempting to track only the payment date and ignore the approval window. That approach misses two things. First, the approval clock can produce a point where the government is treated as having approved an estimate, even though no approval letter exists. Second, the two dates answer different questions, so checking one does not tell you the status of the other.
Keeping both dates in view also helps you judge the tone of a follow-up. A request that is three days into its approval window is a routine check-in. A request that has passed its approval window with no documented extension and no disagreement on file is a specific, firm question for the contracting officer.
Setting up a billing log
A simple spreadsheet can carry both clocks. Use one row for each progress payment request, with columns for the following:
- Request number and the period of work it covers
- Date the contractor submitted the request, with proof of submission
- Dates the billing office received the contractor's estimates and the proper payment request, recorded separately, with the source of each date
- Date of the 7-day approval mark, calculated from when the estimates arrived
- Date of the 14-day payment mark, calculated from when the proper request arrived or from the fallback date
- Any disagreement raised, with its category: quantity, quality, compliance, or amount
- Any extension requested, approved, and documented, with the contract file reference
- Date payment was received, and the amount
The 7-day and 14-day marks are the two dates to watch. Use separate date columns: tie the approval formula to when the billing office receives the contractor's estimates, and the payment formula to when it receives a proper payment request, using the contractor's request date when the fallback applies. Write down the counting convention your client's contract or agency uses, and apply it the same way to every request.
Add a status column with a simple value for each row: on track, approval window open, payment window open, disagreement open, extended, or paid. A status column makes it easy to see at a glance which requests need a call this week.
For related tracking, see government invoice due dates.
Explaining the clocks to your client
Clients often ask why a payment has not arrived when the contract seems to say otherwise. The useful answer usually comes down to which clock is running and where it stands. Explain the two clocks in plain terms, and show the dates from your log rather than quoting the rule from memory.
Start with the date received. Most timing disputes begin with a disagreement about when the request arrived. If your client's own records show a submission date, bring that date to the conversation, along with the billing office's record if it has one. Two dates that differ by a few days are much easier to reconcile when both are on the table.
Next, separate the approval question from the payment question. A client may believe a payment is late when the approval window is still open, or may believe approval is settled when a disagreement is still pending. Naming the clock and its status in each conversation keeps the discussion on the right question.
Be careful with promises. A client who hears from the program office that money will arrive on a certain day may plan around that date. Tell the client what the rules say, what the log shows, and what the government has said in writing. Avoid guessing when money will move, because a guess repeated to the client can start to sound like a commitment.
Finally, agree on a short update rhythm. A weekly note listing each open request, its current clock status, and the next action keeps the client informed without a flood of calls. The same note becomes a useful record if the file is ever reviewed.
When a payment runs past its date
When a payment runs past its 14-day mark, work through the same short checklist each time.
First, confirm the date received. Check the billing office's record against your own submission. A dispute about when the clock started is often the quickest thing to resolve, and it can change the answer entirely.
Second, check for a disagreement. Look at the file and the correspondence for any note about quantity, quality, contractor compliance, or the requested amount. If a disagreement is on record, the clock may not be running in the normal way, and the question shifts to whether it has been resolved.
Third, ask for the documented extension. Ask the contracting officer whether one exists, and ask to see the reference ( FAR 32.904). If nothing is on file, say so in writing.
Fourth, escalate through the right channel. Your client's contract manager or project lead is usually the first contact. Keep the message short and factual. State the request number, the date received you have on record, the 14-day date, and the question you need answered. Attach the proof of submission so the discussion stays on facts.
Keep every follow-up in writing, even when a phone call resolves something. A written record protects your client if a later question comes up about when a request was received, whether it was disputed, or whether it was extended.
Common mistakes to avoid
Several mistakes come up again and again with progress billings.
The first is starting the clock on the wrong date. Counting from the approval date or from the day the work finished will give you the wrong answer.
The second is treating silence as the same thing as approval without checking the conditions. Silence on a request that has a disagreement attached does not work the same way.
The third is merging the two clocks into one. The approval clock and the payment clock have different start points, different triggers, and different extension periods. A log that records only one of them will mislead the team.
The fourth is accepting an extension without a record. An extension given only in a hallway conversation or a verbal promise is not the same thing as the documented justification required by FAR 32.904.
Keep your own proof of submission so you can compare it with the billing office's record.
Keeping the file clean
Good progress payment tracking is mostly good records. Keep the request, the proof of submission, the date received, any disagreement notes, any extension justification, and the payment record together for each request. When a question comes up months later, a complete file answers it in minutes, and a missing piece can turn a simple payment question into a long dispute.
Billing work often changes hands. A colleague may cover the log during leave, or a new analyst may inherit a set of open requests partway through a cycle. A handoff note that lists each open request, its date received, its clock status, and any open disagreement lets the new person pick up the work without rebuilding the history from email.
Review the log on a fixed schedule, such as every Monday or at the start of each billing cycle. Check which requests are close to a mark, which have open disagreements, and which extensions still need paperwork. A short review each week costs little time, and it makes a late payment visible while there is still time to act on it.
Track both, write down every date, and keep the proof. That is the difference between chasing a payment and knowing exactly where it stands.