NetSuite publishes no price for Bill Capture. Its own product page says the feature "is available as an add-on module", which means a quote, not a rate card. What Oracle does publish is the limits, and they are stricter than the popular guides admit: one bill per file, thirty pages per PDF, eight megabytes, and United States subsidiaries only. Every figure below is quoted from Oracle documentation, checked September 2026.
PDF, JPG, PNG, BMP, HEIC and TIFF
Drop files here or click to upload
Up to 50 files
Uploading...
The feature works, and for a single-entity US business it works well. Five documented constraints are what send teams looking for something else, and none of them appear on the product page.
Oracle states it plainly: "One bill per JPEG, PNG, PDF file (multiple bills are not supported)." The moment a vendor emails a single PDF holding a month of invoices, somebody has to sit and split it by hand before capture can start.
The considerations page says "Bill Capture is available only in the United States", and the setup guidance adds "Do not select subsidiaries outside of the United States." A US parent with a Canadian or UK entity cannot run its whole payables function through it.
NetSuite sells Bill Capture as an add-on module priced inside an annual license made of core platform, modules, user count and a one-time implementation fee. Nothing about the module is listed publicly, so budgeting means a quote.
Serial and lot numbered items, bins, inventory status and mandatory line level custom fields are all unsupported on bills without an associated purchase order. Non-PO spend, which is the messy half of AP, is where the gaps show.
Oracle states that "Customization is not supported on the Review Scanned Bill page." Whatever your team needs on screen while approving a scanned bill, that layout is fixed.
The numbers below come from the NetSuite Applications Suite help center, not from partner marketing. Where NetSuite publishes nothing, this page says so instead of filling the gap with a guess.
Three formats. A PDF may run to thirty pages, a JPEG or PNG to exactly one. There is no TIFF, no Word, no Excel and no direct email-body capture of invoice text.
The per-file ceiling is 8 MB. Emailed bills are tighter still: twenty attachments maximum, each under 8 MB, and the whole message under 10 MB.
Oracle documents uploading "a maximum of 50 files at a time for best performance". Batch upload does exist, despite what the most-cited third-party guide claims.
Line level capture covers item name, description, product code, item rates, expense memo and account, billable classification, and ordered, received and billed quantities. This is a genuine strength over header-only capture.
Availability is limited to the United States, and the documentation instructs administrators not to select subsidiaries outside it. This is a hard boundary, not a language preference.
Bill Capture uses the Oracle Cloud Infrastructure Document Understanding Custom Generative Model. Recognition happens on Oracle infrastructure, which is why the geography is fixed.
Four steps turn a quote-only module into a number you can defend at renewal.
Bill Capture is quoted inside the annual license alongside core platform, users and implementation. Ask your account manager to break out the module itself, per year, so it can be compared against anything else.
Go through last month of vendor bills and mark every multi-invoice PDF, every file over 8 MB, every PDF past thirty pages and every bill belonging to a non-US subsidiary. That share still needs a manual path.
Accuracy claims are not published as a percentage by anyone credible. Run your five ugliest recurring invoices, the ones with dense line item tables, and check whether quantities and rates come back clean.
Compare the annual module cost against per-document extraction with no geographic restriction and no one-bill-per-file rule, then decide which half of your payables each path should own.
What Oracle publishes, what it does not, the full field list, the two claims the popular guides get wrong, and what the same volume costs elsewhere.
Capture works until a vendor sends a combined PDF or a scan over 8 MB. You need to know which constraints are permanent and which are configuration.
Bill Capture covers the US entity and stops there. You need a second path for the Canadian, UK or EU books, and you need it to match on fields.
Bill Capture is being quoted as a module. You want the documented limits in hand before agreeing a number that is not published anywhere.
You are sizing an implementation and need the real prerequisites, permissions and boundaries rather than the feature bullets.
Last updated September 2026
NetSuite does not publish a price for Bill Capture. Its own invoice capture page states that "NetSuite Bill Capture is available as an add-on module", and NetSuite licensing is quoted annually as a combination of core platform, optional modules, user count and a one-time implementation fee. There is no per-page rate, no per-invoice rate and no public list price for the module anywhere on netsuite.com or in the help center.
That matters more than it sounds. Every other capture option in this category publishes something: a per-page meter, a monthly page allowance, a per-document credit. Bill Capture publishes none of it, so the only way to know your number is to ask for the module to be broken out of the quote. Treat any blog post citing a specific dollar figure for the module with suspicion, because the vendor has not released one.
No. It is sold as an add-on module rather than bundled at no charge with a NetSuite subscription. This is a common misunderstanding, partly because the feature is switched on under Setup, Company, Enable Features like any native capability, which makes it look included. Enabling the feature flag and being licensed for the module are two different things, and the flag appearing in your account does not settle the commercial question.
These are the documented constraints from the NetSuite Applications Suite help center. They are worth reading before a purchase decision, because several of them are structural rather than configurable.
| Constraint | Documented limit |
|---|---|
| Supported file formats | PDF, JPEG, PNG |
| Pages per PDF | 30 |
| Pages per JPEG or PNG | 1 |
| Maximum file size | 8 MB |
| Files per upload | 50 at a time, for best performance |
| Attachments per email | 20, each under 8 MB |
| Total email size | 10 MB |
| Bills per file | 1, multiple bills are not supported |
| Geographic availability | United States only |
| Subsidiaries | United States subsidiaries only |
| Review Scanned Bill page | Customization not supported |
| Matrix items | Parent matrix items not available, subitems only |
No. Oracle documents the rule as "One bill per JPEG, PNG, PDF file (multiple bills are not supported)." If a supplier sends one PDF containing twelve invoices, someone has to split that file into twelve before Bill Capture will process it, and splitting a scanned PDF correctly means reading it first. For AP teams whose largest vendors consolidate their billing, this single rule can undo most of the time the module was bought to save.
It is also the constraint least likely to change, because it follows from how each file is turned into one scanned vendor bill record on the Scanned Vendor Bills page.
No. The Bill Capture considerations page states that "Bill Capture is available only in the United States", and the setup documentation adds that Bill Capture only supports subsidiaries in the United States and instructs administrators not to select subsidiaries outside it. Recognition runs on Oracle Cloud Infrastructure Document Understanding rather than inside your NetSuite account, which is why the boundary is geographic rather than a matter of language settings.
For a single-entity US business this is irrelevant. For the mid-market US company that acquired a Canadian distributor or opened a UK sales entity, which is a very ordinary NetSuite customer profile, it means the module covers part of the payables function and something else has to cover the rest.
The guide that currently ranks at the top for Bill Capture limitations makes two claims that Oracle documentation contradicts directly. Both are worth correcting because they push buyers toward the wrong conclusion.
| Widely repeated claim | What Oracle documents |
|---|---|
| Available in the US, UK and Australia with SuiteTax | "Bill Capture is available only in the United States" |
| Lacks bulk upload and batch processing | "Upload a maximum of 50 files at a time for best performance" |
The practical effect is that the geography restriction is worse than commonly reported and the batch restriction is better. A UK entity is not covered at all, and a fifty-file drag-and-drop is genuinely supported. If you were dismissing Bill Capture over batch handling, that reason does not hold. If you were counting on it for a non-US subsidiary, that plan does not hold.
More than most ERP-native capture features, and this is the module's real strength. Header and line level are both covered, which puts it well ahead of capture tools that return totals only and leave the table rows to manual entry.
| Level | Fields captured |
|---|---|
| Header | PO Number, Subsidiary, Vendor, Currency, Reference No., Date, Location, Payment Terms, Posting Period, Due Date, Discount Date, Memo, Calculated Amount, Payment Hold, Tax Amount, Department, Class, Custom Segments |
| Line | Item name, description, product code, item rates, expense memo and expense account or category, billable classification, ordered quantity, received quantity, billed quantity |
Two caveats sit on top of that list. The Tax Amount field depends on the SuiteTax Engine being enabled. And on standalone bills, meaning bills with no associated purchase order, serial and lot numbered items, bins, inventory status and mandatory line level custom fields are all unsupported. Non-PO spend is exactly where AP teams need the most help, so check that gap against your own mix before assuming full coverage.
Six features, six permissions and one SuiteApp. Budget implementation time for this rather than treating it as a checkbox, particularly in an account with heavily customized roles.
| Requirement | Detail |
|---|---|
| SuiteApp | Transaction Email Capture, required for the email path |
| Accounting features | Bill Capture, A/P |
| Company features | File Cabinet |
| SuiteCloud features | Custom Records, Client SuiteScript, Server SuiteScript |
| Permissions | Documents and Files (Create and View), Notes Tab (Create), Scanned Vendor Bills (Full), Bills (Full), Vendor Bill Sender custom record (Full) |
| Roles with these by default | Administrator, A/P Clerk, CFO, CEO, and Employee Center with manual global permissions |
Because NetSuite publishes no rate for the module, a like-for-like dollar comparison is not possible and nobody should pretend otherwise. What can be compared honestly is the shape of each option: how it is priced, whether it reads line items, and whether it stops at the US border.
| Option | Pricing model | Line items | Geographic limit | Multi-bill file |
|---|---|---|---|---|
| NetSuite Bill Capture | Quote-only add-on module, no published rate | Yes | US subsidiaries only | Not supported |
| Azure AI Document Intelligence | $10 per 1,000 pages, prebuilt invoice model | Yes | None | Supported |
| AWS Textract Analyze Expense | $10 per 1,000 pages, $8 above 1M | Yes | None | Supported |
| Acumatica AP Document Recognition | Included, 50 pages per month, then packs | Yes | US, UK, Canada | Not supported |
| This tool | Per document, no ERP module required | Yes | None | Supported |
The two hyperscaler meters are the honest yardstick for a buyer trying to sanity-check a module quote. Both charge $10 per 1,000 pages for invoice-specific extraction with no monthly ceiling and no country restriction. If the Bill Capture module is quoted well above what your annual page volume would cost on a meter, that is a fair question to put to your account manager.
The pattern that works for teams sitting outside Bill Capture's boundaries, whether that is a non-US subsidiary, consolidated vendor PDFs or files over 8 MB, is to extract first and import second. Run the bills through an extraction tool that returns header fields and line items as clean rows, review anything the model flagged as low confidence, then bring the result into NetSuite as a CSV import against your existing vendor and item records.
That approach has no geographic restriction, no one-bill-per-file rule and no thirty-page ceiling, and it handles the multi-invoice PDFs that Bill Capture rejects outright. It also runs alongside the module rather than replacing it, which is usually the right answer: let Bill Capture take the clean single-invoice US traffic it handles well, and route the awkward remainder through extraction.
The tool at the top of this page does the extraction half. Upload one of the vendor bills Bill Capture will not take, a combined PDF or a bill from a foreign entity, and check whether the line items come back correctly before you commit to a module quote. Teams comparing ERP options often run the same test against Acumatica AP Document Recognition and its fifty-page monthly allowance, which is priced very differently and capped in a way NetSuite is not.
NetSuite does not publish a price. Its invoice capture page states that Bill Capture "is available as an add-on module", and NetSuite is licensed annually as core platform plus optional modules plus users plus a one-time implementation fee. There is no public per-page or per-invoice rate for the module, so the only reliable figure is the one broken out of your own quote.
No. It is sold as an add-on module rather than included at no charge. The confusion comes from the feature being enabled under Setup, Company, Enable Features like a native capability, but having the feature flag available is not the same as being licensed for the module.
The documented limits are PDF, JPEG and PNG only, 30 pages per PDF and one page per image, 8 MB per file, 50 files per upload, 20 email attachments under a 10 MB total, one bill per file, and United States subsidiaries only. Customization of the Review Scanned Bill page is not supported, and parent matrix items are unavailable.
Yes. Bill Capture is NetSuite native OCR for vendor bills, built on the Oracle Cloud Infrastructure Document Understanding Custom Generative Model. Emailed or uploaded invoices appear on the Scanned Vendor Bills page, where extracted header and line data populates a draft bill for review before it is created.
No. Oracle states that only one bill per PDF, JPEG or PNG file is supported and that multiple bills are not. A consolidated PDF containing several invoices must be split into separate files before capture, which is a real cost for teams whose larger vendors bill in batches.
No. Oracle documentation states that Bill Capture is available only in the United States and that it supports United States subsidiaries only, instructing administrators not to select subsidiaries outside it. A US parent with a Canadian or UK entity needs a separate path for those books.
Yes, and this is its strongest feature. Line level extraction covers item name, description, product code, item rates, expense memo and account, billable classification, and ordered, received and billed quantities. Serial and lot numbered items, bins and inventory status are the exception, unsupported on bills without a purchase order.
PDF, JPEG and PNG only, with a maximum of 8 MB per file. A PDF may contain up to 30 pages while JPEG and PNG are limited to one page each. Emailed bills allow up to 20 attachments provided each is under 8 MB and the whole message stays under 10 MB.
Oracle documents uploading a maximum of 50 files at a time for best performance. This contradicts the frequently repeated claim that Bill Capture has no bulk upload, which is incorrect. Batch upload through the Scanned Vendor Bills page is supported and documented.
Documents and Files at Create and View, Notes Tab at Create, Scanned Vendor Bills at Full, Bills at Full, and the Vendor Bill Sender custom record at Full. The Administrator, A/P Clerk, CFO and CEO roles carry these by default, while Employee Center requires manual global permission setup.
For volume outside the module boundaries, a metered extraction tool is the usual answer. Azure AI Document Intelligence and AWS Textract Analyze Expense both charge $10 per 1,000 pages for invoice extraction with line items, no country restriction and no one-bill-per-file rule, which makes them a fair yardstick for checking whether a module quote is reasonable.
The wider NetSuite AP automation picture: approvals, matching and where capture fits.
Turn vendor bills into a NetSuite-ready import file, including non-US subsidiaries.
The same analysis for Acumatica, which caps recognition at fifty pages a month.
Getting the table rows off a vendor bill, which is where most capture tools stop.
A metered alternative at $10 per 1,000 pages with no geographic restriction.
Analyze Expense rates for invoice extraction, priced per page with no module quote.
Process consolidated vendor PDFs that Bill Capture rejects one bill at a time.
Read invoices from PDFs, scans and photos without an ERP module license.
Start turning your invoices into clean, structured spreadsheet data.
USD
per month
per month
$288 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale invoice extraction across your whole team with automation.
USD
per month
per month
$888 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise‑grade invoice extraction, security, and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
Secure checkout powered by Stripe