Reference · built on requestOperator by FibricFinance & billing

Three-Way Match

Each vendor invoice compared to its purchase order and goods receipt, with a release, short pay, or hold proposed for approval.

Request accessPricing ↗

About

An invoice is safe to pay when three documents agree: the purchase order that authorized the spend, the receipt that proves the goods arrived, and the invoice itself. This operator reads all three from your ledger and your procurement or inventory system and compares them line by line: quantity, unit price, and total, within the tolerance you set.

Where they agree it proposes a release. Where the invoice bills more than was received it proposes a short pay to the received quantity. Where price or vendor disagree it proposes a hold and names the field. A person approves each one, and the receipt shows the three documents side by side.

This is a reference listing. It documents what Fibric would read from Three-Way Match and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Purchase invoices in Business Central with vendorInvoiceNumber, orderNumber, and status Draft, In Review, or Open
  • Coupa invoices by status, including new, pending_receipt, on_hold, disputed, and pending_approval, with their invoice-lines
  • Purchase orders and their lines: Business Central purchaseOrders with fullyReceived, Coupa purchase orders, and NetSuite purchase orders
  • Posted purchase receipts in Business Central and Coupa inventory receipts, matched by order number and line
  • Vendor bills entered in QuickBooks Online, Xero (ACCPAY invoices), or NetSuite that carry a purchase order reference
  • Invoice PDFs dropped in a SharePoint folder, watched through the driveItem delta feed, or in an Amazon S3 bucket
  • The price and quantity tolerance you set, per vendor or for all

Proposed actions

  • Target capability: propose releasing an invoice for payment where order, receipt, and invoice agree within tolerance
  • Target capability: propose a short pay to the received quantity, with the difference and the receipt that supports it
  • Target capability: propose a hold on the invoice where unit price, vendor, or currency differ from the order, naming the field
  • Target capability: propose a Coupa dispute on the invoice, with the mismatched lines quoted in the reason
  • Target capability: propose a message to the buyer asking whether the order or the receipt should be corrected

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Match inside Business Central

    Purchase invoices are compared to their purchaseOrder and posted purchaseReceipt. Agreeing invoices are proposed for release. Mismatched ones wait with the difference named.

    With Microsoft Dynamics 365 Business Central

  • Work Coupa invoices in pending_receipt

    Coupa invoices waiting on a receipt are re-checked when the inventory receipt posts. A match proposes approval; a shortfall proposes a dispute with the lines quoted.

    With Coupa

  • Bills in the ledger, receipts in the warehouse

    Xero ACCPAY invoices carrying a purchase order number are matched to Katana receipts. Short pays and holds are proposed to the controller with the two records attached.

    With Xero, Katana Cloud Inventory

  • Invoices that arrive as files

    PDFs landing in a SharePoint folder are paired to NetSuite purchase orders by the number on the invoice and held for a buyer where no receipt exists yet.

    With Microsoft SharePoint, NetSuite

Requirements

  • A ledger or procurement connector that holds vendor invoices and purchase orders: Business Central, Coupa, NetSuite, QuickBooks Online, or Xero
  • A receipt record in the same or an attached system: Business Central purchase receipts, Coupa inventory receipts, Katana, or Fishbowl Advanced
  • A purchase order number on each invoice, which is how the three documents are joined
  • A tolerance for price and quantity, and a default for invoices that arrive without an order
Authentication
It signs in nowhere itself. Ledger, procurement, and file reads go through the connectors you attach and the roles you give them.

Limits

  • An invoice without a purchase order number is listed as unmatched. It is not paired by amount or vendor alone.
  • It compares what the systems record. A receipt entered late or a line received against the wrong order shows as a mismatch.
  • Releasing an invoice does not pay it. The payment run stays where it is; this operator changes the invoice's status or approval.
  • Image-only PDFs are attached to the case for a person to read. Their contents are not compared.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Three-Way Match ↗

Questions and answers

What does the approver see for each invoice?
Each release, short pay, or hold is its own proposal. It shows the invoice, the order, and the receipt with the compared lines marked. Approve, change the amount, or decline. Batches of clean matches can be approved together.
What is recorded for each invoice it matched?
A receipt per invoice: the three documents compared, the tolerance applied, the result, who approved it, when, and the status it set. Reversing a release is described on the receipt.
Can it pay or reject an invoice by itself?
No. It changes nothing until someone approves, and it never issues a payment. A hold approved once stays a hold until a person lifts it.
Ask about Three-Way Match

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy