What FAR 52.232-27 Demands of Federal Construction Invoicing

October 17, 2026

Federal construction contractors who treat invoice dates as administrative metadata now face a stricter evidentiary standard. Effective March 13, 2026, FAC 2026-01 revises FAR 52.232-27 so the government considers payment made on the day a check is dated or the date an electronic funds transfer is transmitted. Those trigger dates can determine whether a federal agency paid late and whether prompt-payment interest is owed. They are not billing trivia; they are interest-bearing evidence.

This analysis explains what changed and how to apply the revised clause in practice. You will move through the payment-made trigger, the payments the clause covers and excludes, the 14-day progress-payment clock and receipt-annotation trap, retainage release 30 days after contracting officer approval, and the later-of rule and 30-day acceptance window for final payments. It also addresses calendar-day deadline math, the 7-day improper-invoice return rule, interest on late payment, trigger dates you must record, worked examples, G-Invoicing, and how to build trigger-date tracking into billing and closeout. The goal is simple: make every trigger date provable.

What FAC 2026-01 Actually Changed in FAR 52.232-27

FAC 2026-01 carries an effective date of March 13, 2026, shown on the FAR pages for FAR 52.232-27, 52.232-25, 52.232-5, and Subpart 32.9. That makes it the operative change for prompt-payment compliance in this cycle, even though the clause title date on acquisition.gov still reads (Jan 2017). Because the FAC 2026-01 redline has not been reviewed for this piece, treat any summary of what changed as provisional until you read the current clause text yourself.

Watch the payment-made trigger sentence specifically. The published clause and the 2023 CFR text both state that the Government considers payment made on the day a check is dated or the date of an electronic funds transfer. Both use the same wording. Any brief or summary claiming the revision changed the trigger to the day a payment file is transmitted is not supported by the clause text as published. Verify that reading against the actual FAC redline before relying on it in a payment dispute.

Subpart 32.9 remains the umbrella authority. It implements OMB prompt-payment rules at 5 CFR Part 1315 and covers invoice payments, not contract financing payments. That scope distinction governs every deadline calculation that follows, starting with the trigger language itself.

The Payment-Made Trigger: Check Date Versus EFT Date

The clause's deadline arithmetic turns on one sentence. FAR 52.232-27 provides that the Government considers payment as being made on the day a check is dated or the date of an electronic funds transfer, wording that appears unchanged in both the 2023 CFR text and the current clause. Nothing in that sentence points to the day a payment file is transmitted, which is why the distinction matters.

This is a payment-side trigger, not a billing-side one. Your invoice submission date starts the due-date clock; the check date or EFT date decides when payment counts as made for interest purposes. Two different events, two different jobs.

For electronic payments, treat the Government's transmission or credit date as the evidentiary anchor, and source it from remittance advice and payment records rather than internal assumptions about when funds left. Best practice: log that date as a payment event tied to the invoice at the moment you receive it, not as a note buried in email.

Finally, read the trigger alongside the due-date rules in the same clause. The trigger defines late; the due-date rules define on time. Interest exists only when the two are compared correctly, using the same invoice record for both.

Which Payments the Clause Covers and Which It Does Not

Now that the trigger is settled, the next question is which payments the clause actually governs. Subpart 32.9 prompt-payment rules apply to invoice payments and expressly exclude contract financing payments, as stated in Subpart 32.9. That split is not academic. It determines whether a payment application carries a prompt-payment clock at all.

FAR 52.232-27 is the construction-specific companion to the general prompt-payment clause at 52.232-25, which is why its due-date arithmetic reads differently from a supply contract. It covers three streams, each with a separate clock and a separate trigger event:

Progress payments: 14 days after the billing office receives a proper payment request
Retainage releases: 30 days after contracting officer approval
Final payments: the later of 30 days after a proper invoice or 30 days after acceptance

One caveat: the clause lists progress payments among invoice payments, while some agency supplements treat contract financing payments separately. Confirm how your contracting officer classifies each application before you compute a deadline.

A proper invoice is the precondition for most of these clocks. Missing content or an ambiguous date stalls the deadline instead of starting it, which makes invoice content and dating discipline a compliance function rather than routine paperwork.

