Accounts Payable vs Receivable: Invoice Workflow Guide

Accounts payable vs accounts receivable is the difference between money your business owes and money owed to your business. Accounts payable (AP) is money your business owes to suppliers, vendors, contractors, tax authorities, lenders, or other creditors, and in invoice operations it usually starts when you receive a supplier invoice or bill. Accounts receivable (AR) is money customers owe your business, and it usually starts when you create and send a customer invoice.

The simplest way to remember AP vs AR is cash direction: AP manages cash going out; AR manages cash coming in. The invoice-desk distinction is just as useful: AP handles documents received from outside the business, while AR handles invoices the business issues to customers and then collects.

Question	Accounts payable	Accounts receivable
Who owes the money?	Your business owes a supplier or creditor	A customer owes your business
Usual invoice trigger	A supplier invoice or vendor bill arrives	Your business creates and sends a customer invoice
Cash direction	Cash will go out	Cash should come in
Balance-sheet treatment	Liability	Asset
Typical owner	AP clerk, bookkeeper, controller, or finance team	AR clerk, billing team, bookkeeper, controller, or finance team
Main document risk	Paying an incorrect, duplicate, fraudulent, or unapproved invoice	Failing to collect, applying cash incorrectly, or leaving disputes unresolved
Main workflow question	Should we approve and pay this obligation?	Has the customer paid what they owe?

That is the core accounts payable and receivable difference. AP is not just "bills" and AR is not just "sales." Each side is a workflow built around financial documents, dates, amounts, counterparties, terms, approvals, and reconciliation evidence.

Route the document before you think about the ledger

When a document lands in a finance inbox, the first question is not "asset or liability?" It is "which direction did this document travel?"

If the document came from a supplier, vendor, contractor, utility, lender, landlord, or tax authority and asks your business to pay, it usually belongs to accounts payable. A supplier PDF invoice for materials, a vendor bill for software, or a contractor invoice for services all create or support AP work.

If your business created the invoice and sent it to a customer, the document belongs to accounts receivable. The invoice represents a claim against the customer until payment is received, matched, and reconciled.

Some documents support AP or AR without being the main payable or receivable record:

• A purchase order supports AP because it shows what the business agreed to buy, but it is not itself an invoice or a payable.
• A goods receipt or delivery note supports AP matching because it helps prove the goods or services were received.
• A remittance advice, payment receipt, or customer payment email usually supports AR cash application because it helps match money received to customer invoices.
• A bank deposit record may support AR reconciliation, but it does not replace the customer invoice or remittance evidence.

This is where the distinction between purchase orders and invoices matters. A purchase order starts on the buying side before the supplier bills you; the supplier invoice starts the payable review. On the AR side, your own customer invoice is the document you are trying to collect.

For ambiguous documents, classify the obligation or claim they support. If the document supports money your business owes, it points toward AP. If it supports money owed to your business, customer payment, or cash application, it points toward AR.

What accounts payable does with a supplier invoice

Accounts payable begins when the business receives a document that needs to be checked before payment. In everyday finance work, that document is usually a supplier invoice or vendor bill.

A typical accounts payable invoice workflow looks like this:

1. Receive the supplier invoice or bill.
2. Capture the invoice data.
3. Validate the vendor, invoice number, dates, amounts, tax, and payment terms.
4. Code the expense to the right account, department, project, customer, or cost center.
5. Match the invoice to a purchase order, goods receipt, or service evidence when the business uses matching controls.
6. Route the invoice for approval.
7. Schedule payment based on due date, cash position, discount terms, and supplier relationship.
8. Reconcile the payment after it leaves the bank.

The useful AP details live in the document fields. Vendor name, invoice number, invoice date, due date, line items, tax, subtotal, total, currency, purchase order number, payment terms, and coding fields all affect whether the invoice is valid, who should approve it, and when it should be paid. A deeper field list belongs in a dedicated guide to supplier invoice fields for bookkeeping, but the reason those fields matter is simple: AP is trying to pay the right supplier the right amount at the right time.

AP controls are built around the risks of paying too soon, paying twice, paying the wrong party, or paying something that was never approved. Duplicate invoice numbers, changed bank details, missing purchase orders, mismatched quantities, incorrect tax, and vague descriptions are not small data-entry annoyances. They are the points where cash can leave the business incorrectly.

For a quick AP balance check, think in terms of unpaid supplier obligations. In a period view, a simple accounts payable equation is:

Ending AP = beginning AP + supplier invoices added - payments made

AP aging turns that balance into an operating tool by grouping unpaid invoices by due date or days outstanding. The number matters less on its own than what it tells the team to do next: investigate exceptions, approve clean invoices, hold disputed items, and pay valid obligations on schedule.

What accounts receivable does with a customer invoice

Accounts receivable starts on the other side of the transaction. The business has delivered goods, completed work, or reached a billable milestone, then creates a customer invoice and sends it under agreed payment terms. Until the customer pays, that invoice is part of AR.

The AR workflow usually follows this path:

