Contact Us
Three men gather around a computer, discussing and collaborating on a project.

Your AP team swears 3-way matching is set up. Bills still flow through without proper checks. Meanwhile, your Accrued Purchases account keeps growing. Month-end reconciliation takes hours longer than it should.

This happens more than you might think. The problem is rarely a single broken setting. It is usually a chain of small setup gaps that add up. If your NetSuite Services include 3-way matching but bills are not routing correctly, this guide will help you find the root cause and fix it.

Key Takeaways

  • The "Match Bill to Receipt" checkbox is the most common reason 3-way matching fails
  • Proper setup can reduce manual matching work
  • NetSuite can record partial receipts, but the native workflow does not support them
  • Bills can auto-approve when they pass the configured exception checks
  • Proper variance posting supports a cleaner month-end close
Anchor Group Assessment
Contact Us

Is NetSuite right for you?

Six honest questions. We'll tell you straight - even if it's "not yet."

Question 1 / 6 Size
Your verdict
A strong fit

What is 3-Way Matching in Accounting?

Three-way matching compares three documents before you pay a vendor bill. The first is the purchase order. This is what you agreed to buy. The second is the item receipt. This is what actually arrived. The third is the vendor bill. This is what the vendor wants you to pay.

When all three documents agree, the bill approves. When they do not agree, the bill holds for review. This prevents paying for goods you never received. It also catches price errors before money leaves your account.

Why This Matters for Your Business

Without 3-way matching, AP teams manually check every bill against POs and receipts. This takes time. It also creates errors. Proper matching can help reduce the risk of overpayments. That is real money staying in your business.

The matching process also supports audit and compliance needs. External auditors often test 3-way match as part of their review. Clean matching records make audits faster and less stressful.

image10.jpg

Common Variances in NetSuite 3-Way Match

Before you can fix a problem, you need to know what type of problem you have. NetSuite tracks several types of variances between POs, receipts, and bills.

Price Variances

Price variance happens when the vendor bills a different amount than the PO. Maybe the vendor raised prices after you placed the order. Maybe someone entered the wrong price on the PO. Either way, the system flags the difference.

Quantity Variances

Quantity variance happens when the billed quantity differs from the received quantity. The vendor might bill for 100 units. Your warehouse only received 95. That 5-unit gap needs review before payment.

Receipt vs. Bill Mismatches

This is the most common issue. The bill references a PO, but the item receipt does not match. Sometimes goods arrive in multiple shipments. Sometimes the receipt got posted to the wrong PO. These gaps cause bills to get stuck.

NetSuite ERP for Accounts Payable

NetSuite includes built-in tools for AP matching. You do not need extra modules for basic 3-way match. You do need to set them up correctly.

Native Matching Features

The platform offers several matching tools out of the box:

  • Automated PO-Receipt-Bill Comparison: Compares quantities and amounts at the line level
  • Tolerance Limits: Set acceptable variance thresholds by percentage or unit count
  • Variance Account Posting: Posts eligible accounting differences through separate variance journals
  • Exception Routing: Routes out-of-tolerance bills to supervisors for approval

Approval Workflow SuiteApp

NetSuite offers the NetSuite Approvals Workflow SuiteApp that handles 3-way match routing. It includes 23 saved searches for different exception types. You install it, configure your tolerances, and release it. The workflow does the rest.

For more NetSuite Automation ideas, check out our guide on maximizing efficiency with workflows.

VIDEO: AP Automation for NetSuite - Anchor Group Podcast

Step-by-Step Troubleshooting Guide

Here are the six most common reasons 3-way matching fails. We will walk through each one with specific fixes.

Problem 1: "Match Bill to Receipt" Not Checked

This is the number one reason 3-way matching breaks. The checkbox defaults to OFF on item records. Without it, NetSuite can calculate variances using purchase order lines instead of matched receipt lines.

How to fix it:

  1. Go to Lists > Accounting > Items
  2. Open each item type that flows through POs
  3. Find the Purchasing subtab
  4. Check "Match Bill to Receipt"
  5. Save the record

For bulk fixes, use Mass Update. Go to Customization > Mass Update. Select your item types and update the checkbox across all records at once.

Problem 2: Advanced Receiving Not Enabled

Without Advanced Receiving, you do not get a true three-leg chain. Receiving happens inline on the vendor bill. That defeats the whole purpose of 3-way matching.

How to fix it:

  1. Go to Setup > Company > Enable Features
  2. Click the Transactions tab
  3. Enable Purchase Orders and Advanced Receiving
  4. Enable Approval Routing and SuiteFlow
  5. Go to Setup > Accounting > Accounting Preferences
  6. Click Approval Routing
  7. Enable Vendor Bills
  8. Save

