Does Core Invoice work with NetSuite OneWorld and multi-subsidiary setups?

Yes. Each NetSuite subsidiary maps to its own ERP connection in Core Invoice, with distinct credentials, tax mappings, and default accounts. Bills post to the subsidiary linked to the connection — never cross-contaminating books across entities.

How does Core Invoice authenticate to NetSuite?

Token-Based Authentication (TBA) via OAuth 1.0a is the recommended path — an integration record plus a token-record pair generated under your integration user. OAuth 2.0 with Client Credentials is also supported on newer NetSuite versions. Username/password auth has been deprecated by Oracle and is not supported.

Does it post to NetSuite SuiteAnalytics, REST, or SOAP?

REST Web Services (the modern SuiteCloud REST API). The Vendor Bill record is posted to /record/v1/vendorBill with the extracted line items, subsidiary, location, department, and class fields filled in. SuiteScript hooks (e.g. afterSubmit user events) on the Vendor Bill record fire normally.

Can Core Invoice fill custom segments and custbody fields on the Vendor Bill?

Yes. Configure each custom segment (custbody / custcol) in the connection settings with a mapping rule — pull from an extracted field, hardcode a value, or leave for the AP user to fill in review. Common patterns: cost centre from the vendor record, project code from the PO link, location from the integration user's default.

Does 3-way matching work with NetSuite POs?

Yes. If the extracted PO number matches an open transaction.purchaseOrder, Core Invoice reconciles each Vendor Bill line against the PO line with configurable price and quantity tolerances. Item Receipt records are checked too — for stockable items, the bill won't post unless quantity received matches quantity billed within tolerance.

What about NetSuite SmartScan or Bill Capture?

Bill Capture is NetSuite's built-in OCR — it reads headers but is weak on line items and tax breakdowns. Most teams move to Core Invoice specifically to replace Bill Capture for multi-line bills, while keeping Bill Capture for the simpler one-line vendor bills that already work.

Integration · NetSuite

Invoice OCR for NetSuite that handles every line and every segment.

Core Invoice reads supplier bills and posts them into NetSuite as Vendor Bills — with line items, tax codes, subsidiary, location, department, class, and any custom segments your CFO insists on — via the SuiteCloud REST API.

Why NetSuite Bill Capture isn't enough

NetSuite's built-in Bill Capture (formerly SmartScan) reads header fields reliably but struggles with line items, tax breakdowns, and multi-line freight surcharges. On a 15-line bill from a typical industrial supplier, Bill Capture gives you the vendor and total — your AP user keys the rest by hand.

Core Invoice extracts the entire document:

Supplier identity (name, tax ID, address) → matched against your vendor records
Bill metadata (number, date, due date, currency)
Every line: item, quantity, unit price, line total
Taxes per line and per invoice (rate, base, amount)
PO reference numbers — for automatic linkage to open POs

How the connection works

Create an Integration record in NetSuite: Setup → Integration → Manage Integrations → New. Check Token-Based Authentication and copy the Consumer Key + Secret.
Create a Token-Based Authentication role with permissions for the Vendor Bill, Vendor, Subsidiary, and Purchase Order records.
Generate an access token + secret under your integration user.
Add the connection in Core Invoice with your NetSuite account ID, subsidiary ID, consumer key/secret, and token key/secret.
Click Test — Core Invoice runs a no-op GET on /record/v1/subsidiary/<id> and confirms the connection.

What lands in NetSuite

Each extracted bill becomes a vendorBill record posted to /record/v1/vendorBill. The bill is in Pending Approval status (or your configured default approval workflow status) — never posted directly to the GL without a human signing off.

Subsidiary: set from the connection's subsidiary ID — single connection = single subsidiary.
Vendor matching: by tax ID first (the most reliable signal), then by name against vendor.companyName. Unmatched vendors are flagged for human review.
Custom segments: every custbody_* and custcol_* field is mappable in the connection settings.
Tax codes: extracted tax rate is mapped to a NetSuite tax code via the connection's tax mapping table.
Class, Department, Location: pulled from the vendor's default, the linked PO, or hardcoded per connection — whatever fits your accounting policy.

3-way matching with PO + Item Receipt

For PO-referenced bills, Core Invoice reconciles each Vendor Bill line against the open purchaseOrder and the matching itemReceipt if your vendor sends stockable goods.

Quantity against the item receipt — default tolerance 0%
Rate against the PO line rate — default tolerance 5%
Item mismatch is a hard fail (vendor billed for an item not on the PO)

Mismatches flag the bill and either warn (post anyway, note added) or block (hold until corrected) based on your tolerance policy. This complements NetSuite's own 3-way match validation — Core Invoice catches mismatches before the bill hits NetSuite, so your AP team isn't stuck cleaning up posting errors.

Multi-subsidiary (OneWorld) setups

Each NetSuite subsidiary maps to its own Core Invoice ERP connection — with distinct credentials, tax mappings, default G/L accounts, and custom segment mappings. Bills extracted in the EMEA workspace post only to the EMEA subsidiary. Bills extracted in the APAC workspace post only to APAC. There is no cross-subsidiary leakage.

Multi-currency works the way NetSuite expects: extracted currency codes are matched against the subsidiary's allowed currencies, exchange rates are pulled from NetSuite at post time, and the bill records both the foreign currency amount and the subsidiary-base equivalent.

SuiteScript and approval workflows still fire

Bills posted by Core Invoice go through your existing SuiteScript user events (beforeSubmit, afterSubmit) and SuiteFlow approval routings exactly as if a human created them in the UI. Custom validations, default GL overrides, and approval gating all run normally — Core Invoice just provides the data layer.

Security

Consumer and token secrets are encrypted with Fernet server-side and never logged or returned in any API response. We recommend rotating the access token quarterly via NetSuite's Reset Token flow — your Core Invoice connection update takes ~30 seconds.

Try it on your NetSuite sandbox

Point Core Invoice at your NetSuite sandbox account, drop in a real bill, and watch it land as a Vendor Bill in Pending Approval — usually in under 15 seconds.

Start free with NetSuite How the OCR works