What NetSuite does with vendor bills on its own, what you can add on top, and where the work actually goes once the bill has been read.
Runs on NetSuite and NetSuite OneWorld, across subsidiaries and currencies. Your ledger stays where it is.
What NetSuite already does
More than most comparisons admit, and the part that is there works.
Bill Capture reads a PDF or an emailed attachment and produces a draft vendor bill, with the vendor identified and the header fields filled in. You review and submit.
Three-way matching is native. With purchase orders and item receipts in place, NetSuite compares quantity and rate across the purchase order, the item receipt and the vendor bill, and holds the bill when a line falls outside your variance settings.
SuiteApprovals routes bills for approval on your own criteria, and approvers work inside NetSuite without a second login. Teams tend to like that more than vendors expect, and it is a genuine reason to keep what you have.
Bank feeds and Reconcile Account Statement bring in statements and let you match them against bill payments and customer payments.
What NetSuite does not do is the part after the flag. When a line is outside tolerance, when the purchase order number is missing, when a receipt in one currency has to clear bills in another, NetSuite puts it in front of a person. Everything below is about who does that work.
The four options
Option 1: native NetSuite only
Bill Capture, native three-way matching, SuiteApprovals and Reconcile Account Statement, with no SuiteApp on top. Fits teams under roughly a hundred vendor bills a month, one subsidiary, and a supplier base whose bills reliably carry a purchase order number. The cost sits inside your NetSuite licence.
Where it stops: Bill Capture reads the header well and struggles with lines. Bills without a purchase order get coded by hand. And Bill Capture does not learn from your corrections, so the same vendor with the same layout produces the same correction every month.
Option 2: a NetSuite-native SuiteApp
Software that lives inside NetSuite itself rather than calling it over an API, so the data never leaves and the screens look like NetSuite. ZoneCapture and Zone Reconcile from Zone & Co are the best known; there are others in the SuiteApp marketplace. Fits teams that want faster capture and better bank reconciliation without adding a system their auditors have to look at separately, and organisations whose IT policy prefers everything inside the ERP. Zone publishes no prices at all; Zone Reconcile is licensed on the number of bank accounts you manage.
Where it stops, in two places, and they are worth naming precisely because they are the reason people go looking. Capture still stops at reading: a SuiteApp reads better than the native tool and it still hands the exception back. And a native SuiteApp is bounded by NetSuite. It runs inside the account, on NetSuite's scripting model, which is what makes it safe and also what makes it rigid. Custom fields that your business depends on are not always mappable from the captured document, and workflows that ship locked stay locked. In our own implementations that is the single most common reason a NetSuite team starts looking: not that capture is bad, but that a field they need cannot be filled.
Option 3: an AP suite outside NetSuite
A full accounts payable platform alongside the ERP, with its own capture, matching, approvals, supplier portal and often payments. Tipalti, Stampli, Medius, Coupa and Basware are the names you will meet. Fits high volumes, many countries, global payments and tax reporting, and organisations that deliberately want AP to live outside NetSuite. The cost is enterprise contracts, generally without published prices.
Where it stops: not on function but on weight. It is a second system with its own implementation, its own administration and its own version of the truth about your payables, and the reconciliation between the two becomes a job of its own.
Option 4: an intelligent action layer
Software that sits on top of NetSuite rather than beside it, carries out the work after capture, and writes the result back as a vendor bill, a bill payment or a journal entry. That is the category Claridy sits in. Fits teams from roughly a hundred vendor bills a month, with multiple subsidiaries, several currencies, or a lot of bills that do not match cleanly. The price is € 499 per month, fixed and published.
Where it stops: at the cases with no precedent. Those go to a person, with the groundwork done.
Where the work actually goes
Capture is a solved problem and it is not where the hours are. These are, and they turn up in almost every NetSuite account we see.
The tool does not learn from your corrections. The same vendor, the same layout, the same fix every month. Reading accuracy is quoted in every sales deck; the share of bills that go through untouched is quoted almost nowhere, and those are two very different numbers. The controller of a travel services company on NetSuite put it this way:
"First-time processing of a single invoice takes ~30 minutes. The system doesn't learn from corrections."
Line-level coding on multi-line bills. One bill with software subscriptions, connectivity and contractor hours needs three different accounts, and often different departments, classes or locations too. Header capture gets you nothing here.
Mixed tax treatment on one bill. Part of the service delivered domestically at the standard rate, part cross-border and reverse charged. One bill, two tax codes, and no capture tool proposes that split.
A missing or wrong purchase order number. Then there is nothing to match against and someone finds the order by vendor, amount, date and description.
Partial item receipts. The purchase order says a hundred, forty were received, the vendor billed for a hundred. Matching against what was actually received, minus what was already billed, is where the time goes.
Custom fields the capture tool cannot fill. Anyone who rents rather than sells knows this one: quantity is two numbers, units and duration, so the purchase order, the item receipt and the vendor bill all carry a custom field that the standard quantity field cannot hold. If capture cannot map it, three-way matching cannot run.
Duplicates caught after the work, not before. Keying a bill, hitting save and only then being told there is a potential duplicate is the wrong order of operations.
Then the bank side, which is a category of its own.
Cross-currency clearing. A receipt lands in your euro account and clears invoices denominated in Canadian dollars. Standard practice is a suspense account, a manual journal entry per invoice, and the difference written off to foreign exchange. The same in reverse when you pay a Japanese yen supplier from a euro account.
Fees that make the amount not tie. A payment provider takes three percent, a batch payment tool takes a commission. You receive twenty euros against a twenty-two euro invoice, and there is no clean way to close the difference to a cost account inside the match itself.
Batch payments as one bank line. Your SEPA batch shows up as a single line for the total. The detail exists in NetSuite; the bank line does not know that.
Remittance advice as a PDF in a separate email. Hundreds of invoice numbers in a document that nothing reads, cleared one by one against open invoices.
Net settlement. A customer pays an invoice minus a credit memo. Two documents, one payment, and no way to clear them against each other in a single posting.
One-cent differences. A ninety-euro payment against a ninety euro one cent bank line blocks the match until someone posts an adjustment by hand.
What all of these have in common is that they are not reading problems. Better capture does not touch a single one.
If you want to know what that costs at your volume, work it out with the calculator. Or book a demo on your own bills.
Claridy in short
| What for | Purchase invoices from arrival to payment: reading, matching, coding, posting and handling exceptions |
| ERPs | Exact Online, NetSuite, Microsoft Dynamics 365, reading and writing back |
| Migration | None. Your books stay where they are |
| Price | From € 499 per month: up to 500 invoices, one entity, one ERP connection. Each extra entity € 250, modules such as three-way matching and reconciliation € 250 each |
| What is not added | no price per invoice, per document or per user, cancellable monthly |
| Peppol | UBL now, Peppol connection in Q4 2026 |
| Live in | First workflow in two weeks, on your own data |
| Approach | The system proposes first and your team approves. Then you set the line above which it acts by itself |
| Lower bound | From roughly 100 invoices a month |
| Languages | Invoices in any language, no template per language or per supplier. The interface is English |
| Security | CASA Tier 2 audit (TAC Security, February 2026), SOC 2 in preparation |
| Where it differs | It acts after capture: splitting across order lines, coding on all your dimensions, investigating differences and emailing the supplier |
Claridy also runs on Microsoft Dynamics 365 and Exact Online.
What Claridy adds
Line-level matching against purchase order and item receipt. Multiple purchase orders on one bill, partial item receipts, consolidated bills. Claridy works out what was received, what was already billed and what is therefore open, and matches against that rather than against the order total.
Matching when the purchase order number is missing or wrong. Claridy falls back to vendor, amount, date, description and, where it applies, the rental or service period, and shows how confident it is in that match before you approve. Where a vendor's wording differs from your item names, a reference table maps the two.
Custom fields, including the ones NetSuite does not have a standard field for. If your purchase order, item receipt and vendor bill carry a custom quantity or a custom period, Claridy reads it, computes on it and writes it back.
Coding on your own posting history. Account, department, class, location and subsidiary, learned from how your team already posts, including several accounts and several tax codes on a single bill.
Differences resolved, not flagged. Claridy pulls in the purchase order, the item receipt and the vendor's email, puts one decision in front of a person, and emails the vendor with the difference already worked out when something is missing.
Cash application and bank reconciliation. Bank lines matched to open invoices, remittance advice read whatever its layout, partial payments left partially open, provider fees written to the account you nominate, batch lines expanded to the bills they contain, and cross-currency receipts cleared against invoices in another currency without a suspense account and a manual journal per invoice.
Approvals stay where you want them. Claridy can block a bill for payment until it is approved in NetSuite, so your approvers keep working in the system they already use and do not need another login.
Instruct it like a colleague. You describe how the work should go in plain language, let it run in parallel with your current process, and then set the threshold above which it acts on its own. Every correction your team makes becomes a rule, so the same exception does not come back next month.
The AI reads, the rule decides. The model reads and interprets; the decision that leads to a posting is deterministic and logged. The same bill always produces the same posting, and afterwards you can show which rule applied, what context was pulled in, and what the confidence was.
When you do not need Claridy
Below roughly a hundred vendor bills a month there is too little repetition to learn from, and native Bill Capture or a capture SuiteApp is cheaper.
If your bills reliably carry a purchase order number, your receipts are complete, and you code to a handful of accounts, native three-way matching does what you need.
If Zone Reconcile is doing your bank reconciliation well, keep it. It sits inside NetSuite, it is close to the bank feed, and swapping something that works out for something new is not free. Several of the teams that come to us for capture stay on Zone Reconcile for the bank, and that is a reasonable answer.
And if you want accounts payable to live outside NetSuite, with a supplier portal and global payments, an AP suite is the more logical choice.
Frequently asked questions
It can, and it does not have to. Claridy can sit alongside either, run in parallel on the same data, and take over when the numbers have earned it. Teams often start by replacing capture and matching and keeping Zone Reconcile for the bank.
No. Claridy connects to NetSuite over the API and writes vendor bills, bill payments and journal entries back into your account. Nothing is installed inside NetSuite and nothing is customised, which is what makes the first workflow possible in two weeks. The trade-off is honest: a native SuiteApp keeps everything inside NetSuite, and an API layer does not.
Yes, one flow across subsidiaries, with the subsidiary determined from the bill itself. Pricing is per subsidiary, so it scales with your structure rather than with your headcount.
Yes. Claridy matches against what has been received and what has already been billed, so a bill against a partial receipt is matched on the open remainder rather than rejected.
No. There is no master-data prerequisite and no chart of accounts to synchronise. Claridy reads and posts on your existing setup.
However you want it. Approval can stay in NetSuite, with Claridy holding the bill for payment until it is approved, or it can run in Claridy. Most teams keep it in NetSuite because their approvers already work there.
€ 499 per month up to 500 bills, one subsidiary and one ERP connection. Each additional subsidiary € 250, modules € 250. Cancel monthly. Everything is on the pricing page.
The first workflow is live in two weeks on your own data. No NetSuite customisation is required, so the time goes into the briefing, not the connection.
Sources: Oracle NetSuite Help Center on Bill Capture, three-way match and item receipts, SuiteApprovals and Reconcile Account Statement, checked 2026-08-18. Vendor product pages for Zone & Co, Tipalti, Stampli, Medius, Coupa and Basware, checked 2026-08-18. Claridy pricing: claridy.ai/prijzen, checked 2026-08-18.
Claridy is an independent vendor and is not affiliated with Oracle. NetSuite and OneWorld are trademarks of Oracle Corporation.