After enabling this, your receiving team will use item receipts. Bills will then pull from those receipts instead of directly from POs.

Problem 3: No Variance Accounts Configured

NetSuite needs GL accounts for posting variances. Without them, you get errors when trying to save bills with price or quantity differences.

How to fix it:

  1. Create GL accounts for Purchase Price Variance, Bill Quantity Variance, and Exchange Rate Variance
  2. Go to Lists > Accounting > Items
  3. Open each applicable item record
  4. Find the Accounting subtab
  5. Assign the Bill Price, Bill Quantity, and Bill Exchange Rate variance accounts
  6. Save

This setup takes about an hour. You can use Mass Update to assign accounts across many items.

Problem 4: Approval Workflow Not Released

Installing the workflow bundle is not enough. It defaults to "Not Running" status. No approval routing happens until you release it.

How to fix it:

  1. Go to Customization > Scripting > Workflows
  2. Find "3 Way Match Vendor Bill Approval"
  3. Click Edit
  4. Go to the Workflow subtab
  5. Change Release Status from "Not Running" to "Released"
  6. Save

This takes five minutes. It is one of the easiest fixes but also one of the most overlooked.

Problem 5: Conflicting Exception Criteria

The native workflow includes strict criteria that can conflict with tolerance settings. Bills route for approval even when variances fall within your allowed range.

How to fix it:

  1. Copy the workflow. Never edit the Oracle-delivered version directly.
  2. Disable these four criteria: VB Qty Greater Than PO Qty, VB Qty Less Than PO Qty, VB Amt Greater Than PO Amt, VB Amt Less Than PO Amt
  3. Keep only the tolerance-based criteria
  4. Test boundary cases before going live

For more on building workflows, see our NetSuite Workflow guide.

Problem 6: Accrued Purchases Account Not Clearing

Your clearing account balance grows month over month. This happens when vendor bill variances have not been posted. Receipts and bills do not match in the GL.

How to fix it:

  1. Run Reports: Transactions > Payables > Open Item Receipts
  2. Run Reports: Transactions > Payables > Unbilled Purchase Orders
  3. Cross-reference to find stuck transactions
  4. Go to Transactions > Payables > Post Vendor Bill Variances
  5. Select Bill or Purchase Order as the transaction type
  6. Select your posting period
  7. Check the bills and POs to process
  8. Click "Create Journal Entries"

Do this monthly before closing the period. Variance journals help clear eligible differences, but open receipts and missing bills may need separate action.

Configuration Best Practices

Getting the setup right from the start prevents most problems. Here are the key settings to check.

Tolerance Levels

Tolerances define how much variance you will accept before routing for approval. Start with limits that match your purchasing rules. Test them against actual bills and adjust based on your exception volume.

You can set tolerances at multiple levels. Item level is most granular. Vendor level applies to all items from that supplier. Subsidiary level sets defaults across the entity.

One important note from Oracle's documentation: if tolerance fields are blank, the related criteria do not execute. Blank does not mean zero. It means disabled.

Supervisor Assignments

The native workflow routes exceptions to the bill creator's supervisor. Make sure every employee who creates bills has a supervisor assigned in their employee record. Without this, exception routing breaks.

Item Receipt Settings

For true 3-way matching, ensure item receipts are required before billing. This means your receiving team must post receipts before AP can create bills. It adds a step, but it is the foundation of the matching chain.

Handling Complex Scenarios

Not every transaction fits the simple PO-receipt-bill pattern. Here is how to handle common exceptions.

Landed Costs

Freight, duties, and other landed costs add complexity. These lines often bypass normal receipt matching. You have a few options.

You can set higher tolerances at the vendor level for shipping vendors. You can also create a separate approval path for landed cost bills. For a full walkthrough, see our Landed Cost guide.

Partial Shipments

Here is an important limitation. NetSuite can record partial receipts, but the native 3 Way Match Vendor Bill Approval Workflow does not support partially received item receipts. Oracle explicitly states this in their documentation.

If you receive goods in multiple shipments against one PO, you need a workaround. Create a saved search to track cumulative billed quantity versus received quantity by PO. Have AP manually review any bill where cumulative billed exceeds cumulative received.

Services Without Receipts

Services do not have item receipts. No receipt means no 3-way match. Use 2-way matching for service items. The system compares the PO to the bill only.

You can flag service items differently in your approval workflow. Route service bills to a different approver who checks that work was actually completed.

Why Good AP Processes Matter