Most of these clocks begin with a payment application you submit on a schedule, so how you structure progress billing for construction determines how many deadlines you are tracking at once.

Map each application to its clause category first. The wrong category produces the wrong deadline and an interest claim that later falls apart under scrutiny.

Progress Payments: The 14-Day Clock and the Receipt-Annotation Trap

Once a payment is classified as an invoice payment rather than contract financing, the progress payment request carries the shortest fuse in the clause.

Under FAR 52.232-27, a progress payment is due 14 calendar days after the designated billing office receives a proper payment request, as set out in the published clause text. The word "proper" does real work here: an incomplete or misdirected request does not start the clock.

The receipt-annotation trap sits in the proof, not the rule. If the billing office fails to annotate the request with the actual date it received it, the clock runs from the date you placed on the request instead. That fallback can move your deadline earlier in your favor, so it only helps when your own documentation is clean enough to defend the date.

Calendar days govern the window. Saturdays, Sundays, and federal holidays do not extend the 14 days unless the contract says otherwise, so compute the due date with straight arithmetic rather than business-day counting.

Your submission date therefore does double duty. It starts the fallback clock when receipt goes unannotated, and it gives you a fixed date to compare against whatever receipt date the Government later asserts.

Send every progress payment request with a transmittal record: a dated cover letter, an electronic submission confirmation, or a receipt acknowledgment. That single artifact decides which date controls when the two sides disagree.

Retainage runs on an entirely different trigger.

Retainage Release: The 30 Days That Start With CO Approval

Progress payments run on a receipt-driven clock. Retainage runs on an approval-driven one, and confusing the two is how contractors lose the 30-day window before it starts.

Under FAR 52.232-27, retained amounts are due as specified in the contract or, if the contract is silent, 30 days after the contracting officer approves release to the contractor. The trigger is an approval event, not an invoice event, so your evidence has to be proof of that approval: a contract modification, a written release, or the CO's documented authorization.

Why Retainage Needs Its Own Receivable

Track retainage separately from the final invoice. Folding it into final billing hides the approval date that starts the 30 days and makes the deadline nearly impossible to reconstruct later. A separate line item with its own due date keeps the clock visible.

When the contract states different retainage terms, follow the contract. Record which document controls, whether the clause, a special provision, or a modification, so your closeout file shows the basis for the deadline you applied.

Calendar days count here too. Because the window runs from approval, a late request for release does not by itself create a late-payment claim; the Government's obligation is measured from its own approval date. Request release early, then hold the documentation. Log the approval date the day you receive it and tie it to the retainage receivable so the deadline is computed from evidence rather than memory.

Final Payments: The Later-Of Rule and the 30-Day Acceptance Window

Retainage runs from an approval event, but final payment runs from a comparison. Under FAR 52.232-27, final payment is due on the later of two dates: the 30th day after the designated billing office receives a proper invoice, or the 30th day after Government acceptance of the work.

Because the rule is later-of, the deadline does not lock in until both events carry a date. Record the invoice receipt date and the acceptance date separately, then compute the later date deliberately. Do not assume the invoice controls.

Acceptance evidence varies by job. It may appear in an inspection report, an acceptance letter, or final acceptance of the contract. Identify the authoritative acceptance record for each project and file it with the payment package so the branch you rely on is provable.

Invoice quality gates the first branch. The invoice must be proper for the 30-day clock to run. If the billing office returns it as improper, the 7-day return rule applies and the deadline analysis restarts from a corrected submission.

Whichever event lands last sets your expectation for funds and the point where interest exposure begins. That is exactly what closeout calendar discipline should answer: not "when did we bill," but "which of the two clocks expires second, and can we prove both dates?" Build that comparison into the final payment record before the file closes.

Calendar Days, Not Business Days: Deadline Math That Does Not Slide

The later-of test still runs on calendar days. That single fact governs every 14-day and 30-day deadline in the clause, and it is where most deadline math quietly breaks.

