How to Submit Your First WAWF Invoice: Contract Instructions, Routing, and Acceptance

Wide Area Workflow, or WAWF, is the invoicing and receiving-report application within the Procurement Integrated Enterprise Environment, PIEE. For a first-time preparer, the useful starting point is a completed contract-to-field worksheet. It gives you something to check against when a screen supplies a default or asks for an unfamiliar code.

On This Page

• Read the contract before choosing a document
• Identify the offices that receive and accept the work
• Prepare the shipment or service records
• Follow a fictional partial-shipment example
• Create, review, and submit in WAWF
• Correct a rejected document
• Check acceptance and payment separately

Read the contract before choosing a document

Find the completed WAWF payment instructions, including the document-type entries and routing table. PGI 232.7004 places these instructions in the contract administration section, such as Section G. Include the relevant task or delivery order and later modifications in your review.

Under DFARS 252.232-7006, the choices depend on the work:

• Fixed-price deliverables: use the invoice and receiving-report types specified by the contracting officer.
• Fixed-price services without shipment: use the specified Invoice 2in1 or invoice and receiving-report arrangement.
• Cost-type, labor-hour, or time-and-materials line items: the clause directs a cost voucher.
• Financing requests: progress payments, performance-based payments, and commercial financing have their own document types.

Fast Pay is permitted only when the contract includes FAR 52.213-1. It is not a shortcut to select because you want payment sooner.

The Combo option is a way to create an invoice and a receiving report together. It does not make Combo the required choice for every award. Nor is it interchangeable with a services-only Invoice 2in1. If the completed instructions are missing, contradictory, or unclear about the line items you are billing, ask the contracting officer to resolve them before creating a submission.

Identify the offices that receive and accept the work

A Department of Defense Activity Address Code, or DoDAAC, identifies a government organization. WAWF uses routing location codes to send documents through the applicable workflow. A code copied from a tutorial may have the right shape and still direct your invoice to the wrong office.

Separate these questions in your worksheet:

Routing question	What to establish from the contract
Who issued and administers the award?	Issue By and Admin offices, where applicable
Where does this shipment go?	Ship To location, including the schedule when it specifies multiple destinations
Where are inspection and acceptance performed?	Source, destination, or other location, plus the applicable office codes
Who approves or accepts services?	Service Approver and Service Acceptor entries when required
Who certifies or processes the payment request?	LPO, if applicable, and Pay Official DoDAAC

Source basis: the routing table in DFARS 252.232-7006 and PGI instructions for completing and validating routing. This worksheet groups the decisions; the fields shown in your document depend on its type and payment system. A local processing office, or LPO, handles payment certification where it occurs outside the entitlement system.

Receipt and acceptance are separate actions. Establish which government office records the arrival of supplies and which authorized acceptor determines acceptance under the contract. Do not assume the person who receives a package is also the person who can accept it in WAWF. For a Combo, the detailed vendor training shows separate routes for the invoice and receiving report, with inspection and LPO steps where applicable.

Recheck the latest modification. PIEE's August 2026 system notices describe pay-office changes associated with the One Pay transition and MOCAS consolidation. Their practical instruction is to verify the current Pay Office DoDAAC against the latest contract information before invoicing. Do not replace a code across all your contracts merely because a notice describes a migration.

Prepare the shipment or service records

The WAWF Combo 101 guide says to keep the contract available during entry and verify prefilled data. Assemble the invoice number, applicable shipment identifier and dates, supplies-or-services selection, line-item details, and required supporting records before you start.

A contract line item number, or CLIN, identifies the work being billed. A SLIN is a subline item. Match the relevant identifier, description, unit, price, and quantity to the contract and this transaction. Include the items actually being shipped or invoiced, rather than every line appearing on the award. For services, identify the actual work or performance period and supporting records required by the instructions. Check the contract currency as well as the amount.

Check what demonstrates performance: for example, the packing record for supplies or the specified deliverable or service record. These examples are preparation aids, not a universal attachment list. Special item-identification, transportation, or other contract requirements need their corresponding information. If two records disagree, settle the discrepancy before using either as the basis for an invoice.

Follow a fictional partial-shipment example

Assume a fictional fixed-price order calls for 20 storage cases at an invented unit price of $125. Its instructions permit an invoice and receiving report created through Combo, with destination acceptance. The supplier has shipped 8 cases in this transaction. No taxes, freight charges, discounts, or prior billings are included in this arithmetic example.

Worksheet entry	Fictional example	Why the entry matters
Contract and order	Use the actual award and order identifiers	No demonstration identifier belongs in a real submission
Document selection	Invoice and receiving report through Combo	This choice follows the example's assumed instructions
Line item	CLIN 0001, storage cases, unit EA	The description and unit must match the actual line
Quantity this time	8 cases	The 20-case order quantity is not the shipment quantity
Unit price and extension	$125 each; $1,000 total	The amount represents this assumed shipment only
Shipment and invoice identifiers	Separate identifiers from the supplier's records	Retain a way to reconcile both documents to the transaction
Shipment date	Actual dispatch date from the shipping record	If an estimated date is allowed and used, identify it as estimated
Final shipment and final invoice	No, under these assumptions	Twelve cases remain to be delivered and billed
Routing and acceptance	Actual codes from the current award; destination acceptance	No real or invented government routing codes are supplied here
Supporting record	Packing record identifying the 8 cases, plus anything required by the award	Give the reviewer records that match the submitted quantity

