AI for procurement.
The whole procurement lifecycle, from request to reconciliation, on your own servers.
Procurement ensures the best outcome for every dollar the company spends.
We hold ourselves to the same standard.
Procurement teams are asked to justify every purchase: the price, the risk, the value delivered. The software they buy should pass that test too.
Priced on what it processes
Pay per invoice or one flat annual fee. No per-seat fees, so adding approvers never adds cost.
No new vendor risk to vet
It runs on your servers, inside your security controls. There's no hosted service to assess, monitor and re-review every year.
Every claim shows its evidence
Every status names its source and every figure has one written definition. Nothing is estimated, and nothing is called done until your ERP says so.
One green tick hides four different facts.
Reviewed is not approved. Approved is not posted. Posted is not paid. Most tools fold all of it into one badge, and people pay on the badge. Postver keeps every fact apart, each with its source.
Each field traced to its place on the page
Engineering rule, version 3
Read back from NetSuite, not assumed
A downloaded payment file is not a payment
What Postver refuses to do.
Our principles are written as prohibitions. Each one is a decision on record, not a preference, and the product is built so it can't quietly break them.
Call a downloaded file “paid”.
Paid, part-paid, returned and reversed come only from a payment your ERP has recorded.
Say “AI approved”.
Models suggest and say they're AI. A person decides, or a published, versioned rule that's named on the record.
Let one person pay alone.
The person who prepares a payment run and the person who approves it are always two different people. No administrator can waive that.
Retry blindly.
When your ERP doesn't answer, “outcome unknown” is a state with an owner. Nothing posts twice.
Go touchless on a hunch.
An invoice skips a person only inside an exact rule backed by measured accuracy. Any drift sends it back to review.
Take a supplier's word as an instruction.
“Change our bank account” in an email or PDF is just text. Bank details change only in your ERP.
Balance tax away.
Four tax records stay apart. A difference is shown with its reason; it's never relabeled as rounding.
Call preparation a filing.
Reconciliations, credit reports and 1099 readiness are internal preparation. Nothing here files a return.
Send data somewhere undeclared.
One page lists every place your data goes. A new destination needs a second person's approval first.
Estimate a number.
Every figure is computed from recorded events for a stated time. If your ERP data is stale, it says “not computed”.
How an invoice moves.
Five stages, each visible to the people who need it. Anything unresolved stays next to the decision, never buried in an activity log.
From your own mailbox or the supplier portal. The same invoice sent both ways becomes one payable.
Every extracted field points to its place on the page, and stays unverified until a person reviews it. On long invoices, select lines, code them once and fill down — every line is still checked.
Against purchase orders from your ERP or Coupa, receipts and contracts, with remaining capacity shown in units.
One versioned playbook holds your routing, reminders and escalations, in plain language. Delegates act alongside owners, the deadline never quietly resets, and approving from email still asks the approver to confirm it's them.
Invoices above $50,000 in Engineering: department approver, then Finance. Remind after 2 business days, escalate after 4.
Engineering · approvedSep 1, 2026, 11:20 AM ET
Finance · either can approve, both can see itDue Sep 3, 2026, 6:00 PM ET
Sent, acknowledged and read back. If the line drops mid-send, Postver says so and reconciles.
Pay what's ready. Hold only what isn't.
Payment Ready is a gate you can read: seven checks, each one visible, evaluated for every installment on its own. A dispute on one line holds that amount. The rest of the invoice can still go out in the next run.
- Per installment, not only per invoice. If a dispute grows after an installment joins a run, it's checked again and leaves the run before the file is made, with the reason.
- Early-payment discounts such as 2/10 net 30 carry a pay-by date on the invoice, the run and the forecast. A discount counts as taken only when your ERP shows it.
- Bank details come from your ERP, masked. Instructions printed on an invoice are ignored.
- Holds carry a reason and an owner, so someone is always on it.
AI suggests. People decide.
Postver's AI reads, drafts and suggests, and it always says it's AI. It never approves, posts or pays. When an invoice passes without a person, a published rule made that call, and the rule's name and version are on the record.
- Evidence first. Every suggestion cites the page or record it came from.
- Your model route. Each suggestion shows which model answered and where the data went.
- Rules are versioned, reviewed by a second person and never edited in place.
- Start from your own policy. The policy reader drafts approval rules from your written purchasing policy; a person reviews and publishes them.
Code line 2 to GL 6120 Software subscriptions, cost center ENG-02. The last six invoices from this supplier were coded this way.
Two people for every payment run.
The person who prepares a run cannot approve it. The checker sees the exact manifest, totals and control counts, and signs in again before approving. Postver writes the payment file; your bank moves the money; your ERP tells Postver what was actually paid.
- Downloaded is not paid. Status changes only on evidence from your ERP.
- Same file, same bytes. A re-download is identical, and any bank-detail change stops the run.
Prepared the run ≠ RARachel
Approves the run
Know what you owe. Including what your ERP hasn't seen yet.
Your ERP only knows an invoice once it's posted, so the liability that matters at month end sits in inboxes. Postver adds every open bill in your ERP to every invoice still on its way, and counts each one once.
- Twenty-five reports, each answering one question: liability and aging, close readiness, cash due, payment files, tax, controls and suppliers.
- One definition per number. Open any headline figure to see how it's calculated, the records behind it, and export them with the scope and time in the file.
- Honest about freshness. Every figure shows when your ERP was last read. If that's stale, the figure says so instead of mixing old and new.
Tax, country by country.
Each entity follows its own country's rules, in one workspace. Postver keeps four records apart: what the supplier billed, what your policy expects, what your reviewer approved and what your ERP posted. Choose a country to see its review.
| Component | Supplier billed | Policy expects | Reviewer | NetSuite |
|---|
A portal suppliers can read at a glance.
Suppliers submit invoices and tax documents, and follow each one in plain words. They never see your internal notes or bank details. A payment date appears only when it can be estimated, and it's labeled as an estimate.
- Up to three equal logins per supplier. No admin, no hierarchy. A supplier down to one login is reminded to add another, and never blocked.
- Remittance advice only after your ERP records the payment.
- Invitation only. Sensitive changes ask the supplier to sign in again.
Your servers. Your data.
Postver installs in your environment. Invoices, documents, backups and AI calls stay where you put them, and one page shows exactly where that is. A new destination needs a second person's approval before any data flows to it.
One less vendor to vet.
Postver runs in-house, on your infrastructure. Your supplier, bank and tax data stays on your own systems, and every team that signs off has less to review.
Less risk
Supplier, bank and tax records stay inside your own security controls from day one.
One less security posture
No hosted service to assess, monitor and re-review every year.
Easier sign-off
Procurement, IT and legal review software you run yourself, not a new place your data lives.
Residency, settled
Data residency and sovereignty follow from where you install it: your data center, your country, your cloud account.
An audit log you can check
Every action records who acted, on whose behalf and under which rule version. The log is hash-chained, so gaps show.
Recovery you can see
The age of your last recovery point is always on screen. Amber at 15 minutes, red when it's heading past 60.
Configuration with a second pair of eyes
Rules go from draft to test to review to publish. Nobody approves their own change.
Start with what you already have.
Start with accounts payable, anywhere in the world. Grow into the rest of procurement on the same platform.
Install
Run Postver in your own environment, next to the systems it serves.
Connect
Your ERP, starting with NetSuite. Coupa for purchase orders. Your invoice mailbox and identity provider. Postver shows what each connection can and cannot do.
Bring your records
Import people, open invoices and contracts. A dry run lists every row-level problem before anything is committed.
What we're building now.
One self-hosted platform for procurement across the whole company.
Pricing you can plan around.
Two ways to pay. Choose the one that fits your volume.
Per invoice
Pay only for the invoices Postver processes. Suits growing or seasonal volume.
- No per-seat fees
- Costs rise and fall with your volume
Flat annual
One annual fee with unlimited invoices. Suits steady, high volume.
- No per-seat fees
- The same price whatever your volume
Postver vs Zip.
Both are procurement platforms for the whole company. Zip runs in its cloud and is priced by quote. Postver runs in your environment and is priced on your invoices.
Switching from Zip?
Show us your current Zip order form and we'll take 60% off your Postver price. No questions asked.
| Topic | Postver | Zip |
|---|---|---|
| Where it runs | In your own environmentNext to your ERP, on servers you choose | Zip's cloud serviceHosted and operated by Zip3 |
| Your invoice data | Stays with youYour database, document storage, backups and AI route | Held in Zip's cloudTransfers outside the EEA and UK rely on the EU-US Data Privacy Framework or standard contractual clauses1 |
| Pricing model | Two simple optionsPer invoice processed, or a flat annual fee with unlimited invoices | Quote onlyNo public prices2 |
| What you pay for | Invoices, not peopleNo per-seat fees | Platform, seats and modulesPlatform fee, per-seat pricing, add-on modules, and separate implementation fees2 |
| Reported cost | Priced on your volume60% off when you switch from Zip | About $88,000 a yearMedian of 75 purchases; range $26,586 to $214,7502 |
| Built for | Company-wide procurementStarting with accounts payable, for teams anywhere in the world | Company-wide procurementEmployees who request, and the teams that approve and buy3 |
| Coverage | Invoice to payment, livePurchase requests, purchase orders, contracts, budgets and global payments are being built now | Intake to paymentIntake, sourcing, contracts, risk and payments3 |
- Zip, zip.com/trust. Checked Sep 29, 2026.
- Vendr, Zip HQ pricing, based on 75 purchases. Updated Feb 2026.
- Zip, zip.com. Checked Sep 29, 2026.
Zip is a trademark of its owner. Postver is not affiliated with Zip. The comparison above uses public information as of Sep 29, 2026; if something has changed, tell us and we'll correct it. Switch offer: 60% off Postver's price when you show a current Zip order form.
Questions.
Does the AI approve invoices?
No. AI output is always a suggestion that a person reviews. Invoices can pass without a person only under a published, versioned rule, such as an exact three-way match, and the record names that rule.
Does Postver send payments?
No. It prepares payment files that your team uploads to your bank. An invoice is marked paid, partly paid or returned only when your ERP records it.
Which ERP does it work with?
NetSuite first. More ERP connectors are on the way, and your ERP always stays the system of record.
We buy through Coupa. Does Postver work with it?
Yes. Postver reads purchase orders from Coupa and matches invoices against them, so purchasing stays where it is.
Where does it run?
In your environment. Your database, document storage, mailbox, identity provider and AI route are all yours, and the “Where your data goes” page lists each one.
What can suppliers see?
Their own invoices and documents, a plain status for each, and remittance advice after payment. Never your internal comments or anyone's bank details.
How do we know what we owe at month end?
The complete liability report adds every open bill in your ERP, including bills entered there directly, to invoices that haven't reached your ERP yet, each counted once. Every headline number has one written definition you can open, down to the records behind it.
Does it handle early-payment discounts?
Yes. Discount terms give each invoice a pay-by date, shown on the invoice, the payment run and the cash forecast, and the discounted amount goes in the payment file. A discount counts as taken only when your ERP records the payment that took it.
Can one installation serve entities in different countries?
Yes. Each buying entity keeps its own currency, tax registrations and rules, and people switch between the entities they are allowed to see. US and India tax rules are live; Australia, the EU, the Middle East and Southeast Asia are being built now.
See Postver
with your own team.
Leave your work email and we'll set up a walkthrough on your ERP, with the entities and tax rules that matter to you.