Skip to content

Early Access

NetSuite AP Automation: Early Access

Aequo connects to Oracle NetSuite so invoices can be captured, coded and approved in Aequo and then written to NetSuite as vendor bills. The connector is in early access: we offer it to selected teams and finish it with them. It is not yet released to all customers.

Early access covers the core accounts payable loop: vendors and accounts come in from NetSuite, approved invoices go back out as bills, and Aequo checks that each bill arrived. The parts listed under "Not included yet" are still to come. If you need a connector that every customer can use today, QuickBooks Online, Xero, FreshBooks, Zoho Books and Microsoft Dynamics 365 Business Central are available now.

Last reviewed 2026-10-22. Current availability details are maintained on our brand facts page.

Apply for early access

What the connector syncs in early access

Connection
Token-Based Authentication (TBA) or OAuth 2.0 client credentials signed with a certificate. Oracle is phasing out new TBA integrations, so OAuth 2.0 is supported from the start. Credentials are stored encrypted.
Vendors
Your NetSuite vendor list is pulled with SuiteQL, so invoices in Aequo are assigned to vendor records that already exist in NetSuite.
Chart of accounts
GL accounts are pulled so that coding in Aequo uses your NetSuite account numbers. A line coded to an account NetSuite does not recognize is stopped before it is sent.
Vendor bills in NetSuite
Bills changed since the last sync are read back by last-modified date. A scheduled sync runs every hour, and you can start one at any time.
Writeback
Each approved invoice becomes a NetSuite vendor bill with expense lines, one per coded line, carrying the vendor, the vendor invoice number as the reference number, the invoice date and the due date. Each bill carries a unique external ID, so a retried writeback cannot create a second copy.
OneWorld
If you use NetSuite OneWorld, one subsidiary can be set per connection and is stamped on the bills Aequo creates.
Reconciliation
Aequo reads each bill back from NetSuite to confirm it exists. Diagnostics, "Reconcile now" and "Retry failed" actions show and fix writebacks that did not complete.

What syncs between Aequo and NetSuite?

Vendors, GL accounts and vendor bills come in from NetSuite through SuiteQL; approved invoices go out as vendor bills through the SuiteTalk REST API; and Aequo reads each bill back to confirm it arrived.

Authentication uses Token-Based Authentication or OAuth 2.0 client credentials with a certificate. Oracle is ending new TBA integrations, so OAuth 2.0 is supported alongside it. Credentials are stored encrypted.

A scheduled sync runs every hour and you can start one at any time. Each bill carries a deterministic external ID, so a retried writeback is refused by NetSuite instead of creating a second bill.

Diagnostics, "Reconcile now" and "Retry failed" show and fix writebacks that did not complete.

Aequo and NetSuite sync, by object
DataDirectionWhat happens
VendorsNetSuite to AequoPulled with SuiteQL so invoices land on existing vendor records.
Chart of accountsNetSuite to AequoAccount numbers are resolved to NetSuite internal IDs; a line coded to an unknown account is stopped before it is sent.
Vendor billsBoth waysBills changed since the last sync are read by last-modified date. Approved invoices become vendor bills with one expense line per coded line, the vendor, the invoice number as reference, and the invoice and due dates.
Subsidiary (OneWorld)Aequo to NetSuiteOne subsidiary per connection is stamped on the bills and vendors Aequo creates.
Bill confirmationNetSuite to AequoEach bill is read back by ID, or by vendor and reference, to confirm it exists.
Purchase orders and item receiptsNot synced yetNot imported, so matching against NetSuite POs is not available.
PaymentsNot syncedYou pay in NetSuite.

How does the NetSuite AP workflow run in Aequo?

Invoices are captured, coded to NetSuite GL accounts, approved by rule, checked for duplicates and written to NetSuite as vendor bills; PO matching against NetSuite is not part of the connector yet.

  1. Capture: invoices arrive by forwarding inbox or upload; AI extracts header and lines for review.
  2. Coding: vendor defaults apply first, then AI suggests a GL account from your NetSuite chart for each remaining line. Lines are coded to accounts, not items.
  3. Matching: invoices are not matched to NetSuite purchase orders or item receipts yet. If you keep purchase orders in Aequo itself, invoices can be matched against those.
  4. Approval: rules by amount, vendor, GL code or department route invoices through one or more steps, with escalation and delegation; approver suggestions cover invoices no rule matches.
  5. Duplicate check: each invoice is scored against past invoices from the same vendor before approval.
  6. Writeback: the approved invoice becomes a NetSuite vendor bill with expense lines, stamped with your subsidiary on OneWorld. You pay and report in NetSuite.

How does Aequo complement NetSuite’s own AP?

NetSuite has bill capture with generative AI and a three-way match approval workflow in its Approvals Workflow SuiteApp. Aequo adds an AP work queue in front of NetSuite: rule-based approvals for people who are not NetSuite users, approver suggestions, duplicate scoring and flat pricing.

