Straight into the service manual page
WrenchQuarry
More

Routine payment request or claim: 4 triggers to watch

WrenchQuarry Editorial Team · Published · 13 min read · How these guides are written

A routine payment request can become a claim when its amount is disputed or not acted on in a reasonable time. Most payment requests are boring. You finish a phase, you bill for it, the owner or general contractor pays, and everyone moves on. Nobody on the crew thinks about the word "claim" at all. Then one invoice sits unpaid for weeks, or the reviewer writes back asking why the number is different from last month, and suddenly the office is using words like "dispute," "certify," and "decision" that nobody planned for.

Key takeaways

  • Record whether each request is routine or disputed when it is sent.
  • Watch for a disputed amount or a request left unacted on too long.
  • Answer reviewer questions quickly, with backup, and ask for objections in writing.
  • Keep extra and missed work on its own supplemental path.
  • Know your cutoffs and the disputes clause before you need them.

This post is about the moment a routine payment request changes character. On public and contract work, the same piece of paper can be a simple request for payment or the start of a formal dispute, depending on a few facts. Knowing those facts ahead of time lets an owner or office lead decide what to do before the situation gets expensive.

Nothing here is legal advice. Your contract, your state's rules, and your lawyer control the final answer. What follows is a practical map, built on official rules that are public, so you can recognize the two paths and plan for each.

Two documents that look alike

A payment request and a claim can have the same dollar amount, the same job number, and the same attached backup. What separates them is the posture: whether the amount is agreed, whether it is disputed, and what the sender is asking the other side to do.

A routine request says, in effect, "here is the work we did under the contract, please pay it." It assumes both sides agree the work happened and the number is right. It is an administrative step in a process that both parties expect.

A claim says something different. It says, "we believe we are owed this, and we are asking for a decision." It usually arises when the other side has said no, has said the amount is wrong, or has simply not acted. Once a claim is in play, the paperwork, deadlines, and certification requirements can matter far more than the work itself.

The same stack of paper can land on either side of this line. Requests with identical totals can have very different status, because one was agreed in a meeting last week and the other was rejected by email this morning. The paperwork does not tell you which is which. The file notes do, and so does the memory of whoever spoke with the reviewer. That is why the status of each request should be recorded at the time it is sent, not reconstructed months later when someone asks.

The useful question for an office lead is simple: on the day I send this, is the amount in dispute? If the honest answer is no, you are probably sending a routine request. If the answer is "not yet, but they have pushed back," the situation is changing, and the next message you send may carry different weight.

The federal disputes clause in the Federal Acquisition Regulation, 52.233-1 draws this same line in plain terms. It says that a voucher, invoice, or other routine request for payment that is not in dispute when submitted is not a claim under the federal contract disputes statute. That sentence is the core of the whole topic. The status depends on whether the request is in dispute when it is submitted, not on how angry anyone sounds.

Path one: the request that stays routine

On a healthy job, a payment request moves through a sequence that everyone understands. The field crew records quantities. The office prepares the request with backup. The reviewer checks it against the schedule of values, the measured quantities, and any change orders. The owner or prime approves it, and the money moves.

The routine path has a few features that keep it routine.

The amount is agreed before or at submission. If you already talked with the reviewer about a line item and both sides understood the number, the request is not in dispute. If you are sending a number the reviewer has never seen, expect questions, and treat the first round of questions as normal review rather than a fight.

The request follows the process in the contract. Many public and contract jobs have a defined cycle for submitting, reviewing, and paying. Using the right form, the right cutoff, and the right backup keeps the request inside the process where it belongs.

The sender stays on schedule. A request that goes out on time and gets handled on time never needs a second look. Delays are where routine requests start to drift, which is why a calendar matters as much as the math.

The language stays factual. "Attached is our request for work completed through the end of the month, following the schedule of values" is routine. Language that argues about who caused a problem, or threatens consequences, is not routine. It signals that the sender has moved into a different category, even if the money is the same.

Path two: the request that becomes a claim

The most common triggers are simple to name, even if they are frustrating to live through.

