FousWide Area Workflow
Get your WAWF invoice statuses through an API
Read the status of your WAWF invoices and receiving reports, the payment details behind a Paid document and your Rejected Invoices folder with one API call each. Workflows can check that folder each weekday morning and send new Paid vouchers to accounting.
Works with your own Wide Area Workflow account. Fous is an independent product.
What you can build on WAWF
Check document status by contract
Build thisSearches the Document History Folder by contract number and CAGE code and reads each document's type and status, from Submitted to Paid.
- Takes
- Contract number, CAGE code (optional), Pay Official DoDAAC (optional)
- Returns
- Contract number, invoice or shipment number, document type, status, Pay Official DoDAAC
Get payment details for a paid invoice
Build thisOpens the Paid status link on an invoice found in the Document History Folder and reads the payment details.
- Takes
- Contract number, invoice number
- Returns
- Disbursing station, voucher number, payment date, amount, EFT trace or check number
List rejected invoices and receiving reports
Build thisReads the Rejected Invoices Folder and the Rejected Receiving Reports Folder in the Vendor working folders.
- Takes
- CAGE code (optional)
- Returns
- Folder, contract number, invoice or shipment number, document type, Pay Official DoDAAC
Correct and resubmit a rejected invoice
Build thisOpens a document in the Rejected Invoices Folder, changes only the data elements you give and resubmits it.
- Takes
- Contract number, invoice number, corrected fields and values
- Returns
- Contract number, invoice number, status
Automate WAWF with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
New rejected invoices and receiving reports
Build this- Starts
- Every weekday at 7:00
- Step 1
- List the documents in the Rejected Invoices and Rejected Receiving Reports folders.
- Step 2
- Keep the ones that were not there on the last run.
- Step 3
- Email you each one with its contract number, invoice or shipment number and document type.
Paid invoices, handed to accounting
Build this- Starts
- Every weekday at 17:00
- Step 1
- For each contract you name, check the status of its documents in the Document History Folder.
- Step 2
- Keep the invoices that changed to Paid since the last run.
- Step 3
- Get the payment details of each and post them to your accounting system's webhook.
Weekly report of unpaid WAWF invoices by status
Build this- Starts
- Every Monday at 8:00
- Step 1
- For each contract you name, check the status of its invoices.
- Step 2
- Keep the invoices that are not Paid or Void.
- Step 3
- Group them by status, from Submitted to Processed, and email you the report.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Check document status by contract” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "piee.eb.mil/check_document_status",
"input": {
"contract_number": "W00000-25-C-0117",
"cage_code": "1ABC2"
}
}'
{
"status": "completed",
"data": {
"contract_number": "W00000-25-C-0117",
"cage_code": "1ABC2",
"documents": [
{
"invoice_number": "ACME0042",
"shipment_number": "ACME042",
"document_type": "Invoice and Receiving Report (Combo)",
"status": "Paid",
"pay_official_dodaac": "HQ0000"
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
WAWF’s own options
WAWF takes vendor documents three ways: web entry, EDI and SFTP flat files. EDI and SFTP are for sending invoices and receiving reports in volume, and are set up and tested with the PIEE Help Desk and the Joint Interoperability Test Center. PIEE documents no web API for vendors: statuses and payment details are read on screen in WAWF, and myInvoice sends Advice of Payment notifications on request.
| Option | What it covers | What it takes |
|---|---|---|
| EDI | Invoices as X12 810, receiving reports as 856, Combo documents as 857, attachments as 841, with a guide for each. | A Help Desk ticket, forwarded to JITC, where a technician tests your files. Third-party companies may send on your behalf. |
| SFTP flat files | The same invoices and receiving reports sent as flat files, in file layouts tested with JITC. | Setup and file testing through the PIEE Help Desk and JITC, as for EDI. |
| myInvoice | Data for your own CAGE or NCAGE codes only, and Advice of Payment notifications on request. | A PIEE account with the role activated by your Contractor Administrator. |
| WAWF by hand | Create Document, the Document History Folder, the Rejected Invoices and Correction Required folders, one search at a time. | A PIEE Vendor account for each person, activated by your company's Contractor Administrator. |
Read on November 12, 2026: PIEE vendor getting started, WAWF EDI guides, WAWF Vendor role training.
Signing in to WAWF
PIEE signs vendors in with a user ID and password and a second step by email or an authenticator app; certificates are optional for vendors and skip that step. Sessions end after 30 minutes idle. With Fous you sign in once through PIEE's own sign-in with your own account: the login is sealed with AES-256, the second step is handled when PIEE sends it by email, and an expired session is signed back in.
Worth knowing
- Log in within 34 days
- PIEE deactivates users who have not logged in within 34 days, and a session expires after 30 minutes of inactivity.
- One login per person, roles from your CAM
- PIEE logins are individual and should not be shared. Every vendor group needs a Contractor Administrator (CAM), who activates the Vendor role for each person under your CAGE code.
- An invoice is voided only after a rejection
- You can void an invoice only after the LPO or Payment Official rejects it, and never once an EDI transaction was sent. Otherwise you ask the next step in the workflow to reject it back.
- Saved drafts last 7 days
- Documents in the Saved Documents Folder are kept for 7 days, or 30 days for DLA Energy documents.
More in Government: US federal
- BSA E-Filing System
- FINRA Gateway
- PostalOne
- USPS Business Customer Gateway
- Invoice Processing Platform
- FMCSA Drug & Alcohol Clearinghouse
- E-Verify
- EPA Central Data Exchange
- SAM.gov
- CM/ECF
- EFTPS
- FBI NICS E-Check
- FLAG
- HUD Secure Systems
- USCIS online account
- IRIS Taxpayer Portal
- Motus
- TRACS / iMAX
- USPTO Patent Center
- EDGAR Filer Management
- COD
- IRS e-Services
- IRS Tax Pro Account
- EIV
- USPTO Trademark Center
- SSA Business Services Online
- NetDMR
Other industries: Cal eProcure, INTIME, SIDES E-Response, Fastenal, SAP Fieldglass, Henry Schein online ordering.
Frequently asked questions
No web API for vendors appears in PIEE's documentation. WAWF accepts invoices and receiving reports by web entry, EDI (X12 810, 856, 857) or SFTP flat files, set up and tested through the PIEE Help Desk and JITC. Statuses and payment details are read on screen in WAWF, and myInvoice sends Advice of Payment notices on request.
Its status reads Paid, and the Paid link shows the disbursing station, voucher number, payment date, amount and EFT trace or check number. Before that, Processed means the pay office has it in its entitlement system, and Extracted means it was sent there but not yet processed.
Open it from the Rejected Invoices Folder, correct only the data elements that need it and resubmit; its status then reads Resubmitted. You can also void it once it has been rejected by the LPO or Payment Official, unless an EDI transaction was already sent.
No. PKI certificates are optional for vendors. You can sign in with a user ID and password and a second step by email or an authenticator app. Users who sign in with a CAC or software certificate skip that step.
No. Fous is an independent product. You use it with your own PIEE account, and a method reads and does only what that account can.
Put Wide Area Workflow behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextE-VerifyEPA Central Data ExchangeSAM.govCal eProcureHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Wide Area Workflow (US Department of Defense). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.