Good accounts payable processes protect your cash flow. They also save your team time and stress.

Time Savings

Manual PO-receipt-bill matching takes hours each week per AP clerk. Automated matching cuts that work to minutes. Your team can focus on exceptions instead of checking every bill.

Error Prevention

Proper matching helps catch incorrect quantities, billing differences, and potential overpayments. That is real money staying in your business instead of leaving your account.

Faster Close

Month-end reconciliation goes faster when your Accrued Purchases account clears cleanly. Proper variance posting supports a cleaner month-end close.

Audit Readiness

Auditors test AP controls as part of every financial audit. Clean 3-way match records with documented approvals make audits smoother. Your team spends less time pulling support and answering questions.

Comparison: Native vs Third-Party 3-Way Match

Feature NetSuite Native Third-Party Tools
Validation Timing During bill workflow processing Depends on integration
Partial Receipt Support Not supported Often supported
Tolerance Levels Item, vendor, subsidiary Often more granular
Setup Complexity Feature and workflow configuration Varies by tool
Cost Included in NetSuite Additional cost

Strong Fit for NetSuite Native Matching

  • Clean, fully-received POs with minimal partial shipments
  • In-house NetSuite admin who knows workflow setup
  • Smaller AP volume under 500 bills per month
  • Supervisor-only approval routing works for your business

For advanced reporting on your matching results, SuiteQL Query Tool can help you dig deeper into the data. And for tracking exceptions, NetSuite Saved Searches are your best friend.

How Anchor Group Helps with NetSuite 3-Way Match Issues

Fixing 3-way matching can be challenging, especially when dealing with inherited configurations or unclear settings. Experienced NetSuite Consultants can help identify and resolve these issues.

Anchor Group helps distributors, manufacturers, and e-commerce companies troubleshoot AP workflows by:

  • Identifying configuration gaps: Reviewing item records, variance accounts, and workflow settings to find and fix issues.
  • Documenting fixes: Ensuring your team can maintain configurations going forward.
  • Reconciling stuck balances: Cleaning up years of unresolved Accrued Purchases balances.
  • Customizing approval workflows: Using experienced NetSuite Developers to build logic beyond native capabilities.

Not sure where to start? Anchor Group's FREE 30-minute NetSuite fix offers a practical consultation to address your NetSuite challenges with no sales pitch, just expert guidance.

image10.jpg

Frequently Asked Questions

What causes a 3-way match to fail in NetSuite?

The most common cause is the "Match Bill to Receipt" checkbox. It is not checked on item records. This checkbox defaults to OFF. Without it, NetSuite can calculate variances using purchase order lines instead of matched receipt lines. Check this setting first on any item that flows through purchase orders. It is the single biggest reason bills skip receipt matching.

How can NetSuite workflows help resolve variances?

Workflows route out-of-tolerance bills to supervisors. The supervisor reviews the variance and approves or rejects. This creates an audit trail. It also prevents unauthorized payments from going through. The native approval workflow includes 23 saved searches for different exception types. You configure your tolerances once, and the system handles routing from there.

What is the difference between 2-way and 3-way matching?

Two-way matching compares the PO to the bill. It checks price and quantity ordered versus billed. Three-way matching adds the receipt. It checks what arrived versus what you agreed to pay for. Three-way is stronger because it catches shortages. If goods never showed up at your dock, 3-way match will flag it before payment goes out.

Does NetSuite handle landed costs in 3-way matching?

Landed costs add complexity. They often bypass normal matching. Set higher tolerances for vendors who bill freight. Or create separate approval paths. You can also flag landed cost items differently in your workflow. Route them to approvers who understand freight charges. For full setup steps, see our Landed Cost guide.

Can NetSuite handle partial receipts in 3-way matching?

NetSuite can record partial receipts. But the native 3 Way Match Vendor Bill Approval Workflow does not support partially received item receipts. Oracle documents this limitation. You need a workaround. Create a saved search to track cumulative quantities. Have AP review bills manually when cumulative billed exceeds received. This keeps partial shipments from blocking your approval workflow.

Related Articles

NetSuite Purchase Order Process 2026: From Requisition to Receipt

The NetSuite purchase order process is a structured procure-to-pay workflow that runs from internal purchasing needs through vendor ordering, goods receipt, vendor bill review, and payment approval. In most NetSuite environments, the full cycle can be understood in six stages: purchase requisition, requisition approval, purchase order creation, PO approval, item receipt, and three-way matching with vendor bill processing.

Read the Article A person standing before a whiteboard and speaking to two men sitting at a table.

Tagged with Troubleshooting, Financial Management