Government Contractor Invoice Requirements: FAR Proper Invoice Guide

Every federal contractor learns the same lesson sooner or later: the government does not pay against invoices that fail to meet its precise regulatory definition of "proper." Unlike commercial transactions where invoice formats are negotiated between buyer and seller, government contract invoicing is governed by the Federal Acquisition Regulation (FAR), and for defense work, the Defense Federal Acquisition Regulation Supplement (DFARS). These are not guidelines or best practices. They are binding requirements, and compliance is the prerequisite for getting paid.

Under FAR 32.905, a proper invoice must include specific elements: the contractor's name and address, the invoice date, the contract number, a description of the supplies or services delivered, quantities and unit prices, shipping and payment terms, and the name and address of the official designated to receive payment. Miss any one of these fields, and the contracting agency is required to return the invoice within 7 days. When that happens, the 30-day payment clock under the Prompt Payment Act resets entirely, meaning the contractor waits not from the original submission date but from whenever the corrected invoice is resubmitted and accepted.

That distinction between "proper" and "improper" carries real financial weight. The Prompt Payment Act obligates federal agencies to pay a proper invoice within 30 days (with shorter timelines for construction and perishable goods contracts). But this obligation only activates upon receipt of a proper invoice. An invoice that looks complete but omits a single required data element is not proper under the regulation, and no payment timeline is triggered. For contractors managing cash flow against payroll, materials, and subcontractor obligations, a preventable rejection can cascade into weeks of delayed revenue.

The scale of federal contracting makes these requirements matter at every level. According to the U.S. Small Business Administration, in fiscal year 2024 the federal government awarded $183.27 billion in prime contracts to small businesses alone, representing 28.78% of all federal contracting dollars. Each of those contracts generates invoices that must clear the same FAR compliance bar. Multiply small formatting or data gaps across thousands of contractors submitting invoices monthly, and the aggregate impact on payment processing becomes significant for both contractors and agency finance offices.

Where commercial invoicing relies on whatever terms two parties agree to, federal government invoice requirements layer regulatory specificity on top of contractual terms. Your contract will reference FAR clauses that dictate not just what appears on the invoice but how and where you submit it, what supporting documentation must accompany it, and which electronic systems you are required to use. Defense contracts add DFARS provisions that go further still, requiring data elements that civilian agency invoices do not.

This guide consolidates the full scope of government contractor invoice requirements into a single practitioner reference, structured as a desk resource you can return to throughout the life of a contract. It covers the FAR 32.905 field-by-field breakdown, the Prompt Payment Act timelines that govern when agencies must pay, the two primary electronic submission systems (the Invoice Processing Platform for civilian agencies and Wide Area Workflow for defense contracts), DFARS additions specific to defense work, how subcontractor invoicing flows through prime contractors, SAM.gov registration prerequisites that must be in place before your first invoice, and a practical checklist for preventing the most common invoice rejections.

FAR 32.905 Proper Invoice Requirements: A Field-by-Field Breakdown

Federal Acquisition Regulation (FAR) 32.905(b) defines exactly what constitutes a "proper invoice" for government contract payments. Miss a single required element and the government's payment office will reject your invoice, resetting the payment clock entirely. Below is every required field, what it means in practice, and the nuances that trip up contractors.

Before working through the FAR-specific requirements, it helps to have a solid grasp of understanding standard invoice fields and structure. The government builds on these general concepts but adds regulatory precision that leaves no room for ambiguity.

1. Contractor Name and Address

Your company name and address must appear exactly as shown in the contract. This is not your current business address or the address on your letterhead if either has changed since contract award. If your company has relocated or changed its legal name, you need a contract modification before your invoices will reflect the new information. Even minor discrepancies (abbreviating "Street" to "St." when the contract spells it out, or using a DBA name instead of the legal entity name) can trigger a rejection.

2. Invoice Date

The date you prepare or submit the invoice. This date matters more than most contractors realize: under the Prompt Payment Act, the government's payment clock starts from either the invoice receipt date or the acceptance date, depending on the contract terms. Use the actual date of submission, not the date you started drafting the invoice or the end of the billing period. For electronic submissions through IPP or WAWF, the system typically records this automatically.

3. Invoice Number

A unique sequential identifier you assign to each invoice. The government uses this number to track your payment through its processing systems, and duplicates will cause confusion and delays. Most contractors use a numbering scheme that incorporates the contract number or project code for easy cross-referencing, such as "W52P1J-24-C-0012-INV-003." Whatever scheme you choose, keep it consistent across the life of the contract. Never reuse an invoice number, even for corrected resubmissions (append a revision indicator like "-R1" instead).

4. Contract Number, Task Order Number, or Delivery Order Number

