Predictable software. Value-based setup.

Setup covers provisioning your dedicated environment plus the configuration work to get your hosts and suppliers wired up and validated. It’s quoted per project because the effort scales with how much bespoke logic you need — a straightforward mapping is a small fee; deep custom enrichment is scoped separately.

Plans carry a 1-year minimum. When you upgrade, your full configuration and validation history carries forward at no migration charge — you start a fresh term from the upgrade date.

Validations inspect and flag the wire against rules you define — nothing is changed. Translations actively rewrite the payload (units, codes, identity, extrinsics) on its way through. Inspecting is available from SE; mutating the live wire is Standard and up.

PunchProxy works with cXML-based punchout from major procurement platforms — including Coupa and Ariba — and others. The engine is wire-format-agnostic underneath, so it can also bridge toward emerging API-first and Peppol/UBL standards over time.

Yes. The Single-Supplier tier is two-sided: a buyer can make one nuisance supplier work, or a hard-to-connect supplier can use it as an off-ramp to onboard a customer they were struggling with — or win back one they’d otherwise lose because they couldn’t transact.

If a supplier can produce a flat file or an EDI 810, you can onboard them for structured invoicing: convert the format once and feed clean invoices into your host. We’re an e-invoicing on-ramp, not OCR or a full AP-automation suite — and the invoice ROI calculator shows when it pays for itself. (Custom invoice conversion starts at the Standard tier.)

Each customer runs single-tenant on its own dedicated, isolated cluster, database and routing snapshot — no shared multi-tenant store and no standalone admin login surface to expose. The dual-plane design is failover / load-balanced capable, and the codebase keeps a lean, auditable dependency footprint: it’s engineered to survive an IT security review, not generated to look impressive.

Absolutely. Many teams start with a single supplier or the SE tier to get visibility, then move to Standard once they need live translations on the production path — carrying everything they built forward.