A community resource for the acquisition workforce not a .gov website
part52.dev Federal Acquisition Clause Monitor
DFARS Clause ACTIVE

252.232-7006

Wide Area WorkFlow Payment Instructions.
Search on acquisition.gov · View on eCFR.gov
Effective Date
JAN 2023
Active Deviations
3
Versions
4 (since 2016-12-22)
DEV
This clause is modified by 3 active class deviations
  • 2026-O0043 — DFARS RFO Implementation (Part 4)
  • 2026-O0028 — DFARS RFO Implementation (Part 12)
  • 2026-O0022 — DFARS RFO Implementation (Part 32)
    Add clause 252.232-7006
View per-deviation details →
252.232-7006 Wide Area WorkFlow Payment Instructions.

As prescribed in 232.7004(b), use the following clause:

Wide Area Workflow Payment Instructions (JAN 2023)

(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 System (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 financing, submit a commercial financing request.

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

[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

LPO DoDAAC

DCAA Auditor 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.

[77 FR 38734, June 29, 2012, as amended at 78 FR 28758, May 16, 2013; 78 FR 30232, May 22, 2013; 83 FR 66064, Dec. 21, 2018; 88 FR 6595, Jan. 31, 2023]
RFO
Prescription superseded under the RFO

The prescription shown below is from the codified eCFR. The Revolutionary FAR Overhaul relocates this clause's prescription as follows:

  • 212.301212.205 (prescriptive text also revised)

See the deviation memorandum for the current prescription authority.

View deviation: 2026-O0043 → · View deviation: 2026-O0028 → · View deviation: 2026-O0022 →

R-DFARS Prescription Source

This clause is prescribed in the R-DFARS by the following deviation:

  • 2026-O0022 — DFARS RFO Implementation (Part 32) (DFARS Part 232)
    Add clause 252.232-7006
232.7004(b)
(b) Use the clause at 252.232-7006, Wide Area WorkFlow Payment Instructions, in solicitations and contracts, task orders, or delivery orders, including solicitations and contracts using FAR part 12 procedures for the acquisition of commercial products and commercial services, when 252.232-7003 is used and none of the exceptions at232.7002(b)(1) apply. See PGI 232.7004 for instructions on completing the clause.
Prescription data sourced from eCFR as of 2026-06-10 03:16 UTC. Cross-references within the prescription are not resolved automatically.

Regulatory Stack

The layers of regulation that govern this clause, from the FAR prescription through agency-specific supplements and any active deviations.

R-DFARS R-DFARS Prescription Per Deviation 2026-O0022 (DFARS Part 232)
2026-O0022: DFARS RFO Implementation (Part 32) — DFARS Part 232

View Deviation 2026-O0022 →

DFARS DFARS Supplement (eCFR) ⚠ May be superseded by RFO 232.7004(b)
(b) Use the clause at 252.232-7006, Wide Area WorkFlow Payment Instructions, in solicitations and contracts, task orders, or delivery orders, including solicitations and contracts using FAR part 12 procedures for the acquisition of commercial products and commercial services, when 252.232-7003 is used and none of the exceptions at232.7002(b)(1) apply. See PGI 232.7004 for instructions on completing the clause.

Search on acquisition.gov · View on eCFR.gov

Version History

Version history is sourced from the codified eCFR. Changes published only as class deviations or by the Revolutionary FAR Overhaul do not appear here until they are incorporated into the eCFR. For RFO-driven changes see the RFO Version tab and any active deviations cited above.

4 versions tracked from 2016-12-22 to 2023-01-31.
JAN 2023 January 31, 2023 CURRENT
Removed in this version
Added in this version
Unchanged
NOV 2019 (previous)
JAN 2023 (current)
2 removed
(v)
(v) For commercial item financing, submit a commercial item financing request.
(v)
(v) For commercial financing, submit a commercial financing request.
46 removed
(3)
(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 * (* 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).)
(3)
(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 *
NOV 2019 November 20, 2019 SUBSTANTIVE
Removed in this version
Added in this version
Unchanged
DEC 2018 (previous)
NOV 2019 (current)
2 added, 1 removed
(b)
(b) Electronic invoicing. The WAWF system providesthe method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation System (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(b)
(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 System (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
DEC 2018 December 21, 2018 SUBSTANTIVE
Removed in this version
Added in this version
Unchanged
DEC 2016 (previous)
DEC 2018 (current)
20 added
(a)
(a)
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.
7 added, 3 removed
(b)
(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(b)
(b) Electronic invoicing. The WAWF system providesthe method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation System (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
5 added, 37 removed
(1)
(1) Document type. The Contractor shall use the following document type(s). (Contracting Officer: Insert applicable document type(s). Note: If a "Combo" document type is identified but not supportable by the Contractor's business systems, an "Invoice" (stand-alone) and "Receiving Report" (stand-alone) document type may be used instead.)
(1)
(1) Document type. The Contractor shall submit payment requests using the following document type(s):
5 added, 5 removed
(2)
(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.
(2)
(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.
7 added, 2 removed
(f)
(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:
(f)
(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:
35 added, 6 removed
(3)
(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* (Contracting Officer: Insert applicable DoDAAC information or "See schedule" if multiple ship to/acceptance locations apply, or "Not applicable.")
(3)
(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 * (* 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).)
25 added, 41 removed
(4)
(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.
(4)
(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.
11 added, 33 removed
(5)
(5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system. (Contracting Officer: Insert applicable email addresses or "Not applicable.")
(5)
(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.
13 added, 5 removed
(i)
[Not present in prior version]
(i)
(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.
7 added, 5 removed
(ii)
[Not present in prior version]
(ii)
(ii) For fixed price line items -
39 added, 5 removed
(A)
[Not present in prior version]
(A)
(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.)
61 added, 5 removed
(B)
[Not present in prior version]
(B)
(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.)
14 added, 5 removed
(iii)
[Not present in prior version]
(iii)
(iii) For customary progress payments based on costs incurred, submit a progress payment request.
11 added, 5 removed
(iv)
[Not present in prior version]
(iv)
(iv) For performance based payments, submit a performance based payment request.
11 added, 5 removed
(v)
[Not present in prior version]
(v)
(v) For commercial item financing, submit a commercial item financing request.
DEC 2016 December 22, 2016 SUBSTANTIVE
Earliest version available from the eCFR

Active Class Deviations

DFARS RFO Implementation (Part 4) Modify clause 252.232-7006
MODIFIED
DFARS RFO Implementation (Part 12) Modify clause 252.232-7006
MODIFIED
DFARS RFO Implementation (Part 32) Add clause 252.232-7006
MODIFIED

Related Clauses

References

252.232-7003
Use with AI assistant
Copy a link and prompt for use with Gemini or another AI assistant.