The specific contract instrument under which you performed the work. For straightforward firm-fixed-price contracts, this is simply the contract number. For indefinite-delivery/indefinite-quantity (IDIQ) contracts, you must reference the task order or delivery order number, not just the parent contract number. If your work spans multiple orders, submit separate invoices for each. The contract number format follows federal conventions (e.g., FA8732-25-C-0001 for an Air Force contract), and you should copy it character for character from your contract document.

5. Description of Supplies Delivered or Services Performed

This field requires enough detail for the contracting officer's representative to verify what you are billing for. For supplies and products, describe each item delivered, referencing the contract line item number (CLIN) where applicable. For services, include the period of performance covered by the invoice (e.g., "Program management services for the period 1 January 2026 through 31 January 2026"). Time-and-materials contracts demand particular attention here: break down labor categories, hours worked per category, and any materials or travel costs as separate entries. Vague descriptions like "consulting services rendered" will be rejected.

6. Quantity, Unit of Measure, Unit Price, and Extended Price

Every line item needs all four components:

Quantity: The number of units delivered or hours worked
Unit of measure: Each, hours, lots, months, or whatever the contract specifies
Unit price: The per-unit rate from your contract
Extended price: Quantity multiplied by unit price

These figures must match your contract's pricing schedule exactly. If your contract prices Item 0001 at $47.50 per unit, your invoice must show $47.50, not $47.49 or a rounded figure. For cost-reimbursement contracts, the breakdown becomes more complex, requiring separation of direct costs, indirect rates, and fee calculations that align with your approved accounting system.

7. Shipping Number and Date of Shipment

This requirement applies primarily to supplies and physical deliverables, not services. Include the bill of lading number, shipping date, and weight of shipment. If you shipped via a government bill of lading (GBL), reference that number. For partial shipments against a single line item, clearly indicate which shipment this invoice covers and the cumulative quantities shipped to date. Service contractors can generally note "N/A" for this field, though some contracts with deliverable work products may require evidence of delivery (such as a transmittal letter reference).

8. Terms of Any Discount for Prompt Payment

If you offer the government a discount for paying early (e.g., "2/10, Net 30" meaning a 2% discount if paid within 10 days), state those terms on every invoice. If you do not offer a discount, you still need to address this field, typically by stating "Net 30" or "No discount offered." Government payment offices look for this field specifically, and its absence can flag an invoice as defective even when no discount applies.

9. Name and Address of Payment Recipient

The name and address of the official or office to whom payment should be sent. This must match the information in the contract or, if payment has been assigned to a third party (such as a bank or factor under the Assignment of Claims Act), the current assignment records on file. If your payment destination differs from your contractor address in field #1, both must be present and clearly distinguished. Changes to payment address require formal notification to the contracting officer and the paying office.

10. Point of Contact for Defective Invoices

Provide the name, title, and phone number of the person on your team who can respond if the government identifies a problem with the invoice. This should be someone with direct knowledge of the billing, not a general company receptionist or automated phone system. When the payment office finds a deficiency, they contact this person to resolve it. A responsive, knowledgeable contact here can mean the difference between a quick correction and weeks of back-and-forth delays.

11. Taxpayer Identification Number (TIN)

Your company's TIN (typically the Employer Identification Number, or EIN) must appear on the invoice unless the contract already requires it elsewhere, such as through the SAM.gov registration or a specific contract clause. In practice, most contractors include the TIN on every invoice regardless, since its presence never causes a rejection and its absence sometimes does. This number must match your SAM.gov registration and your W-9 on file.

12. Electronic Funds Transfer (EFT) Banking Information

FAR 32.7 requires that most government payments be made via EFT. Your invoice must either include your EFT banking information (bank name, routing number, and account number) or reference where this information is already on file, typically through your SAM.gov registration. Do not include full banking details on the face of the invoice if your contract directs you to maintain this information in SAM.gov. The invoice should note that EFT information is on file in SAM and consistent with contract records.

Beyond the Minimum: Contract-Specific Additions

These twelve elements are the minimum requirements under FAR 32.905(b). Individual contracts frequently add requirements through specific clauses. Common additions include:

DCAA-auditable cost breakdowns for cost-reimbursement contracts
Progress milestones or completion percentages for progress-based payments
Separate identification of materials, labor, and other direct costs for time-and-materials contracts
Certifications required by specific agency supplements (DFARS, GSAM, etc.)

Always review your contract's Section G (Contract Administration Data) and any referenced clauses for additional invoice requirements beyond this baseline. A proper invoice under FAR 32.905 that omits a contract-specific field is still defective under that particular contract.

How the Prompt Payment Act Governs Government Invoice Timelines

