Most finance teams treat accounts payable and accounts receivable as separate worlds. AP owns the vendor relationships. AR owns the customer relationships. Never the twain shall meet.

But what happens when a vendor is also a customer? Or when two subsidiaries are constantly billing each other? You end up making gross payments in both directions. Two wire transfers, two sets of bank fees, two reconciliation headaches. The real economic exposure is just the difference.

That's the problem AP/AR netting solves. And it's one of those processes that sounds straightforward until you try to implement it properly.

What Netting Actually Means

Netting is the process of offsetting amounts owed between two parties and settling only the net balance.

If your company owes Vendor ABC $10,000, and Vendor ABC owes your company $3,000, netting produces a single $7,000 payment rather than two separate transactions. The gross flows disappear. The net obligation remains.

Simple concept. The complexity lives in the details: legal enforceability, accounting treatment, system configuration, and the very different ways netting shows up across different business contexts.

The Three Contexts Where Netting Appears

1. Intercompany Netting

This is the most common use case for mid-market and enterprise companies on NetSuite. Subsidiaries within the same corporate group transact constantly: management fees, shared services, intercompany loans, cost allocations. Left unmanaged, each of those transactions generates a separate payment. Intercompany netting consolidates them into a single periodic settlement, typically monthly.

The operational benefit is significant. A company with ten subsidiaries billing each other routinely could have dozens of intercompany payments per month. Netting collapses that into one settlement run per period.

2. Vendor-Customer Netting

This occurs when a single counterparty appears in both your vendor master and your customer master. A supplier who also buys finished goods from you. A distributor who resells your product but also provides services back to your company. A professional services firm that is both a client and a subcontractor.

In these situations, the same legal entity is generating both AP and AR balances. Netting lets you settle the net amount rather than exchanging gross payments.

3. Interbank or Multi-Currency Netting

For companies with significant cross-border transactions, netting can be applied across currencies, converting foreign-denominated balances to a functional currency and settling the net FX exposure. This is more complex and typically involves treasury management functions beyond standard NetSuite configuration.

Is Netting Right for Your Organization?

Not every company needs a formal netting program. Before investing in the process design and configuration, it's worth asking whether the economics justify it.

Netting is most clearly worth doing when one or more of the following are true:

  • You have recurring bilateral relationships. A counterparty that generates both AP and AR transactions at least monthly is a strong candidate. A counterparty that buys from you once a year is not.
  • Transaction volumes are meaningful. If the gross AP and AR flows with a counterparty total less than $50,000 per year, the administrative overhead of netting may exceed the benefit. Once you're in the hundreds of thousands, or millions, the cash flow and fee savings become real.
  • You operate across multiple subsidiaries. For OneWorld clients, intercompany netting is almost always worth doing once the transaction count crosses a handful per month per subsidiary pair. The elimination benefit alone justifies it.
  • Your counterparty is a willing participant. Vendor-customer netting requires agreement from the other side. Most counterparties prefer it (it simplifies their reconciliation too) but confirm before designing the process.
  • Your treasury policy supports it. Some organizations have policies requiring gross settlement for control or banking relationship reasons. Check before assuming.

On the other hand, netting adds complexity you may not need if your AP and AR relationships are largely non-overlapping, if you're a single-entity business without intercompany activity, or if your counterparty relationships are too irregular to justify a formal settlement process.

The honest filter: if netting a counterparty relationship saves you less than two hours of reconciliation work per month, it probably isn't worth the setup effort. If it saves half a day and reduces your bank fees, do it.

The Accounting Foundation

Before configuring anything in NetSuite, you need to understand the accounting. Getting this wrong creates misstatements on the balance sheet and breaks your subledger reconciliation.

The Right of Offset

US GAAP (ASC 210-20) and IFRS (IAS 32) both require that a right of offset exist before you can net AP and AR balances in financial statement presentation. That right exists when:

  • Both amounts involve the same legal counterparty
  • You have a legally enforceable right to offset
  • You intend either to settle net or to settle simultaneously
  • Both amounts are due and payable (not contingent)

