Fourteen suites. Two different purchases. One honest table each.

Requisition, approval, sourcing or tender, evaluation, award, contract, purchase order, receipt, invoice, three-way match and payment status — in one system, on one database, with one audit trail. No stage handed to a second product, no re-keying at a boundary, and the whole cycle reconstructable as one story.

One plain-language box. Every derived value names the record it came from, and ambiguity refuses rather than guesses. The estimated value and triage answers are never derived — the two things a person must own. It consults contracts and suppliers, so it can say “there is already a contract for this” while that is still cheap to hear.

A first-class schedule: named authority levels, per-department bands, “A or B” alternatives, a quorum of distinct people, segregation of duties, split-purchase detection, and a band no foreign-currency figure can slip under. Ivalua reaches the same place by configuration; nobody else ships it as a construct.

Available = budget − pre-commitment − commitment − actual pulled from the general ledger. Over budget forces an admin decision and a written justification; an unknown position counts as over; a foreign-currency figure cannot slip under a band. Checked against posted actuals, not our own records.

All four are first-class objects rather than notes on a PO, and the order is pushed as a real commitment to the eight connected ledgers that have a purchase-order document.

A stock ledger across locations, reorder points, automated replenishment runs and bills of materials with a produce action — and, since September 2026, batch and lot identification with a trace from one batch to every place it went, expiry on the stock with a first-expired-first-out order, unit-of-measure conversion declared per item, landed cost allocated across a consignment on a stated basis, and non-conformance recorded at receipt against the batch. More than any of them ship inside the procurement product itself. SAP's and Oracle's inventory is S/4HANA and Fusion ERP: a different product, a different licence.

Named evaluators scoring individually, then consensus with a recorded fallback when agreement fails. Sealed bids with an explicit unseal, mandatory criteria as pass/fail before scoring, controlled negotiation disclosure, per-bidder debriefs and an audit binder. The rank a bidder was shown is stored rather than recomputed, because a challenge asks what they were told at the moment they bid. Commercial suites score bids; few defend the score afterwards.

Derived from receipts, invoices, returns and invitations — not typed in once a quarter. Compliance driven by category requirements, qualification that expires by segment, risk taking the worst of its parts. Most modules here are still survey-and-scorecard.

Clause rules that change by jurisdiction and entity type, generated documents, legal/commercial/risk gates before signature, milestones that certify, invoice, pay and release retention. A real hierarchy from master agreement to statement of work to amendment, with a cycle refused. Redline writes as well as reads, emitting a counter-proposal with genuine Word tracked changes. Bulk import where one error imports nothing.

A year of imported AP history classified retrospectively against UNSPSC, then read for what is only visible in aggregate: four suppliers for the same thing, a contract about to renew unexamined, maverick spend outside an agreement. Asked in plain language — and no model ever touches the data, because the question becomes a query, not the rows a prompt.

CFTA, NWPTA and federal floors encoded per entity category and province, with the minimum posting period, the standstill and the complaint route that follow from them. Read from the agreements themselves, not from a summary. CETA and CPTPP sub-central thresholds are added on request.

Statutory prompt-payment and holdback rules for all thirteen Canadian jurisdictions plus federal, and the UAE — each read from primary legislation. Bonds per contract, subcontractor disclosure, multi-lot tenders. Atlas states no legal date it lacks the figures for.

Route guidance, evaluation design, negotiation prep and category strategy written into the screens where the decision is made — not a help centre in another tab. Nothing else in either field attempts it.

Thirty-four narrated films, recorded against the running product and served from inside it — each screen offers the film for that screen. Re-recorded when the product changes, so a walk-through never survives the screen it described. Competitors ship a help centre and a services quote.

Hosted in Canada (Toronto) today, cloud only — and a dedicated instance in your own region is stood up when you sign, under the same licence. Pricing published on this site. Live in days to weeks, not an implementation programme.

Requisition, approval, sourcing or tender, evaluation, award, contract, purchase order, receipt, invoice, three-way match and payment status — in one system, on one database, with one audit trail. No stage handed to a second product, no re-keying at a boundary, and the whole cycle reconstructable as one story.

