NetSuite Bill Capture is Oracle NetSuite's built-in way to turn a vendor's PDF or image into a vendor bill. You email or upload the file, NetSuite reads it, suggests the vendor, dates, terms, PO, and lines, and a person reviews the suggestions before the bill is created.
For many NetSuite teams it removes most of the typing in accounts payable. It also has documented limits, and it leaves three-way matching and approval to other parts of NetSuite. This guide covers what Bill Capture does, where Oracle's own documentation says it stops, and how to tell when you need more than it offers.
What Does NetSuite Bill Capture Do?
According to Oracle's NetSuite documentation, Bill Capture:
- Takes in bills by email or upload. Email arrives through the Transaction Email Capture SuiteApp. PDF, JPEG, and PNG files are accepted.
- Reads them with a generative model. Oracle describes the extraction model as "Built with Llama", and it learns from the corrections reviewers make.
- Suggests the bill. Subsidiary, vendor, currency, reference number, date, terms, due date, and PO number, plus item and expense lines matched to the PO. With no PO match, it falls back to the vendor's past transactions; the default expense account comes from the vendor record.
- Waits for a person. Suggestions "need to be verified before creating the bill." One preference lets NetSuite create the bill automatically when a PO is linked.
Oracle sells it as an add-on module and as part of NetSuite AP Automation. Because it lives inside NetSuite, there is no separate connection to set up and nothing to sync.
What Are Bill Capture's Documented Limits?
Oracle's Bill Capture considerations page lists these, at the time of review:
- United States only. The feature is available only in the United States, and in OneWorld accounts it "only supports subsidiaries in the United States."
- File types and sizes. PDF, JPEG, and PNG only; 8 MB per file. By email, up to 20 attachments, with the whole email under 10 MB.
- Pages. PDFs up to 30 pages; images are one page.
- One bill per file. A PDF that bundles several invoices needs splitting first.
- Bills without a PO cannot carry serial or lot numbers, bins, inventory status, or mandatory line-level custom fields.
- No parent matrix items, and the review page cannot be customised.
None of these is unusual for a native feature. They matter most for companies with subsidiaries outside the US, vendors who send statements with many invoices in one PDF, and item-heavy bills without POs.
Does Bill Capture Do Three-Way Matching?
Not by itself. Bill Capture matches a bill to open purchase orders, supports Bill in Advance of Receipt and partial billing, and follows your account's preferences on whether a receipt is required. Oracle's documentation says three-way match and approvals run outside Bill Capture.
NetSuite's native three-way match lives in Vendor Bill Matching tolerances: quantity and amount tolerances (as percentages) and a quantity difference (as a number), each against the PO and against the item receipt. You set them on the item, the vendor, or the subsidiary, and the NetSuite Approvals Workflow SuiteApp uses them to send out-of-tolerance bills to a supervisor. A blank tolerance means that check does not run.
One detail is easy to miss: Oracle's documentation for that workflow says partially received item receipts are not supported. If your vendors invoice each partial delivery, test that case before relying on it.
How Do Closed Periods and Approval Fit In?
Both stay where they were in NetSuite:
- Periods. A closed period blocks any change that hits the general ledger. Lock A/P on the Period Close Checklist stops new payables postings, except for users with permission to override period restrictions. The Allow Transaction Date Outside of the Posting Period preference (Disallow, Warn, or Allow) decides what happens when a bill is dated into a period that is already locked.
- Approval. NetSuite has a standard vendor bill approval status (Pending Approval or Approved) and supports custom SuiteFlow approval workflows. Bills pending approval do not post to the ledger.
The practical gap is timing. A late invoice dated last month reaches the bill form before anyone decides which period it belongs in. Under Disallow or Warn, NetSuite moves a bill dated into a locked period to the current open period; whether that is right for the accrual is a judgment someone still has to make.
When Do You Need More Than Bill Capture?
Bill Capture is a good fit when your subsidiaries are in the US, most bills are one invoice per file, and your reviewers have time to check each suggestion. Teams usually look further when:
- Subsidiaries outside the US need the same process.
- Partial deliveries are common, and each partial invoice needs to match what is still billable.
- Reviewers are the bottleneck. The suggestions are good, but every bill still needs someone to confirm the PO, receipt, coding, and period.
- Bills keyed by hand collide with captured ones: the same invoice entered by a colleague, with the prefix dropped.
What Does an AP Automation Layer Add on NetSuite?
An AP automation layer reads and checks bills outside NetSuite, then creates them through NetSuite's API. NetSuite stays the system of record, and approval and payment stay in NetSuite. With Fluxity, for example:
- OneWorld coding. Subsidiaries, departments, locations, classes, and custom segments are supported. The subsidiary comes from the invoice's evidence, starting with the matched PO's, and is left for a person when that evidence is weak.
- Partial receipts. Each line is compared with what is still billable on its PO line, received minus already billed, so a second partial invoice matches too.
- Bills already keyed in NetSuite. Before creating a bill, Fluxity checks NetSuite's own bills for the same vendor and invoice number, including near misses such as a dropped prefix or a bill still pending approval.
- Amount check. The bill Fluxity built must equal the invoice total before anything is sent. It posts its own checked lines with PO line links rather than copying lines from the PO.
- Closed periods. Set the date your books are closed through, and a bill dated into a closed period is held for review instead of pushed.
- Units. An invoice billed in bags against a PO in pounds is converted only when the factor can be proven from the documents.
See NetSuite AP automation for the data flow and field mapping.
NetSuite Bill Capture FAQs
Is NetSuite Bill Capture included with NetSuite?
Oracle sells it as an add-on module and as part of NetSuite AP Automation. Check your contract or ask your account manager whether your account has it.
Does Bill Capture work for subsidiaries outside the United States?
Not according to Oracle's documentation at the time of review: Bill Capture is available only in the United States, and in OneWorld accounts it supports only US subsidiaries.
Can Bill Capture read several invoices in one PDF?
No. Oracle's documentation says one bill per file, so multi-invoice PDFs need splitting before capture.
Does Bill Capture approve bills?
No. Approval runs through NetSuite's vendor bill approval status or a SuiteFlow workflow, outside Bill Capture.
Further Reading
- NetSuite AP Automation: how Fluxity works with NetSuite, with the field mapping
- ERP Integration Guide: what matters when connecting document processing to an ERP
- Month-End Close: where late invoices slow the close
- PO Matching with Fluxity: 2-way and 3-way matching before the bill is created
