Federal agencies must return a defective payment request within 7 days of receiving it, with a statement identifying each defect. If you sell to a federal agency, a payment request that comes back can feel like a dead end. It usually is not. A defective payment request is one the agency returns to you with a statement of what is wrong, and that statement tells you what to fix before you send the request again.
For small-business owners and bookkeepers, the most important detail is timing, because the window starts when the agency receives the request, not when you sent it.
This post covers the 7-day rule, what a return notice should contain, how to handle a return step by step, and where the federal rule stops applying. Many of your customers will not be federal agencies, so that last part matters.
Key takeaways
- Note the date the agency received the request, since the 7-day window starts there.
- Expect a statement that names each defect, and ask about anything vague.
- Check each listed defect against the contract or purchase order before you resubmit.
- Confirm which rule set applies to each customer.
What the 7-day rule says
The U.S. Department of the Treasury's Prompt Payment Act guidance for heads of government departments and agencies sets out the core requirement in one sentence. A defective payment request must be returned to the vendor within 7 days after the agency receives it, with a statement identifying the defect or defects.
Two parts of that sentence matter most. The first is the deadline. The 7 days run from the day the agency receives the request, so the agency's intake date is the starting point. The second is the statement. A return that says only "rejected," or that hands the request back with no explanation, does not give you what the rule is meant to provide. You should be able to read the statement and know exactly what to change.
Do not confuse the return window with the payment date. A separate provision decides the due date, and it reads: "The payment due date for invoices shall be determined in accordance with Rebates (refer Section 5065)." A fast return helps you fix a problem, but it does not by itself set when the money arrives.
The rule is short, so it helps to be precise about its limits. It sets the deadline for returning a defective request and requires the reasons to be stated. It does not describe how an agency decides that a request is defective, and it does not say how soon you will be paid after you resubmit. Those points depend on the agency's own procedures, the terms of your contract, and the wider framework of payment rules. If you have a question beyond the return itself, get the answer in writing. For how payment clauses fit a contract, see federal prompt payment clauses.
Who the rule covers
The rule is written for federal agencies. Its full title is Chapter 5000 Prompt Payment Act (PPA) Guidance for Heads of Government Departments, Agencies, and Others Concerned. If the customer that sent the request back is a federal department or agency, plan around the 7-day window.
Figuring out whether a customer is federal is not always obvious. A name that sounds official can belong to a state office, and a contractor can serve a federal agency through a prime contractor. Check the contract or order for the agency that will pay, and look at the address on the purchase order. If you still cannot tell, ask the customer in writing which rule set applies. Until you know, plan around the faster timeline, because it is the one you can meet safely.
Many small businesses sell to customers that are not federal. State agencies, cities, counties, school districts, and private companies all make payment requests of their own, and whether this federal rule reaches them depends on its terms, so check rather than assume. Their deadlines come from their own policies, from state or local rules where those apply, and from the terms in your signed agreement or purchase order.
This creates a practical problem for bookkeepers. A single receivables list can hold federal and private customers side by side. The federal rule sets a 7-day window for the agency's return, while private customers' deadlines come from their own agreements or purchase orders, which may be shorter or longer. Mark each customer with the rule set that applies to them, so that when a return arrives, you can see at a glance how quickly you need to act.
| Customer type | Where the deadline comes from | What to do first |
|---|---|---|
| Federal department or agency | The 7-day return rule | Expect the return within 7 days after the agency receives the request, then correct and resubmit promptly. |
| State agency, city, or county | Its own policies and state or local rules | Confirm the deadline in writing |
| School district or hospital | Its own policies and your agreement | Read the purchase order terms |
| Private company | The signed agreement or purchase order | Follow the terms as written |
What a return notice should tell you
Because the rule requires a statement of defects, a useful return notice has a few parts. Look for:
- The request it refers to, including the invoice number, the date you sent it, and any contract or purchase order number.
- A list of each defect, stated clearly enough that you can find the matching item in your files.
- The date the agency returned the request.
- A contact name, office, and way to reach that person with questions.
If any of these are missing, ask for them before you change anything. A return with no defect list, or one that names only a vague category such as "documentation issue," gives you very little to work with. Reply politely and ask which document the agency means, which line is affected, and what the agency needs to see.
A good notice also names the requirement behind each defect, such as the document type or clause it relies on. When the notice gives you the requirement, you can check your request against the requirement itself instead of guessing.
Read the whole notice before you act. Some returns list several defects, and it is easy to fix the first one and resubmit with the others still wrong.
Common defects and where to look
The rule does not list every possible defect, and each agency has its own requirements. Still, the groups below are a useful place to start. Errors can come from comparing a request against an old invoice instead of the contract or order it should match.
| Defect group | Where to look | Common cause |
|---|---|---|
| Identifying information | Contract, purchase order, office code, billing address | Copying an old invoice to start a new one |
| Math and totals | Each line, the subtotals, and the tax and fee terms | A spreadsheet formula that no longer matches the terms |
| Items and services | The order and the delivery records | Quantities that differ between order and invoice |
| Supporting documents | The agency's list of required backup | Proof of delivery or timesheets left out |
| Dates and periods | The work period in the contract | A billing period outside the work period |
| Recipient | The agency's instructions | Sent to the wrong office or person |
Identifying errors are easy to make when you reuse an old invoice, so compare each identifier against the original order or contract rather than the previous invoice. Math errors hide easily in spreadsheets. A formula can carry an old rate and produce a wrong total with no visible error, so recalculate rather than trusting the cell.
Supporting documents deserve special attention. Agencies often ask for proof of delivery, timesheets, or other backup, and that backup is easy to forget when a job wraps up in a hurry. Build it into your process when the work is done, so the invoice and its support go out together. When the agency lists specific attachments, match your package to that list line for line.
Confirm the correct person before you send anything, because a request sent to the wrong desk can look like a defect even when the invoice is right.
Why the clock matters to you
The 7-day window works in your favor. A fast return lets you correct the request while the work is still fresh. A defect that goes unnoticed for weeks is much harder to explain later, and you might not learn about it until you call to ask why payment has not arrived.
Cash flow is the other reason. Many small firms plan payroll and supplier bills around expected incoming payments. A return that sits for weeks can push those plans off track, while a quick correction keeps the payment date close to what you planned. Build the possibility of a return into your cash forecast, so a returned request is a delay you expected rather than a surprise.
Timing can also affect money in both directions. A separate provision of the same Treasury guidance covers amounts a vendor has received but has not earned. For those, interest is to "be computed on the basis of the average bond equivalent rates of 91-day Treasury bills auctioned at the most recent auction of such bills prior to the date the vendor received the unearned amount." The reference date is when the vendor received the amount, not when the request was sent.
A separate Federal Acquisition Regulation clause shows how timing matters in federal payments too. The clause for fixed-price architect-engineer contracts says that, when computing any interest penalty owed the contractor, the government will take into account whether it notifies the contractor of an improper invoice in an untimely manner. See FAR clause 52.232-26. That clause covers a specific contract type, so do not assume it governs your contract. It does show why a late notice about a defective invoice can change the amounts owed.
Illustrative example: correcting a returned request
Imagine a small consulting firm that bills a federal office for several weeks of work under an existing contract. The agency returns the request within the 7-day window. The notice says two things: the purchase order number on the invoice does not match the number on file, and the timesheet for one week is missing.
Here, the bookkeeper pulls the purchase order number from the signed contract file rather than from memory or an old invoice. They attach the missing timesheet and confirm that the hours on the invoice match the timesheets. They check the total, then send the corrected request to the office and contact named in the notice. A reminder set for a few days later covers the follow-up.
The return is a paperwork correction, and the fix takes an afternoon rather than a negotiation.
What a return does not mean
A returned request is not a rejection of the work. It does not automatically mean the amount is wrong, the work was not done, or the agency refuses to pay. It means the request, as submitted, does not meet the agency's requirements. A missing number or an omitted attachment can be one cause.
A return is also not a finding of fault.
Treat a return as a routine correction step, not a crisis.
When you disagree with a defect
Sometimes you will believe a listed defect is wrong. The agency may have misread a purchase order, or it may expect a document that does not apply to your contract. In that case, do not simply resubmit the same request and hope for a different result. Reply in writing, quote the line you disagree with, and explain why you believe the request was correct. Attach the document that supports your position.
Keep the tone factual. The goal is to resolve a question, not to win an argument. If the disagreement cannot be settled with the contact, ask whether a supervisor or a designated office handles returned requests.
A step-by-step routine for returns
When a request comes back, a simple routine keeps the work organized and the deadlines visible.
- Read the notice and list every defect. Mark the invoice as returned, not as paid or overdue, so it stays on your list.
- Ask about anything unclear. If an item is vague, contact the agency's named contact and ask for specifics. Get the answer in writing.
- Gather the source documents. Pull the contract or purchase order, your delivery or time records, and the original request. Check each defect against these documents.
- Correct each listed defect. While the document is open, scan the rest of it, but leave correct items alone. Unnecessary changes raise new questions.
- Check the correction against the defect list. If a second person is available, have them review the revised request. A reviewer who did not prepare the original often spots leftover errors quickly.
- Resubmit through the right channel. Send the request to the office and contact the agency specified.
- Follow up on a schedule. If you do not hear back within a reasonable time, contact the agency to confirm it arrived and what comes next.
Keep records that make returns easy to handle
Keep one folder or record for each payment request that includes:
- The original request as sent, with the date it was sent.
- The return notice, with the date it arrived.
- Notes on every phone call or meeting about the return, including the names of the people involved.
- The corrected request and the date you resubmitted it.
- Any confirmation that the agency received the resubmission.
See electronic invoice records for more.
For amounts like the ones described above, the date the vendor received the money matters, so keep those dates accurate in every record.
Bookkeepers should also add a return status to their workflow. A simple "returned, awaiting correction" label shows which requests need action this week. Review that list at least once a week, and do not let returned requests sit alongside paid invoices where they can be forgotten.
Working with private customers
For customers that are not federal agencies, the terms of your signed agreement or purchase order usually govern. Look for language that describes how invoices should be prepared, what documents must be attached, how a request can be returned, and how quickly the customer will respond. If the agreement is silent on any of these points, ask the customer in writing how they want returns handled.
Private customers may also use different systems or invoice recipients than the person who ordered the work.
If a private customer goes quiet after a return, the same routine applies. Follow up on the schedule you set, use the contact named in the original notice, and keep your messages short and factual. Silence is not a rejection, but it does need a response from you, because an unanswered return can stall the entire payment.
Final checklist
Before you send any payment request, confirm that:
- Every identifier matches the contract or purchase order on file.
- Each line item matches the order and the delivery or time records.
- The math has been recalculated and the totals are correct.
- Every supporting document the customer asked for is attached.
- The request is going to the recipient named in the instructions.
See also the invoice approval checklist.
The bottom line
For federal agencies, the rule sets a firm 7-day deadline to return a defective payment request, and it requires a statement identifying the defects. Use that statement to fix the request precisely, check the correction carefully, and resubmit through the channel the agency specified.
For private customers, look to your own agreement rather than the federal rule. Either way, a quick, organized response is the best way to get the request paid.
Next step today: check one returned or pending request against the contract or purchase order on file.
Frequently asked questions
How long does a federal agency have to return a defective request?
A federal agency must return it within 7 days of receiving it, with a statement identifying the defect or defects.
Does the 7-day rule apply to private customers?
Not necessarily, so check your signed agreement or purchase order.