Corpay

Accounts Payable Terminology: 40 Terms Finance Teams Should Know

Category:AP Automation
Updated:2026-09-15
Author:David Luther

Accounts payable terminology covers the vocabulary of the invoice-to-payment cycle, from how an invoice arrives through how it gets matched, approved, paid, and closed. The forty terms below are grouped by where you meet them in the workflow rather than alphabetically, because the order you encounter them is the order that makes them make sense.

Alphabetical order is fine for looking something up and bad for learning how the pieces connect. If you need the cross-domain A to Z view that also covers cards and currency, the wider Corpay glossary is the index for that. Everything here stays inside AP, and each definition is written so it can be lifted into a process document or an audit memo without editing.

Key Takeaways

  • The AP vocabulary splits cleanly into six stages, and most confusion in practice comes from terms that live in adjacent stages being used interchangeably.

  • Invoice capture is a process and OCR is one technology used inside it, which is the single most common conflation in AP conversations.

  • Tolerance is a rule you set in advance and an exception is what happens when an invoice breaks it, so a high exception rate is often a tolerance-configuration problem.

  • Delegation of authority and segregation of duties answer different audit questions, and having one does not satisfy the other.

  • Payment rail terminology matters because ACH credit, ACH debit, wire, virtual card, and check each carry a different control profile and a different fraud profile.

  • Vendor master data quality determines whether everything downstream works, which is why bank account validation belongs to AP rather than to procurement.

The 40 terms at a glance

Term

One-line gloss

Group

1099

IRS information return reporting payments to non-employees

Suppliers and data

Accounts payable

Short-term obligations owed to suppliers for goods and services received

Intake and capture

Accrual

Recording an expense in the period incurred rather than when paid

Close and measurement

ACH credit

A push payment where the payer instructs their bank to send funds

Payment execution

ACH debit

A pull payment where the payee initiates the withdrawal with authorization

Payment execution

Approval routing

The rules that decide who approves a given invoice

Approval and controls

Approval workflow

The defined sequence of reviews an invoice passes through

Approval and controls

Audit trail

The immutable record of who did what to an invoice and when

Approval and controls

Bank account validation

Confirming supplier banking details belong to the supplier

Suppliers and data

Business email compromise

Fraud using impersonated email to redirect payments

Approval and controls

Check

A paper payment instrument drawn on a bank account

Payment execution

Cost per invoice

Fully loaded processing cost divided by invoice volume

Close and measurement

Days payable outstanding

Average days taken to pay suppliers

Close and measurement

Delegation of authority

The documented spend limits attached to each role

Approval and controls

Duplicate payment

The same obligation paid more than once

Approval and controls

E-invoicing

Exchange of invoices as structured data between systems

Intake and capture

ERP integration

The connection between an AP system and the accounting system of record

Close and measurement

Exception

An invoice that cannot proceed without human intervention

Validation and matching

Goods receipt

The record confirming ordered items were delivered

Validation and matching

Invoice

A supplier's request for payment for goods or services

Intake and capture

Invoice capture

Getting invoice data out of the arriving document and into a system

Intake and capture

Line-item detail

Invoice data at the individual product or service level

Intake and capture

Optical character recognition

Technology that converts document images into machine-readable text

Intake and capture

Payment run

A scheduled batch of approved invoices released for payment

Payment execution

Payment terms

The agreed window and conditions for paying a supplier

Suppliers and data

Purchase order

A buyer's formal commitment to buy specified goods at a stated price

Validation and matching

Purchase requisition

An internal request for approval to buy something

Validation and matching

Reconciliation

Confirming payment records agree with bank and ledger records

Close and measurement

Remittance advice

The detail telling a supplier what a payment covers

Payment execution

Segregation of duties

Splitting incompatible tasks across different people

Approval and controls

Straight-through processing

Invoices completing the cycle with no human touch

Close and measurement

Supplier enrollment

