Trade payables vs accounts payable for controllers

Accounts payable is the balance sheet caption and general ledger (GL) control account that records short-term amounts a business owes vendors and creditors for goods or services already received but not yet paid for. AP sits under current liabilities on the balance sheet. It covers unpaid obligations from vendor invoices, including raw materials, packaging, office rent, utilities, software subscriptions, legal fees, and contractor bills.

AP excludes obligations from formal financing instruments. Bank loans, lines of credit, and promissory notes sit in notes payable or short-term debt. Your accounts payable management approach shapes how each obligation moves through recognition, approval, and payment. A GL structure behind that workflow keeps close accuracy and balance sheet presentation intact.

That broad scope creates the classification problem. Non-trade items land in AP, too, including office rent, utilities, contractor invoices, capital expenditures on credit. They’re real liabilities, but they fall outside the trade payables subset. A cloud hosting invoice, a logistics consultant’s month-end statement, or a fixture purchase on net-60 terms all sit in AP. These items typically fall outside the trade payables subset because they don't arise from day-to-day revenue-generating activity. Separate these items at the GL account level, and the trade subset stays useful for close and DPO analysis.

When businesses use accounts payable

Accounts payable can cover far more than trade inputs. The scenarios below show how the caption applies to overhead, professional services, and capital purchases bought on credit.

Overhead and operating expenses

Let’s say a professional services firm receives a $4,000 cloud hosting invoice on net-30 terms. There’s no purchase order (PO) and no inventory impact. The obligation gets coded to an expense GL account and recorded as AP until the firm pays it.

Contractor and service invoices

In another scenario, a manufacturer receives a $12,000 invoice from a logistics consultant at month-end. The amount has been invoiced and formally agreed, so it’s recorded in AP alongside other invoiced vendor obligations. That keeps the liability inside the normal AP workflow rather than pushing it into accruals.

Capital expenditures on credit

Another example would be if a retailer purchases $80,000 in display fixtures on net-60 terms. Even though the fixtures will be depreciated over time as capital items, the unpaid obligation stays in AP until it’s paid. AP records the obligation once an invoice arrives or an amount is formally agreed, whether it’s a trade input, an overhead cost, or a capital expenditure. The broader scope is why AP is typically larger than the trade payable balance used in operating analysis.

Trade payables are defined as “liabilities to pay for goods or services that have been received or supplied and have been invoiced or formally agreed with the supplier.” Two conditions apply. The obligation has to arise from an ordinary-course business transaction, and the amount has to be invoiced or formally agreed.

Some items sit inside AP but fall outside trade payables, including income taxes payable, dividends payable, accrued salaries, royalties payable, and accrued interest. Many finance teams draw the line between trade payables from accruals based on whether the amount has been confirmed or formally documented with the supplier.Trade creditors are the vendors behind these obligations, and what you owe them form the ordinary-course part of your liabilities.

When businesses use trade payables

Trade payables track the obligations tied directly to revenue-generating activity. The scenarios below show what qualifies once goods or services arrive and an invoice or agreement follows.

Manufacturer purchasing raw materials

Let’s say your company orders $50,000 in material procurement on net-45 terms. Goods arrive, the invoice follows, and the obligation sits in trade payables because it feeds directly into the product you sell.

Retailer purchasing inventory

In another scenario, a seasonal wholesale order for 500 units at $120 each on net-30 terms creates a trade payable once goods arrive and the invoice is matched. It’s a direct input to revenue-generating activity, so it lands in the subset used for operating analysis. The procure-to-pay workflow sets the timing, while the invoice-match step is what moves the obligation into trade payables.

Software as a service (SaaS) core product inputs

Let’s say a $3,000-per-month third-party data API that powers your product can be a trade payable. It’s a standard business input to service delivery, which fits how trade payables are typically defined. The same company’s Slack subscription usually isn’t a trade payable because Slack is internal overhead with no direct connection to service delivery. The distinction turns on whether the purchase supports the product or just the back office.