The Prompt Payment Act establishes the federal government's legal obligation to pay contractors on time and creates enforceable consequences when it fails to do so. For contractors, understanding this law is essential because it directly ties invoice compliance to cash flow. A properly submitted invoice triggers the government's payment clock. An improper one means that clock never starts.

The Payment Clock: 30 Days From Receipt

The core mechanism is straightforward. Once a federal agency receives a proper invoice, it must pay within 30 days of the invoice receipt date or the date goods and services are accepted, whichever is later. Two categories of contracts operate on shorter timelines:

Meat, dairy, and perishable agricultural commodities: 7 days
Construction contracts: 14 days

For most government contractors, the 30-day standard applies. The clock begins only when the agency has both a proper invoice in hand and has accepted the deliverables or services described in that invoice. If acceptance happens before the invoice arrives, the invoice date controls. If the invoice arrives first, the acceptance date controls.

The 7-Day Rejection Rule

When an agency receives an invoice that fails to meet proper invoice requirements under FAR 32.905, it must act quickly. The Prompt Payment Act requires agencies to return a deficient invoice within 7 days of receipt, accompanied by a written statement identifying what is wrong or what information is missing.

This 7-day window matters for two reasons. First, it prevents agencies from sitting on flawed invoices indefinitely without notifying the contractor. Second, it defines when the payment clock reset occurs. If an agency holds a deficient invoice for 20 days before returning it, the contractor has lost nearly three weeks with no recourse, and the payment obligation has not yet begun.

How a Single Missing Field Resets the Clock

The payment clock reset is where Prompt Payment Act invoice requirements have the most direct impact on contractor cash flow. When an agency returns an improper invoice and the contractor submits a corrected version, the 30-day clock starts fresh from the date the agency receives the corrected proper invoice. It does not resume from where it left off.

Consider the practical effect. A contractor submits an invoice on March 1 but omits the contract line item number. The agency returns it on March 7. The contractor corrects the invoice and resubmits on March 14. The government's 30-day payment obligation now runs from March 14, not March 1. What should have been an April 1 payment becomes an April 13 payment at the earliest. If the corrected invoice still contains an error, the cycle repeats. A single missing field on the original submission can delay payment by weeks or months depending on how many correction cycles are needed.

This is why the proper invoice requirements outlined in FAR 32.905 are not administrative formalities. They are the precise trigger that starts the government's payment obligation. Every field serves a verification purpose, and every omission is grounds for rejection and clock reset.

Interest Penalties for Late Government Payments

When the government fails to pay a proper invoice within the required timeframe, contractors are entitled to interest on the overdue amount. The interest rate is set by the Department of the Treasury and is published semiannually based on the current value of funds to the Treasury.

Two details make this provision particularly notable:

Contractors do not need to request interest. Federal agencies are required to calculate and pay interest automatically whenever they miss a payment deadline on a proper invoice. There is no claim form and no dispute process needed for the base interest entitlement.
Interest accrues from the day after the payment due date through the date of actual payment. For a proper invoice received on March 1 under the standard 30-day timeline, interest begins accruing on April 1 if payment has not been issued.

While automatic interest payments provide some protection, they are a remedy for agency delay on proper invoices, not a substitute for submitting compliant invoices in the first place. If the invoice was never "proper" under FAR 32.905, no payment deadline was ever triggered, and no interest obligation exists.

Scope and Applicability

The Prompt Payment Act applies to federal executive branch agencies. Contractors working with legislative branch entities (such as the Architect of the Capitol or the Government Accountability Office) or judicial branch agencies operate under separate payment rules that may differ in timelines and procedures. Contractors with contracts spanning multiple branches should verify which payment framework governs each agreement.

For the vast majority of government contractors, the executive branch rules define the payment relationship. Meeting government invoice payment requirements under FAR 32.905 is the single most controllable factor in determining how quickly payment arrives. The Prompt Payment Act gives contractors a legal right to timely payment, but that right activates only when the invoice itself passes muster.

Electronic Submission: IPP for Civilian Agencies vs. WAWF for Defense

The federal government requires electronic invoicing for the vast majority of contracts. Which system you use depends on the contracting agency, and if you hold both civilian and defense contracts, you will need to work within both platforms. The two primary systems are the Invoice Processing Platform (IPP) for civilian agencies and Wide Area Workflow (WAWF) for defense contracts.

Invoice Processing Platform (IPP) for Civilian Agencies

IPP is operated by the Bureau of the Fiscal Service, a division of the Department of the Treasury. It serves as the government's primary electronic invoicing system for non-defense federal contracts.

Registration and setup. Before you can submit through IPP, you need an active SAM.gov registration with current banking information. From there, you register at IPP.gov, where the system links your vendor profile to your SAM.gov data. Your contracting officer or contracting officer's representative (COR) must also be set up on the platform to receive and review your submissions.

