Short answer: NetSuite AP automation usually means capturing and approving bills faster. The more valuable question is what has already gone wrong: duplicate payments, early-payment discounts taken without earning them (or earned and missed), vendor credits never applied, and payments that do not match the bill. Finding these means sweeping paid bills, vendor credits and payment history for patterns, then separating money you can still recover from process gaps you should close. That sweep can be automated inside NetSuite without changing how your team enters bills.
Seibert Consulting Group builds Meridian, a set of AI agents that run inside NetSuite, including an accounts payable leakage sweep. This article covers where AP money leaks and how to find it, whatever tools you use.
Where AP money leaks in NetSuite
| Leak | How it happens | What to look for |
|---|---|---|
| Duplicate payments | Same invoice entered twice with a different reference, from email and portal, or by two people | Same vendor, amount and date window with different bill numbers |
| Unearned discounts | Early-payment discount deducted after the discount period ended | Discount taken vs payment date vs terms |
| Missed discounts | Terms offered a discount but payment ran late | Paid after discount date on eligible terms |
| Unapplied vendor credits | Credit memo recorded but never applied to a bill | Open vendor credits with no application |
| Short or over payments | Paid amount differs from bill without a documented reason | Bill balance vs payment amount |
| Payments to inactive or changed vendors | Bank details or vendor status changed near payment | Vendor record changes close to payment date |
Why NetSuite’s built-in checks are not enough
With the Duplicate Number Warnings accounting preference turned on, NetSuite warns when a vendor bill reuses a reference number for the same vendor, which catches exact duplicates. Real duplicates are rarely exact: a reference number with and without a leading zero, an invoice keyed from a PDF and again from a vendor statement, or the same amount entered under two vendor records. Catching those needs fuzzy matching across vendor, amount, date and description, run against history, not only at entry.
Recoverable vs preventable: report them separately
A good AP review produces two different lists:
- Recoverable: money you can still claim back, such as a duplicate payment the vendor can refund or a credit you can apply to the next bill.
- Preventable: exposure you should close, such as an approval step that let duplicates through or terms that are not set on vendor records.
Never add the two together. A recoverable figure is the number a CFO acts on and checks. Mixing in preventable exposure inflates it and damages trust in the whole review. Meridian’s AP sweep keeps these apart by design.
How to run an AP leakage sweep
- Pull 12 to 24 months of paid vendor bills, vendor payments, vendor credits and bill credits.
- Match likely duplicates by vendor (including near-duplicate vendor names), amount, date window and normalized reference number.
- Check discounts by comparing payment dates to terms on each bill.
- List open vendor credits and when each was created.
- Compare paid amounts to bill amounts and flag unexplained differences.
- Split findings into recoverable and preventable, with the supporting transactions for each.
- Act: request refunds or apply credits, then fix the process causes.
Doing it with Meridian
Meridian runs this sweep inside your NetSuite account. Every total and count is calculated in SuiteScript from your NetSuite records before the AI writes the report, so figures tie back to transactions you can open. Nothing is posted automatically; any journal entry the review suggests is created as a draft for approval.
The same approach covers receivables. Meridian’s recovery agents include Short Pay and Deduction Resolution, which finds customer deductions that were never chased and classifies them against terms and dates, and Unapplied Cash Cleanup, which finds payments already received but not applied to an invoice. These report different things and are never summed, for the same reason as above. See Meridian.
Preventing the next duplicate
- Turn on Duplicate Number Warnings (Setup > Accounting > Accounting Preferences) so exact repeats are caught at entry.
- Require vendor invoice number on every bill and normalize its format.
- Merge duplicate vendor records and restrict who can create vendors.
- Set payment terms on vendor records so discounts are calculated, not typed.
- Route bills above a threshold through approval.
- Run the leakage sweep on a schedule, monthly or before each payment run.
Frequently asked questions
Can NetSuite detect duplicate vendor bills?
Yes, for exact matches: with the Duplicate Number Warnings preference on, NetSuite warns when a reference number is reused for the same vendor. Near-duplicates with different references, amounts entered under two vendors, or bills keyed from different sources need a separate review against history.
What is AP leakage?
Money that leaves accounts payable and should not have: duplicate payments, unearned discounts, unapplied credits and unexplained short or over payments.
How far back should an AP review go?
Twelve to twenty-four months is typical. Vendors are more likely to refund recent duplicates, and older findings still show which controls need fixing.
Does automating AP review change how we enter bills?
It should not. A sweep reads existing NetSuite records and reports findings; your bill entry and approval process stays the same unless you choose to change it.