Winning a Department of Defense contract does not get money into a bank account — submitting a clean invoice through Wide Area Workflow does. Since Section 1008 of the FY2001 National Defense Authorization Act, DoD contractors have been required to submit payment requests and receiving reports electronically, and the mechanism is codified in DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports. WAWF is not a standalone system anymore; it now lives inside the Procurement Integrated Enterprise Environment (PIEE), DoD's consolidated procurement portal. Understanding how the two fit together — and where invoices actually get stuck — is the difference between routine 30-day payment and a chase that drags on for months.

The Electronic Submission Mandate

DFARS 252.232-7003 requires that "the Contractor shall submit payment requests and receiving reports in electronic form" and states that the only acceptable electronic form for that submission is WAWF. Acceptable input methods include Electronic Data Interchange, Secure File Transfer Protocol, or direct entry through the WAWF website inside PIEE. The clause defines a narrow set of exceptions: written contracting-officer permission with alternate instructions, approved commercial-transportation payment systems, TRICARE's Encounter Data System, and purchase-card transactions, where only the receiving report must go through WAWF. A companion clause, DFARS 252.232-7006, gives contractors the specific WAWF payment instructions — document type, DoDAAC routing codes, and contract administration office — that must be read directly out of each contract before an invoice is created; guessing at these fields is a common cause of rejection.

How an Invoice Actually Moves

Before creating a document, a contractor needs an active PIEE vendor account, a current SAM.gov registration with banking information matching what DFAS expects to pay, and a CAGE code linked to that account. Every company needs at least one Group Administrator to approve PIEE access; a company that loses its administrator without naming a replacement ends up with an "orphaned CAGE" resolved only through the DISA PIEE Help Desk. Inside WAWF, the contractor selects the exact document type the contract specifies — Invoice 2-in-1 for fixed-price services with no physical shipment, Invoice and Receiving Report Combo for fixed-price supplies, a standalone invoice when another party submits the receiving report, a cost voucher for cost-reimbursement work, or a progress-payment or performance-based-payment document for milestone billing — then enters the CLIN, ACRN, quantity, and unit price exactly as the contract states them. Once submitted, the document routes to an inspector or acceptor, typically the COR, then to a Local Processing Officer where required, and finally to the Defense Finance and Accounting Service for payment.

Why Invoices Get Rejected

The overwhelming majority of WAWF rejections trace back to a small set of recurring errors rather than DFAS discretion. Banking information in WAWF that does not match the contractor's SAM.gov record is an automatic rejection, as is an expired SAM.gov registration that lapsed between award and invoice submission. Selecting the wrong CLIN or Accounting Classification Reference Number, particularly on incrementally funded contracts spanning multiple ACRNs, is another frequent cause, as is choosing the wrong document type outright, since the correct type depends on the contract's payment terms and is specified in the contract's Section G WAWF instructions rather than left to the contractor's judgment. Even small discrepancies in company name or address — an abbreviated "St." where the contract spells out "Street," or a DBA name used instead of the registered legal entity — can trigger a bounce, and a legal name change requires a contract modification before invoices will process correctly. Submitting a fixed-price supply invoice before delivery is complete, or mistakenly marking a submission as the "final invoice," both require correction and resubmission rather than a quick fix inside the existing document.

The Prompt Payment Act Clock

Once an invoice is accepted, FAR Subpart 32.9 starts the payment clock. Under FAR 32.904, the standard due date is the later of two events: the 30th day after the designated billing office receives a proper invoice, or the 30th day after government acceptance of the supplies or services. For interest-penalty purposes, acceptance is constructively presumed to occur on the seventh day after delivery unless there is an actual dispute over quantity, quality, or contract compliance — though that presumption does not compel the government to accept before then. Construction contracts run on a faster clock for progress payments, due 14 days after a proper payment request, while architect-engineer and final construction payments follow the standard 30-day rule. If the government misses its due date on an otherwise proper invoice with no compliance dispute, FAR 32.907 requires an automatic interest penalty at the Treasury rate, and contractors who are not paid that penalty within 10 days of the late payment may demand an additional penalty. Construction and architect-engineer contracts follow their own variants of the same rule: progress payments on fixed-price construction contracts are due 14 days after a proper payment request, while final payments on both construction and A-E contracts follow the standard 30-day rule from invoice receipt or acceptance, whichever is later.

PIEE Is Bigger Than WAWF

Contractors who treat WAWF as a standalone invoicing tool miss part of the picture. WAWF is one module inside PIEE, DoD's consolidated procurement portal, and the same vendor account also carries access to MyInvoice, which shows the actual payment-side status of a submission — often more current than the WAWF document view. A document can show "Accepted" in WAWF while payment is still processing at DFAS, and MyInvoice is the tool that shows which stage it is actually stuck in. Civilian agencies do not use WAWF at all; they route invoices through the Invoice Processing Platform or agency-specific systems, so rejection patterns learned on DoD work do not automatically carry over to civilian task orders.

What It Means for Contractors

Read your contract's WAWF payment instructions clause before you ever open PIEE, and keep a printed copy on hand so document type, CLIN structure, and DoDAAC codes are confirmed rather than guessed. Verify SAM.gov banking information and registration status before every invoice cycle, not just at award, since a lapse anywhere in that chain stops payment regardless of how correctly the rest of the invoice is prepared. If an invoice sits at the COR or acceptor level for more than five to seven business days without movement, follow up directly — the Prompt Payment Act clock only helps once government acceptance has actually occurred, so a stalled acceptance is a stalled payment, not yet a penalty-triggering delay.

Sources