Submitting invoices. Once registered, you create invoices directly within the IPP portal by entering header data (contract number, invoice number, dates, amounts) and attaching any required supporting documentation. IPP supports several document types beyond standard invoices, including receiving reports and progress payment requests. You can also submit cost-type vouchers for cost-reimbursement contracts.

Approval workflow. After submission, the invoice routes to the designated government reviewer, typically the COR or contracting officer. They review the invoice against contract terms, verify receipt and acceptance of goods or services, and either approve or reject it within the system. Once approved, IPP transmits payment data to the Treasury for disbursement. You can track your invoice status through the portal at each stage of this process.

Wide Area Workflow (WAWF) for Defense Contracts

WAWF is operated by the Defense Finance and Accounting Service (DFAS) and handles the full invoice lifecycle for Department of Defense contracts, from submission through receipt, acceptance, and payment processing.

Registration and access. WAWF requires either a DoD-issued Common Access Card (CAC) or a username and password obtained through the WAWF portal. You must also have an active SAM.gov registration. Your CAGE code (Commercial and Government Entity code, assigned by the Defense Logistics Agency) and UEI number link your account to your contracts. Getting CAC-based access can take time, so plan for this well before your first invoice is due.

Document types and submission. WAWF supports multiple document types, and selecting the correct one matters. The most common are:

Invoice only — used when the government handles receiving and acceptance separately
Receiving report only — documents delivery of goods
Combo (invoice and receiving report) — the most frequently used format, combining both functions into a single submission
Cost voucher — for cost-reimbursement contracts
Progress payment — for approved progress billing milestones

When creating a document, you enter the contract number, delivery order number, CLIN/SLIN data, quantities, amounts, and shipping information. WAWF validates entries against contract data already loaded in the system, which catches many errors before submission.

Acceptance workflow. WAWF routes submissions through a multi-step acceptance chain. The inspector (often the COR or a designated quality assurance representative) verifies receipt and inspects deliverables. The acceptor then formally accepts the goods or services. After acceptance, WAWF transmits the approved invoice to DFAS for payment processing. This chain of custody creates a complete audit trail from submission to payment.

Key Differences Between IPP and WAWF

Feature	IPP (Civilian)	WAWF (Defense)
Operated by	Bureau of the Fiscal Service (Treasury)	DFAS (DoD)
Access method	Username/password via IPP.gov	CAC or username/password
Primary users	Civilian agency contractors	DoD contractors
Receiving/acceptance	Single reviewer (COR or CO)	Multi-step (inspector then acceptor)
Contract data validation	Manual entry	Validates against loaded contract data
Payment processing	Routed to Treasury	Routed to DFAS
Governing clause	Agency-specific	DFARS 252.232-7006

Processing timelines also differ. Civilian agencies under the Prompt Payment Act generally have a 30-day payment window from receipt of a proper invoice. DFAS payment timelines vary by contract type but follow the same statutory framework, though the multi-step acceptance process in WAWF can add time before the payment clock starts.

Legacy exceptions. A small number of contracts, particularly older indefinite-delivery contracts or contracts with certain small agencies, may still permit paper invoicing or use agency-specific portals. Always check your contract's invoicing clause for the required submission method rather than assuming either IPP or WAWF applies.

Practical Tips for Both Systems

Check the contract first. Your contract will specify the electronic invoicing requirement. For defense contracts, look for DFARS 252.232-7006, which mandates WAWF. Civilian contracts reference IPP in the payment instructions or a specific FAR clause. The contract may also name a specific point of contact for invoicing issues.

Common errors that cause rejection:

Mismatched contract or delivery order numbers (even a single transposed digit)
Selecting the wrong document type in WAWF
Submitting to the wrong office code or DoDAAC in WAWF
Missing or incorrect CLIN/SLIN references
Invoice amounts that exceed the funded or obligated amount on the contract line item
Omitting required attachments or supporting documentation

Monitoring invoice status. Both systems let you track where your invoice sits in the approval pipeline. In IPP, check the invoice dashboard for status updates. In WAWF, use the document history view to see whether your submission has been received, is pending inspection, has been accepted, or has been forwarded to DFAS for payment. Set up email notifications in both systems so you are alerted to rejections or requests for additional information promptly.

If an invoice is rejected, read the rejection reason carefully. Both systems allow the reviewer to include comments explaining what needs correction. Fix the specific issue, then resubmit as a new invoice rather than attempting to modify the rejected record. In WAWF, a rejected document must be corrected and resubmitted as a new transaction. Keep your original invoice number sequence consistent so the government can track the resubmission against the original.

DFARS Additions: Extra Requirements for Defense Contract Invoices

