Control plane and worker boundary already exist in-repo
FoundationThe current foundation already separates workflow control from document-intelligence execution.
Supplier payment protection for AP teams
Protect every supplier payment before it’s approved.
PO Walls helps finance teams verify supplier details, review invoices safely, and stop risky payment changes before approval.
FoundationPlannedLater
Verify before money moves.
Control wall
Built to slow the risky path down.
PO Walls is being built around supplier trust, invoice context, masked review, and explicit reveal or approval controls instead of scattered checks across inboxes and spreadsheets.
- Supplier changes stay inside a controlled trust model instead of living in email threads and memory.
- Invoices move through explainable review, not opaque risk scores or hidden automation.
- Sensitive payment details stay masked until a reviewer has the right context and permission.
Repo truth
Public claims stay tied to what already exists or is explicitly on the roadmap.
The site does not blur current foundation with future delivery. That matters when the product is pre-release and the control model is more important than hype.
Schema already models trust, invoices, jobs, notifications, and audit events
FoundationThe data shape is designed around workspace isolation and durable review state, even before the full product UI lands.
The roadmap is sequenced from trust registry to review and hardening
PlannedPO Walls is being built in a clear order: trust data, intake, deterministic review, alerts, then hardening and mailbox surfaces.
Workflow
From supplier trust to payment decision, one control model.
The roadmap builds PO Walls in the same order an AP team feels the risk: trust state first, controlled intake second, explainable review third, and a preserved decision trace after that.
Step 01
PlannedMap trust before approvals drift
Build a customer-local source of truth for suppliers, contacts, domains, and payment methods so reviewers stop relying on scattered context.
- Supplier registry and trust fields
- Versioned payment methods
- Verification-method capture
Step 02
PlannedIngest invoices into a controlled pipeline
Bring uploads into a tenant-aware workflow with durable jobs, object storage references, and explicit file lifecycle handling.
- Secure web upload
- Object storage and checksums
- Durable job creation
Step 03
PlannedReview with context instead of guesswork
Compare extracted invoice fields to trusted supplier data and keep sensitive bank details masked until someone has the right context.
- Explainable trust verdicts
- Masked viewer and controlled reveal
- Field-level comparisons
Step 04
PlannedKeep the decision trace after the invoice is gone
Preserve the reasoning around supplier updates, review actions, and suspicious events so auditability is built into the workflow.
- Audit events
- Notification routing
- Retention-aware file controls
Value pillars
A product story built around controls, not generic invoice automation.
Build trust around supplier records
PlannedPO Walls is designed around trusted supplier data rather than ad hoc reference checks at approval time.
Inspect every invoice with context
PlannedThe roadmap centers review around document data, trusted supplier context, and explainable matching outcomes.
Mask sensitive payment details by default
PlannedSensitive bank data is intended to stay behind explicit permissions and controlled reveal flows.
Make decisions that stay explainable and auditable
PlannedThe product direction prioritizes deterministic controls and traceable decisions over opaque scoring.
What PO Walls should feel like
A barrier before approval. A cleaner trust model before the next supplier change. A review screen that shows why something is safe, mismatched, unknown, or worth a second look.
Multi-tenant control substrate
FoundationWorkspaces, memberships, invoices, suppliers, jobs, and notifications already exist in the foundational schema.
Supplier trust registry
PlannedThe next product layer is a maintainable source of truth for supplier trust, payable accounts, and payment-method history.
Deterministic review
PlannedPO Walls is being built around explainable match and mismatch outcomes rather than black-box fraud decisions.
Mailbox surfaces
LaterGmail and Outlook concepts are explicitly on the post-MVP roadmap, not part of the current product promise.
FAQ
Clear answers for a pre-release product.
Is PO Walls live today?
The public site represents a pre-release product. The repo already contains the control-plane foundation, worker contract, and foundational schema, while the product workflows are still being implemented across the published roadmap.
Is this purchase-order software?
No. PO Walls is framed as supplier payment protection for AP teams. The name points to payables and payment operations, not to a purchase-order workflow.
What makes the product different from generic invoice automation?
The product narrative is centered on verification, masking, permissioned reveal, and explainable payment decisions instead of raw extraction or automation volume alone.
See the control model before the product surface is fully built.
Book a demo conversation to walk through the roadmap, the current repo foundation, and the AP workflows PO Walls is designed to protect.