Electronic Invoicing — WAWF & IPP
Also known as: WAWF, iRAPT, PIEE, Invoice Processing Platform (IPP), electronic invoice submission
What you do here: Submit invoices through the required electronic portal
At a Glance
- Who it's for
- Contractors billing DoD (WAWF) or many civilian agencies (IPP)
- How you submit
- Through the required electronic portal, not paper/email
- DoD portal
- WAWF / iRAPT within PIEE
- Governing authority
- DFARS 252.232-7003 (DoD); FAR 32.905 invoice content
- Cash-flow effect
- Correct portal use is a precondition to a proper invoice being accepted
What It Is
Getting paid isn't just about the money's destination — it's about submitting the invoice through the channel the agency requires. For the Department of Defense, DFARS 252.232-7003 requires electronic submission of payment requests and receiving reports through Wide Area Workflow (WAWF, now iRAPT within the Procurement Integrated Enterprise Environment, PIEE). Many civilian agencies mandate the Treasury Bureau of the Fiscal Service's Invoice Processing Platform (IPP). These systems route your invoice to the acceptor and the payment office, capture inspection/acceptance electronically, and enforce that your invoice carries the elements a proper invoice needs under FAR 32.905. Submitting to the wrong place — or leaving out required routing codes — means your invoice never properly arrives, and the prompt-payment clock never starts.
When It’s Used
- On DoD contracts, where WAWF/iRAPT submission is generally mandatory (DFARS 252.232-7003).
- On many civilian-agency contracts that mandate Treasury's Invoice Processing Platform (IPP).
- Whenever the contract's invoicing instructions (often Section G) specify an electronic portal and routing codes.
- For both interim and final invoices, and for receiving reports that document acceptance.
Key Features
| Feature | What It Means |
|---|---|
| Portal is mandatory | Where the contract requires WAWF or IPP, an emailed or mailed invoice is not a proper submission and won't start the payment clock. |
| Routing codes | Electronic invoices depend on correct routing codes (e.g., DoDAAC/CAGE, pay office, acceptor) drawn from the contract — a wrong code misroutes the invoice. |
| Electronic acceptance | The portal captures the government's inspection and acceptance electronically, which is what triggers the payment obligation. |
| Invoice content still governed by FAR 32.905 | The portal enforces the proper-invoice elements; missing data gets the invoice rejected back to you. |
| PIEE single sign-on | For DoD, WAWF/iRAPT lives inside PIEE, the same environment used for other procurement functions, under one registration. |
The SDVOSB Cash-Flow Angle
For a small firm new to a given agency, the first invoice is often the hardest — not because of the money, but because the routing codes and portal registration trip people up, and a rejected e-invoice quietly resets the payment clock while you think you've billed. Get your WAWF/PIEE (or IPP) registration done early, pull the exact routing codes from the contract, and do a test invoice if the volume warrants it. This is administrative, but it's the gate every dollar passes through.
How to Get Paid
- Read the contract's invoicing instructions to learn which portal (WAWF/iRAPT or IPP) and routing codes to use.
- Register in the required system (PIEE for WAWF; IPP enrollment for civilian agencies) before your first invoice is due.
- Enter the invoice with correct routing codes and all FAR 32.905 proper-invoice elements.
- Attach or reference the receiving report / evidence of acceptance where the portal requires it.
- Monitor the portal for rejections and resubmit promptly — a rejection restarts the payment clock.
Watch Out For
- An invoice sent by email or mail when the contract requires WAWF/IPP is not a proper submission and doesn't start the clock.
- Wrong routing codes misroute the invoice; it can sit unacted-upon while you assume it's in process.
- Portal registration can take time — don't wait until the first invoice is due to enroll.
- A rejected electronic invoice resets the prompt-payment clock to when you resubmit a corrected one.
Frequently Asked
How do I submit an invoice to the Department of Defense?
Through Wide Area Workflow (WAWF, now iRAPT within the Procurement Integrated Enterprise Environment, PIEE). DFARS 252.232-7003 generally requires electronic submission of payment requests and receiving reports for DoD contracts. You register in PIEE, enter the invoice with the routing codes from your contract, and the system routes it to the acceptor and payment office.
What is the Invoice Processing Platform (IPP)?
IPP is the Treasury Bureau of the Fiscal Service's electronic invoicing system that many civilian agencies require contractors to use for submitting invoices. Like WAWF on the DoD side, it captures invoices and acceptance electronically and enforces proper-invoice content. Check your contract's invoicing instructions to confirm whether IPP (or another portal) is mandatory.
Primary Sources
- FAR 32.905 — Payment documentation and process (proper invoice)
- DFARS 252.232-7003 — Electronic Submission of Payment Requests and Receiving Reports
- Wide Area Workflow / PIEE
- Invoice Processing Platform (IPP) — Treasury Fiscal Service
Plain-English reference, not legal, accounting, or financial advice. Payment and financing terms are set by each contract, and the FAR is amended from time to time — always read the actual contract clauses and invoicing instructions, confirm the applicable procedures with the contracting officer and payment office, and consult qualified counsel or an accountant for your specific situation before relying on this.
Change log (1)
- LaunchedPublished the federal contract financing & payment methods reference covering how an SDVOSB gets paid — invoice payment and the Prompt Payment Act (FAR Subpart 32.9 / 52.232-25), progress payments based on cost (FAR Subpart 32.5 / 52.232-16), performance-based payments (FAR Subpart 32.10 / 52.232-32), commercial product & service financing (FAR Subpart 32.2 / 52.232-29 & -30), construction progress payments and retainage (FAR 32.103 / 52.232-5 & -27), cost-reimbursement and T&M public vouchers (FAR 52.216-7 / Subpart 42.7), payment by electronic funds transfer through SAM (FAR Subpart 32.11 / 52.232-33), electronic invoicing via WAWF and IPP (FAR 32.905 / DFARS 252.232-7003), assignment of claims for bank financing (FAR Subpart 32.8 / 52.232-23), and contract debts and government offsets (FAR Subpart 32.6 / 52.232-17) — each with an at-a-glance quick-facts card, a when-it's-used list, a key-features table, an SDVOSB cash-flow angle, a how-to-get-paid checklist, watch-outs, FAQPage, Article, Dataset, and BreadcrumbList structured data, primary-source citations, and cross-links into the glossary, how-to guides, FAQ, contract types, clauses, forms, thresholds, and the price-to-win and limitations-on-subcontracting calculators.