Defense contracts operate under a dual regulatory framework. Every FAR 32.905 proper invoice requirement covered earlier still applies, but the Defense Federal Acquisition Regulation Supplement (DFARS) layers additional requirements on top. Contractors transitioning from civilian agency work to Department of Defense contracts frequently encounter invoice rejections because they underestimate these additions.

Understanding the DFARS invoice requirements is not optional for defense contractors. These rules dictate how costs are allocated, how payments map to funding sources, and how invoices withstand audit scrutiny.

CLIN and SLIN: Line-Item Precision

Defense contracts are structured around Contract Line Item Numbers (CLINs) and, where applicable, SubLine Item Numbers (SLINs). Every invoiced amount must be broken down to correspond directly to the CLIN or SLIN specified in the contract.

This is not a formatting preference. The contracting officer and payment office use CLINs to verify that billed amounts align with contracted work. If a contract contains five CLINs, the invoice must show charges against each applicable CLIN individually. Lumping charges together or mapping them to the wrong line item will trigger a rejection.

SLINs add another layer of granularity beneath CLINs, often distinguishing between delivery orders, funding increments, or task-specific work. When the contract uses SLINs, invoices must reflect that structure exactly.

Accounting Classification Reference Numbers (ACRNs)

Each CLIN on a defense contract is tied to an Accounting Classification Reference Number (ACRN), which identifies the specific funding source for that line item. Defense invoices must reference the correct ACRN for every CLIN billed.

Mismatched ACRNs are among the most common causes of defense invoice rejection. The ACRN tells the payment office which appropriation, budget activity, and accounting classification to draw from. An incorrect ACRN does not simply slow payment; it creates a funding mismatch that the Defense Finance and Accounting Service (DFAS) cannot process until the contractor submits a corrected invoice.

Contractors should verify ACRNs against the contract schedule and any contract modifications before submitting each invoice. Modifications frequently add or change ACRNs, and invoicing against a superseded code is an easy mistake to make.

Contract Type Dictates Invoice Detail

The level of detail required on a defense invoice varies significantly by contract type.

Cost-reimbursable contracts demand the most granular breakdowns. Invoices must itemize:

Labor categories, hours worked, and billing rates for each employee or category
Materials and supplies with quantities and unit costs
Other direct costs (ODCs) such as travel, equipment, or subcontractor charges
Applied indirect cost rates (fringe, overhead, G&A) with the base amounts they are calculated against
Fee or profit calculations where applicable

Each of these elements must trace back to the CLIN and ACRN structure described above.

Fixed-price contracts require less cost detail but substitute documentation of delivery or milestone completion. The invoice must reference the specific deliverable, shipment number, lot number, or performance milestone that triggers the payment, along with evidence of government acceptance.

Time-and-materials and labor-hour contracts fall somewhere between the two, requiring labor detail similar to cost-reimbursable contracts but without the full indirect rate breakdown.

DCAA Audit Readiness

On cost-type contracts, the Defense Contract Audit Agency (DCAA) has authority to audit any invoiced cost. This does not mean every invoice triggers an audit, but it means every invoice must be defensible as if one were imminent.

Maintaining audit-ready backup documentation is a practical necessity, not just a best practice. For each invoice submission, contractors should retain:

Timesheets supporting billed labor hours
Receipts and purchase orders for materials and ODCs
Subcontractor invoices with evidence of cost reasonableness
Indirect rate calculations with supporting schedules
Documentation of any provisional billing rates and their basis

DCAA auditors compare invoiced amounts against the contractor's accounting system records. Discrepancies between what is invoiced and what the accounting system reflects will result in questioned costs, potential withholdings, or findings against the contractor's accounting system adequacy.

Electronic Submission Through WAWF

DFARS clause 252.232-7006 mandates that defense contractors submit invoices electronically through the Wide Area Workflow (WAWF) system. This requirement applies to virtually all DoD contracts and is not discretionary.

WAWF enforces structured data entry that maps directly to the CLIN, SLIN, and ACRN framework. The system will flag certain mismatches before submission, but it does not catch all errors. Contractors are responsible for verifying that WAWF entries match the contract terms, including any modifications issued after award.

The specific WAWF document type required (invoice, cost voucher, progress payment, or performance-based payment) depends on the contract type and payment terms. Using the wrong document type is itself a basis for rejection.

Agency-Specific Requirements Beyond Standard DFARS

Individual defense agencies often impose requirements beyond what standard DFARS prescribes. The Army, Navy, Air Force, Marine Corps, and specialized agencies like the Missile Defense Agency or Defense Logistics Agency may each have supplemental invoicing instructions written into their contracts.