If those conditions aren't met, you must present AP and AR gross on the balance sheet, even if you're operationally settling them net. This distinction matters for audit and for accurate working capital reporting.

The Clearing Account Mechanism

In practice, netting is almost always executed through a clearing account. Here's why.

You can't simply delete an AP bill and an AR invoice against each other. They live in different subledgers, they may have different due dates, and the audit trail needs to show what happened. Instead, the standard approach uses a wash account (often called "Netting Clearing" or "Due to/from Affiliate") as a pass-through.

Step 1: Apply a customer payment to the AR invoice, but instead of recording cash received, debit the clearing account.

DR Netting Clearing $3,000 / CR Accounts Receivable $3,000

Step 2: Apply a vendor credit to the AP bill, crediting the same clearing account.

DR Accounts Payable $3,000 / CR Netting Clearing $3,000

Step 3: The clearing account nets to zero. The remaining AP balance is settled with a cash payment.

DR Accounts Payable $7,000 / CR Cash $7,000

The clearing account should always zero out after each netting cycle. If it doesn't, something was applied incorrectly. That's your signal to investigate before closing the period.

Why Finance Teams Avoid It (And Why They Shouldn't)

I used to think netting was a treasury optimization, something large enterprises did, but not worth the setup effort for companies under $500M in revenue. In practice, I've found the opposite is true. The teams that benefit most are mid-market companies with 3-10 subsidiaries or a handful of vendor-customer counterparties. The transaction volume is manageable enough to do it well, but high enough that the savings are real.

The reasons teams avoid it:

  • "It's too complex to set up." True for poorly configured systems. Not true with a clear process design and proper NetSuite configuration.
  • "Our counterparties won't agree." Often untrue. Vendors who are also customers typically prefer it. It reduces their administrative burden too.
  • "We don't have a legal agreement in place." This one is valid. You need a netting agreement. But that's a legal task, not a NetSuite task.
  • "We can't track it." This is a configuration problem, not a fundamental limitation.

The real barrier is usually process clarity, not system capability.

NetSuite Deep Dive: How Netting Actually Works in the Platform

NetSuite doesn't have a single "netting module." That's the first thing to understand. Depending on your use case, you'll use different native features, and in some cases, a combination of them.

Here's the decision map:

Use Case Primary NetSuite Mechanism
Intercompany netting (OneWorld) Intercompany Framework + IC Settlement
Vendor-customer same legal entity Manual netting via clearing account
High-volume automated netting Third-party SuiteApp
Subsidiary-to-subsidiary elimination Intercompany Elimination at consolidation

Let's walk through each in detail.

Intercompany Netting in OneWorld

This is the most structured netting path in NetSuite and the one with the most native support.

Prerequisite check:

  • OneWorld must be enabled (this feature is not available on single-subsidiary accounts)
  • Intercompany Framework must be enabled: Setup > Company > Enable Features > Accounting > Intercompany Framework
  • Intercompany accounts must be configured for each subsidiary pair
  • Posting periods must be open for all subsidiaries involved in the settlement

Step 1: Configure Intercompany Accounts

Navigate to Setup > Accounting > Chart of Accounts. You need a "Due To" (liability) and "Due From" (asset) account for each subsidiary relationship, or a shared set of intercompany accounts that apply across all subsidiaries.

Common structure:

  • 1300 - Due From Affiliates (asset, current)
  • 2100 - Due To Affiliates (liability, current)

These accounts must be designated as intercompany accounts on the account record. On each account record, check the Eliminate Intercompany Transactions box if you want them to eliminate on consolidated financials.

For multi-currency environments, set the account currency to match your consolidation currency and ensure exchange rate types are configured at Setup > Accounting > Currencies > Exchange Rate Types.

Step 2: Configure Intercompany Customers and Vendors

Each subsidiary that transacts with another must be set up as both a customer and a vendor in the transacting subsidiary's context.

  • In Subsidiary A: Set up Subsidiary B as a vendor (Vendors > New). On the vendor record, set the Subsidiary field and flag it as an intercompany vendor.
  • In Subsidiary B: Set up Subsidiary A as a customer (Customers > New). Flag it as an intercompany customer.

The key field: on both the customer and vendor records, populate the Represents Subsidiary field. This links the counterparty record to the subsidiary entity and enables intercompany elimination.

Navigation: Lists > Relationships > Vendors or Lists > Relationships > Customers, then open the record and locate the Represents Subsidiary field under the Financial tab.

Step 3: Post Intercompany Transactions

Intercompany bills and invoices post normally through AP and AR workflows. The difference is in how NetSuite recognizes them. Transactions involving a counterparty flagged as an intercompany entity will automatically populate intercompany account lines based on your configuration.

When Subsidiary A bills Subsidiary B:

  • Subsidiary A books: DR Intercompany Receivable / CR Revenue (or Services)
  • Subsidiary B books: DR Expense / CR Intercompany Payable

These entries flow automatically when the Intercompany Framework is active and your account mappings are correct.

Common pitfall: if the "Represents Subsidiary" field is blank on the customer or vendor record, the intercompany account won't populate automatically. You'll end up with transactions that look normal but don't eliminate on consolidation. Always verify this field during testing.

Step 4: Run the Intercompany Settlement

Navigate to Transactions > Financial > Intercompany Settlement (verify this path in your account, as it can vary slightly by NetSuite version).

The settlement screen shows open intercompany balances by subsidiary pair. You can:

  • Select the subsidiaries to settle
  • Choose the settlement date (must fall in an open period for both entities)
  • Select the currency for settlement
  • Generate a settlement journal entry that zeros the intercompany balances

The resulting journal entry debits the Due To account in one subsidiary and credits the Due From account in the other, with the net cash settlement recorded once actual payment is made.

GL impact of settlement:

In the paying subsidiary: DR Due To - [Receiving Subsidiary] $7,000 / CR Cash/Bank $7,000

In the receiving subsidiary: DR Cash/Bank $7,000 / CR Due From - [Paying Subsidiary] $7,000

Step 5: Verify Elimination on Consolidation

After settlement, run a consolidated balance sheet and confirm that the Due To/Due From accounts net to zero. Navigate to Reports > Financial > Balance Sheet, set the reporting subsidiary to your consolidation entity, and verify the intercompany accounts show no remaining balance.

If balances remain, the most common causes are: a transaction posting to a non-intercompany account, a currency revaluation that created a residual balance, or a transaction where the "Represents Subsidiary" field was missing.

Pitfall worth flagging: Intercompany revaluations can create FX gains and losses in the Due To/From accounts. These need to be eliminated too, or you'll have phantom P&L on your consolidated financials. Run the multi-currency revaluation (Transactions > Financial > Revalue Open Currency Balances) before running intercompany settlement, and confirm your elimination account is mapped to capture FX differences.

Vendor-Customer Netting (Manual Process)

When a counterparty is both a vendor and a customer, but not a subsidiary, NetSuite doesn't automate the netting. You're building the process manually, using a clearing account as the mechanism.

Why NetSuite Can't Auto-Match AP and AR Natively

This is a question worth addressing directly. Can NetSuite automatically identify that Vendor ABC and Customer ABC are the same legal entity and offset their balances?

No. Not natively.

The reason is architectural. In NetSuite, vendor records and customer records are separate master data objects. There is no native field that links a vendor record to a customer record representing the same legal entity. The system treats them as entirely distinct relationships, with different record types, different subledgers, and no automatic cross-reference.

This means NetSuite has no built-in way to surface a "net position" view across both subledgers for a counterparty that exists in both. It can't automatically propose a netting match or generate the clearing entries on its own.

There is a partial exception worth knowing about: NetSuite does offer a Customer/Vendor entity type, sometimes called a combined record, which allows a single entity to serve as both a customer and a vendor. This can simplify master data management for counterparties that clearly belong in both roles. However, even with this setup, NetSuite still doesn't automate the netting offset. The AR invoices and AP bills remain in separate subledgers, and you still need the clearing account mechanism to settle them. The combined entity record solves an administrative problem, not a netting problem.

For automated matching and settlement, you need either a SuiteApp or a SuiteScript-powered custom solution. More on that below.

Step 1: Set Up the Netting Clearing Account

Navigate to Setup > Accounting > Chart of Accounts > New.

  • Account Type: Other Current Asset
  • Account Name: AP/AR Netting Clearing
  • Description: Note the purpose and the counterparties it applies to
  • Currency: Match your functional currency (for multi-currency netting, consider separate accounts by currency)

Keep this account off your published financial statements by excluding it from your FSG row definitions, or nest it under a parent account that rolls up to zero when properly used.

Important: This account should always have a zero balance at period-end. Add it to your close checklist as a reconciliation item. A non-zero balance means a netting entry was partially applied. Find it before you close.

Step 2: Identify Open Balances for Netting

Before each netting cycle, pull two reports:

AR aging for the counterparty: Navigate to Reports > Accounts Receivable > A/R Aging Detail. Filter by customer to isolate the counterparty's open invoices.

AP aging for the counterparty: Navigate to Reports > Accounts Payable > A/P Aging Detail. Filter by vendor to isolate the counterparty's open bills.

Compare the two lists. Identify which invoices and bills are eligible for netting based on:

  • Due dates (both should be due or past due, don't net a bill due in 90 days against a receivable due today)
  • Agreement terms (your netting agreement should specify which transactions are eligible)
  • Currency (netting across currencies requires FX conversion, see below)

Step 3: Apply the Customer Payment to the Clearing Account

Navigate to Transactions > Customers > Receive Payments.

  • Customer: Select the netting counterparty
  • Payment Method: Select a non-cash method, or create a custom payment method called "Netting" for reporting clarity
  • Deposit To: Select your Netting Clearing account (not your bank account)
  • Amount: Enter the AR amount being netted
  • Apply to the specific invoice(s) being netted

This entry produces:

DR AP/AR Netting Clearing $3,000 / CR Accounts Receivable $3,000

The AR invoice is now closed. No cash moved. The clearing account absorbed it.

Pitfall: Be careful with partial applications. If you're only netting some of a counterparty's invoices, apply the payment to specific invoices rather than letting NetSuite auto-apply to oldest-first. A misapplication here creates an aging discrepancy that's painful to unwind.

Step 4: Apply the Vendor Credit to the Clearing Account

Navigate to Transactions > Payables > Pay Bills.

  • Vendor: Select the same counterparty (in their vendor role)
  • Account: Select your Netting Clearing account (not your bank account)
  • Amount: Enter the AP amount being netted (up to the AR amount you just applied)
  • Apply to the specific bill(s) being netted

This entry produces:

DR Accounts Payable $3,000 / CR AP/AR Netting Clearing $3,000

The AP bill (or the netted portion of it) is now closed. The clearing account returns to zero.

Step 5: Settle the Remaining Balance

The remaining AP balance is settled with a standard cash payment:

Navigate to Transactions > Payables > Pay Bills. Select the vendor, apply to the remaining bill balance, and pay from your bank account normally.

DR Accounts Payable $7,000 / CR Cash $7,000

Step 6: Document and Reconcile

After each netting cycle, run both aging reports to confirm the netted transactions are fully closed. Then run a saved search on the Netting Clearing account to confirm a zero balance.

Maintain a netting log for each cycle: counterparty, AR invoices netted, AP bills netted, net amount, settlement date, payment reference, and approver. Your auditors will ask for this. A clean log makes that conversation short.

How to Reverse a Netting Entry

Mistakes happen. A netting entry gets applied to the wrong invoice. A counterparty disputes a transaction after the offset is recorded. A posting period needs to be corrected.

The process for reversing depends on where you are in the cycle.

Reversal Before Cash Settlement

If the cash payment hasn't been made yet (meaning you've applied the clearing entries but not yet settled the net balance) you can reverse both legs of the clearing entry directly.

Reverse the customer payment: Navigate to Transactions > Customers > Receive Payments, open the payment record, and use the Void button if the period is still open. This reopens the AR invoice and reverses the debit to the clearing account.

Reverse the vendor payment: Navigate to Transactions > Payables > Pay Bills, open the bill payment record, and void it similarly. This reopens the AP bill and reverses the credit to the clearing account.

After both voids, the clearing account is back to zero and both the AR invoice and AP bill are open. You can then re-apply correctly.

Important: Voiding is only available while the posting period is open. If the period has been closed, you'll need a reversing journal entry instead (see below).

Reversal After Cash Settlement

If the net cash payment has already been made, reversal is more complex because you've already reduced your cash balance. The steps:

  1. Create a reversing journal entry to reopen the original clearing account entries. Navigate to Transactions > Financial > Make Journal Entries. Reverse the original DR/CR entries, memo the reason, and reference the original transaction.
  2. Reopen the AR invoice by creating a new customer payment applied to the clearing account, reversing the prior application.
  3. Reopen the AP bill by creating a vendor bill credit applied to the clearing account.
  4. Post a corrected netting cycle with the right invoices and bills.
  5. If a refund to or from the counterparty is required due to the correction, process that as a separate transaction with clear memo documentation.

The clearing account should net to zero after all correcting entries are posted. If it doesn't, trace each entry individually before proceeding.

In practice, I've found that most netting reversals stem from two causes: the wrong invoice was selected during application (easily prevented by reviewing the apply-to list before saving), or a counterparty dispute was raised after settlement (harder to prevent, but faster to resolve when the netting log is current). Both argue for a pre-settlement review step in your process design.

Automating with Workflows, Saved Searches, and SuiteApps

The manual process works. It doesn't scale. For high-volume netting relationships, systematize it.

Build a Netting Monitoring Saved Search

Create a saved search that surfaces counterparty net positions automatically, eliminating the need to pull separate AR and AP aging reports each cycle.

Navigate to Lists > Search > Saved Searches > New. Search type: Transaction.

Key filters:

  • Type: Is any of Invoice, Bill
  • Status: Open
  • Amount Remaining: Greater than 0

Key result columns:

  • Type
  • Entity (customer or vendor name)
  • Document Number
  • Due Date
  • Amount Remaining
  • A formula column: CASE WHEN {type} = 'Invoice' THEN {amountremaining} ELSE -{amountremaining} END (this shows AR as positive and AP as negative, so the sum by entity gives you the net position)

Add a summary by Entity with a SUM on the formula column. The result is a single-view report showing your net exposure with every counterparty that appears in both subledgers.

This search won't automatically know that "ABC Corp (Vendor)" and "ABC Corp (Customer)" are the same entity unless they share the same entity name exactly. If your master data naming is inconsistent, you'll need to normalize it or add a custom field linking the two records.

Use SuiteFlow to Route Netting Approvals

For companies with a formal netting agreement, you likely need documented approval before executing each offset. Build a workflow on the Customer Payment record:

Navigate to Customization > Workflow > Workflows > New.

  • Record Type: Customer Payment
  • Trigger: After Submit
  • Condition: Payment Method = "Netting"
  • Action: Send approval notification to Controller

This creates an audit trail showing that each netting entry was reviewed before posting. Pair it with a corresponding workflow on the Bill Payment record for full segregation coverage.

Consider a SuiteApp for High Volume

If you're processing more than 20-30 netting transactions per month, the manual clearing account process becomes operationally burdensome. Several NetSuite SuiteApps offer automated netting, matching AP and AR transactions by counterparty, generating the clearing entries automatically, and providing a netting statement for counterparty confirmation.

Evaluate these with eyes open: SuiteApps add cost, create vendor dependency, and introduce upgrade risk. For most mid-market companies, a well-designed manual process with saved search monitoring is sufficient. The SuiteApp conversation becomes relevant at enterprise scale or when netting spans multiple currencies and entities simultaneously.

Multi-Currency Netting: The Added Layer

When AP and AR balances are denominated in different currencies, netting requires an FX conversion step. This is where the process gets materially more complex.

The core issue: you can't directly offset a $10,000 USD payable against a €3,000 EUR receivable without converting one to the other. The exchange rate you use, and when you use it, determines both the net cash settlement and the FX gain/loss that hits your P&L.

The Standard Approach

  1. Convert the foreign-currency balance to your functional currency using the spot rate on the netting date
  2. Calculate the net settlement amount in functional currency
  3. Book an FX gain or loss for the difference between the original transaction rate and the netting date rate

In NetSuite, this means running the Revalue Open Currency Balances function (Transactions > Financial > Revalue Open Currency Balances) before executing the netting settlement. This marks AR and AP balances to market in your functional currency, and the resulting FX gain/loss posts to your unrealized FX accounts.

After revaluation, proceed with the clearing account process using the revalued functional currency amounts.

GL impact of revaluation prior to netting:

DR Accounts Receivable $200 (FX revaluation gain) / CR Unrealized FX Gain/Loss $200

Then net at the revalued amount.

1099 Reporting and the Impact of Netting

This is one of the most overlooked downstream effects of vendor-customer netting, and it can create real year-end headaches if you haven't thought it through.

The question is straightforward: if you pay a vendor $10,000 in gross invoices over the year, but netted $3,000 of that against AR, what amount do you report on the 1099?

The answer under IRS rules is the gross amount paid, $10,000, not the net settlement amount of $7,000. The 1099 reports cash payments made to vendors for services, and the right of offset doesn't change the economic substance of the gross transactions.

This matters for configuration because NetSuite's 1099 reporting is driven by vendor bill payments. When you use the clearing account mechanism, the "payment" applied to the AP bill via the clearing account is still recorded as a bill payment in NetSuite, so it should be captured in the 1099 reportable amount. But this depends on how your netting payment method and clearing account are set up.

To verify your 1099 treatment is correct:

Navigate to Reports > Accounts Payable > 1099 Detail Report. For each vendor subject to 1099 reporting, compare the reportable amount to the sum of all bill payments (including clearing account payments) for the year. The total should reflect gross payments, not net settlement.

If your netting payment method was set up in a way that excludes those bill payments from the 1099 calculation (for example, if the payment method is marked as non-reportable) you may be under-reporting. Correct this before year-end.

Best practice: Flag all 1099 vendors in your netting program for a manual 1099 reconciliation each December. Run the gross AP activity for those vendors, compare to the 1099 Detail Report, and resolve any discrepancies before the January filing deadline.

On the vendor setup side, confirm that each 1099-eligible vendor has the correct Tax ID populated and the 1099 Eligible box checked on the vendor record. Navigate to Lists > Relationships > Vendors, open the vendor record, and verify these fields under the Financial tab.

Month-End Close Considerations

Netting adds steps to your close process. Design them deliberately, or they'll become fire drills.

Timing. Execute netting entries before the subledger close. AP and AR subledgers should be fully reconciled before you run the clearing account entries. Otherwise you're netting against numbers that may still move.

Reconciliation. Add the netting clearing account to your balance sheet account reconciliation checklist. It should tie to zero every period without exception. In practice, I've found that teams who treat this as optional eventually accumulate a clearing account balance that nobody can explain, usually discovered at year-end audit.

Aging accuracy. Confirm that the netted invoices and bills are marked fully applied after each netting cycle. An invoice that was "netted" but still shows open in AR will inflate your aging and misstate your working capital.

Intercompany elimination. For OneWorld clients, confirm that intercompany eliminations run after netting settlement, not before. Netting changes the intercompany balances, and elimination needs to reflect the post-netting state.

Cutoff. Establish a firm netting cutoff date, typically 2-3 business days before month-end. Any transactions that fall after the cutoff go into the next netting cycle. Document this policy. Inconsistent cutoff treatment is one of the most common causes of period-over-period AR/AP variance that makes no sense on first inspection.

Internal Controls and Audit Considerations

Netting carries real internal control risk if you don't design it carefully.

Segregation of duties. The person who applies the customer payment should not be the same person who applies the vendor credit. Both actions together effectively authorize a cash flow offset. That's a treasury function and needs a second set of eyes.

Configure this in NetSuite by ensuring that the roles with access to Receive Payments and Pay Bills are distinct, and that the netting clearing account requires Controller or CFO approval for journal entries posted to it. Navigate to Setup > Users/Roles > Manage Roles to review role permissions.

Netting agreements. Maintain a signed netting agreement with each counterparty before executing netting transactions. The agreement should specify: eligible transaction types, netting frequency, settlement currency, dispute resolution, and termination provisions. File this in your contract management system and note the counterparty in NetSuite under the vendor/customer record.

Audit trail. NetSuite's system notes provide an audit trail for every transaction, but supplement this with a netting log, a record of each netting cycle showing what was offset, at what rate, who approved it, and when it settled. Your auditors will ask for population completeness, and a clean log makes that conversation short.

Presentation. Revisit the ASC 210-20 / IAS 32 conditions each year. If your netting arrangement changes (a counterparty restructures, the legal agreement expires, or your intent shifts) you may need to reclassify back to gross presentation on the balance sheet.

Common Pitfalls (And How to Avoid Them)

These are the ones I've seen trip up real implementations:

1. Netting without a legal agreement. Operationally convenient. Legally exposed. Get the agreement signed before you start. Without it, your right of offset is questionable, and your audit exposure is real.

2. Applying the clearing account to the wrong subsidiary. In OneWorld environments, the netting clearing account must post to the correct subsidiary. A clearing entry posted to the parent when it should be in a subsidiary creates an elimination problem that's annoying to unwind mid-audit.

3. Ignoring the currency revaluation step. If you net before revaluing, your clearing account may not zero out exactly due to FX movements. You'll end up with a small residual that's technically an FX gain/loss but looks like an unreconciled balance.

4. Inconsistent counterparty setup. The vendor and customer records for the same counterparty must have matching legal names and tax IDs. Mismatches create 1099 reporting issues and make it harder to run a clean counterparty-consolidated aging report.

5. Not confirming the clearing account at period-end. This is a close discipline issue, not a configuration issue. Add it to your close checklist. Every period, no exceptions.

6. Over-automating before the process is stable. I've seen teams jump to a SuiteApp solution before they've run the manual process even once. The manual process teaches you the edge cases. Learn those first, then automate. Start small. Measure. Iterate. Then scale.

7. Under-reporting 1099 amounts. If your netting payment method is set up to exclude cleared amounts from 1099 tracking, you're under-reporting. Verify your 1099 detail against gross AP activity for all reportable vendors before year-end.

8. Skipping the reversal design. Most teams design the forward process and assume they'll figure out reversals if needed. Then something goes wrong in month three and nobody knows how to unwind it cleanly. Design the reversal path before you go live.

Crawl, Walk, Run

If you're building this capability for the first time, sequence it this way.

Crawl: Pick one counterparty with a simple, consistent bilateral relationship. Design the clearing account. Run the manual process for one quarter. Build the reconciliation habit. Document the reversal procedure before you need it.

Walk: Expand to all eligible vendor-customer counterparties. Create the monitoring saved search. Add the 1099 reconciliation step to your year-end close checklist. Document the process formally with a designated owner and a netting cutoff date.

Run: Evaluate whether SuiteFlow approvals add value for your volume. Assess whether a SuiteApp is warranted. For OneWorld clients, implement the full intercompany settlement workflow and automate the elimination process.

Don't skip ahead. The teams that jump to automation without process clarity end up with faster errors, not faster closes.

The Bottom Line

AP/AR netting isn't glamorous. It's not a transformation initiative. It's a working capital and operational efficiency lever that most finance teams have access to and most choose not to fully exploit, usually because no one has taken the time to design the process properly.

The accounting is straightforward. The legal foundation is a signed agreement and a clear right of offset. The NetSuite configuration is achievable with native tools for most use cases. What it takes is process discipline: consistent execution, a clearing account that closes to zero every period, and an audit trail that tells a clear story.

If you're reading this and realizing you have counterparties that qualify, and you've been exchanging gross payments for years, pick one and run the manual process this month. One counterparty, one cycle, one quarter. See how it feels. That's all it takes to know whether this is worth building out.

Build it right once. Then it runs.