Onboarding a supplier onto a payment method and capturing their data

Suppliers and data

Supplier portal

A self-service interface for submitting invoices and checking status

Intake and capture

Three-way match

Comparing invoice, purchase order, and goods receipt

Validation and matching

Tolerance

The pre-set variance allowed before an invoice becomes an exception

Validation and matching

Two-way match

Comparing invoice and purchase order only

Validation and matching

Vendor master

The authoritative record of every supplier and their details

Suppliers and data

Virtual card

A single-use card number generated for one payment

Payment execution

W-9

The IRS form collecting a US supplier's taxpayer identification

Suppliers and data

Wire transfer

A same-day, irrevocable bank-to-bank funds transfer

Payment execution

Which terms describe how an invoice arrives?

Everything in AP starts with a document showing up, and the intake stage decides how much manual work the rest of the cycle inherits. An invoice that arrives as structured data behaves very differently from the same invoice arriving as a PDF attached to an email, even though both are legally the same request for payment.

Term

Definition

Accounts payable

Accounts payable is the set of short-term obligations a business owes suppliers for goods and services it has already received. It sits on the balance sheet as a current liability and is distinct from accrued expenses, which cover obligations not yet invoiced. A broader treatment of what accounts payable covers runs through the function as well as the account.

Invoice

An invoice is a supplier's formal request for payment, stating what was supplied, in what quantity, at what price, and by when payment is due. It becomes an obligation once validated against the underlying commitment. The steps it moves through are covered in the accounts payable process.

Invoice capture

Invoice capture is the process of extracting invoice data from an arriving document and creating a structured record in the AP system. It covers intake across email, mail, portal upload, and EDI, plus the validation and coding that follow. Capture is a workflow stage, not a single technology.

Optical character recognition (OCR)

Optical character recognition is technology that converts an image of text into machine-readable characters. In AP it reads scanned or PDF invoices so their fields can be mapped to a data model. OCR is one component inside invoice capture, and accuracy varies sharply with document quality and layout consistency.

E-invoicing

E-invoicing is the exchange of invoices as structured data between a supplier's system and a buyer's system, with no document image required. Regulatory pressure is now driving adoption. The European Commission's VAT in the Digital Age package was adopted on 11 March 2025 and entered into force on 14 April 2025, allowing member states to mandate domestic e-invoicing without a special EU derogation.

Supplier portal

A supplier portal is a self-service interface where suppliers submit invoices, update their details, and check payment status without contacting AP. Well-adopted portals cut inbound status inquiries substantially, which is usually where the return shows up first. The mechanics are covered in the supplier portal walkthrough.

Line-item detail

Line-item detail is invoice data captured at the individual product or service level rather than as a single header total. It's what makes accurate general ledger coding, three-way matching, and category-level spend analysis possible. Header-only capture is faster to implement and blocks most of the analysis anyone later asks for.

What is the difference between invoice capture and OCR?

Invoice capture is the whole process of getting an invoice into your system; OCR is one technology used at one step inside it. Conflating them leads to bad vendor evaluations, because a demo that shows impressive character recognition says nothing about intake channels, coding accuracy, or how the system handles an invoice that doesn't match its template.

The practical test during an evaluation is to hand over twenty of your own ugliest invoices, including the handwritten one and the one that arrives as a photo of a printout. Accuracy on a vendor's clean sample set is not a measurement of anything you'll experience.

What does e-invoicing actually require?

E-invoicing requires structured, machine-readable data in an agreed format, which a PDF attachment is not, regardless of how neatly it's laid out. A PDF is a picture of an invoice that happens to contain selectable text; an e-invoice is a data file that a receiving system can validate without interpretation.

Timelines are worth knowing even for US-only teams with European subsidiaries. Under ViDA, Digital Reporting Requirements apply to cross-border business-to-business transactions from 1 July 2030, with domestic systems aligned to EU standards by 1 January 2035, according to the European Commission's VAT in the Digital Age materials.

