All Things Workplace

How Invoices and AP/AR Work (for Non-Finance People)


Someone in Finance says an invoice is “stuck in AP,” a customer is “on the AR aging,” or a vendor renewal needs a PO first. Ops, sales, CS, and new managers hear this without a clean map.

This article is workplace finance literacy, not financial, accounting, tax, or investment advice. Companies differ on POs, revenue rules, and approval rights. Follow your Finance partner and policy when they conflict with this guide.

For the bigger money story, see how companies make and spend money. For how spend shows up on statements, see P&L explained simply.

The insight that makes AP and AR click

AP and AR are trust clocks between companies. Every unclear statement of work (SOW), missing purchase order (PO), or fuzzy acceptance criteria does more than create “admin work.” It resets the trust clock, slows cash, and cools relationships. Clarity upstream is cheaper than collections downstream.

What is an invoice?

An invoice is a formal bill: one company telling another what is owed for goods or services, under what terms, and when payment is due.

It usually lists the parties, what was delivered, the total, taxes or fees if applicable, payment instructions, and terms (due on receipt, net-30, and so on). Quotes, proposals, and contracts set expectations. The invoice is the ask for payment under your company’s rules.

What is Accounts Payable (AP)?

Accounts Payable (AP) is money your company owes vendors for invoices received but not yet paid. The “bills we need to pay” side.

AP matches invoices to approvals and purchase records, then schedules payment. “In AP” usually means the invoice is in that process, not that cash already left.

What is Accounts Receivable (AR)?

Accounts Receivable (AR) is money customers owe your company for invoices sent but not yet collected. The “bills we are waiting on” side.

AR tracks open invoices, reminders, disputes, and credit memos. AR aging sorts open customer invoices by how long they have been unpaid.

AP and AR are mirrors. Your vendor’s AR is often your AP.

How a vendor invoice gets approved and paid

Companies vary, but the path often looks like this:

  1. Need and vendor. Someone picks or renews a vendor for a tool, service, or goods.
  2. PO or approval path. Many firms require a purchase order or other pre-approval before work starts. Not every company requires POs for every spend.
  3. Delivery. The vendor delivers.
  4. Invoice arrives. Sent to the email, portal, or address your company designated.
  5. Match and route. AP or a system checks the invoice against the PO, receipt, or contract (two-way or three-way match when PO, receipt, and invoice are compared).
  6. Business approval. A manager or budget owner confirms receipt and amount.
  7. AP schedules payment. Payment runs according to terms and cash practices.
  8. Vendor is paid. Remittance details may travel with the payment so the vendor applies cash correctly.

Flow: vendor → invoice → match/approval → AP → payment.

Fuzzy entity names, missing POs, no receipt, or unclear owners cause waits. Waiting resets the trust clock.

How a customer invoice gets created and collected

  1. Contract or order. Order form, SOW, subscription, or similar sets what you bill.
  2. Delivery or billing trigger. Milestone, period start, or another company-defined trigger.
  3. Invoice created. Billing or Finance issues it (sometimes from a system of record).
  4. Customer AP receives it. Your invoice enters their payables process.
  5. AR tracks it. Open receivable and due dates.
  6. Collection. Reminders and follow-up if payment lags.
  7. Cash applied. Payment closes or partially closes the invoice; credits or disputes may adjust it.

Flow: contract/delivery → customer invoice → AR → collection → cash applied.

Sales and CS shape this more than many people admit. Delayed signatures, unwritten scope, “we’ll invoice later,” and handshake discounts scramble AR.

What are POs, and when are they needed?

A purchase order (PO) is your company’s official “we intend to buy this” document: vendor, amount, terms, and budget or project.

POs help AP match invoices to authorized spend and reduce surprise bills. Many enterprises delay or refuse payment without a required PO.

Not every company requires POs for every purchase. Cards, small spends, or some categories may follow another path. Ask AP or Finance for thresholds and exceptions. Day-to-day card and reimbursement habits sit in how to do expense reports.

What net-30 and payment terms mean

Payment terms say how soon payment is due after the invoice date (or after receipt or acceptance).

Net-30 commonly means due 30 days after the invoice date. Net-15, net-45, and net-60 work the same way with different day counts. “Due upon receipt” means pay now. Some contracts use end-of-month or milestone due dates.