The reviewer disputes the amount. They say the quantity is too high, the rate is wrong, or a line should not be billed. Once the disagreement is on the table about liability or amount, the request is no longer only routine. The federal clause puts it this way: a submission may be converted to a claim, by complying with the clause's submission and certification requirements, if it is disputed as to liability or amount, or not acted upon in a reasonable time.

The request sits too long. Silence is also a position. Under the same federal clause, a submission left unacted on for a reasonable time can become a claim, but only by complying with the clause's submission and certification requirements. That means a request that just sits in someone's inbox can turn into a dispute by drifting, not only by anyone saying no.

The sender adds a demand. Sometimes a firm sends a routine request and then, when the reviewer pushes back, writes a letter asserting entitlement to more money, interest, or extra time. That letter may be a claim on its own, depending on its content and the contract. A firm that wants to keep a request routine should avoid adding new demands to it without thinking through the consequences.

The work was never in the schedule. This is where public work has its own quirks. A change or extra that was never documented, approved, or included in the regular estimate may not fit cleanly into the normal request, and the owner may say so. The Texas Department of Transportation's estimating guidance describes one such route: "The purpose of a Progress Supplemental Estimate is to pay for work that was not included or missed in the regular monthly progress estimate." That is a reminder that work outside the normal cycle often needs its own paper trail.

A middle ground often shows up before anyone uses the word "claim." The reviewer agrees to part of the request and holds back the rest, or the owner approves the quantities but questions the rate. This is a partial dispute, and it is common. The routine part of the request can usually still be paid on its normal cycle, while the disputed line gets its own note in the file. Splitting the request this way keeps the undisputed money moving and makes the disagreement narrower and easier to resolve. Office leads should ask for the reviewer's objection in writing, line by line, so the file shows exactly which amounts are still open.

The key point for office leads is that the change is often gradual. Nobody sends a dispute on a single bad day. It starts with a question from the reviewer, then a line item gets struck, and the request still sits unpaid the following month. By the time someone uses the word "claim," the file may already have most of the facts a claim would need.

Illustrative example: one request, two paths

Suppose a firm sends its monthly request on the owner's cutoff date and the reviewer agrees to every line. That request stays routine and is paid on the normal cycle. Now suppose the reviewer strikes one line. That line is in dispute, so the office writes a file note, asks for the objection in writing, and keeps the rest on its cycle.

Where the dollar amount changes the rules

On federal contracts that include the disputes clause, the dollar amount of a demand matters a great deal. The clause sets different rules for different sizes of claims.

For a written demand seeking payment of more than $100,000, the clause says the demand is not a claim under the statute until it is certified. That is a significant line. A firm that sends a large written demand without the certification the clause requires has not yet made the kind of claim the statute covers, and the paperwork is incomplete. The clause also requires the contractor to provide the specified certification when submitting any claim exceeding $100,000, and the disputes clause sets out the details.

For claims of $100,000 or less, the clause gives the contractor a specific tool. If the contractor requests a decision in writing, the contracting officer must render a decision within 60 days of the request. For certified claims over $100,000, the contracting officer must, within 60 days, either decide the claim or notify the contractor of the date by which the decision will be made. Both timing rules are in the same clause.

Those numbers are useful because they show that a dispute has a clock. But they only apply where the clause applies. A subcontractor on a private job, or a firm working under a state or local contract, should not assume the same thresholds or timing. The point to take away is structural: large demands face certification rules, and requests for decisions can carry deadlines.

The clause also sets a time limit on bringing a claim forward. A claim by the contractor must be made in writing and, unless the contract says otherwise, submitted within 6 years after the claim accrues. A window of six years is long, and it is easy to forget the start point. An office should keep the records anyway, because the clock is only one part of a dispute. Documents go missing and people leave.

Finally, the clause opens with a statement that matters for every firm reading this: the contract is subject to the federal contract disputes statute, 41 U.S.C. chapter 71. If your contract says that, the federal rules govern the disputes process.

Public work runs on a calendar