These requirements appear in Section G (Contract Administration Data) or Section H (Special Contract Requirements) of the contract document. They may specify particular invoice formats, additional certifications, unique approval workflows, or reporting requirements tied to specific program offices.

Contractors should treat the contract itself as the final authority on invoicing requirements. DFARS sets the floor, but the individual contract may raise it.

Subcontractor Invoicing Through Prime Contractors

A substantial portion of government contract work flows through subcontractors, yet most FAR invoice guidance focuses exclusively on the prime-to-government relationship. Subcontractors face a distinct set of invoicing requirements that combine elements of commercial billing with government-mandated documentation standards.

How the Invoicing Chain Works

Subcontractors do not invoice the government directly. Instead, they submit invoices to the prime contractor, who reviews and approves the charges before incorporating those costs into their own invoice to the contracting agency. This creates a two-step payment chain where the subcontractor's invoice quality directly affects the prime's ability to bill the government accurately and on time.

For the prime contractor, managing this chain means reconciling subcontractor invoices against subcontract terms, verifying cost allowability, and ensuring the amounts roll up correctly into CLIN-level billing on the government invoice. Any discrepancy at the subcontractor level cascades upward.

What Subcontractor Invoices Must Include

While specific requirements vary by subcontract, most prime contractors and flow-down clauses demand the following on every subcontractor invoice:

Subcontract number. Reference the subcontract number assigned by the prime, not the prime contract number. Many primes also require the prime contract number as a secondary reference so they can trace costs to the correct government contract.

CLIN/SLIN references. Map each billed item to the applicable contract line item number or subline item number from the subcontract. This alignment is essential for the prime to allocate costs correctly on their government invoice.

Period of performance. Clearly state the start and end dates for the work being billed. Government auditors and prime contractor reviewers will verify that billed work falls within the authorized performance period.

Detailed cost breakdowns. Cost-reimbursement subcontracts require itemized breakdowns of direct labor (by labor category and hours), materials, travel, other direct costs, and applied indirect rates. Even firm-fixed-price subcontracts should include enough detail for the prime to verify milestone completion or deliverable acceptance.

Required certifications. Depending on the prime contract's flow-down provisions, subcontractors may need to certify cost accuracy, compliance with Cost Accounting Standards (CAS), or adherence to specific regulatory requirements. Invoices lacking required certifications will be returned.

Flow-Down Clauses and Their Impact on Invoicing

Prime contracts routinely contain clauses that flow down to subcontractors through the subcontract agreement. These flow-down provisions can impose invoicing requirements that go well beyond standard commercial billing practices.

Common flow-down impacts on invoicing include:

Prescribed invoice formats that mirror the prime's own billing structure to the government
Backup documentation requirements such as timesheets, receipts, travel authorizations, or inspection reports that must accompany each invoice
Cost Accounting Standards compliance for subcontracts above the CAS threshold, requiring consistent cost allocation methods
Audit rights granting both the prime contractor and government auditors (typically DCAA) access to the subcontractor's books and records supporting invoiced amounts
Limitations on indirect rate billing where the prime contract caps certain overhead or G&A rates

Subcontractors should review their subcontract's flow-down schedule carefully before submitting their first invoice. Requirements that seem buried in boilerplate frequently become the basis for invoice rejections.

Prompt Payment Act Protections for Subcontractors

The Prompt Payment Act extends protections to subcontractors, though the mechanism differs from the government-to-prime relationship. Under FAR 52.232-27, prime contractors must pay subcontractors for satisfactory performance within 14 calendar days of receiving payment from the government for amounts that include the subcontractor's contribution.

If the prime pays late, the subcontractor is entitled to interest penalties calculated at the same rate the government would owe the prime. This provision exists because subcontractors, particularly smaller firms, cannot absorb the cash flow impact of delayed payments on government work.

Key practical points for subcontractors:

The 14-day clock starts when the prime receives the government payment, not when the prime processes it internally
Primes must include a payment clause in subcontracts that commits to these timelines
Subcontractors should track the prime's government invoice submission dates when possible, since that establishes the expected payment timeline
Interest penalty claims are enforceable, though pursuing them can strain the business relationship

The Practical Documentation Challenge

Subcontractor invoicing sits at the intersection of two sets of requirements. Each invoice must satisfy the subcontract terms and any government flow-down provisions, while also providing enough detail for the prime contractor to defensibly incorporate those costs into their government billing.

This means subcontractors often need to maintain documentation standards that approach what the prime itself provides to the government. The process of matching invoices against purchase orders and contracts becomes particularly critical in this chain, where a single misaligned line item can hold up payment across multiple tiers.

For cost-type work, subcontractors should expect that their invoiced indirect rates may be subject to audit and adjustment. Provisional billing rates are common, with final reconciliation occurring after annual rate audits. Building this expectation into cash flow planning prevents surprises.

