Purchasing control workspace
VERIQAYCheck the supplier papers before you pay.
One workspace for cafés, shops, wholesalers, and importers — domestic or overseas. Match the purchase order to the supplier invoice. Missing stays unknown. Conflicts stay visible. A named person decides. VERIQAY never moves money.
- Never moves, holds or initiates money
- Every value linked to its source page
- No score, no green light. A person decides.
Sample order journey
Sample- Quote
- Specs
- Packing
- Discrepancy
- Draft request
- Promise
- Claim
- Payment review
Sample order journey — one connected case. Shipped today: the P0 checker, five CTO-018 modules, all ten CTO-019 workspace modules (PackMath through CompliancePack), and the retention loop (waiting-on, supplier playbook, cited chase email, supplier-reply paste). Capabilities beyond those freezes are not claimed as shipped.
Order case · PO-FIX-10000
Fictional Glassworks Co.
Source
Purchase order
- Qty 10000 pcs
- Unit price GBP 4.00
- Total GBP 40000.00
- 70% balance after pre-shipment inspection
Invoice
- Less deposit received GBP 12000.00
- Balance due GBP 28000.00
Inspection report
- Quantity: 9750 pcs
Evidence
Quantity
10000 pieces
ExtractedPurchase order · p.1Unit price
GBP 4
ExtractedPurchase order · p.1Total
GBP 40000
ExtractedPurchase order · p.1Deposit stated paid
GBP 12000
ExtractedInvoice · p.1Balance requested
GBP 28000
ExtractedInvoice · p.1Inspection quantity
9750 pieces
Third-party reportedInspection report · p.3Milestone condition · Deposit
Not in any document
UnknownMilestone condition · Balance
70% balance after pre-shipment inspection
ExtractedPurchase order · p.2
Decision
Review neededConfirm whether the inspection quantity counts inspected, packed, accepted or shipped units, and record who decided and why.
VERIQAY prepares evidence for a human decision. It never moves, holds, or initiates money.
- Keep your bank and payment provider
- No wallet, no escrow, no FX
- Export a decision packet that travels with your payment
The problem
The commercial truth is scattered across the whole order journey.
The quote sits in email. Specs live in a signed PO. Packing counts arrive as a PDF. A discrepancy note lands in chat. A draft correction request waits to be sent. A promise sits in a calendar. A claim gathers evidence in a folder. The balance review lands in finance. Before you release a milestone, someone rebuilds the story by hand.
Quote
Email thread
Specs
Signed PO
Packing
Packing list
Discrepancy
Chat note
Promise
Deadline reminder
Claim
Evidence folder
One purchasing control workspace
Every stage, every value and every open question for one order case, in one place — without moving money.
How it works
Open one order. Follow the whole case.
Five product screens you can use today. Evidence first, then deterministic checks, then a named decision — with workspace modules for packing math, specs, quotes, cost lines, inspections, supplier memory, scenarios, compliance packs, and the retention tools that keep open work visible.
Sample order journey
Sample- Quote
- Specs
- Packing
- Discrepancy
- Draft request
- Promise
- Claim
- Payment review
Sample order journey — one connected case. Shipped today: the P0 checker, five CTO-018 modules, all ten CTO-019 workspace modules (PackMath through CompliancePack), and the retention loop (waiting-on, supplier playbook, cited chase email, supplier-reply paste). Capabilities beyond those freezes are not claimed as shipped.
Step 01
Open an order case
Each purchase order gets one case in the workspace: the supplier, the milestone, open exceptions and the next action, all in one inbox.
app.veriqay.comSample
- Next action shown
- Exceptions counted
Step 02
Bring the journey documents in
Drop the PO, invoice and related files. Originals are stored privately and never altered. A new file becomes a new version, never an overwrite.
app.veriqay.comSample
- Original kept
- Versioned
Step 03
Check each value against its page
AI proposes candidate values, each with a quote and a page number. You confirm or correct them while the source page is highlighted beside you. Experimental modules can deepen terms, lots and beneficiary fields on the same case.
app.veriqay.comSample
- Cited to the page
- Extracted until you confirm
Step 04
Run the checks. Keep discrepancies visible.
Deterministic, versioned rules compare quantities, prices, amounts, currency, totals, duplicate numbers and deposits. A mismatch is flagged, never settled by a guess. ResolveDesk can draft a correction request you still send yourself.
app.veriqay.comSample
- Blocking for review
- Same inputs, same result
Step 05
Decide at payment review
A named reviewer records the decision and the reason. The packet lists the exact document versions and rule set used, ready to travel with your payment instruction — VERIQAY never sends the money.
app.veriqay.comSample
- Named reviewer
- Exact versions recorded

