# NetSuite AP and AR Automation: Bills, Coding, and Cash Application

> Test NetSuite Bill Capture, 3-way match, and Automated Cash Application on your own subsidiaries, partial receipts, and short pays before you scale up.

- Canonical page: https://procindex.com/blog/netsuite-ap-ar-automation
- Author: ProcIndex Editorial Team
- Published: 2026-01-20
- Updated: 2026-11-10
- Topics: netsuite, ap-automation, ar-automation, cash-application, vendor-bills

The same supplier sells equipment to one subsidiary and maintenance to another. A draft bill that remembers last month's account looks right until AP opens the invoice and sees a capital purchase. Meanwhile AR is reapplying a customer payment that landed on the wrong invoice. Both problems start at the same place: a value in NetSuite that nobody can trace back to its source.

Before buying another tool, open a vendor bill AP had to send back and a customer payment AR had to reapply. Follow each to the point where someone needed evidence that was not on screen. That is the work to test.

## What NetSuite already does

Check what is enabled in your account before evaluating anything else. Oracle documents several native features relevant to AP and AR:

| Feature | What Oracle documents | What to check in your account |
| --- | --- | --- |
| Bill Capture templates | Save selected field values for a vendor and subsidiary combination; when a PO is linked, PO data takes precedence over the template | Which vendors have templates, and whether any carry stale coding |
| 3 Way Match Vendor Bill Approval workflow | Compares the bill with the PO and the item receipt; Oracle documents a limitation for partially received item receipts | How your configuration handles split deliveries |
| Automated Cash Application | Generates customer payments from imported bank lines and applies them to invoices | What happens with incomplete or wrong references |
| Period Close Checklist and preliminary locks | Limit transaction posting before the period closes | How any outside tool responds to a locked period |

Sources: [Bill Capture templates](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_1217105627.html), [vendor bill matching](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4096219721.html), [customer payments and cash application](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_38152706945.html), [accounting period close](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1452509.html).

Run every test below in a sandbox with redacted documents. The goal is to find where people still leave NetSuite to finish the job.

## AP: getting the subsidiary and coding right

### Identify the subsidiary from the document

Take a supplier whose name appears on vendor records for two subsidiaries. Give the reviewer the PDF and ask what identifies the buyer: the bill-to address, the PO number, or a delivery location. If the document is ambiguous, the draft should wait for a person to confirm the subsidiary, not default to the last one used.

When AP changes the subsidiary on a draft, check that the vendor record, account, and dimensions (department, class, location) still apply in the new entity. A correct account in one subsidiary can be invalid or wrong in another.

### Know where each suggested value came from

For any AI-assisted coding, separate three kinds of values:

1. **Printed on the invoice.** Invoice number, date, amounts, bill-to. Verifiable against the PDF.
2. **Pulled from NetSuite.** PO lines, vendor defaults, Bill Capture template values.
3. **Inferred from past bills.** A guess based on history.

Show the source beside each field on the draft. The third category is where errors hide: the tool repeats last month's maintenance account on this month's equipment bill.

Because PO data takes precedence over a Bill Capture template when a PO is linked, test one bill with a linked PO and one without. Ask the reviewer to show where each proposed value came from in both cases.

### Test set for vendor bills

| Bill to test | What AP should verify |
| --- | --- |
| Routine maintenance bill | Agreed account and department, original invoice attached |
| Same supplier, equipment purchase | Proposed treatment and the accountant who confirms capitalization |
| PO bill whose coding differs from the template | What the PO supplied and what appears on the saved bill |
| Shared bill across two departments | Distribution totals and approval for the split |
| Bill edited after approval | Which fields changed and the approval status after the edit |

### Worked example: a split bill (illustrative)

A $4,800 facilities maintenance invoice is shared 60/40 between Production and Warehouse. The distribution should be $4,800 × 0.60 = $2,880 to Production and $4,800 × 0.40 = $1,920 to Warehouse, totalling $4,800. Check that the saved bill carries both lines, that the lines add back to the invoice total, and that each department's approver saw their share. If the approval route is driven by department, confirm the bill reached both approvers and not just the first line's.

## AP: partial receipts and the three-way match

Add a PO bill for a split delivery. This is where NetSuite's documented limitation for partially received item receipts in the 3 Way Match workflow matters. Run the case in your configuration and record where the bill lands, what evidence the buyer sees, and who can release the hold.

### Worked example: partial receipt (illustrative)

A PO orders 500 units at $12.00, or $6,000. The warehouse has received 300 units. The supplier bills the full 500.

| | Quantity | Amount |
| --- | --- | --- |
| Billed | 500 | $6,000 |
| Received (item receipt) | 300 | $3,600 |
| Unreceived and billed | 200 | $2,400 |