Public agencies usually pay on their own cycles, and those cycles shape when a request turns into a problem. The Texas Department of Transportation construction manual gives one example. It says that the agency's accounts payable group determines and notifies the districts by email of the monthly estimate deadline for construction projects, as set out in the TxDOT estimates section. That means the monthly estimate has a fixed deadline set by the agency, and a firm that misses it may see its work roll into the next cycle.

For a field-service firm, that means the calendar is not something you guess at. The owner or prime may have a monthly estimate cutoff. Office leads should find out the cutoff for every active public job, write it down, and check it against the crew's schedule. For more on timing rules, see Progress payment applications: 3 timing rules to check.

Those cutoffs also explain why supplemental requests exist. If work was missed in the regular estimate, the process has a separate path for it. The TxDOT manual describes that path as a Progress Supplemental Estimate. Using the right path matters. Sending missed work through the regular request can create confusion. Sending it through a supplemental path, with clear backup, keeps it visible.

A simple way to keep this under control is to build a cutoff sheet for each public job. List the owner's submission date, the date the reviewer is expected to respond, the name and email of the person who sends the cycle notices, and the place where supplemental requests go. Update it whenever the owner sends a new notice, and attach the notice itself to the sheet. When a question comes in, the office can check the sheet instead of relying on memory, and the crew can see at a glance whether work needs to go into this cycle or the next one.

The general lesson is that some disputes on public work can begin with timing rather than money. A request that arrives after the cutoff, or work that was never put in the right estimate, can look like a dispute to the reviewer even when the sender thinks it is routine.

A practical checklist for the office

Here is what a small firm can do this month without a lawyer, starting with the next request that goes out.

Mark every request as routine or not before it leaves the office. Write a short note in the file: "Amount agreed with reviewer on [date]" or "Amount disputed; reviewer raised [issue]." This is the single most useful habit. It forces the question of whether the request is in dispute, and it leaves a record.

Keep a calendar of each owner's submission cutoffs, review periods, and any stated deadlines. Put the dates in the same place the crew can see them. If the owner notifies you of a deadline by email, file that email with the job. For a closeout checklist, see Job file closeout: 6 steps to track deadlines.

Respond to questions quickly. A reviewer's question is not yet a dispute. An unanswered question becomes one faster than most people expect. Answer with backup, not argument, and note when you answered.

Track any request that has sat without action. If a request has not been acted on in a reasonable time, that fact belongs in the file. Send a dated, factual follow-up that asks for a status and, where the contract allows, a decision date.

Keep extra work separate and documented. Changes, extras, and missed quantities should get their own approvals and their own backup. If the owner has a supplemental process, use it rather than folding the work into a routine request.

Read the disputes section of your contract before you need it. Know whether it cites a statute, what it says about certification, whether it sets deadlines, and who receives written notices.

Get advice before you send anything large or hostile. A written demand that asserts entitlement to significant money, or that threatens a claim, is the point where a short conversation with a lawyer who knows public contracts is cheap compared to the cost of getting the form or the timing wrong.

Keep requests routine when you can

The best outcome is a request that never becomes a claim. That usually comes from three habits: agreeing the number before it goes out, following the owner's cycle, and dealing with questions while they are still questions.

When a request does start to turn, slow down. Ask what specifically is in dispute. Separate the amount from the liability. Check whether the work was in the regular estimate or should go through a supplemental path. Often the disagreement is narrower than the first email suggested, and a corrected request resolves it.

If the dispute is real, you still have a process to follow. The paperwork, deadlines, and certification rules are there so both sides know where they stand. Treat them as a map rather than a trap.

Your next step: before the next request leaves the office, write one line in its file saying whether the amount is agreed or disputed.

Frequently asked questions

Is a routine request ever a claim?

No. Under the federal clause, a voucher, invoice, or other routine request that is not in dispute when submitted is not a claim.

Does a claim over $100,000 need certification?

Yes. Under the federal clause, a written demand seeking more than $100,000 is not a claim until it is certified, and the contractor must provide that certification when submitting it.

Sources

More field guides