Small Business Subcontracting Considerations

Government contracts exceeding $750,000 ($1.5 million for construction) generally require the prime contractor to maintain a small business subcontracting plan under FAR 19.702. Accurate subcontractor invoicing feeds directly into the prime's compliance reporting on these plans.

For small business subcontractors, this means your invoices serve a dual purpose. Beyond triggering payment, they generate the data the prime uses to report subcontracting achievement to the contracting officer. Invoices that clearly identify the subcontractor's size status and socioeconomic category help the prime meet their reporting obligations under the Individual Subcontracting Report (ISR) and Summary Subcontracting Report (SSR).

Primes that fall short of their small business subcontracting goals face consequences ranging from reduced past performance ratings to liquidated damages. This gives small business subcontractors meaningful leverage in negotiating reasonable invoice processing timelines and payment terms.

SAM.gov Registration and Payment Prerequisites

Before a contractor can submit a single invoice to the federal government, certain registrations must be in place. The most critical is an active registration in SAM.gov (System for Award Management), the federal government's primary database for entities doing business with federal agencies. Without it, a contractor cannot receive a contract award, submit invoices through IPP or WAWF, or receive payment.

SAM.gov registration is often treated as an administrative checkbox during onboarding. In practice, it is a living prerequisite with ongoing maintenance requirements that directly affect whether invoices get processed and payments get released.

Unique Entity ID and the End of the DUNS Number

Every entity registered in SAM.gov is assigned a Unique Entity ID (UEI), which replaced the DUNS number in April 2022. Unlike the old system, which required a separate registration through Dun & Bradstreet, the UEI is now generated directly within SAM.gov during the registration process. No third-party registration is needed.

The UEI serves as the contractor's identifier across all federal systems. It must appear on every invoice and must match exactly what is recorded in the contract. A mismatch between the UEI on an invoice and the UEI in contract records will trigger a rejection, regardless of whether the invoice is otherwise correct.

Contractors who held DUNS numbers prior to the transition were automatically assigned UEIs. Those entering the federal market after April 2022 obtain their UEI as part of the SAM.gov registration workflow.

EFT Banking Requirements Under FAR 32.7

FAR 32.7 mandates that federal payments be made via Electronic Funds Transfer (EFT). The banking information that controls where payments are routed is not pulled from the invoice itself. It is pulled from SAM.gov.

This distinction matters. A contractor could submit a perfectly formatted invoice with correct banking details printed on it, and the payment would still be sent to whatever account is on file in SAM.gov. If that banking information is outdated, incorrect, or missing, the payment will fail.

Contractors must ensure their SAM.gov banking records reflect their current account and routing numbers. Any changes to banking relationships, such as switching banks or restructuring accounts, must be updated in SAM.gov before the next payment cycle. Failure to do so does not delay just one payment; it can cascade across all active contracts until the records are corrected.

Annual Renewal and the Lapse Problem

SAM.gov registration is not permanent. It expires annually and must be actively renewed. If a contractor's registration lapses, the consequences are immediate:

Invoices submitted during the lapse period cannot be processed.
Payments already in the pipeline are held until the registration is reactivated.
Contracting officers may be unable to issue new task orders or modifications.

The registration expiration date often passes without notice, and the contractor only discovers the problem when payments stop arriving. Setting a calendar reminder 30 to 60 days before expiration prevents this entirely.

Connection to IPP and WAWF

Both of the government's primary invoicing platforms, IPP for civilian agencies and WAWF for defense contracts, pull contractor information directly from SAM.gov. The contractor's legal name, address, UEI, and banking details must be consistent across SAM.gov and the invoicing system.

When discrepancies exist, invoices are rejected at the system level before a human reviewer ever sees them. Common examples include a legal name that was updated in SAM.gov but not yet reflected in the contract, or an address change that creates a mismatch with WAWF records.

Entity Validation Lead Times

New SAM.gov registrations include an entity validation step that verifies the organization's legal existence, physical address, and authorized representatives. This process typically takes 7 to 10 business days, though it can extend longer if documentation issues arise.

Contractors entering the federal market should initiate their SAM.gov registration well before their first invoice is due. Waiting until a contract is awarded to begin registration creates a gap where work may be performed but invoices cannot be submitted, pushing the first payment further out. For subcontractors who may need SAM.gov registration depending on contract terms, the same lead time applies.

Common Government Invoice Rejections and How to Prevent Them

Even experienced contractors encounter invoice rejections. Each rejection resets the Prompt Payment Act clock, delaying payment by weeks or longer while the corrected invoice works its way back through the approval queue. Understanding the most frequent rejection triggers and building systematic prevention into your process eliminates most of these costly delays.