The practical split between the two terms shows up in five places in a Controller’s workflow. Scope, qualifying items, balance sheet presentation, DPO calculation, and classification trigger each answer a different reporting question.

Scope

Accounts payable captures short-term vendor obligations across trade inputs, overhead, professional services, and capital purchases on credit. Trade payables cover only obligations tied to goods and services that support day-to-day revenue generation. A trade payable can sit inside accounts payable, but part of the AP balance falls outside that subset.

Qualifying purchases for each

Trade payables cover goods received and services rendered in the normal course of revenue-generating activity. Other AP items can include rent, utilities, income taxes payable, accrued salaries, interest payable, and dividends payable. Those obligations are real, but they don’t come from purchases of goods or services used to generate revenue.

Balance sheet presentation

The scope difference can stay invisible in internal reporting and still matter on the balance sheet. Companies often show both within a single accounts payable or payables line internally. Public companies that file with the SEC commonly show trade creditors separately from related-party payables, bank borrowings, and other obligations on the face of the balance sheet. Companies that report under IFRS commonly show a separate "trade and other payables" line, sometimes with further breakdown. The specific presentation and disclosure rules that apply to a given company depend on its reporting framework and regulator, so finance teams typically confirm current requirements with their own auditors or legal counsel. Either way, the internal classification choice shapes external presentation.

DPO calculation basis

The same distinction shows up in performance reporting. DPO uses trade payables in the numerator, one of the core accounts payable metrics finance teams track through close. Trouble starts when Controllers substitute the full AP balance. Rent accruals, income taxes payable, and accrued salaries in the numerator produce a ratio that won’t benchmark cleanly against peers whose comparisons isolate the trade payables subset. Your accounts payable turnover ratio gets more useful once the trade-only portion is separated before the calculation runs.

Classification trigger

The reporting differences above depend on one operational question at close: has the obligation been invoiced or formally agreed with the supplier? Many finance teams treat that point as when a trade payable comes into existence, distinguishing it from an obligation that's been incurred but not yet invoiced, such as a software renewal that auto-renewed but whose invoice hasn't arrived, or a consulting engagement whose month-end statement is still pending. How a specific obligation gets classified depends on a company's accounting policy, reporting framework, and facts and circumstances, so finance teams typically work through classification questions with their own accounting advisors or auditors.

The five differences become most visible in the reports and workflows finance teams touch each month. They show up first in DPO, then in close, then in enterprise resource planning (ERP) configuration and supplier-finance review. Each of those steps depends on keeping the trade subset separate from the broader AP balance.

In your DPO report

DPO depends on keeping trade payables in the numerator. A Controller who uses the full AP balance may produce a ratio the chief financial officer (CFO) can’t cleanly compare against peers whose comparisons isolate the trade subset.Your AP subledger needs to identify the trade payables subset before the DPO report runs. Accounts payable reporting can automatically surface this segmentation, and clean segmentation makes the ratio more useful for internal decisions and external comparison.

At the AP subledger during month-end close

The same distinction applies at the transaction level during close. Many companies treat a vendor invoice received on the 28th but not yet approved as still belonging in AP, since the invoice itself has been received even though internal approval is pending. A service consumed in the month for which no invoice has arrived is more commonly treated as an accrued liability instead. How a specific company classifies each case depends on its accounting policy, reporting framework, and facts and circumstances, so finance teams typically work through classification questions with their own accounting advisors or auditors.

Applying accounts payable best practices at close means classifying each obligation against that cutoff before finalizing the subledger. In a goods-received workflow, goods receipt alone usually doesn’t create the trade payable. The obligation comes into existence at the invoice-match step, so invoice matching controls set the timing. Consistent classification keeps the aging, balance sheet, and close support aligned and gives audit reviewers a cleaner path from the source document to the reported liability. Accounting reconciliation at period-end depends on that same classification clarity to confirm that the subledger balance ties to the balance sheet line.

In your ERP or AP automation vendor master

