Latest modification awareness
The latest effective contract modification controls CLIN quantity, price and funding comparisons.
Recurring WAWF / PIEE preflight and rejection control
Preflight WAWF billing before errors delay contractor cash
Saxum reconciles contract authority, invoice or receiving-report data and acceptance evidence before submission, then turns any rejection into a controlled correction worklist.
Start file-first without portal credentials. Customer-authorized provider transport is activated only after the customer account is qualified. No guaranteed external result.
Flagship product depth
Contract-to-cash control depth
Deeper deterministic controls reduce setup and recurring review work while preserving customer-controlled submission and qualification boundaries.
Three-way reconciliation
Contract, invoice and receiving evidence are reconciled before the correction package is released.
Funding and lifecycle evidence
Funding exhaustion, historical duplicates, days to acceptance and days to payment are made visible without predicting government action.
Review how Saxum separates internal execution from external proof →
Current WAWF transition — One Pay sunsets 31 January 2027. PIEE says affected contracts are receiving Pay DoDAAC modifications through 30 September 2026 and vendors must verify the latest contract/modification before invoicing because incorrect routing can cause rejection and payment delay. Read the current PIEE system notice →
Qualification: external proof pending. This executable engine is internally verified. Live source credentials, provider acceptance, recovery evidence, measured intervention, false-positive results and renewal proof are still required before production qualification.
Fail-closed reviewUnsupported facts remain unresolved.
Transparent changesCorrections receive a visible audit trail.
Least-data intakeOnly necessary information is requested.
Independent serviceNo agency or platform affiliation implied.
Reviewed 19 August 2026
Current system boundary
PIEE/WAWF returns rejected invoices and receiving reports for correction through the official workflow. Saxum diagnoses the supplied rejection path and prepares a controlled correction packet; government acceptance, entitlement and payment decisions remain external.
Recognize the failure
WAWF problems controllers see in the real workflow
PIEE documents vendor-rejected invoices and correction-required receiving reports, and current PIEE guidance requires the invoice Pay DoDAAC to match the contract in EDA. SAXUM translates those recognizable states into deterministic controls without pretending its internal codes are government rejection codes.
Pay DoDAAC disagrees with contract authority
Compare the invoice routing value against the latest supplied contract/modification or bound EDA/PDS authority before release.
Invoice number already exists in supplied history
Block a likely duplicate before it becomes another rejected or disputed billing cycle.
Invoice line cannot be tied to the supplied CLIN/SLIN population
Keep the line unresolved until contract authority supports it instead of guessing the mapping.
Invoiced quantity exceeds supplied acceptance evidence
Surface the acceptance gap before the authorized customer submits or resubmits.
PIEE boundary: official rejection messages, contract/EDA data and government workflow status remain authoritative. The labels above are SAXUM control codes used to organize the evidence and correction worklist.
The operational problem
Why the standard portal or checklist is not enough
A rejected document can sit between contract terms, line-item data, shipment evidence, acceptance roles and portal validations. The operational cost is delayed cash and repeated handoffs between billing, contracts and government personnel.
Truth boundary: Saxum controls preparation, evidence and technical review. It does not replace the customer’s legal, tax, accounting, scientific or regulatory professionals, and it does not control external acceptance.
Best-fit customer
GovCon accounting firms and consultants managing defense-contractor billing, plus individual small defense contractors
Problems this product helps control
WAWF and PIEE invoice or receiving-report workflows where routing, import processing, rejection evidence and downstream government status need controlled diagnosis.
What Saxum needs
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- WAWF or PIEE rejection message
- Invoice or receiving-report data
- Relevant contract, CLIN and shipment facts
- Prior accepted document, when available
The deliverable
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Plain-English rejection map
- Contract-to-document field crosswalk
- Corrected candidate where supported
- Missing-evidence and role-action list
- Payment-delay exposure summary
- Resubmission checklist
Controlled workflow
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Trace
Map the portal message to the document, contract and responsible role.
Reconcile
Check quantities, identifiers, dates, amounts and acceptance facts.
Correct
Prepare supported changes and separate unresolved contract questions.
Escalate
Give each stakeholder a precise action rather than a generic error dump.
GovCon firm workflow
One controlled billing desk across the firm's contractor portfolio
Keep each contractor segregated while reusing approved mappings, review policy and exception playbooks across the team.
Portfolio queue
Track contractor-specific invoices, receiving reports, deadlines, rejection states and payment evidence without mixing client records.
Preflight before rejection
Reconcile current contract authority, CLIN data, quantities, funding and acceptance evidence before the customer submits.
Customer-qualified activation
Begin with file-first shadow review; any PIEE/WAWF transport remains customer-authorized, credential-bound and separately qualified.
First-cycle outcome proof
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Commercial fit
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
Indicative pricing
$599 onboarding · from $599/month per contractor · adviser plans from $1,500/month
Recurring contract, acceptance, invoice and rejection exports can run on schedule. An authorized PIEE/WAWF user retains official submission and response responsibility.
Start a WAWF preflight assessment →Questions buyers ask
WAWF / PIEE Control FAQ
Direct answers on access, responsibility, deliverables and limits.
No. The contractor retains credentials and submission control.
No. Contract facts are authoritative and unresolved conflicts are escalated.
No. It is operational document control and rejection diagnosis.
Yes. A preflight can compare the draft against the supplied contract and prior accepted pattern.
Contractors with regular invoicing can reuse mappings, controls and an exception history.
Primary references
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 19 August 2026. Re-check before each engagement.
Related Saxum desks
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Evaluate before onboarding
Evaluate the WAWF workflow before onboarding
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.