What NetSuite does well: Oracle’s Bill Capture feature takes PDF, JPEG or PNG invoices by email or upload, extracts the fields with an OCI generative model, and matches them to vendors, items and purchase orders. Email intake needs the Transaction Email Capture SuiteApp. Oracle notes that three-way match and approval workflows are not part of Bill Capture; they come from the "3 Way Match Vendor Bill Approval" workflow in the NetSuite Approvals Workflow SuiteApp, which needs Accounts Payable, Purchase Orders, Advanced Receiving, Approval Routing and SuiteFlow turned on, and assigns each bill creator’s supervisor as approver.

Where teams outgrow it: supervisor-based routing is hard to bend to amount, department or vendor rules without SuiteFlow work, and every approver needs a NetSuite login. Teams also want the invoices that need a person, and why, in one queue.

Where Aequo adds to NetSuite: Exception-first matching: invoices that fit the PO within your tolerances clear on their own, and the rest land in an exception queue with a reason, an owner, an SLA and a proposed fix.

Approver suggestions: when no approval rule covers an invoice, Aequo suggests the person who approved similar invoices from that vendor before, with a confidence level and the reason. Nobody is assigned until a person confirms.

Duplicate detection: each invoice is compared with past invoices from the same vendor, including near-identical invoice numbers and amounts within about 2%, and given a risk level with the evidence.

Flat pricing with unlimited users: approvers, reviewers and auditors do not need paid seats. Starter is $199 a month for up to 250 documents, Growth $699 for 1,000 and Scale $1,999 for 5,000, all with unlimited users.

If you also use NetSuite vendor bill approval, decide during onboarding whether bills from Aequo should be approved again in NetSuite, so nobody approves the same invoice twice.

How does Aequo compare with NetSuite AP add-ons?

BILL, Stampli, Tipalti, Zone & Co, Medius and AvidXchange all integrate with NetSuite, and several match against NetSuite POs today, which Aequo does not yet. Aequo’s case is a simpler AP queue at a published flat price.

If you need invoices matched to NetSuite purchase orders and item receipts today, or a Built for NetSuite SuiteApp, BILL Enterprise, Zone & Co or Medius fit better right now. Aequo fits teams that code invoices to GL accounts, want approvers outside NetSuite without extra licenses, and want to know the price before a sales call.

Common NetSuite AP add-ons
ToolWhat the vendor publishes about this systemPricing model (vendor’s own page)
BILLTwo- and three-way PO matching that syncs back into NetSuite; bi-directional sync; "no extra integration fees"NetSuite sync on the Enterprise plan (custom pricing)
StampliLists NetSuite among supported ERPsQuote-based
Tipalti"Extends existing NetSuite capabilities"; pricing page lists two- and three-way PO matchingFrom $99 a month plus per-invoice and per-payment fees; unlimited users
Zone & Co (ZoneCapture, ZoneApprovals)Three-way matching and split-screen review inside NetSuite; approvals through ZoneApprovalsTiered, quote-based
MediusSuiteApps carry Built for NetSuite certificationCustom quote; unlimited users
AvidXchangeLists Oracle NetSuite among its integrationsNo public pricing
AequoVendor and GL sync, vendor bill writeback with read-back confirmation, approvals, approver suggestions, duplicate scoringStarter $199 a month; unlimited users
Each row is taken from the vendor’s own integration and pricing pages, checked 2026-10-24. "Not stated" means the page did not say, not that the feature is missing. Features and prices change; confirm with the vendor.

How do you set up Aequo with NetSuite?

Your NetSuite administrator creates an integration record and credentials; you enter them in Aequo, sync, and test with a small batch, ideally in a sandbox first.

  1. Create an integration record in NetSuite and either a TBA token or an OAuth 2.0 client-credentials certificate.
  2. Create a role for Aequo that can read vendors, accounts and vendor bills and create vendor bills (and vendors, if you want Aequo to add new ones).
  3. Enter the account ID and credentials on the Integrations page in Aequo, set the subsidiary if you use OneWorld, and run the connection test.
  4. Sync vendors and the chart of accounts, then set vendor coding defaults and approval rules.
  5. Run a few real invoices through capture, coding and approval, write them back, and check the vendor bills in NetSuite.
  6. If you are leaving another AP tool, finish its open approvals and stop its bill creation first. The external ID on each Aequo bill stops Aequo from duplicating its own bills, and the duplicate check flags invoices already seen.

Who early access is for

Early access suits finance teams that already run NetSuite as their ledger and spend too much time keying supplier invoices into it. Typical fits receive most invoices as PDFs by email, code them to GL accounts rather than items, and approve by amount, vendor or department.

You will need a NetSuite administrator who can create an integration record and a role for Aequo, and a person in AP who can test with us for a few weeks and tell us what does not work. A NetSuite sandbox account helps but is not required.