- Next action shown
- Exceptions counted
The workspace
Everything on one order case — easy to scan.
Four layers, one story. Short plain-language cards — not a feature laundry list. Every module below is frozen and available behind its feature flag where flagged.
Payment readiness
The core checker every buyer uses first.
Documents
Upload originals. Each file becomes a version, never an overwrite.
Evidence
Cited candidates wait until a named person confirms or corrects them.
Seven checks
Deterministic rules own arithmetic and mismatches — never a guess.
Named decision
Approve or reject with a reason. Eligibility is never an instruction to pay.
Worked example
The 10,000-bottle order.
A fictional importer orders 10,000 bottles for £40,000: a 30% deposit, then 70% after inspection. The deposit is recorded as paid and the supplier invoices the £28,000 balance. The inspection document reports 9,750 units within its own scope.
What the documents say
- bottles on the purchase order
- 10,000
- order total
- £40,000
- deposit recorded as paid
- £12,000
- balance on the supplier's invoice
- £28,000
- units in the inspection report, within its own scope
- 9,750
What VERIQAY says
Review neededReview required: apparent 250-unit difference. Confirm whether 9,750 is inspected, produced, packed, accepted or shipped, and whether the contract allows the remaining £28,000 to become payable.
What it will never do
- Tell you the correct payment is £27,300
- Hold back £700 on its own
- Treat an inspection count as units received
- Call the supplier a fraud
- Approve the payment for you
Fictional illustration from the product strategy. Not legal, financial or contractual advice.
What it checks
Seven deterministic checks. Zero guesses.
Rules own the arithmetic and the matching; the AI never does. Every check is versioned, so the same documents always give the same result.
Quantity
Invoice quantity against the PO, line by line. Cartons and pieces are never compared without a conversion you confirmed.
Unit price
Invoice unit price against the PO unit price, each per its own document's unit.
Line amount
Each stated line amount against that document's own quantity and unit price, on the PO and on every invoice.
Currency
Every amount in one currency. Mixed currencies are flagged. Nothing is ever converted.
Invoice total
The invoice's stated total against the sum of its own lines.
Duplicate invoice number
The same invoice number on another invoice from the same supplier. Exact matches only, and you can explain a genuine revision.
Deposit and balance
Invoice total less the deposit it says was paid, against the balance it requests. A check, never an amount to pay.
Six checks block for review. A duplicate number is a warning you can explain.
When an input is missing or units differ, a check says "Not compared" instead of guessing.
Honest states
Unknown is an answer, not a gap to fill.
Every value carries its provenance. Missing values stay unknown, disagreeing values stay conflicted, and nothing the AI read becomes confirmed until a named person says so.
First-class states
- Unknown
No document holds it. It will not be filled with a plausible number.
- Conflicted
Documents disagree. Both values stay on screen until someone resolves it.
- Uploaded
The file is stored. Nothing has been read from it yet.
- Extracted
Read from a document with a quote and a page. Waits for a person.
- Buyer-confirmed
A named person on your team confirmed it against the source.
- Third-party reported
Reported by someone else, such as an inspector, and kept within its scope.
- Assumed
A person chose to proceed on an assumption, with a written note.
- Superseded
Replaced by a newer version and kept in the history.
A decision moves through clear states
- Draft
- Missing evidence
- Review needed
- Eligible for your approval
- Approved by reviewerRejected by reviewer
Eligible for human approval is not "safe to pay". A named person decides.
Why VERIQAY
Built for the supplier-purchase review.
Payment platforms move money well, AP tools match bills, and sourcing suites run supplier operations. VERIQAY is the evidence and exception workspace around one order case — domestic or overseas — before a named person decides.
| Spreadsheets and email | Payment platforms | AP automation | Sourcing suites | VERIQAY | |
|---|---|---|---|---|---|
| Each value linked to the page it came from | NoBy hand | Varies by product | Varies by product | Varies by product | YesWith the page highlighted |
| Missing and disagreeing values kept visible | No | PartlyWithin tolerance rules | PartlyWithin tolerance rules | Varies by product | YesNever auto-resolved |
| Keep your bank and payment provider | Yes | NoPayments run through them | Varies by product | Varies by product | YesWe never touch the money |
| Inspection scope kept apart from quantities received | No | No | No | Partly | YesThird-party reported, scoped |
| Product spec vs inspection/packing text compared for review | No | No | No | Varies by product | YesSpecGuard on the Sample case — human review, not certification |
| Open work and supplier follow-ups stay on the order case | PartlyScattered threads | No | Partly | Varies by product | YesWaiting-on, playbook, cited email, reply paste |
| A named person makes every payment decision | Yes | PartlyAuto-approval is possible | PartlyAuto-approval is possible | Varies by product | YesAlways, with a reason |
Based on public product pages reviewed in October 2026. Your setup may differ, and many teams use VERIQAY alongside these tools.
Boundaries
The things we will never do are the product.
Never moves money
VERIQAY prepares evidence for a human decision. It never moves, holds, or initiates money.
No score, no green light
Nothing rates a supplier or a payment with a single number, and there is no all-clear. Each reason for doubt stays visible on its own.
AI proposes, people decide
The AI suggests values with quotes and drafts explanations. It never calculates, classifies a discrepancy or approves anything.
Records you can't quietly edit
Decisions are append-only. New evidence marks an old decision as stale rather than rewriting it.
Your data stays yours
Every record is scoped to your organisation. Another organisation's data simply does not exist for you.
Originals kept private
Documents sit in private storage and open only through short-lived links after an access check.
Free to use
Use VERIQAY free.
Create an organisation, upload documents, run checks, and record named decisions. Access stays free for now. For the first twelve weeks we ask a short weekly product-feedback questionnaire; you can also send free-text feedback anytime.
Questions? Email us — no form and no tracking on this site. [email protected]
FAQ
Straight answers.
One connected order journey from quote through payment review, for UK businesses buying from suppliers at home or overseas. Built today: the payment-readiness checker; five CTO-018 modules (Trade Replay, TermMap, LotLens, ResolveDesk, BeneficiaryDiff); all ten CTO-019 modules from PackMath through CompliancePack; and the retention loop (waiting-on, supplier playbook, cited chase email, supplier-reply paste). Modules may sit behind feature flags and are not on for every organisation. VERIQAY never moves money.