One plain-language box. Every derived value names the record it came from, and ambiguity refuses rather than guesses. The estimated value and triage answers are never derived — the two things a person must own. It consults contracts and suppliers, so it can say “there is already a contract for this” while that is still cheap to hear.

A first-class schedule: named authority levels, per-department bands, “A or B” alternatives, a quorum of distinct people, segregation of duties, split-purchase detection, and a band no foreign-currency figure can slip under. Ivalua reaches the same place by configuration; nobody else ships it as a construct.

Available = budget − pre-commitment − commitment − actual pulled from the general ledger. Over budget forces an admin decision and a written justification; an unknown position counts as over; a foreign-currency figure cannot slip under a band. Checked against posted actuals, not our own records.

All four are first-class objects rather than notes on a PO, and the order is pushed as a real commitment to the eight connected ledgers that have a purchase-order document.

A stock ledger across locations, reorder points, automated replenishment runs and bills of materials with a produce action — and, since September 2026, batch and lot identification with a trace from one batch to every place it went, expiry on the stock with a first-expired-first-out order, unit-of-measure conversion declared per item, landed cost allocated across a consignment on a stated basis, and non-conformance recorded at receipt against the batch. More than any of them ship inside the procurement product itself. SAP's and Oracle's inventory is S/4HANA and Fusion ERP: a different product, a different licence.

UBL 2.1 and CII/Factur-X parsed by local element name; a PDF read on a hard rule that an unreadable figure returns nothing rather than zero. A cumulative three-way match that tolerates part delivery, on a tolerance you set. Duplicates caught on the invoice number, not the amount.

cXML punchout, supplier-agnostic — proved live against Amazon Business with Amazon's own record coming back. Three bands on your figures, and the ceiling is the control: straight through under one threshold, one approver under the next, refused above.

The two rows above, taken together. Lots, rubrics and addenda on the running side; sealed bids, consensus with a recorded fallback, stored rank, debriefs and an audit binder on the defending side.

Derived from receipts, invoices, returns and invitations — not typed in once a quarter. Compliance driven by category requirements, qualification that expires by segment, risk taking the worst of its parts. Most modules here are still survey-and-scorecard.

Screened against the real files — OFAC, UN and UK OFSI — with no per-check fee. Bank-detail changes monitored as an event, not an edit; duplicate invoices caught on the supplier's invoice number; split purchases detected against the authority band they were splitting under.

Clause rules that change by jurisdiction and entity type, generated documents, legal/commercial/risk gates before signature, milestones that certify, invoice, pay and release retention. A real hierarchy from master agreement to statement of work to amendment, with a cycle refused. Redline writes as well as reads, emitting a counter-proposal with genuine Word tracked changes. Bulk import where one error imports nothing.

A year of imported AP history classified retrospectively against UNSPSC, then read for what is only visible in aggregate: four suppliers for the same thing, a contract about to renew unexamined, maverick spend outside an agreement. Asked in plain language — and no model ever touches the data, because the question becomes a query, not the rows a prompt.

CFTA, NWPTA and federal floors encoded per entity category and province, with the minimum posting period, the standstill and the complaint route that follow from them. Read from the agreements themselves, not from a summary. CETA and CPTPP sub-central thresholds are added on request.

Statutory prompt-payment and holdback rules for all thirteen Canadian jurisdictions plus federal, and the UAE — each read from primary legislation. Bonds per contract, subcontractor disclosure, multi-lot tenders. Atlas states no legal date it lacks the figures for.

Drafting a request from a sentence, suggesting a UNSPSC code, reading an invoice PDF, turning a spend question into a query. The data never goes to the model in analytics, and an unreadable figure returns nothing rather than a guess. No agent platform, deliberately.

Group, company, division, branch — with authority bands, budgets and approval routes that belong to the level they were set at rather than being copied down.

Route guidance, evaluation design, negotiation prep and category strategy written into the screens where the decision is made — not a help centre in another tab. Nothing else in either field attempts it.

Thirty-four narrated films, recorded against the running product and served from inside it — each screen offers the film for that screen. Re-recorded when the product changes, so a walk-through never survives the screen it described. Competitors ship a help centre and a services quote.

Hosted in Canada (Toronto) today, cloud only — and a dedicated instance in your own region is stood up when you sign, under the same licence. Pricing published on this site. Live in days to weeks, not an implementation programme.