FAR 52.232-27 states that all days referred to are calendar days unless otherwise specified, and then points to paragraph (a)(3) for payments falling due on Saturdays, Sundays, and legal holidays. Read that paragraph and your contract before assuming anything. A due date landing on a weekend does not automatically become the next business day.

Build your deadline calculators on straight calendar-day arithmetic. Progress payments: 14 days. Retainage: 30 days from approval. Final payments: 30 days from the later of invoice receipt or acceptance. Then flag any computed date that falls on a weekend or federal holiday, not to move the deadline, but to warn your team that follow-up has to happen earlier. The legal date does not slide to fit your schedule.

Document the computed due date at submission. Write it into the invoice record the day you transmit. Reconstructing that arithmetic months later, after closeout, is how valid interest claims get lost.

Finally, confirm which clock applies. These prompt-payment rules cover invoice payments and expressly exclude contract financing payments. Wrong clock, wrong deadline, unprovable claim.

Improper Invoices: The 7-Day Return Rule and What It Costs You

Calendar-day deadline math presumes a proper invoice. When the billing office determines an invoice is improper, FAR 52.232-27 requires it to return the invoice within 7 days and state the reasons. If the notice is late or silent on the defect, the invoice is treated as properly submitted for prompt-payment purposes, and interest can begin accruing on a date nobody planned for.

The same standard cuts both ways: an improper invoice you submit can delay payment without penalty to the Government, while an untimely or vague notice from the billing office strengthens your interest position. Because interest calculation accounts for untimely notice, your invoice log should capture the submission date, the date any notice of impropriety arrived, and precisely what it said.

Prevention is cheaper. Review invoice content against the contract's proper-invoice requirements, including any g-invoicing or billing-office routing instructions, before you transmit. Confirm required data elements, reference numbers, and supporting documents are present.

If you do receive a notice of impropriety, correct the defect and resubmit with a new documented submission date, then confirm receipt in writing. The deadline arithmetic restarts from that new date, so the clock you rely on later depends entirely on the evidence you create now. Verify the current clause text before relying on any summary of this rule in a dispute. That verification habit is what makes the interest claim in the next section computable.

Interest on Late Payment: What the Clause Sets in Motion

A returned or resubmitted invoice resets the deadline arithmetic; the next question is what happens when the Government still pays past the recomputed due date. FAR 52.232-27 creates interest exposure on amounts unpaid after the due date, computed under the applicable prompt-payment rules. The source set behind this analysis did not include the rate or accrual method, so treat the mechanics here as framework rather than formula. Before relying on detailed interest guidance, pull the full 52.232-27 text and 5 CFR Part 1315 to confirm the rate formula, the accrual start and end points, and any exceptions.

Interest runs from the due date, not from the day you notice the payment is late. Your deadline math and your interest math should therefore use the same trigger dates. A payment arriving after the 14-day progress-payment window or the later-of final-payment deadline is running interest from that computed date forward.

Dollar amounts are often small. The signal is not: a pattern of late payments is a compliance risk worth documenting. Record the accrued interest and raise it in writing rather than letting it lapse.

Treat the interest figure as an output of good recordkeeping. You cannot compute it without documented invoice, receipt, approval, acceptance, and payment dates. Each date feeds the same clock, and each is provable only if it lives in your records rather than your memory.

The Trigger Dates You Must Record to Prove a Late Payment

Interest arithmetic is only as good as the dates you feed it. Assemble five data points on every invoice and payment request, at the moment each event occurs.

Invoice and submission date. Date the invoice or payment request as close as possible to the date of mailing or transmission, as the clause directs, and keep the transmittal record that matches: certified mail receipt, courier confirmation, or email delivery log. If those two dates diverge, your own documents undercut you.

Receipt date. Record the designated billing office's annotated receipt date. When the office does not annotate, the clock runs from your request date, so the transmitted copy becomes the controlling proof.

Approval and acceptance dates. Retainage release runs from the contracting officer's approval date. Final payment runs the later-of test between proper invoice receipt and Government acceptance. Capture the modification, release letter, or acceptance record that establishes each.

Payment-made date. Pull the check date or EFT date from remittance records. That is the date the Government considers payment made, and it tells you whether interest stopped or kept running.