Once the close rule is clear, the next question is where that classification gets set. In ERP and AP automation workflows, classification is controlled by the GL account or ERP field mapping used to route each transaction. Your automated invoice processing configuration determines which GL account the trade liability credits are applied to, which then decides whether each obligation lands in the trade subset used for close and DPO. Brex can enforce the trade vs. non-trade split at invoice intake through accounts payable automation software and bill pay that support custom field mapping and auto-coding rules, including rules that exclude specific values so non-trade categories do not post to the trade payables GL account. If the vendor master and chart-of-accounts mapping isn’t set up correctly before go-live, the distinction may need to be manually rebuilt each period. Setting it correctly at implementation can reduce cleanup at every close.

On your balance sheet if you run a supplier-finance program

The same classification discipline matters even more when a supplier-finance program is involved. Supplier-finance programs, also called reverse factoring or supply chain finance, create a specific classification question. If program terms become atypical, the obligation may need to be reclassified from trade payable to short-term bank debt. That reclassification can shift leverage ratios and, depending on covenant language, trigger debt covenants.

Whether a specific program should be reclassified is a fact-specific accounting and legal question. Companies running these programs typically work through that analysis with their own accounting advisors, auditors, and legal counsel, since the answer depends on program terms, disclosure obligations, and how the arrangement is structured.

Regulators and standard-setters have also increased disclosure expectations around these programs in recent years, generally expecting buyers to describe their key program terms and outstanding obligations. That disclosure focus makes the trade-payable-versus-debt classification visible for any company running a supplier-finance program, even when reclassification itself isn't required. AP automation setup can flag which vendors participate in these programs so the disclosure and classification review doesn't start from scratch each period.

Getting the trade payable vs. accounts payable distinction right can keep DPO comparable to peers, support clear balance sheet presentation, and give supplier-finance disclosures a clear starting point for review. It also shapes the subledger, the journal entries behind invoice matching, and the current liabilities that appear at close. When the trade subset is coded cleanly, finance may be able to explain the balance faster and defend it more confidently.

Brex supports that split through bill pay and ERP field mapping. Brex bill pay, corporate card, and Brex business account transactions are mapped to ERP fields and GL codes, and that teams can set custom auto-coding rules through Brex’s accounts payable automation software. Brex product pages also state that teams can manage invoiced and non-invoiced spend in one place and that transactions sync to ERP in real time. GL coding set at invoice intake then carries through to close without manual reconciliation. Product availability, eligibility, underwriting outcomes, and implementation results vary by business and are subject to review.

“AP was the simplest part of the audit. Everything was in one place, and they didn't push back on a single thing.” — Liz Hanson, Director of Accounting, HappyCo

Accounting automation keeps trade payable classification intact from invoice intake through payment, carrying GL coding through each period without the manual reconciliation work that piles up when the trade vs. non-trade split isn’t set at invoice intake. The full accounts payable process, from vendor setup through subledger close, is where that classification either holds or breaks down.

Created with AI assistance and reviewed by Brex. This article reflects Brex’s perspective at the time of publication and is intended for general informational purposes only. It is not intended as legal, tax, accounting, or financial advice. Laws, regulations, and guidance may vary based on your specific circumstances, and interpretations or outcomes may differ. Information may also change over time. Before making any decisions, you should consult your own qualified legal, tax, accounting, or financial advisors.

The testimonials and case studies presented herein reflect the individual experiences of specific customers and are not representative of typical results. Individual outcomes will vary based on a number of factors, including but not limited to company size, spend volume, and product usage. Brex did not compensate any testimonial participants for their statements. Following the completion of certain case studies, some participants received an unsolicited gift valued at less than $100.00 as a gesture of appreciation. Such gifts were not offered, promised, or agreed upon prior to or as a condition of participation, and do not constitute payment, endorsement fees, or material compensation under applicable FTC guidelines. The views expressed in these testimonials are those of the individual participants and were not influenced by the receipt of any gift.