Longer terms help the buyer’s cash and strain the seller’s. Shorter terms do the reverse. They are timing choices, not morals. For revenue, cost, and cash clocks, see how companies make and spend money.

Why invoices get stuck (and how to unblock them)

Common blockers: wrong email or legal entity; missing or wrong PO; amount mismatch; no proof of delivery or acceptance; unclear budget owner; scope or quality disputes; vendor not set up in the payables system; customer stuck in their internal approval (your AR problem).

Unblocking needs specifics, not vague urgency. Share PO number, contract or SOW reference, delivery dates, who accepted the work, correct legal entity, and one approver. “Please escalate” without those details rarely helps.

Accrued expense vs. paid invoice (high level)

An accrued expense is a cost the company knows it incurred in a period even if the invoice is unpaid or has not arrived. Books try to match cost to when value was received.

A paid invoice means a payment run settled the bill.

Work in March, invoice in April, payment in May is normal. Accruals, AP balances, and cash can diverge. “We have not paid yet” is not “this did not cost us.” Finance may ask for estimates when invoices lag. See budget vs forecast vs actual.

How sales and CS actions affect AR

  • Fuzzy SOWs create “not in scope” disputes.
  • Verbal discounts that never hit the order form create credit-memo chaos.
  • Delayed signatures delay billing triggers.
  • Undefined acceptance criteria let customers stall payment.
  • Side emails promising free months or custom terms undermine the invoice their AP team holds.

Treat billing readiness as part of delivery: clear scope, clear trigger, clear AP contact, no surprise promises.

Checklist: before you approve an invoice

  1. Right vendor and legal entity?
  2. Authorized (PO, contract, or approved exception)?
  3. Did we receive what we are billed for (dates and quantities)?
  4. Amount matches PO, rate card, or quote (taxes/fees explained)?
  5. Correct budget or cost center?
  6. Not a duplicate?
  7. Who follows up if something is wrong?

Approving is a business attestation that the company should pay, not a courtesy click.

How this connects to cash

Pay vendors slowly and you hold cash longer (AP). Customers pay you slowly and cash stays out of your bank (AR). Leaders care because payroll, rent, and investment need cash, not only a healthy-looking P&L. Skip internet “average days” benchmarks; ask Finance how cash and collections show up in your reviews, including how to read a financial update at work.

Hypothetical AR aging snapshot (teaching only)

Figures below are made up, not a benchmark or a real company.

Bucket Open invoices (hypothetical) What it often means
Current (not yet due) $80,000 Normal billed pipeline
1 to 30 days past due $25,000 Reminders; possible admin friction
31 to 60 days past due $12,000 Dispute or process risk
61+ days past due $5,000 Needs a named owner and a plan

Aging shows where trust clocks stalled. It does not by itself assign blame.

Plain-English glossary

Term Plain meaning
PO Purchase order: authorized buy document.
SOW Statement of work: scope, deliverables, often acceptance rules.
Credit memo Reduces what a customer owes (or adjusts a vendor bill) after a dispute, return, or concession.
Remittance Says which invoices a payment covers.
Aging Sorting open AP or AR by age.
Two-way / three-way match Comparing invoice to PO (and often receipt) before paying.

Put it to work next week

Map one vendor bill and one customer bill end to end: who creates it, who approves, what blocks it, when cash moves. Fix one upstream ambiguity, not only the stuck invoice.

Related: budget vs forecast vs actual and gross margin, CAC, and burn explained.

FAQ

Is AP the same as expenses?

Not exactly. Expenses are costs in the P&L story. AP is unpaid vendor invoices on the “we owe this” list. Timing of recognition and payment can differ.

Do all companies require a PO?

No. Many require them for certain amounts or categories; others use cards, contracts, or manager approval. Ask your policy.

What if a vendor threatens to cut off service over late payment?

Share invoice number, PO, approval status, and payment-run timing with AP. Do not promise dates you cannot control.

Why does Finance care about “clean” customer invoices?

Messy invoices create disputes, slow cash, and burn AR and sales time.

Is this legal or tax advice?

No. Use Finance, Legal, and company policy.