DFARS 252.232-7006 Wide Area WorkFlow Payment Instructions. Basic (Dec 2018) (Current)

As prescribed in 232.7004(b), use the clause at 252.232-7006, Wide Area WorkFlow Payment Instructions, in solicitations and contracts or task or delivery orders, including solicitations and contracts using FAR part 12 procedures for the acquisition of commercial items, when 252.232-7003 is used and none of the exceptions at 232.7002(b)(1) apply. See PGI 232.7004 (DFARS/PGI view) for instructions on completing the clause.


      (a)  Definitions.  As used in this clause—

      “Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

      “Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

      “Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

      “Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

      (b)  Electronic invoicing.  The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

      (c)  WAWF access.  To access WAWF, the Contractor shall—

              (1)  Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

              (2)  Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

      (d)  WAWF training.  The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/

      (e)  WAWF methods of document submission.  Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

      (f)  WAWF payment instructions.  The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

              (1)  Document type.  The Contractor shall submit payment requests using the following document type(s):

                    (i)  For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

                    (ii)  For fixed price line items—

                            (A)  That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.


(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

                            (B)  For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.


              (Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

                    (iii)  For customary progress payments based on costs incurred, submit a progress payment request.

                    (iv)  For performance based payments, submit a performance based payment request.

                    (v)  For commercial item financing, submit a commercial item financing request.

              (2)  ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

      (f)  [Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

              (3)  Document routing.  The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

                                                                                 Routing Data Table*

Field Name in WAWF

Data to be entered in WAWF

Pay Official DoDAAC


Issue By DoDAAC


Admin DoDAAC


Inspect By DoDAAC


Ship To Code


Ship From Code


Mark For Code


Service Approver (DoDAAC)


Service Acceptor (DoDAAC)


Accept at Other DoDAAC






Other DoDAAC(s)


(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert “See Schedule” or “Not applicable.”)

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

              (4)  Payment request.  The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

              (5)  Receiving report.  The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

      (g)  WAWF point of contact.

              (1)  The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.


(Contracting Officer: Insert applicable information or “Not applicable.”)

              (2)  Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)


Subcontractor ✖   DFARS 212.301 
⚠ =252.232-7003 Basic

Working with a set of FAR clauses from an RFP or contract?

Try pasting them into our tool to instantly generate a risk profile, including the basic flow down recommendation.


Works best with Chrome and Edge browsers!