The Top Rejection Reasons and How to Avoid Each

1. Missing or incorrect contract number, task order number, or delivery order number. These identifiers are how the paying office matches your invoice to the correct funding. Transposing a single digit or omitting a task order number on a multi-award IDIQ sends your invoice into a black hole. Before submission, verify every reference number against the contract face page or the most recent modification. If you operate under multiple task orders, confirm you are invoicing against the correct one for the work performed.

2. Invoice amounts that don't match contract line items or authorized ceiling amounts. Billing above a CLIN's funded amount or misallocating costs across line items will trigger an immediate return. Pull the latest contract modification to confirm current funded ceilings for each CLIN before calculating invoice totals. For incrementally funded contracts, track cumulative billings against each funding increment rather than the total contract value.

3. Missing or incorrect CLIN/SLIN references on defense contracts. Defense agencies require invoices to trace every dollar to a specific Contract Line Item Number or Sub-Line Item Number. Generic line items without CLIN mapping will be rejected. Maintain a CLIN crosswalk document that maps your internal cost categories to contract line items, and update it each time the contract is modified.

4. Period of performance dates outside the contract's authorized period. Invoicing for work performed before the contract start date or after expiration is a common rejection, particularly near option year transitions. Check both the base period and any exercised option periods. If work spans a period of performance boundary, split the invoice at the correct date.

5. Insufficient description of services or supplies. Vague descriptions such as "consulting services" or "supplies delivered" give the contracting officer's representative nothing to verify against their acceptance records. Mirror the contract's statement of work language. For services, include specific deliverables completed, labor categories, and hours. For supplies, list part numbers, quantities, and unit prices that correspond to contract terms.

6. Name or address on invoice doesn't match the contract or SAM.gov records. If your company changed its name, restructured, or moved offices, the invoice must reflect what is on file. Any discrepancy between the invoice, the contract, and your SAM.gov registration creates a three-way mismatch that halts processing. After any organizational change, update SAM.gov first, then request a contract modification before submitting invoices under the new information.

7. Missing EFT banking information or information that doesn't match SAM.gov. The paying office validates your Electronic Funds Transfer data against SAM.gov. If your banking details changed and SAM.gov was not updated, the payment cannot be processed. Verify your banking information in SAM.gov quarterly, and immediately after any bank account changes, confirm the update is reflected before your next invoice submission.

8. Expired SAM.gov registration at time of invoice submission. An expired registration blocks payment even if the invoice is otherwise perfect. SAM.gov registrations must be renewed annually, but processing the renewal can take days or weeks. Set renewal reminders at least 60 days before expiration, and confirm active status on the day you submit each invoice.

9. Missing required backup documentation. The documentation standard varies by contract type. Time-and-materials contracts require timesheets with labor categories and hours. Cost-reimbursable contracts require receipts, travel vouchers, and detailed cost breakdowns. Fixed-price supply contracts require proof of delivery or shipment documentation. Before submission, cross-reference your contract's invoicing instructions to confirm every required attachment is included.

10. Incorrect Accounting Classification Reference Numbers (ACRNs) on defense invoices. ACRNs tie invoice line items to specific funding sources. Using the wrong ACRN or failing to include one means the paying office cannot charge the correct appropriation. Maintain a current ACRN-to-CLIN mapping from the contract's accounting data, and verify it against the latest modification before each submission.

11. Invoice submitted to the wrong system or wrong office. Civilian agencies generally require submission through IPP, while defense contracts use WAWF. Submitting through the wrong portal, or sending to the incorrect office code, results in rejection or simply a lost invoice. Confirm the designated submission system and office codes during post-award kickoff, and note them in your internal invoicing procedures for each contract.

12. Missing discount terms when the contract includes prompt payment discounts. If your contract specifies a discount for early payment, every invoice must state the discount percentage and the number of days. Omitting this information when the contract requires it is a technical deficiency. Review Section I of your contract for any prompt payment discount clause, and build the required language into your invoice template for that contract.

Pre-Submission Validation Checklist

Use this checklist as a final gate before submitting any government invoice:

Building a Sustainable Validation Process

Contractors who submit invoices across multiple contracts need more than a one-time checklist. Implementing a consistent invoice validation process and checklist that your team follows for every submission prevents the expensive cycle of rejection, correction, and resubmission. Each contract should have its own invoice preparation file containing the correct reference numbers, CLIN mappings, ACRN codes, submission system, and office codes drawn from the latest contract modification.

It is also worth requesting any agency-specific invoice submission guides during your post-award kickoff meeting. Many contracting officers and their payment offices publish their own checklists or formatting requirements that go beyond the FAR minimums. Incorporating these agency-specific requirements into your preparation process from the start catches issues that generic compliance alone would miss.