Which terms describe how an invoice gets validated?

Validation is where an invoice is checked against what was actually ordered and received, and it's the stage that generates almost all of the manual work in a typical AP function. The vocabulary here is precise for a reason, because the difference between a tolerance and an exception is the difference between a rule and a symptom.

Term

Definition

Purchase order

A purchase order is a buyer's formal commitment to purchase specified goods or services at agreed quantities and prices. It's issued before delivery and becomes the reference document an invoice is matched against. The distinction from the invoice itself is covered in purchase order vs. invoice.

Purchase requisition

A purchase requisition is an internal request seeking approval to buy something, raised before any commitment to a supplier exists. It's the control point where spend is authorized rather than merely recorded. The purchase requisition breakdown covers how it feeds the PO.

Goods receipt

A goods receipt is the record confirming that ordered items or services were actually delivered, in what quantity, and when. It's created by whoever receives the delivery rather than by AP. Without it, three-way matching is impossible and the buyer is paying on a supplier's word.

Two-way match

A two-way match compares the invoice against the purchase order on quantity and price, with no receipt check. It suits services and other spend where delivery confirmation isn't practical. It accepts more risk than a three-way match in exchange for moving faster.

Three-way match

A three-way match compares the invoice, the purchase order, and the goods receipt before an invoice is approved for payment. It's the standard control for physical goods. The full mechanics, including partial deliveries and price variances, are in the three-way matching guide.

Exception

An exception is an invoice that cannot proceed automatically and needs human intervention, whether from a match failure, missing PO, coding ambiguity, or a duplicate flag. Exception volume is the best single proxy for how much manual work AP is absorbing. Roughly 89% of organizations use at least some AP automation, yet half still process more than 5,000 invoices a month through workflows that are not fully automated.

Tolerance

A tolerance is the variance a business allows before a match discrepancy becomes an exception, set as a percentage, an absolute amount, or both. Tolerances that are too tight generate exception volume nobody can clear; tolerances that are too loose let real errors through. It's a policy decision, reviewed periodically rather than set once.

What counts as an exception, and what counts as a tolerance?

A tolerance is a rule you configure in advance and an exception is the outcome when an invoice breaks it. Teams that treat a rising exception rate purely as a data-quality problem often find the actual cause is a tolerance threshold set years ago against a different supplier mix.

The PYMNTS Intelligence and WEX 2026 Business Payments Tracker figures above suggest the scale of manual handling still in play, and in most of the environments I've reviewed, a meaningful share of it traces back to threshold settings nobody has revisited.

Where do purchase orders and requisitions fit?

The requisition authorizes the spend, the purchase order commits the company to a supplier, and the invoice requests payment against that commitment. Losing the requisition step is how organizations end up with spend that was never approved by anyone with the authority to approve it, discovered at invoice time when the money is already owed.

The full upstream sequence, including sourcing and contract steps, is laid out in the procure-to-pay cycle.

Which terms describe approvals and controls?

Controls exist because payment authority is the most attractive target in a finance organization. AFP's 2026 Payments Fraud and Control Survey Report found that 76% of US organizations experienced attempted or actual payments fraud in 2025, which makes this vocabulary less academic than it looks.

Term

Definition

Approval workflow

An approval workflow is the defined sequence of reviews an invoice passes through before it's released for payment. It specifies the stages and their order. The design choices that keep invoices from stalling are covered in the invoice approval workflow guide.

Approval routing

Approval routing is the set of rules determining which specific people or roles receive a given invoice for approval, based on attributes like amount, cost center, category, or entity. Routing is the logic; the workflow is the structure. Poor routing shows up as invoices sitting with people who have no context for them.

Delegation of authority

Delegation of authority is the documented schedule of spend limits attached to each role, stating who may approve what value of commitment. It's the reference an auditor uses to test whether an approval was valid. It needs a defined process for temporary delegation during absence, or approvals quietly migrate to whoever is available.