1. Create the customer invoice with the right customer, invoice date, due date, line items, tax, totals, and payment instructions.
2. Send the invoice through the agreed channel.
3. Record the receivable.
4. Track the due date and aging status.
5. Send reminders or statements when payment is late.
6. Receive payment, remittance advice, or other payment evidence.
7. Apply cash to the correct customer invoices.
8. Resolve disputes, short payments, credit notes, or bad-debt decisions.
9. Reconcile deposits against the bank and accounting records.

AR risk is different from AP risk. The problem is not accidental overpayment to a supplier; it is slow collection, disputed invoices, short payment, credit exposure, poor cash application, or expected cash that never turns into actual bank deposits.

That risk is common enough to matter for small businesses. Based on data from the 2023 Small Business Credit Survey, roughly four of every five small firms face challenges related to customer payments, according to the Federal Reserve Banks payment survey. That is why accounts receivable is not merely "money coming in." It is the work of converting issued invoices into collected, reconciled cash.

AR aging shows how long customers have owed the business. AP aging shows how long the business has owed suppliers. They look similar as reports, but they drive opposite actions: AR teams chase, dispute, apply, and reconcile incoming cash; AP teams approve, schedule, pay, and reconcile outgoing cash.

The accounting difference matters because the workflows manage opposite risks

AP and AR sit on opposite sides of working capital. Accounts payable protects cash by making sure the business pays only valid supplier obligations, at the right time, with the right approval evidence. Accounts receivable protects cash by making sure customer invoices are collected, applied, and reconciled before they become stale or disputed.

The formulas are useful only when they explain the work:

• AP balance is the unpaid supplier obligations the business has accepted but not yet paid.
• AR balance is the unpaid customer invoices the business has issued but not yet collected.
• AP aging organizes unpaid supplier obligations by due date or days outstanding.
• AR aging organizes unpaid customer balances by how long they have been outstanding.

That is enough accounting structure for most AP vs AR decisions. A journal entry can explain why AP is a liability and AR is an asset, but daily finance work depends on whether the supporting documents are complete and trustworthy.

The same data points can matter for different reasons. Invoice dates and payment terms help AP decide when a supplier should be paid; due dates and remittance evidence help AR decide whether a customer invoice has been collected correctly. Amounts, tax, line items, counterparties, and reference numbers matter on both sides, but they answer different questions.

Clean records are the shared foundation. AP needs reliable invoice data, approvals, matching evidence, payment records, and reconciliation. AR needs reliable customer invoices, payment terms, collection notes, remittance evidence, cash application records, and reconciliation. The accounting labels differ, but both workflows depend on turning financial documents into usable control evidence.

Why AP automation and AR automation are not the same job

AP automation usually starts with documents the business did not create. Supplier invoices arrive as PDFs, scans, images, email attachments, portal downloads, or mixed-format batches. Each supplier may use a different layout, invoice numbering pattern, tax presentation, line-item structure, and payment instruction format.

That makes AP automation heavily dependent on extraction, normalization, validation, approval routing, and exception handling. The system has to turn third-party documents into structured data, then support checks such as vendor validation, duplicate detection, coding, purchase order matching, receipt matching, approval status, and payment readiness. For teams with purchase orders or receiving records, invoice matching controls are a core part of deciding whether the supplier invoice is safe to pay.

AR automation often begins from cleaner internal data because the business usually generates its own customer invoices from a billing, accounting, ERP, ecommerce, or subscription system. The automation problem then shifts toward delivery, reminders, payment links, collections workflows, cash application, dispute tracking, credit notes, and reconciliation.

Both workflows still depend on accurate documents. The difference is where the uncertainty enters. In AP, uncertainty often starts with external supplier documents that need to be captured and verified. In AR, uncertainty often starts after the invoice is issued, when the team must collect, match, and reconcile the customer's payment.

That is why broader invoice and financial document automation has to be understood by workflow, not just by the word "invoice." A received supplier invoice and an issued customer invoice may use similar fields, but the control points, risks, and next actions are not the same.

Quick way to decide whether something belongs to AP or AR

Use three questions when the accounts payable versus accounts receivable distinction is not obvious:

1. Did the business receive the document from a supplier or issue it to a customer?
2. Does the document support money the business owes, or money owed to the business?
3. Is the next action payment approval, or customer collection and cash application?

Common routing calls:

• Supplier invoice or vendor bill: AP, because it asks the business to pay a supplier or creditor.
• Vendor statement: AP support, because it helps compare supplier records against unpaid bills.
• Purchase order: AP support, because it shows what the business agreed to buy before the supplier invoice arrives.
• Goods receipt or receiving note: AP support, because it helps prove goods were received before payment approval.
• Customer invoice: AR, because it asks a customer to pay the business.
• Credit note: AR or AP depending on direction, because it reduces an amount owed and should be classified by who issued it and which balance it changes.
• Remittance advice: AR support, because it helps match customer payment to open invoices.
• Payment receipt: Usually AR support when received from a customer, because it supports cash application and reconciliation.
• Bank deposit evidence: AR support, because it helps reconcile incoming customer payments against recorded receivables.

The practical difference between accounts payable and accounts receivable is not just the label. AP asks, "Should we approve and pay this obligation?" AR asks, "Has the customer paid what they owe, and have we applied the cash correctly?" If the document helps answer the first question, it belongs with AP. If it helps answer the second, it belongs with AR.