The supported amount today is 300 × $12 = $3,600. The remaining $2,400 should be held until receiving confirms the other 200 units or the supplier issues a credit. Your test should show the held line, the receipt quantity available, and the named person who resolves it. Confirm that the held bill stays out of the payment run. For tolerance and match design, see [two-way, three-way, and four-way matching](https://procindex.com/blog/three-way-matching); for clearing holds safely, see [invoice holds and payment blocks](https://procindex.com/blog/invoice-holds-and-payment-blocks).

## AR: one deposit, several invoices

Use an imported bank line with a remittance listing several invoices. Start with a deposit that covers every invoice in full. Then repeat with a short payment.

### Worked example: short payment (illustrative)

A customer remits $18,450 against three invoices:

| Invoice | Open amount | Applied | Remaining |
| --- | --- | --- | --- |
| 1041 | $7,200 | $7,200 | $0 |
| 1042 | $5,750 | $5,750 | $0 |
| 1043 | $6,000 | $5,500 | $500 |
| **Total** | **$18,950** | **$18,450** | **$500** |

The invoices total $18,950, so the customer paid $500 short. Apply $7,200 + $5,750 = $12,950 to the first two in full and the remaining $18,450 − $12,950 = $5,500 to invoice 1043, leaving $500 open. Record the deduction reason separately (pricing dispute, damaged goods, unearned discount) and route it to whoever owns deductions. Do not let a tool write the $500 off or spread it across invoices without a decision. The [customer deductions and short pays guide](https://procindex.com/blog/customer-deductions-short-pays) covers the resolution workflow.

Ask the AR reviewer to trace the bank line to the customer payment record and each application. Then test what happens when the payment reference is incomplete or points to a different customer. The uncertain portion should stay unapplied with a reason.

### Check customer balances and the bank separately

A deposit can tie to the bank perfectly while the money sits on the wrong customer's invoice. The bank reconciliation passes. The correct invoice stays open, and collections sends a reminder to a customer who already paid. Review the customer balance and the bank reconciliation as two separate checks. More cases are in the [cash application automation guide](https://procindex.com/blog/cash-application-automation).

## Writes, retries, and permissions

Decide where each decision lives. If NetSuite owns bill approval, show that an imported bill still follows the expected approval workflow. If an outside review happens before the write, the original document and review decision must stay traceable from the saved NetSuite record. Payment release stays with the people who own it today.

When evaluating any AI layer, separate what it can read from what it can change. Oracle's NetSuite AI Connector Service FAQ says the SuiteQL tools are read-only and that queries respect the NetSuite role's permissions ([Oracle's NetSuite AI Connector Service FAQ](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_4160616848.html)). Ask any vendor to show the specific role and tool behind each write it claims. Include a test record from a subsidiary the role cannot access and confirm it stays out of view.

Test locked periods too. A bill dated into a period under a preliminary lock should come back to the controller with its intended date and the failure reason, not quietly move to the next open period.

### Evidence to ask for

| Test case | Evidence |
| --- | --- |
| Supplier shared across subsidiaries | Vendor and subsidiary IDs, original document, source of coding |
| Receipt missing for part of an order | Held line, available receipt quantity, person assigned |
| Bill edited after approval | Changed fields, approval status after the edit |
| Deposit with several invoice references | Customer payment ID, amount applied per invoice, unapplied balance |
| Connection times out after a write | A lookup for an existing NetSuite record before any retry |

ProcIndex is one of the tools that connects to NetSuite (along with QuickBooks and Sage Intacct), and the same checks apply to it as to any other.

## Measure, then expand

Pick the queue your team corrects most often. Count corrections by field and by invoice type, before and during the pilot. Measure the time spent finding the source and validating the proposal, not just entry time. If routine bills pass but equipment purchases still need accounting review, keep that split visible rather than averaging it away.

Keep a list of records the workflow could not finish and who took over. Expand to another subsidiary only after testing its vendors, dimensions, and approval rules there. For approval routing design, see [invoice approval workflows](https://procindex.com/blog/invoice-approval-workflows).

## Three NetSuite tests to run first

- [ ] Review Bill Capture templates on vendors shared across subsidiaries and clear any stale coding.
- [ ] Run a split-delivery PO bill through your 3 Way Match configuration and confirm the unreceived amount stays out of the payment run.
- [ ] Simulate a write timeout and a bill dated into a locked period; confirm no duplicate bill and no silent re-dating.

## Sources

- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_1217105627.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4096219721.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_38152706945.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_4160616848.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1452509.html

---

Published by ProcIndex, which builds AI accounting agents for construction and manufacturing finance teams. ProcIndex currently connects to NetSuite, Sage Intacct, and QuickBooks. Worked examples in this guide are illustrative, not customer results.