Segregation of duties

Segregation of duties is the separation of incompatible responsibilities so that no single person can create, approve, and pay an obligation. In AP the classic separation is between vendor master maintenance and payment release. It's a structural control, and it survives staff turnover better than any detective control does.

Audit trail

An audit trail is the sequential record of every action taken on an invoice, capturing who acted, what changed, and when, in a form that cannot be edited afterward. It's what makes an approval defensible after the fact. An audit trail assembled from email threads is not an audit trail.

Duplicate payment

A duplicate payment is the same obligation paid more than once, usually from duplicate vendor records, a resubmitted invoice, or an invoice number entered inconsistently. Recovery is possible but slow and relationship-dependent. Prevention mechanics are covered in the duplicate payment breakdown.

Business email compromise

Business email compromise is fraud in which an attacker impersonates an executive or supplier by email to redirect a legitimate payment to an account they control. AFP reported that BEC affected 74% of organizations in 2025. The defense is procedural verification through a known channel rather than technical filtering.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper
protect-cashflow-with-ap.jpg

What is the difference between an approval workflow and approval routing?

The workflow defines the stages and the routing decides who sits in them. A single workflow can serve an entire organization while routing rules vary by entity, amount band, and cost center underneath it.

Getting this distinction right matters during system configuration, because teams frequently build a separate workflow per department when what they actually needed was one workflow with better routing rules. The result is dozens of near-identical workflows that all have to be maintained separately.

Why do auditors ask about segregation of duties and delegation of authority?

They test different things. Delegation of authority establishes whether the person who approved had the authority to approve that amount; segregation of duties establishes whether any single person could have completed a fraudulent payment unaided.

An organization can have an immaculate delegation schedule and still fail a segregation test, which is the situation small AP teams run into constantly. When headcount makes true separation impossible, the accepted compensating control is a documented independent review of payment files before release, performed by someone outside AP. Write down which control you're relying on before the auditor asks, because the answer assembled under questioning is never the good answer. The broader fraud patterns are covered in the guide to AP fraud.

Which terms describe how the money moves?

Each payment rail carries a different speed, a different reversibility, and a different fraud profile, and the vocabulary distinctions map directly onto control decisions. AFP found paper checks were the payment method most targeted by fraud at 58%, ahead of ACH debits at 30% and wire transfers at 25%.

Term

Definition

ACH credit

An ACH credit is a push payment in which the payer instructs their bank to send funds to the payee's account through the automated clearing house network. It's the dominant electronic rail for US supplier payments. The origination mechanics are in the ACH credit explainer.

ACH debit

An ACH debit is a pull payment in which the payee initiates a withdrawal from the payer's account under a prior authorization. In AP it appears mostly in recurring supplier arrangements. The authorization and return rules are covered in the ACH debit explainer.

Wire transfer

A wire transfer is a same-day, bank-to-bank funds transfer that settles individually rather than in a batch, and is effectively irrevocable once sent. Its speed and finality are why it's the preferred target in payment-redirection fraud. Reserve it for urgent or high-value payments with verified banking details.

Virtual card

A virtual card is a card number generated for a specific payment, typically limited to one use, one supplier, and one amount. Single-use numbers remove the standing account number that static card payments expose. The virtual card explainer covers acceptance and settlement.

Check

A check is a paper instrument drawn on a bank account, still widely used in US B2B despite carrying the highest fraud exposure of any rail. Volume is falling steadily. Check payments fell to 9.2 billion by number and $24.45 trillion by value in 2024, according to Federal Reserve data.

Payment run

A payment run is a scheduled batch of approved invoices released for payment together, usually weekly or twice weekly. Batching creates a clean control point for review before funds move. Its cadence is one of the few working-capital levers AP controls directly.

Remittance advice

