PIEE is the Procurement Integrated Enterprise Environment, a DoD procurement and payment-evidence suite that includes WAWF, EDA, MDO, GFP, IUID, JAM, SPM, closeout, solicitation, reporting, and related support capabilities.
PIEE blueprint for procurement, payment evidence, GL, and disbursement lineage
Procurement Integrated Enterprise Environment / PIEE Suite Blueprint
Explore PIEE as the DoD procurement and payment-evidence suite connecting solicitation, award, EDA, MDO, WAWF, myInvoice, GFP, IUID, JAM, SPM, closeout, purchase-card support, ERP GL systems, entitlement, DFAS disbursing, Treasury/CARS/IPAC, DDRS/GTAS, and audit evidence.
Core PIEE lineage scenarios
Award -> WAWF -> GL -> Pay -> TreasurySystem profile
What it is, who uses it, and why it matters
Vendors, contracting officers, contract specialists, CORs, inspectors, acceptors, pay officials, LPOs, property users, auditors, DFAS/pay offices, ERP/accounting teams, and DoD procurement oversight users rely on PIEE data.
It supports solicitation/award evidence, contract repository access, modifications and orders, invoice submission, receiving, inspection, acceptance, cost vouchers, contract financing, property records, COR appointments/surveillance, payment status, closeout, and audit support.
Operational DoD enterprise environment; public PIEE pages show version 7.7.x-era training and public access points, while exact production integrations require authorized DoD/PIEE documentation.
PIEE standardizes procurement-to-payment evidence so GL systems can post supported obligations, AP, accruals, expenses, assets, ULOs, and outlays, and so disbursing/Treasury/audit teams can trace payment from contract to statement.
The blueprint models 12 major PIEE feeder/partner categories across procurement, accounting, payment, Treasury, reporting, and audit.
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected PIEE scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Requirements, Award, and Contract Sources
PIEE pre-award, award, contract repository, modification, delivery order, vendor, CAGE, DoDAAC, and procurement-data sources.
PIEE Suite Applications and Workflow
WAWF, EDA, MDO, GFP, IUID, JAM, SPM, closeout, solicitation, purchase-card, and operational support capabilities.
Procurement and Payment Documents
Invoice, receiving report, combo, cost voucher, progress payment, performance-based payment, property transfer, acceptance, COR, and closeout detail.
ERP GL, Entitlement, and Disbursing Handoff
Interfaces and control points that connect PIEE evidence to accounting systems, pay entitlement, DFAS/disbursing systems, and Treasury classification.
Data Warehouse, Risk, and Reporting
PIEE data warehouse, SPRS, Advana-facing data, EDA extracts, payment status, audit sampling, and enterprise reporting.
Financial Statement and Audit Outputs
Obligation, ULO, AP, expense, asset, outlay, FBWT, SBR, SNC, GTAS/DDRS, and contract-file audit outputs.
Scenario lineage explorer
Award to WAWF Acceptance, ERP GL, Entitlement, and Disbursement
Traces standard procure-to-pay from award source and EDA through WAWF invoice/receipt/acceptance, ERP GL posting, entitlement, DFAS disbursing, Treasury/CARS, and statement support.
Business flow
- Award-writing and EDA establish contract, CLIN, funding, vendor, payment-office, and delivery terms.
- The vendor or government submits WAWF invoice, receiving, combo, or related payment-support documents.
- Authorized government users inspect, accept, reject, review, certify, process, hold, recall, or void documents based on role and workflow.
- ERP/accounting systems post obligation liquidation, AP, accrual, expense, asset, inventory, or GL effects using PIEE evidence.
- Entitlement and DFAS/disbursing systems certify and pay the voucher, while CARS/Treasury and FBWT records support outlay reporting.
AI / audit exception tests
- award not in EDA
- WAWF reject unresolved
- acceptance missing
- ERP AP mismatch
- payment not tied to WAWF
- FBWT difference unresolved
Audit lens
Where the AI UoT analyzer should watch
These are the places where completeness, accuracy, timeliness, and traceability commonly break.
Completeness
Source events missing from the ERP, subledger items not posted to GL, or financial statement balances without supporting populations.
Traceability
Broken reference keys across feeder, interface, subledger object, GL document, trial balance, and statement line item.
Timing
Authorization, receipt, invoice, voucher, payment, and GL posting dates crossing accounting periods without appropriate accrual or adjustment.
Supportability
Transactions posted to GL without valid approval, contract, receipt, invoice, voucher, asset record, or other audit evidence.
Enterprise infrastructure
Support services that make the blueprint work
Award and Contract Repository
Solicitation, award-writing, EDA contract access, MDO modifications/delivery orders, PDS data, attachments, CLIN/ACRN, vendor, and payment-office context.
WAWF Payment Evidence
Invoice, receiving report, combo, cost voucher, financing request, inspection, acceptance, rejection, recall, void, pay official, and LPO workflow evidence.
Property and COR Oversight
GFP, IUID, property transfers, JAM appointments, SPM surveillance, service performance evidence, acceptance support, and asset/property traceability.
ERP and GL Integration
Obligation, AP, accrual, expense, asset, inventory, ULO, GL, USSGL, TAS, and interface reject reconciliation across GFEBS, Navy ERP, DAI, DEAMS, LMP, DLA EBS, CEFMS, and other accounting systems.
Entitlement and Disbursing
Pay office, entitlement validation, voucher certification, DFAS payment, ADS/DCAS/DDS disbursing records, payment status, CARS/Treasury classification, and FBWT reconciliation.
Reporting and Audit
PIEE/WAWF data warehouse, EDA extracts, SPRS risk support, Advana-facing analytics, document aging, audit sample packages, DDRS/GTAS support, and statement tie-outs.