It is not the right fit yet if you need to match invoices to NetSuite purchase orders and item receipts, post bills to several subsidiaries from one connection, or pay vendors from Aequo.

How early-access onboarding works

  1. Apply with the form on this page. We reply about fit and timing, usually after a short call about your NetSuite setup, invoice volume and approval rules.
  2. Your NetSuite administrator creates an integration record and either a TBA token or an OAuth 2.0 certificate, with a role that can read vendors, accounts and vendor bills and create vendor bills.
  3. You enter the account ID and credentials on the Integrations page in Aequo and run the connection test.
  4. You sync vendors and the chart of accounts, then set vendor coding defaults and approval rules in Aequo.
  5. You run a small batch of real invoices through capture, coding and approval, write them back, and check the bills in NetSuite. We suggest a sandbox first if you have one.
  6. Once the bills look right, you widen the rollout to more vendors. We review diagnostics and failed writebacks with you during early access.

Not included yet

  • Purchase orders and item receipts are not imported from NetSuite, so two-way and three-way matching against NetSuite POs is not part of early access.
  • Bills are written with expense lines only. Item lines, custom transaction forms and multi-currency bills are not supported yet.
  • One OneWorld subsidiary per connection. Mapping several legal entities to their own subsidiaries is not started.
  • The connector is not Built for NetSuite certified.
  • Vendor payments in Aequo are coming soon. During early access you keep paying vendors in your ERP, as you do now.

Low-friction next step

Apply for Oracle NetSuite early access

Tell us where to reach you and we will follow up about fit, timing and what early access involves.

We will email a confirmation link first, then send the resource once you confirm. We may follow up with related product guidance.

Frequently asked questions

Is the Aequo NetSuite integration available now?

It is in early access for selected teams and is not yet released to all customers. Apply on this page and we will tell you whether it fits your setup. QuickBooks Online, Xero, FreshBooks, Zoho Books and Microsoft Dynamics 365 Business Central are available to all customers today.

Which NetSuite authentication methods does the connector use?

Token-Based Authentication or OAuth 2.0 client credentials with a certificate. Your administrator creates the integration record and credentials; Aequo stores them encrypted.

Does it work with NetSuite OneWorld?

Yes, with one subsidiary per connection, which Aequo stamps on the bills it creates. Mapping several subsidiaries from one connection is not available yet.

Can Aequo match invoices to NetSuite purchase orders?

Not yet. Purchase orders and item receipts are not imported from NetSuite during early access, so PO matching against NetSuite is not included.

Can I pay vendors from Aequo?

Not yet. Vendor payments in Aequo are coming soon. Approved bills go to NetSuite, and you pay vendors there.

Does NetSuite do three-way matching?

Yes, through the "3 Way Match Vendor Bill Approval" workflow in Oracle’s NetSuite Approvals Workflow SuiteApp, which needs Purchase Orders, Advanced Receiving, Approval Routing and SuiteFlow enabled. Aequo’s NetSuite connector does not import NetSuite purchase orders or item receipts yet.

What does Aequo write to NetSuite?

Approved invoices become vendor bills with expense lines, each coded to a GL account, with the vendor, vendor invoice number, invoice date and due date, and your subsidiary on OneWorld. Each bill carries a unique external ID so retries cannot duplicate it.

How do you automate the AP process in NetSuite?

Automate the steps before the bill: capture invoices from one inbox, code them against your NetSuite accounts with vendor defaults, route approvals by rule, check for duplicates, and create the vendor bill automatically once approved. Aequo does those steps and writes the bill; NetSuite keeps payments and reporting.

How much does AP automation software cost?

Pricing models differ more than features. Some tools charge per user (BILL lists $49 to $89 per user a month), some charge a platform fee plus per-invoice or per-payment fees (Tipalti starts at $99 a month plus usage), and several publish no prices at all (Stampli, AvidXchange, Medius, Zone & Co). Aequo charges a flat monthly price by document volume: Starter is $199 a month for up to 250 documents, Growth $699 for 1,000 and Scale $1,999 for 5,000, all with unlimited users.

Sources

Checked on 2026-10-24. Vendor features and prices change; confirm current details with each vendor.

  1. Oracle NetSuite Help, Bill Capture (capture, generative extraction, scope)
  2. Oracle NetSuite Help, 3 Way Match Vendor Bill Approval (required features, supervisor routing)
  3. BILL + NetSuite (matching and sync)
  4. BILL pricing (NetSuite on Enterprise)
  5. Tipalti + NetSuite (integration)
  6. Tipalti pricing (plans and matching)
  7. Zone & Co ZoneCapture (matching inside NetSuite)
  8. Medius, for your ERP (Built for NetSuite)
  9. Medius pricing (custom quote)
  10. Stampli pricing (quote-based)
  11. AvidXchange integrations (NetSuite listed)