Remittance advice is the detail sent to a supplier explaining which invoices a payment covers and how any deductions were applied. Without it, suppliers cannot apply cash and your AP team absorbs the reconciliation calls. The remittance advice guide covers required fields.

How do ACH credit and ACH debit differ?

The difference is who initiates. In an ACH credit the payer pushes funds out; in an ACH debit the payee pulls funds in under an authorization the payer granted earlier.

For AP that distinction is a control question rather than a mechanical one. Credits keep initiation inside your own controls. Debits hand initiation to the supplier, which is convenient for recurring obligations and worth limiting to counterparties you'd extend that trust to deliberately. ACH transfers reached 39.7 billion payments worth $104.06 trillion in 2024, within a total of 236.6 billion noncash payments, according to the Federal Reserve's 2025 Federal Reserve Payments Study.

When is a virtual card the right rail?

A virtual card fits when the supplier already accepts cards, the payment is discrete, and the buyer wants a per-payment control plus rebate participation. It fits badly when acceptance costs would push a supplier to raise prices or when the relationship can't absorb the conversation.

Worth being straight about this, since finance buyers have heard the pitch before. Suppliers pay the acceptance cost, and a card program built by pressuring reluctant suppliers onto a rail they don't want tends to produce exactly the friction the program was meant to remove. Enrollment works when there's a real benefit on the supplier side, usually faster settlement, and it stalls when there isn't.

Which terms describe suppliers, data, and measurement?

Supplier data is the layer everything else depends on, and measurement is how you find out whether any of it is working. Deloitte's 2025 Global Business Services Survey found roughly 50% of organizations achieved more than 20% savings from their global business services operations, which is the kind of result that only becomes visible with consistent measurement underneath it.

Term

Definition

Vendor master

The vendor master is the authoritative record of every supplier, holding legal name, remit-to address, banking details, tax identification, and payment terms. Every downstream process inherits its accuracy. Change controls on this file matter more than almost any other AP control.

Supplier enrollment

Supplier enrollment is the process of onboarding a supplier onto a payment method and capturing the data needed to pay them, including banking details and tax forms. It's labor-intensive and rarely staffed adequately. Enrollment quality determines what share of spend can move to electronic rails.

Bank account validation

Bank account validation is confirming that the banking details on file genuinely belong to the named supplier, through micro-deposits, third-party verification services, or callback to a known contact. It's the specific control that stops payment-redirection fraud. Email confirmation of a bank change is not validation.

Payment terms

Payment terms are the agreed window and conditions for paying a supplier, such as net 30 or 2/10 net 30, which offers a 2% discount for payment within 10 days. Terms are a working-capital instrument as much as an administrative detail. The business payment terms guide covers the common structures.

W-9

Form W-9 is the IRS form used to collect a US supplier's legal name, taxpayer identification number, and tax classification. It's collected at onboarding and supports year-end information reporting. Chasing W-9s after the fact during January is one of the more avoidable annual fire drills.

1099

A 1099 is an IRS information return reporting certain payments to non-employees, most often Form 1099-NEC for contractor compensation. Accuracy depends entirely on vendor master classification and W-9 data captured earlier. Misclassification surfaces as a filing problem in January and a tax problem later.

Reconciliation

Reconciliation is confirming that payment records agree with bank statements and the general ledger, with differences identified and explained. It's the close activity most affected by payment-method fragmentation. Single-file settlement across rails reduces the work more than any reporting improvement does.

Accrual

An accrual records an expense in the period it was incurred rather than the period it was paid, capturing obligations for goods or services received but not yet invoiced. Accrual accuracy at close depends on knowing what's in flight. The AP aging view is a common input to that estimate.

Days payable outstanding

Days payable outstanding is the average number of days a business takes to pay its suppliers, calculated as accounts payable divided by cost of goods sold, multiplied by days in the period. It's read as a working-capital indicator. The days payable outstanding guide covers interpretation and its limits.

Straight-through processing