A five-column table, one row per invoice, holds the chain together:

That log keeps closeout documentation in step with billing, so an interest claim rests on records rather than recollection.

Worked Examples: Deadline Arithmetic for Three Common Scenarios

With those dates captured, the arithmetic becomes mechanical. Three scenarios show where errors creep in.

The billing office receives a proper payment request May 4. Fourteen calendar days later, the due date is May 18. If the office never annotates receipt, the clock runs from your transmitted request date instead: April 30 plus 14 days is May 14. The earlier date governs, so keep the transmittal as proof.

The CO approves release June 1. If the contract is silent, 30 calendar days sets the deadline at July 1. Follow up before July 1 rather than waiting for payment.

A proper invoice is received July 15; acceptance is documented August 3. The later-of test compares August 14 (invoice plus 30) with September 2 (acceptance plus 30). The deadline is September 2, when interest exposure begins if the amount remains unpaid.

In all three examples, write the computed due date into the invoice record at submission. That single entry keeps follow-up tasks and any interest calculation tied to the same arithmetic.

Where G-Invoicing Fits in Federal Invoice Submission

Those examples all trace back to documents the contractor either controls or receives. G-Invoicing sits in a different lane entirely.

G-Invoicing is the Government's system for ordering and invoicing between federal agencies. It governs intra-governmental transactions, not the contractor invoice payments that FAR 52.232-27 times. When you bill a federal agency directly, your prompt-payment arithmetic does not change: the clock runs from billing-office receipt of a proper invoice or payment request, and payment counts as made on the check date or the EFT date.

Keep that distinction explicit in your written procedures. If an internal procedure applies G-Invoicing terminology to agency-to-agency ordering, label which documents fall outside the prompt-payment trigger so nobody applies the wrong deadline to a live job.

There is one place the two can touch. If your contract's ordering or acceptance flow runs through G-Invoicing or a related order system, retain those records as acceptance evidence for the final-payment later-of test. Do not treat an order-system event as the payment-made trigger. The clause defines that trigger as the check date or the EFT date, and that definition controls your interest math.

From here, the work is making every one of those dates provable.

Building Trigger-Date Tracking Into Billing and Closeout

However the submission channel is classified, compliance value lives in the fields you keep. Treat invoice date, submission date, receipt date, contracting officer approval date, acceptance date, and payment date as structured fields on the invoice record. Free text in an email thread cannot be sorted, aged, or produced as evidence.

Build calendar-day calculators for the 14-day progress-payment clock, the 30-day retainage clock, and the later-of final-payment test, with weekend and holiday flags. This matches the discipline in What Is a Takeoff in Construction? A Contractor's Guide, where measurement before pricing prevents margin loss.

Drive aging reports from the computed FAR due date, not a generic days-outstanding count. A 31-day-old invoice is not necessarily late; a progress payment at day 15 is. Deadline-based alerts tell your team when to call the billing office or contracting officer.

At closeout, roll those dates into the final payment file, so the evidentiary chain for an interest claim is assembled before the file closes rather than reconstructed later.

A job-costing and invoicing platform such as Crew & Cost gives you the invoice and payment fields to record these trigger dates alongside costs, change orders, and closeout documents, keeping compliance data in the same system as the job record.

Conclusion: Make Every Trigger Date Provable

With those fields in place, the compliance question narrows to a single standard: can you prove every date you rely on?

Start by verifying the current clause text against the FAC 2026-01 redline before acting on any summary. Until that text says otherwise, treat the payment-made trigger as the date on the check or the date of the electronic funds transfer, not the day a payment file is transmitted.

Then date every invoice and payment request as close as possible to transmission, and keep the transmittal record that proves it. Build calendar-day math directly into your invoice log: 14 days for progress payments, 30 days for retainage release, and the later-of test for final payment, each flagged when the computed date lands on a weekend or holiday.

Finally, record invoice, submission, receipt, approval, acceptance, and payment dates on every invoice. A late-payment interest claim built on those six dates is evidence. One built on recollection is a request the contracting officer can simply decline.