Invoice Requirements in Government Contracts

Government contract invoice requirements define the specific data elements, format standards, submission procedures, and supporting documentation that a contractor's invoice must contain and satisfy before the government is obligated to process payment, established in the contract's payment clauses (Section I/Section G) and agency-specific electronic invoicing procedures, typically through Wide Area Workflow (WAWF).

What are Invoice Requirements in Government Contracts?

Unlike commercial invoicing, where a vendor can send a simple paper or PDF invoice to accounts payable, federal government invoicing is governed by mandatory contract clauses, agency-specific data requirements, and in most cases, mandatory electronic submission through government invoicing systems. An invoice that does not meet all requirements is a "improper invoice", the agency is permitted (and sometimes required) to return it for correction, restarting the Prompt Payment Act payment clock.

FAR 52.232-25 (Prompt Payment) establishes the baseline invoice requirements: contractor name, address, and taxpayer identification number; invoice number and date; contract number and task or delivery order number; CLIN number and description for each billed item; quantity, unit price, and extended amount for each CLIN; and name, title, and contact information for the invoice point of contact. DoD contracts add Defense Finance and Accounting Service (DFAS) requirements including ACRN (Accounting Classification Reference Number) coding that maps each invoice line to the specific funding citation.

For most DoD contracts, Wide Area Workflow (WAWF) is the mandatory electronic submission system. WAWF requires contractors to submit invoices through an online portal (wawftraining.eb.mil or the production system), selecting the correct document type (2-in-1 Invoice for services, Combo for supplies + receiving report, or Cost Voucher for cost-type contracts), attaching supporting documentation (timesheets, travel receipts, vendor invoices for ODCs), and routing the invoice to the correct Contracting Officer Representative (COR) and DCAA (for cost vouchers).

Cost vouchers on cost-type contracts require additional documentation: a detailed cost breakdown by cost element (direct labor, fringe, overhead, G&A, materials, travel, other direct costs) with supporting computations, DCAA-approved billing rates applied to actual costs incurred, and the cumulative cost-to-date against the contract's estimated cost ceiling.

Why Invoice Requirements Matter for Government Contractors

Invoice compliance is a cash flow issue. Every improper invoice rejection resets the Prompt Payment Act clock by days or weeks while the contractor corrects the deficiency and resubmits. On large programs with monthly invoices, systematic invoice deficiencies, wrong CLIN numbers, missing ACRNs, incorrect WAWF document type selection, unsupported ODC backup, can create chronic payment delays that cascade into working capital problems. Building a compliant invoicing process at contract start-up (during the period when the contract's specific requirements are fresh) prevents months of corrective action cycles.

Example

A government IT contractor submits its first T&M invoice through WAWF for a new DHA contract. The invoice includes the correct contract and task order number, CLIN breakdown showing hours billed by labor category sub-CLIN at the approved rates, supporting timesheets for each employee by CLIN, and the ACRN codes from the contract's funding document. The COR reviews the invoice in WAWF, approves it, and routes it to DFAS. DFAS processes payment within 18 days of invoice receipt, ahead of the 30-day prompt payment deadline. On the second month's invoice, the contractor inadvertently omits the ACRN codes; DFAS returns the invoice as improper within 7 days, resetting the payment clock. The contractor corrects and resubmits within 24 hours, and payment issues on day 30 of the resubmitted invoice.

Frequently Asked Questions

What is WAWF and is it required for all government contracts?

Wide Area Workflow (WAWF) is the DoD's mandatory electronic invoicing, receipt, and acceptance system. All DoD contractors are required to submit invoices through WAWF (or its successor, the Procurement Integrated Enterprise Environment, PIEE) unless a specific waiver is obtained. Civilian agency contracts may use WAWF or other electronic systems (for example, IPP, Invoice Processing Platform, used by Treasury and some other civilian agencies). Contractors should check the contract's payment clause (typically G.2 or G.3) to identify the specific required invoicing system.

What is an Accounting Classification Reference Number (ACRN) and why does it matter?

The ACRN is a two-letter code (AA, AB, AC, etc.) that identifies a specific funding citation within a DoD contract. Because DoD contracts are funded from multiple appropriations (different fiscal years, different programs), each CLIN may be funded from a different appropriation with its own ACRN. When invoicing, the contractor must identify the ACRN for each billed CLIN so that DFAS can route the payment to the correct appropriation. Missing or incorrect ACRNs are the most common cause of DoD invoice rejection. The contract's funding document (DD Form 1155 or equivalent) lists all ACRNs and the CLIN or SLIN each funds.

What supporting documentation is typically required for T&M invoices?

T&M invoices typically require: labor detail showing each employee who charged hours to the invoice period, their labor category, hours charged, and rate; timesheets or equivalent labor recording system output demonstrating hours were actually worked and assigned to the correct CLIN; ODC backup documentation (vendor receipts for materials, travel receipts, subcontractor invoices); and a cumulative cost summary showing total hours and ODCs billed to date versus the CLIN ceiling. The contract's payment clause specifies exactly what supporting documentation is required, requirements vary by agency and contract type.

Can a contractor submit multiple invoices in the same period?

Yes. There is generally no restriction on invoice frequency other than what the contract specifies. Most contracts allow monthly invoicing; some large contracts allow more frequent (bi-weekly) invoicing to accelerate cash flow. The contract may specify a billing cycle (invoices must cover a calendar month, for example) but unless the contract imposes a minimum interval, the contractor can submit invoices as frequently as it has billable costs to report. However, high-frequency invoicing on cost-type contracts increases DCAA review burden and may result in slower processing, monthly invoicing is the standard and generally recommended approach.