3-Way Matching in Accounts Payable Journal Entry

3-way matching in accounts payable is a core finance control that helps teams verify a purchase before they record the journal entry and release payment. It compares the purchase order, the supplier invoice, and the goods receipt or receipt confirmation to make sure the amounts, quantities, and references line up.

For finance teams that handle a high volume of vendor bills, the process is often repetitive and time-sensitive. Manual spreadsheet checks can work for small volumes, but they become harder to audit as invoice counts grow. A structured reconciliation workflow helps teams review matched items, isolate exceptions, and keep AP journal entries aligned with source documents.

What 3-way matching means in accounts payable

3-way matching is the process of comparing three documents before approving an accounts payable entry:

• Purchase order (PO): what the company expected to buy
• Invoice: what the vendor billed
• Goods receipt: what the company received or confirmed

When all three records agree, the AP team has stronger evidence that the expense or liability should be recorded. If one document differs, the team can investigate before posting the journal entry or before releasing payment.

This control is especially useful when vendors bill for variable quantities, mixed pricing, partial deliveries, freight charges, tax, or other adjustments that can create differences between documents.

Why 3-way matching matters for AP journal entries

The AP journal entry is only as reliable as the supporting documents behind it. If the invoice is entered before the receipt is verified, or if the billed amount does not match the purchase order, the ledger can reflect an incorrect liability.

A 3-way matching process helps finance teams:

• reduce duplicate or incorrect payments
• identify vendor billing differences early
• support audit review with a clear evidence trail
• keep accruals and liabilities closer to the actual transaction
• avoid downstream cleanup during month-end close

It also gives controllers and audit teams a clear view of which items were fully matched, which were partially matched, and which still need review.

How the matching process typically works

A practical 3-way matching workflow usually follows these steps:

1. Collect the source documents

   • Purchase order data
   • Vendor invoice data
   • Goods receipt or proof-of-delivery data

2. Map the fields

   • Date
   • Amount
   • Quantity
   • Vendor reference
   • PO number, invoice number, or receipt identifier

3. Run the comparison

   • Match records by identifiers, amounts, or both
   • Allow for partial matches where the reference aligns but the amount does not
   • Flag missing, duplicate, or incomplete rows

4. Review exceptions

   • Price differences
   • Quantity differences
   • Missing receipts
   • Missing invoices
   • Partial deliveries or split bills

5. Record the journal entry

   • Once the transaction is validated, the AP team can record the liability with greater confidence

Common 3-way matching exceptions

Even well-run AP processes generate exceptions. The most common ones include:

• invoice amount higher than the PO amount
• goods received in part, but invoice raised for the full quantity
• tax or freight charges not reflected in the PO
• missing receipt for a delivered item
• invoice reference mismatch because of formatting differences
• duplicate invoices submitted by a vendor
• credit notes or adjustments that need to be netted against the invoice

These cases are not necessarily errors, but they do need review. Finance teams typically want a clear separation between fully matched items and open exceptions so the AP queue stays manageable.

How Cointab supports AP 3-way matching

Cointab is a reconciliation platform built for finance teams that need to compare records, identify discrepancies, and produce audit-ready reports. For AP workflows, it can support a custom reconciliation setup for purchase orders, invoices, and goods receipts or other vendor-side records.

Reusable workflow for recurring AP checks

Once a 3-way matching workflow is configured, the same setup can be reused for future periods. Teams do not need to rebuild mapping logic every month. They can upload the latest files, run reconciliation, and review the report.

That makes the process useful for recurring vendor review, month-end close, and audit preparation.

Flexible file handling and field mapping

Cointab supports CSV, XLS, and XLSX uploads. Finance users can map the relevant fields once and reuse the configuration for later runs. Typical fields include:

• vendor or supplier name
• PO number
• invoice number
• receipt or GRN reference
• date
• amount
• quantity
• tax or fee fields where relevant

