Accounts payable manages the money a business owes to its suppliers for goods and services already received. Its main purpose is to make sure every payment is valid, accurate, properly approved and made on time. In practice, the team receives invoices, checks them against purchase orders and receiving records, records the liability in the ledger, and schedules payment. Done well, this protects cash, keeps supplier relationships healthy and gives management reliable figures on what the company owes. For example, a manufacturer that pays a distributor late may lose favorable terms, while one that pays the same invoice twice loses cash that must then be recovered through a difficult refund process.
Supplier invoices arrive by mail, email, electronic data interchange or a supplier portal, and each must be captured as a structured record. Many organizations scan paper invoices with optical character recognition, which extracts the vendor name, invoice number, date, line items and totals. The captured data is then validated against vendor master records and routed through an approval workflow. Routing rules send invoices to the right approver based on amount, department or cost center. Clean capture reduces manual keying errors and creates an audit trail showing when each document arrived, who handled it and what decisions were made along the way.
Three-way matching compares three documents before an invoice is paid: the purchase order that authorized the buying, the receiving record that proves goods or services arrived, and the supplier invoice requesting payment. If quantities, prices or totals differ beyond an agreed tolerance, the invoice is held for review instead of being paid. This check stops payments for items never ordered, goods never delivered and prices never agreed. It also exposes duplicate invoices, because the same purchase order line should not be matched twice. Many finance systems automate the comparison and route only exceptions to a person, which saves time while keeping human judgment where discrepancies genuinely need resolution.
Two-way matching compares only the purchase order and the supplier invoice, skipping the receiving record. Organizations may use it for services, subscriptions or low-risk spend where there is no physical receipt to verify. Four-way matching adds an inspection or quality acceptance record between receiving and invoicing, which suits regulated industries or high-value goods that must pass testing before payment. The choice reflects a trade-off between control strength and processing speed. More matching steps catch more errors but slow payment and add administrative effort, so a sound policy assigns the depth of matching to the risk and value of each category of spend.
Segregation of duties means that no single person controls every stage of a transaction, such as creating a vendor, approving an invoice, releasing payment and reconciling the bank account. When one individual can perform several of these steps, the risk of fraud or error rises sharply, because the person can create a fictitious supplier and pay it without any independent check. Separating these roles means that a second person must review and confirm each critical action. Approval limits, delegation matrices and system-enforced permissions help maintain this separation. Auditors routinely test these controls, and weaknesses are often a primary focus of internal control assessments.
The vendor master file holds the legal name, tax identification, bank details, payment terms and remittance address for every supplier the company pays. Errors or unauthorized changes here can misdirect payments entirely, which makes it a frequent target for payment diversion fraud. Good practice requires formal onboarding with documented approval, verification of tax and banking details through an independent channel, restricted edit rights and a log of every change. Periodic reviews remove duplicate or dormant vendors. Because so many downstream processes depend on this file, its accuracy strongly influences the reliability of matching, payment and reporting.
Payment terms set when a supplier expects to be paid, such as thirty days after the invoice date. Paying later keeps cash in the business longer, while paying earlier can capture a discount. A common arrangement offers two percent off if the invoice is settled within ten days. Expressed as an annualized rate, that discount can be substantial compared with many borrowing costs, which is why it is often attractive. The right choice depends on the company's cash position and funding costs. Accounts payable teams therefore track due dates and discount deadlines, coordinating with treasury so that payments support liquidity without damaging supplier trust or missing valuable savings.
The decision compares the discount's implied annual return with the company's cost of capital and its alternative uses of cash. A two percent discount for paying ten days early, instead of thirty days, implies a return far above typical short-term borrowing rates, so it is usually worth taking when liquidity allows. However, the analysis should also consider whether the company has spare cash, whether paying early would strain a covenant or revolving facility, and whether the discount is truly available or offset by price increases. Documenting the calculation helps the organization apply a consistent rule across suppliers and avoids decisions based on habit rather than evidence.
An accounts payable balance represents invoices received from suppliers that are approved and awaiting payment. An accrued liability represents an obligation for goods or services received during the period for which no invoice has yet arrived, such as utilities consumed or consulting work performed near period end. Accrual ensures that expenses and liabilities appear in the period they were incurred, consistent with accrual accounting principles. Accounts payable teams often work with accruals by estimating amounts at month end and reversing them when the actual invoices post. Keeping this distinction clear prevents double counting and gives a more accurate picture of what the company owes at any reporting date.
Duplicate payments occur when the same invoice is entered and paid more than once, sometimes with a slightly altered number or date to evade simple checks. Preventive controls include system warnings when an invoice number, vendor and amount repeat, and restrictions on manual overrides. Detective analytics go further by comparing amounts, dates, descriptions and vendor fuzzy names across a payment history. Many organizations run periodic recovery audits that flag probable duplicates for review. Because recovered cash can take months to return, early detection matters. The combination of prevention at entry and regular analysis afterward gives the strongest protection.
A payment run is a scheduled batch in which approved invoices due on or around a particular date are selected and paid together. Many companies run weekly or semimonthly, which simplifies bank file transmission and approval. The schedule is shaped by due dates, discount deadlines, cash forecasts and any dependencies, such as paying critical suppliers before a production cycle. Treasury often reviews the total before release to confirm sufficient funds. Consistent, predictable timing builds supplier trust, while flexibility allows the business to delay non-critical payments within agreed terms when cash is tight, without breaching contractual obligations.
Common electronic methods include automated clearing house transfers, wire transfers, virtual cards and real-time payment networks. Automated clearing house payments are low cost and suitable for routine supplier batches, but they settle over a short window and may be reversed. Wire transfers are fast and final, which makes verification of beneficiary details essential before release. Virtual cards allow card acceptance by suppliers that prefer it, with rebate potential for the buyer, though not every supplier accepts them. Each method needs dual authorization, callback verification of changed bank details and reconciliation against bank statements to limit fraud and misdirected funds.
After payments are released, the bank statement shows which transfers cleared, failed or were returned. Bank reconciliation compares this external record with the company's internal payment ledger to identify differences such as outstanding checks, timing gaps, bank fees or unauthorized debits. Accounts payable supports this process by providing payment files, remittance details and returned item reports. Clearing reconciling items promptly prevents errors from accumulating and helps detect fraud early. A payment recorded as sent but never received, for instance, may signal a misdirected or intercepted transfer that requires immediate investigation with the bank and the supplier.
A supplier statement lists the invoices, credits and payments the vendor believes are open on the buyer's account. Reconciling it with the company's own subledger identifies differences caused by unrecorded invoices, duplicate postings, timing of payments, or disputed credits. The process typically compares each line, investigates unmatched items and documents explanations. Regular reconciliation keeps balances accurate, reduces disputes and supports month-end close, because the reported liability should agree with supplier evidence. It also strengthens relationships, since problems surface early rather than during an overdue collection call. Many teams perform this reconciliation for their largest or most active suppliers first.
Cutoff means assigning each transaction to the correct accounting period, so that liabilities and expenses for goods and services received before the period end are recorded in that period, even if the invoice arrives later. Errors in cutoff can overstate or understate expenses, distort profit and mislead lenders or investors. Procedures include reviewing receiving logs dated near period end, examining invoices received shortly after the close, and recording accruals for unbilled items. Organizations also set a clear close calendar so that invoice processing stops at a defined time. Strong cutoff discipline makes monthly results more comparable and reliable for decision-making.
Days payable outstanding measures the average number of days a company takes to pay its suppliers, calculated from accounts payable, cost of goods sold or purchases, and a period length such as 365 days. A higher figure means the company holds cash longer, which can improve liquidity, while a very high figure may signal supplier stress or strained relationships. Accounts payable practices, including payment timing, discount policies and invoice processing speed, directly shape this metric. Analysts use it alongside receivable and inventory days to view the cash conversion cycle. Managers should interpret the metric in light of industry norms and supplier expectations rather than pursuing a number in isolation.
Supply chain finance lets suppliers receive early payment from a bank, while the buyer pays the bank on the original due date, often extending its payment terms. From an accounts payable perspective, the invoice may still be recorded as an obligation to the buyer, though the agreement's classification affects how it appears in financial statements. Because such programs can lengthen payables without obvious disclosure, regulators and analysts scrutinize them to ensure transparency about debt-like arrangements. Organizations should document the economic substance, assess disclosure requirements and monitor supplier participation. Used responsibly, these programs can strengthen suppliers' liquidity while supporting the buyer's working capital, but they must be understood and reported accurately.
Accounts payable carries several compliance duties, including collecting accurate tax identification from vendors, withholding taxes where required and reporting certain payments to tax authorities. In many jurisdictions, organizations must issue information returns for payments to contractors or service providers above specified thresholds. Sales and use tax, value-added tax and customs duties may also affect invoice treatment. Recordkeeping rules require retention of invoices, approvals and payment evidence for defined periods. The specific obligations depend on location, industry and entity type, so reader should consult qualified tax and legal advisors and current official guidance. This page is educational and does not replace licensed professional judgment.
Internal control frameworks, such as the widely used COSO model, describe components including the control environment, risk assessment, control activities, information and communication, and monitoring. Within accounts payable, control activities include authorization limits, three-way matching, segregation of duties, vendor master restrictions and independent reconciliation. Auditors focus on these controls because the accounts payable cycle is a common route for both error and fraud, and because liabilities are often material. They test controls by sampling transactions, reviewing approvals and examining system access. Effective controls reduce audit effort and give management confidence that reported liabilities and expenses are complete and accurate.
Common schemes include fictitious vendor fraud, in which an employee creates a shell supplier and submits false invoices, and payment diversion, in which bank details are changed to redirect legitimate payments. Business email compromise can also trick staff into altering remittance instructions. Duplicate billing and inflated invoices round out the list. Reduction measures include strict vendor onboarding, independent verification of bank detail changes using known contact information, segregation of duties, data analytics to flag unusual patterns, and staff training on social engineering. No single control is sufficient, so layered defenses and periodic review provide the most reliable protection against evolving tactics.