Straight-through processing describes invoices that complete the full cycle from receipt to payment with no human touch. It's the cleanest measure of automation maturity because it only moves when the process genuinely changes. Deloitte found 66% of organizations plan to invest in generative AI within the next three years, much of it aimed at this metric.

Cost per invoice

Cost per invoice is total fully loaded AP processing cost divided by invoices processed in the same period, including labor, systems, and overhead allocation. The Hackett Group found Digital World Class finance organizations operate at 45% lower cost as a percentage of revenue than peers, with close cycles 35% to 57% shorter.

ERP integration

ERP integration is the connection between an AP system and the accounting system of record, carrying invoices, payment status, and general ledger entries in both directions. Depth varies enormously between a nightly file drop and a real-time bidirectional API. The ERP explainer covers the systems themselves.

What lives in a vendor master, and why does it decide everything downstream?

The vendor master holds the supplier's legal identity, remit-to details, banking information, tax data, and terms, which means every payment, every tax filing, and every duplicate check depends on it being right. A duplicate vendor record is the root cause of a large share of duplicate payments, and an unvalidated bank change is the mechanism behind most successful payment-redirection fraud.

The control that matters is who can change banking details and what verification is required before the change takes effect. Practices for maintaining that file sit inside broader vendor management discipline, and the answer at most companies is less rigorous than the org chart implies.

Which four numbers tell you whether AP is working?

Cost per invoice, invoice cycle time, exception rate, and days payable outstanding cover efficiency, speed, quality, and cash between them. Adding more metrics rarely adds more insight until those four are reliable.

Reliability is the catch, and it depends on ERP integration rather than on reporting tools. A metric computed from a monthly export describes the state of the world at export time, and the wider spend management picture has the same dependency. Fix the connection before you build the dashboard.

Automate AP end to end

Replace manual approvals, check runs, and reconciliation with a single automated workflow that syncs to your ERP — so your AP team spends time on strategy, not paperwork.

Explore AP Automation
Card infrastructure that grows with you image.png

Put the vocabulary to work across your ERP

Most of the terms above describe work that has to happen whether or not anyone is staffed to do it. Supplier enrollment, exception follow-up, payment delivery, and reconciliation are the four that quietly consume an AP team, and they're the four a managed service is built to absorb.

Corpay runs fully managed AP across virtual card, ACH, and check, with single-use virtual cards where acceptance makes sense. Connections run through 100+ ERP integrations including NetSuite, Sage Intacct, Business Central, and Acumatica, so the data behind your metrics stays current rather than exported. Customers typically save about 40% of AP team time, go live in weeks, and collectively earn more than $800 million in rebates per year. The AP automation overview covers how the pieces fit together.

Frequently Asked Questions

What does accounts payable mean in accounting?

In accounting, accounts payable is a current liability representing amounts owed to suppliers for goods and services already received but not yet paid. It's recorded when the obligation arises rather than when cash moves, which is what distinguishes accrual accounting from cash accounting in this context.

What is the difference between accounts payable and accounts receivable?

Accounts payable is money your business owes to suppliers; accounts receivable is money customers owe your business. The two functions mirror each other in process and sit on opposite sides of the balance sheet, and the payables versus receivables comparison covers where the mechanics actually differ.

What does AP automation cover?

AP automation covers invoice capture and coding, matching against purchase orders and receipts, approval routing, payment execution across rails, and the reconciliation and reporting that follow. Scope varies substantially by vendor, and the boundary that matters most in an evaluation is whether supplier enrollment and exception follow-up are included or left with your team.

Which AP metrics matter most?

Cost per invoice, invoice cycle time, exception rate, and days payable outstanding give you efficiency, speed, quality, and cash. Straight-through processing rate is the best single indicator of automation maturity, because unlike the others it only improves when the underlying process actually changes.

Headshot.JPG

David Luther

Product Marketing Program Manager
David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.
AP Automation

Smarter payments. Stronger growth. Keep business moving.

Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.