{
  "question_id": "CG-P1B-FULL-122",
  "slug": "what-is-one-way-matching-in-accounts-payable",
  "display_title": "What is one-way matching in accounts payable, and when is a vendor invoice approved on a single-document match?",
  "format": "article-v2",
  "applies_to": {
    "countries": [
      "US"
    ],
    "frameworks": [],
    "tax_year": null,
    "platforms": []
  },
  "general_concept": true,
  "summary": "One-way matching is an informal name for approving a vendor invoice on the invoice alone, with no purchase order or receiving record. The invoice is checked against the standing agreement, the vendor record and an approver's knowledge of delivery. It suits designated low-value spend under an agreement, such as subscriptions, utilities or rent, within vendor, category and amount limits. Anything undesignated or above the policy's value ceiling gets a fuller match; anything above its designation's ceiling, a second approver.",
  "body": "## What is one-way matching, and what is the invoice checked against?\n\nAccountingTools' three-way matching article describes a two-way match as comparing the authorizing purchase order to the supplier invoice to ensure that the billed price is correct. One-way matching drops the order too, leaving the vendor invoice as the only transaction document.\n\nThe term is informal. AccountingTools' three-way matching article treats this ground as exceptions, particularly for low-risk or low-value purchases, where companies may use two-way matching or waive the matching process entirely, and names recurring expenses like utilities or software subscriptions as common exceptions due to their predictable nature. As used below, the name means a designated, controlled version of that waiver, in which the invoice is still validated against three things:\n\n- **The standing agreement.** The lease, subscription terms, retainer letter or contract fixes the payee, amount or rates, frequency and end date.\n- **The vendor record.** The payee, remit-to address and bank details must agree with the record on file, which decides where the money goes.\n- **The approver's knowledge.** A person with authority over the spend confirms that the service was delivered for the period billed. For a period billed in advance, the approver confirms instead that the service is in place and the prior period was delivered.\n\nAccountingTools' accounts payable controls article calls invoice approval a relatively weak control if the approver only sees the supplier invoice, since there is no way to tell whether the goods or services were received or the prices were agreed. The agreement answers the price question and the approver's knowledge the receipt question, narrowing that weakness without removing it.\n\nEach match degree down gives up a check: two-way gives up the receiving record, and one-way also gives up the price test against an authorized order. It is a graded reduction, not another name for the higher degrees, and it stays the weaker control. Running two-, three- or four-way matching is a separate question.\n\n## What separates a single-document policy from not checking?\n\nThe Federal Trade Commission's guide to scams against small businesses tells owners to make sure procedures are clear for approving purchases and invoices and to ask staff to check all invoices closely. A single-document policy is one such procedure: it decides what an invoice is compared with, not whether it is checked, and leaves evidence an absent control lacks:\n\n| A designated policy has | An absent control has |\n|---|---|\n| A written list of designated vendors and categories, each tied to an agreement | Approval of whatever arrives without an order |\n| A named approver for each category | Approval by whoever opens the mail |\n| Limits configured in the system where possible | Limits held in someone's head, if anywhere |\n| Differences held before payment | Differences found later, if at all |\n| A dated review with findings | No review |\n\nCalling the right-hand column one-way matching is a mistake in itself: naming a gap after a control stops anyone treating it as a gap to close.\n\n## Which spend qualifies for single-document approval?\n\nAccountingTools' purchase order definition says many organizations set thresholds or exceptions for low-value or routine transactions, but that purchase orders are strongly recommended for significant, high-risk, or contract-based spending. This degree departs from that recommendation for contract-based spending, relying on the exceptions the three-way matching article names; the departure holds only where the agreement does the purchase order's job of authorizing the commitment. An agreement makes a single-document invoice checkable; it does not make large or risky spend safe to approve this way. A category qualifies only when all of these hold:\n\n- **An agreement exists.** A lease, subscription, retainer or service contract states the amount or rates, the frequency and the term.\n- **The agreement was authorized.** Someone with authority to commit the business signed or approved it.\n- **The amount is predictable.** It is fixed, or it follows the agreement's rates with usage comparable to recent periods.\n- **Nothing is received and counted.** The spend is a continuing service or right, such as occupancy, power or software access.\n- **Each invoice is under the value ceiling.** The owner sets in the policy a per-invoice amount above which nothing is designated, however predictable; that spend keeps a purchase order and the higher match. No figure is a standard.\n- **The vendor is established.** It is already in the vendor record, with payment details verified as described below.\n- **Someone can vouch for delivery.** A named person knows whether the service was provided in the period billed or, if billed in advance, that it is in place and the prior period was delivered.\n\nSubscriptions, utilities, a small retainer and rent under the ceiling usually pass; delivered goods, one-off purchases, new vendors and spend with no agreement do not. Each invoice then gets its own test:\n\n| If the invoice | Then |\n|---|---|\n| Is from a designated vendor, in its category, and matches the agreement within the ceiling | The named approver approves it on the invoice |\n| Exceeds the policy's value ceiling | It is not eligible: it takes a purchase order and the higher match |\n| Is from a designated vendor and category and exceeds its designation's ceiling but not the value ceiling, or differs from the agreement | It is held before payment for the second approver |\n| Is from a vendor or category that is not designated | It goes to the higher match; an invoice with no purchase order at all is a separate question |\n| Has failed a two- or three-way match | It stays with that match and never takes the single-document route |\n\nThe last row matters most: moving failed matches here would put the riskiest invoices on the weakest control.\n\n## Which controls must be in place before a designation takes effect?\n\nCOSO's Internal Control — Integrated Framework lists authorizations and approvals, verifications and reconciliations among control activities. COSO names these only as general categories, prescribing no set of controls for approval on the invoice alone; the five below apply them, drawing on AccountingTools' accounts payable controls article and the FBI alert below. Put each in place before the first invoice is approved this way:\n\n- **A named approver.** One person with authority over the spend approves each designated category; a second person, often the owner, decides anything held for a difference or above the ceiling.\n- **The agreement on file.** The current agreement sits where the approver works, with its amount or rates, escalation terms, agreed variation and end date noted.\n- **A protected vendor record.** Every change to a designated vendor's bank details, remit-to address, phone number or email address is verified before the next payment by calling a number taken from the signed agreement or confirmed when the vendor was set up. Never use a number or address given in the request or changed since, never reply to the email that made the request, and have someone who does not pay bills sign off the change.\n- **A duplicate check.** Recurring invoices look alike from period to period, so each invoice number is entered exactly as printed, and the approver confirms on every designated invoice that the period billed has not already been paid.\n- **A scheduled review.** The date and owner of the first review are fixed when the category is designated.\n\nThe FBI's Internet Crime Complaint Center advises using secondary channels or two-factor authentication to verify requests for changes in account information. Its business email compromise alert says the scam is frequently carried out by compromising legitimate business or personal email accounts, so a reply to the vendor's usual address is not a second channel. Treat every vendor-record change as part of this approval degree, not as upkeep.\n\nIntuit's help page on bill approval and payment release workflows shows why that sign-off matters: in QuickBooks Online with QuickBooks Bill Pay Elite, the Bill payer role can view and pay bills and edit vendor details, and the Bill clerk role can add and edit vendors. Where the system lets roles be customized, keep vendor editing out of any role that can pay.\n\nAccountingTools' accounts payable controls article warns that an invoice number recorded once with leading zeros and once without will not be flagged as a duplicate. Check your system's documentation for whether it flags duplicate bill numbers and blocks or only warns.\n\nCOSO's framework says that where segregation of duties is not practical, management selects and develops alternative control activities. At a minimum, the person who pays should neither approve designated invoices nor sign off vendor changes. The full design needs three people: named approver, second approver and payer. With two, the non-payer holds both approval roles and signs off vendor changes, and each checks the other's vendor-record changes before every payment run. The payer releases no held invoice without the non-payer's recorded decision and runs the periodic review, and the policy records that held invoices have lost their second approval. Where one person records, pays and reconciles, the checks that fit are a separate question.\n\n## How are the limits by amount, vendor and category enforced?\n\nA limit written only in a policy expands quietly. Each designation carries three bounds: the vendors covered, the expense category and a per-invoice ceiling no higher than the value ceiling. For a fixed charge the ceiling is the agreed amount plus any agreed variation. For a usage-priced service such as a utility, the agreement fixes rates, not an amount, so the owner sets the ceiling from recent bills and records its basis.\n\nIntuit's help page on bill approval and payment release workflows says Bill Pay Elite customers can add a bill approval workflow whose conditions for the amount, vendor, location, or a combination of conditions are what triggers the approval process. A workflow whose conditions combine a designated vendor with an amount above the designation's ceiling can then require the second approver's approval. A further When this happens and Do this block, which Intuit's page provides for when the initial conditions are not met, can send the same vendor's bills within the ceiling to the named approver. The page lists amount, vendor and location as the conditions, not category, and calls them what triggers approval, so treat a bill meeting none as not routed for approval: the workflow cannot by itself keep a non-designated or off-category bill off the single-document route. The approver therefore checks the category on every designated bill, and before each payment run someone confirms that every bill being paid is within a designation and carries the named approver's noted comparison, or has completed the higher match. In another tool, confirm in its documentation which bounds it can enforce.\n\nBefore each payment run, someone who neither pays bills nor made the changes also lists every change to a designated vendor's record since the last run, from the system's change history where its documentation shows one, and confirms each was verified by call-back and signed off; payments to a vendor with an unverified change are held.\n\n## What happens when an invoice differs from the agreement?\n\nComparison with the agreement is this degree's only substantive check, so the response to a difference is where the control lives. The named approver notices, because they hold the agreement. The agreed variation is recorded at designation: none for a flat subscription or fixed rent, and for a utility, the agreement's rates with a usage range drawn from recent periods. Each invoice then takes one of two paths:\n\n- **Within the agreed variation.** The approver approves it and notes the comparison on the bill.\n- **Outside the agreed variation.** The invoice is held, and before its due date the second approver either confirms a documented change and updates the agreement on file and the ceiling, or disputes the invoice with the vendor. The ceiling may rise only to the value ceiling; a confirmed change above it ends the designation, and the invoice takes the higher match.\n\nA documented change is one the approver can point to, such as an escalation clause, a signed order for more seats or a rate change the agreement permits. A subscription for 25 seats at 18.00 each costs 450.00 a month. An invoice for 504.00 bills 28 seats, outside the agreed variation, so it is held: the owner approves it only against a signed order for the three added seats, then updates the agreement on file and the ceiling to 504.00, or disputes it with the vendor.\n\n## What does a completed designation look like?\n\nA designation takes effect only when every row is filled in; a blank row keeps the category on the higher match. This one, with invented figures, is for a software subscription billed by invoice:\n\n| Checklist item | Software subscription |\n|---|---|\n| Agreement on file | 12-month order form, 25 seats at 18.00 each a month, price fixed for the term |\n| Agreement authorized by | Owner, at signing |\n| Vendor and category covered | This vendor only; software subscriptions |\n| Predictable amount | 450.00 a month |\n| Nothing received and counted | Software access |\n| Under the value ceiling | Yes; the policy ceiling is 1,000.00 per invoice |\n| Established vendor | In the vendor record since signup, bank details verified by phone |\n| Delivery vouched by and approver | Office manager, who administers the seats |\n| Second approver | Owner |\n| Agreed variation | None; added seats need a signed order |\n| Ceiling in the system | 450.00 |\n| Vendor-record changes | Verified by calling the number on the signed order form; signed off by the owner, who does not pay bills |\n| Duplicate check | Invoice numbers entered as printed; the system's duplicate check confirmed |\n| Review | At renewal and at each scheduled review |\n\n## What changes when a system rule approves the invoice?\n\nWhen a payables tool approves bills automatically by rule, the last human glance is gone and the rule's scope becomes the whole control. Bound the rule by the designation's three bounds, confirm in the tool's documentation that it enforces each, and never widen it to shorten a queue. Before each payment run, someone other than the rule's owner lists every bill the rule approved since the last run and compares each with its agreement and the vendor record. Any bill that should not have passed is held, and the rule is tightened before the next run.\n\n## What can one-way matching not detect?\n\nAdopting the degree means accepting these exposures by name:\n\n- **Services not delivered.** No document records receipt, so only the approver's knowledge stands in for it. A period billed in advance is paid before anyone can confirm it was delivered.\n- **Wrong quantities.** AccountingTools' three-way matching article notes that without a comparison to receiving documentation there is a risk of paying an invoice for an incorrectly billed quantity. On a usage-billed service the billed usage is the vendor's own figure, so overbilling under the ceiling passes.\n- **Drift from the agreement.** Uplifts, added lines and billing after the agreement ends pass for as long as nobody re-reads the agreement.\n- **Convincing fake invoices.** The Federal Trade Commission's small-business scams guide warns that scammers create phony invoices that look like you ordered products or services. One imitating a designated vendor is caught only by checking its payee details against the vendor record.\n- **Diverted payments.** If a designated vendor's bank details are changed on a false request, every correctly approved invoice pays the wrong party.\n\n## How should the designated population be reviewed?\n\nAccountingTools' accounts payable controls article warns that without periodic review, outdated or fraudulent payments may continue unnoticed, and says regular monitoring helps confirm that the underlying agreements are still in effect and that amounts and vendors are correct. Schedule the review in the policy, and also run it whenever an agreement renews or changes. Someone other than the category approvers runs it, in this order:\n\n1. From the payables system, list by vendor every bill approved or paid since the last review with no purchase order or receiving record behind it, including non-designated vendors.\n2. Compare that list with the designation list, move any vendor or category not on it back to the higher match, and recheck its bills.\n3. For each designated vendor, re-read the agreement, confirm it is still in force, and compare the total paid with what its amount, rates and variation support.\n4. Confirm, from the same change history, that each change to a designated vendor's record was verified by a call to a number from the agreement or vendor set-up and signed off by someone who does not pay bills.\n5. Where a workflow or rule enforces the bounds, confirm it is still enabled and matches the designation list and ceilings.\n6. Record the date, reviewer, exceptions and actions, and end any designation whose agreement has expired.",
  "sources": [
    {
      "id": "REF::1",
      "url": "https://www.accountingtools.com/articles/what-is-three-way-matching.html",
      "title": "Three-way matching definition",
      "publisher": "AccountingTools, Inc. (Steven Bragg)",
      "published": "May 14, 2026",
      "retrieved_at": "2026-09-25T15:31:12+00:00",
      "sha256": "f2704b3f9412907c9e2f7ce741d83da236f795b03abc4fd1933938128a591cc0",
      "supports": [
        "C1",
        "C2",
        "C3",
        "C19"
      ]
    },
    {
      "id": "REF::2",
      "url": "https://www.accountingtools.com/articles/accounts-payable-controls",
      "title": "Accounts payable controls",
      "publisher": "AccountingTools, Inc. (Steven Bragg)",
      "published": "May 02, 2026",
      "retrieved_at": "2026-09-25T15:31:13+00:00",
      "sha256": "80d00f0c8def80c4f3896e1752ddbd079d3a58f99de389e348eaa49d24733b6a",
      "supports": [
        "C4",
        "C15",
        "C21",
        "C22",
        "C30"
      ]
    },
    {
      "id": "REF::3",
      "url": "https://www.ftc.gov/business-guidance/resources/scams-your-small-business-guide-business",
      "title": "Scams and Your Small Business: A Guide for Business",
      "publisher": "Federal Trade Commission",
      "published": "July 2023",
      "retrieved_at": "2026-09-25T15:31:13+00:00",
      "sha256": "58c091376f535de9451a605fdb00cd74d7200ff515a68620192b7bd97e78e22c",
      "supports": [
        "C5",
        "C20"
      ]
    },
    {
      "id": "REF::4",
      "url": "https://www.accountingtools.com/articles/purchase-order",
      "title": "Purchase order definition",
      "publisher": "AccountingTools, Inc. (Steven Bragg)",
      "published": "December 03, 2025",
      "retrieved_at": "2026-09-25T15:31:14+00:00",
      "sha256": "564def0c350bad768f09f5e1e5a73dfae92208b949f98f6e2664aa871cdc457c",
      "supports": [
        "C6",
        "C7",
        "C23",
        "C24",
        "C25"
      ]
    },
    {
      "id": "REF::5",
      "url": "https://www.coso.org/_files/ugd/3059fc_1df7d5dd38074006bce8fdf621a942cf.pdf",
      "title": "Internal Control — Integrated Framework: Executive Summary",
      "publisher": "Committee of Sponsoring Organizations of the Treadway Commission (COSO)",
      "published": "May 2013",
      "retrieved_at": "2026-09-25T15:31:15+00:00",
      "sha256": "488d8ddec9ed24b61aea05374e255824fe7d181ea861b9cbedc63c5e2675fd59",
      "supports": [
        "C8",
        "C16",
        "C26",
        "C27",
        "C29"
      ]
    },
    {
      "id": "REF::6",
      "url": "https://www.ic3.gov/PSA/2023/PSA230609",
      "title": "Business Email Compromise: The $50 Billion Scam",
      "publisher": "Federal Bureau of Investigation, Internet Crime Complaint Center",
      "published": "June 9, 2023",
      "retrieved_at": "2026-09-25T15:31:16+00:00",
      "sha256": "1aed62f75da5ed7fbcb526d2274420c6769bab109905e8e4aa8a73239da86962",
      "supports": [
        "C9",
        "C10",
        "C28"
      ]
    },
    {
      "id": "REF::7",
      "url": "https://quickbooks.intuit.com/learn-support/en-us/help-article/manage-workflows/set-use-bill-approval-payment-release-workflows/L1IOLL9hv_US_en_US",
      "title": "Set up and use bill approval and payment release workflows",
      "publisher": "Intuit Inc.",
      "published": "QuickBooks Online, updated 8/26/2026",
      "retrieved_at": "2026-09-25T15:33:17+00:00",
      "sha256": "bfbecfdedb4249af45d8982c949f95a56b049d102f78cf90bd842182d3426556",
      "supports": [
        "C11",
        "C13",
        "C14",
        "C17",
        "C18",
        "C31",
        "C32"
      ]
    }
  ],
  "related": [
    {
      "question_id": "CG-MCE-023",
      "slug": "what-checks-can-a-very-small-business-put-in-place-when-the-same-person-records",
      "display_title": "What checks can a very small business put in place when the same person records, pays and reconciles?"
    },
    {
      "question_id": "CG-P1B-001",
      "slug": "what-is-two-way-and-three-way-invoice-matching-in-accounts-payable",
      "display_title": "What is 2-way and 3-way invoice matching in accounts payable, and how do I run it across POs, receiving documents, and vendor invoices?"
    },
    {
      "question_id": "CG-P1B-009",
      "slug": "how-a-small-business-can-manage-and-automate-its-accounts-payable-workflow",
      "display_title": "How should a small business manage and automate its accounts-payable vendor-invoice and document workflow?"
    },
    {
      "question_id": "CG-P1B-FULL-114",
      "slug": "what-is-four-way-matching-in-accounts-payable",
      "display_title": "What is four-way matching in accounts payable, and which four documents are matched?"
    }
  ],
  "review_class": "consequential",
  "review_class_trigger": "claim_level_review_required",
  "provenance": {
    "author_model": "claude-opus-5-5",
    "reviewer_model": "claude-opus-5-5",
    "review_verdict": "ACCEPT",
    "review_source": "closure",
    "review_verdict_on_sha256": "1226bdfd5652a566c9e5b46463cb8a507837903b19b9ef39b92e537c2c629f2e",
    "editorial_disposition": "ACCEPT",
    "corrections": 1,
    "approved_by": null,
    "approved_at": null,
    "article_sha256": "1226bdfd5652a566c9e5b46463cb8a507837903b19b9ef39b92e537c2c629f2e",
    "source_map_sha256": "c0548ae779fd043dcdb1d464be2aaa2cc13e65ec24beaabcdedd13fe5eb2300a",
    "transform_sha256": "15bc005637f39383b520d4788fc3e6a929e9ead056b6c943100f0942596370c5"
  },
  "offer": "ask",
  "offer_id": null,
  "sample_target_id": null,
  "datePublished": "2026-09-26T01:29:00Z",
  "reviewed_at": "2026-09-26T01:29:00Z",
  "content_sha": "383f8c80dea48ed6fe1024f3a1fb76c1eb6c2558b115ab2fa25bf1038734437e",
  "release": "2.7.0",
  "slug_provenance": "minted at first publication",
  "question_text": "What is one-way matching in accounts payable, and when is a vendor invoice approved on a single-document match?",
  "jsonld_types": [
    "Article"
  ],
  "related_question_ids": [
    "CG-MCE-023",
    "CG-P1B-001",
    "CG-P1B-009",
    "CG-P1B-FULL-114",
    "CG-P1B-FULL-121"
  ],
  "aliases": [],
  "alias_provenance": []
}