Submitted, accepted and paid describe different stages. A supplier needs the right document type, contract routing information and delivery evidence to understand where its invoice stands.
Submitting an invoice in Wide Area Workflow is a step in a payment process, rather than confirmation that the customer has accepted the work or that payment has been made. For a small defense company, the useful question is which step the document has reached and what evidence supports the next action.
WAWF sits within the Procurement Integrated Enterprise Environment. Its usefulness depends on the contract information entered and the workflow selected. Finance staff need access to the awarded invoicing instructions, while the delivery team needs to explain what was supplied and how the customer's acceptance requirements were addressed. Bringing those records together is more productive than treating an unpaid invoice as a single undifferentiated problem.
DFARS 252.232-7006 provides contract-specific WAWF instructions. It distinguishes cost vouchers, fixed-price invoicing, services and financing requests, and includes fields completed by the contracting officer. The relevant version in the awarded contract or order is the starting point for deciding what to submit.
The clause also provides a routing table for applicable organisational codes, including the payment office and acceptance roles. A DoDAAC identifies a particular unit, activity or organisation. Staff should use the contract's completed routing information and seek clarification from the stated contact where it is missing or unclear.
Consider a hypothetical company delivering a fixed-price data-migration service. Its accounts team previously invoiced a commercial customer by emailing a PDF. For the government order, it needs to establish the specified WAWF document type and the responsible acceptance office before the first billing event. Copying another supplier's workflow would leave those contract-specific questions unanswered.
The company can prepare a one-page invoicing brief containing the contract and order identifiers, relevant line items, permitted billing event, document type, routing information and internal owner. It should point to the awarded instructions rather than paraphrase away an important qualification. A finance colleague can then process the invoice while retaining a clear route back to the underlying authority.
The PIEE document-type guidance explains that an Invoice and Receiving Report Combo creates two separate documents from one data-entry session. The receiving report follows inspection and acceptance; the invoice follows the payment-approval route. One submission session therefore does not mean that every subsequent action occurs together.
The same guidance distinguishes the services-only Invoice 2-in-1, which creates a single combined document and follows its applicable acceptance and payment workflow. Those options should not be selected merely because their names sound similar. The contract's instructions and the nature of the billed requirement determine which route applies.
For the data-migration company, the distinction affects what staff monitor. If the applicable process involves separate documents, checking only the invoice can leave an acceptance issue undiscovered. If it uses a combined service document, colleagues should understand that workflow instead of expecting a separate receiving report to appear.
Map the actual route once with the person responsible for contract administration. Keep the explanation short enough for the project manager to use: what the supplier submits, which government role acts next and where finance can see the resulting status. This is an operational reference for that contract, rather than a universal diagram for every defense customer.
The strongest invoice record begins with the contract's billing basis. For the hypothetical project, that might require staff to establish completion of a specified service milestone. The company should retain the relevant delivery record and customer correspondence so that the invoice description can be reconciled with what actually occurred.
Avoid allowing the project manager's informal statement that work is “finished” to become the only evidence available to accounts. Completion can mean different things to software engineers, project managers and commercial staff. Identify the contractual deliverable and record what supports the billing event being claimed.
If the customer requests further work, establish whether it falls within the existing obligation or requires a separate contractual decision. That question belongs with the responsible commercial and contracting personnel. Altering an invoice description cannot resolve uncertainty about the agreed scope.
This preparation also helps when staff change. A colleague taking over the project should be able to connect the invoice to the order and supporting delivery record without depending on the memory of the original project lead. The same record supports ordinary reconciliation after payment arrives.
PIEE's status guide gives each status a specific meaning. Submitted indicates that initial government action is pending. Extracted means internal WAWF processing is complete and a transaction has been sent to the payment office, which has not yet processed it. Processed indicates processing by the payment office within the entitlement system; it is distinct from the Paid status and its historical payment details.
Those distinctions change the next useful enquiry. A document awaiting its first government action raises a different question from one already processed by the payment office. Record the document identifier, status and date checked before contacting anyone. A precise account reduces the chance that different colleagues chase different versions of the same issue.
For the service supplier, an internal receivables review can distinguish delivery evidence awaiting completion, a document awaiting the relevant government action, and a payment record needing reconciliation. These are suggested management categories, not substitutes for WAWF's official status definitions. Their purpose is to assign the next action to the person who can actually perform it.
DFAS's invoice-status guidance directs suppliers to myInvoice in PIEE or its customer-service routes. It describes checking processed documents and running the relevant payment report. For assistance, suppliers should identify the servicing payment office from the DoDAAC.
The page also states that DFAS cannot change a contract, invoice, acceptance or authorisation to pay on the vendor's behalf. If the underlying issue is an incorrect contractual instruction or an acceptance action, sending repeated general payment requests does not itself correct that record.
Prepare an enquiry that identifies the document and the unresolved fact. Explain what has already been checked and provide the relevant references through the appropriate channel. Keep a record of the answer and the assigned follow-up so the next employee does not restart the same investigation.
When payment information becomes available, compare it with the company's receivables record before closing the item. If the amount differs from what finance expected, retain the payment reference and identify the unexplained difference. Do not quietly change the internal invoice to make the figures agree. A documented reconciliation lets the commercial owner investigate the actual discrepancy and leaves a usable record for the next reporting period.
When a document is rejected or needs correction, read the reason and establish the applicable correction route. Recreating documents without understanding their status can make the company's own records harder to reconcile. The person correcting the issue should know which submission remains operative and how the corrected record relates to the original.
Our guide to prime and subcontract responsibilities explains why the identity of the invoicing supplier matters. The SAM registration guide provides context for the business identity behind the transaction. Together with the contract's WAWF instructions, those records help the supplier follow a coherent path from delivered work to an identifiable payment, with each unresolved step assigned to the right person.
DFARS 252.232-7006, PIEE document-type and status guidance, and the May 2026 DFAS invoice-status page were directly read on 6 September 2026. The service-provider example and suggested internal reconciliation are BDI analysis. Actual contract clauses and completed routing instructions govern invoicing; no universal payment deadline is inferred.
Suggest a correction