If a file does not match the configured format, the system can reject it with a clear error so the issue is visible before reconciliation continues.

Supporting data for AP enrichment

AP teams often need supporting data before matching can begin. Cointab allows optional supporting files that can help enrich or prepare the primary data, such as:

• vendor master data
• PO reference files
• tax mapping files
• product or item master data
• delivery or receipt reference files

This is useful when the invoice or receipt file needs lookup values or derived fields before the final match.

Derived columns for normalization

Vendor data is rarely perfectly aligned. Cointab allows users to create derived columns using Excel-style formulas, including formula suggestions through AI.

Examples of useful derived columns include:

• cleaned PO number
• normalized invoice reference
• net amount after tax
• amount after discount
• receipt quantity in comparable units
• combined reference key

These calculated fields can improve matching without forcing finance teams to manually edit source files.

Structured matching with clear exception buckets

Cointab’s reconciliation engine can compare records using structured matching logic and separate results into:

• fully matched
• partially matched
• unmatched
• skipped

That makes it easier to focus on the exceptions instead of checking every row manually. For AP teams, this is especially helpful when invoice and receipt references are present but the amounts do not tally exactly.

Manual match and audit-friendly review

Some AP exceptions require human judgment. A team may know that a missing receipt is due to a late delivery, or that a small difference is caused by freight or tax treatment.

Cointab supports manual matching for cases where the system cannot confidently resolve an item. Manual actions remain visible, which helps maintain auditability and internal control.

Reports for finance review

Once reconciliation is complete, users can review the dashboard and download Excel reports. The report gives finance teams a practical way to review matched, partially matched, unmatched, and skipped records for follow-up, audit, and period-end review.

When AP teams should automate 3-way matching

Automation becomes more valuable when the AP process is recurring and time-sensitive. It is especially useful when teams handle:

• many vendors or entities
• repeated monthly invoice cycles
• high-volume purchasing
• frequent partial deliveries or split invoices
• tight close calendars
• audit-heavy review processes

Cointab also supports automated data input through email, SFTP, or API-based flows, so recurring AP reconciliation can become part of the finance workflow rather than a one-off spreadsheet exercise.

3-way matching and the month-end close

For finance leaders, the value of 3-way matching is not just payment control. It also improves the quality of the AP ledger during month-end close.

When invoices, receipts, and POs are matched consistently, the team has a cleaner view of open liabilities, unmatched invoices, and items requiring follow-up. That helps reduce last-minute reconciliation work and supports a more controlled close process.

Key takeaways

3-way matching in accounts payable helps teams verify that purchase orders, invoices, and goods receipts align before the AP journal entry is finalized. It reduces the chance of payment errors, improves control over vendor liabilities, and gives audit teams a clearer paper trail.

For teams that rely on repeated spreadsheet checks, a structured reconciliation platform can make the workflow more consistent, reusable, and easier to review. Cointab supports that process with field mapping, supporting data, derived columns, exception tracking, manual match, and downloadable reports.

FAQs

What is 3-way matching in accounts payable?

3-way matching is the process of comparing a purchase order, an invoice, and a goods receipt before recording the AP entry or approving payment. It helps confirm that the billed amount relates to what was ordered and received.

Why is 3-way matching important before an AP journal entry?

It helps finance teams avoid posting liabilities based on incomplete or incorrect source documents. That reduces payment errors and supports a cleaner audit trail.

Can Cointab handle partial matches and differences?

Yes. Cointab can separate fully matched, partially matched, unmatched, and skipped records so finance teams can review exceptions instead of checking every transaction manually.

Can recurring AP matching be automated?

Yes. Once a reconciliation workflow is configured, it can be reused for future runs, and files can be brought in manually or through automated data input methods such as email, SFTP, or API.

Can AP teams use supporting files in the workflow?

Yes. Supporting data can be used to enrich or prepare the source files before reconciliation, such as vendor master data, tax mappings, or reference lookups.