Illustrative amount = 8 cases × $125 per case = $1,000. Remaining quantity = 20 cases − 8 cases = 12 cases.

Every quantity and price above is fictional. The worksheet applies the field relationships in the official Combo training; it is not a screenshot, a real contract, or an instruction to use these entries on another award.

Suppose the government reports that only seven cases arrived in acceptable condition. The supplier's eight-case shipment record does not establish acceptance of all eight. Reconcile the receiving report, government action, and invoice with the responsible officials before deciding how to correct the documents. Keep the order quantity, shipped quantity, and accepted quantity distinct while resolving the discrepancy.

Create, review, and submit in WAWF

First confirm that you have access to the WAWF Vendor role for the appropriate company CAGE code, the identifier associated with the vendor. The official vendor training index includes document-specific instructions and practice material. A PIEE login alone does not establish that the needed role is active.

For a contract that calls for the Combo workflow, the detailed creation tutorial follows this sequence:

1. Open Vendor, then Create Document. Select the appropriate CAGE and enter the contract and applicable order.
2. Check the Pay DoDAAC and choose the relevant line items. Select the authorized document type and inspection/acceptance locations.
3. Complete routing, header dates, final indicators, and line items. Check values brought in from Electronic Document Access, or EDA; do not casually change the system-supplied invoice date.
4. Add required supporting files. Complete the attachment-type field and confirm the upload appears on the document.
5. Review both Preview CI, for the invoice, and Preview RR, for the receiving report. Correct errors before submitting and address warnings according to their meaning.
6. Submit and retain the success confirmation and document identifiers.

The current index lists this detailed Combo demonstration as updated in March 2025; the introductory Combo 101 guide is dated April 2020. These steps reflect the public official training and help, rather than a walkthrough of your account. Screens and available fields vary with the selected workflow. Use the guidance for your document type when an older illustration differs.

Saving is a different action. The production WAWF menu help distinguishes Saved Documents Folder, containing unsubmitted drafts, from the history and rejected-document folders. If you leave midway, verify whether the record was merely saved. PIEE's navigation notice warns against browser Back; use the application's controls to avoid losing unsaved entry.

Correct a rejected document

Start by opening the actual document and reading the government's reason. The Vendor role guidance allows vendors to correct rejected data and resubmit. It also provides history of government actions and contact information to support follow-up.

Use Rejected Invoices Folder for an invoice returned to you and Rejected Receiving Reports Folder for a returned receiving report. Correction Required Folder is a separate route for receiving-report corrections. These folders are identified in the production menu help.

For a quantity mismatch, compare the contract line, shipment or service evidence, and rejection comments. For a routing issue, compare the current modification and the office that received the document. Correct the identified problem, review the related document too, and retain the resubmission trail. This is a practical review sequence, not a promise that every field can be edited at every stage.

If a contract number, order, invoice identifier, or shipment identifier is wrong, establish whether correction, recall, voiding, or replacement is appropriate for the current state. The official status guidance makes those actions conditional. Creating another invoice without resolving the original can leave two records to reconcile.

Check acceptance and payment separately

Use the document's history to establish where it is, then direct the question to the office responsible for that stage.

Status or milestone	What it establishes	Next check
Submitted	Document awaits initial government action	Confirm the intended routing
Received	Receipt recorded on the applicable receiving report	Check acceptance action separately
Accepted	Acceptance has occurred; later certification or payment steps may remain	Follow the invoice's downstream status
Extracted	Data sent to the payment office, not yet processed there	Check for subsequent processing
Processed	Pay office has processed it into the entitlement system	Look for payment information in myInvoice
Paid	Payment-history information is available	Reconcile amount and payment reference

Source: PIEE document-status definitions. This is a selected set, not a mandatory sequence for every document.

DFAS's current invoice-status instructions direct users to confirm processing and use myInvoice's Reports > Status and Date Report or Reports > Payment Report for the relevant CAGE. If that does not answer the question, identify the servicing payment office by DoDAAC and use its customer-service channel. DFAS cannot repair the contract or perform acceptance for the responsible office.

For follow-up, have the contract/order, invoice and shipment identifiers, current status, relevant dates, and specific discrepancy ready. Ask for the missing action or explanation. Submission, physical delivery, acceptance, and cash receipt are different milestones; none of the earlier ones supplies a guaranteed payment date.

Before sending the first invoice, be able to trace every routing entry and billed amount to the current award and performance record. After sending it, retain proof of submission and track both acceptance and payment until the transaction reconciles.

Source notes

• DFARS 252.232-7006, Wide Area WorkFlow Payment Instructions: Official contract clause covering document types and payment instructions.
• PGI 232.7004, Contract clause instructions: Official guidance for completing routing and inspection/acceptance entries.
• WAWF Invoice and Receiving Report COMBO 101: Introductory vendor training, listed April 2020.
• Vendor Create Combo Document: Detailed official creation tutorial, listed March 2025.
• WAWF Vendor Role training: Document-specific training, roles, history, and correction capabilities.
• WAWF Post-Logon Help: Public production help for vendor menus and folders.
• WAWF Document Status: Official meanings of workflow statuses and conditional correction actions.
• DFAS, Check Invoice Status: Payment-report and customer-service instructions, updated May 26, 2026.
• PIEE login and system notices: Current pay-office transition notices and application navigation guidance.

Last checked: September 9, 2026.