tupicAcademy

Chapter 02 — Liabilities & Payment Accounting

·article·2026-06-12

Chapter 02 — Liabilities & Payment Accounting

"An expense is when you owe it. A payment is when you settle it. These are two different events."

This chapter explains the difference between incurring a cost and paying for it — the foundation of accrual accounting — and the two most common short-term liabilities every operating company carries: Accounts Payable (AP) and Accrued Expenses.

2.1 Cash Basis vs. Accrual Basis

There are two ways to answer the question "When did this cost happen?"

Cash BasisAccrual Basis
Expense is recorded when…money leaves the bankthe obligation is incurred (goods/services received)
Used byvery small businesses, personal budgetingvirtually all serious companies; required by GAAP/IFRS
Strengthsimplematches costs to the period they belong to
Weaknessdistorts timingrequires tracking liabilities

Worked Example

You use $8,000 of AWS compute in June. AWS invoices you on July 3, and you pay on July 20.

Cash basis:     June expense = $0       July expense = $8,000
Accrual basis:  June expense = $8,000   July expense = $0

The accrual view is correct economically: the servers powered June's customers, so the cost belongs to June. Between June 30 and July 20, the $8,000 you owe is a liability on your balance sheet.

Rule of thumb: Expense follows usage; liability bridges the gap until cash moves.

2.2 Accounts Payable (AP)

Definition: Amounts you owe to suppliers for goods or services already received, supported by an invoice. AP is the most concrete short-term liability: the amount, the counterparty, and the due date are all documented.

Lifecycle:

1. Receive service/goods  →  2. Receive invoice  →  3. Record AP  →  4. Pay  →  5. AP cleared

Worked Example

On June 5 your agency delivers a brand video and invoices $15,000, net-30 terms.

June 5  — Record:
   Expense (Marketing)        +$15,000   → hits June P&L
   Accounts Payable           +$15,000   → balance sheet liability

July 4  — Pay:
   Bank account               −$15,000
   Accounts Payable           −$15,000   → liability cleared

Notice that the expense appears once (June) and the cash moves once (July). The AP entry connects them.

Why companies like AP: Net-30 / net-60 terms are effectively a free short-term loan from suppliers. Managing the AP aging schedule (paying neither too early nor late) is a core treasury skill.

2.3 Accrued Expenses (Accruals)

Definition: Costs you have incurred but for which no invoice has arrived yet. The obligation is real; the paperwork just hasn't caught up. The amount is therefore an estimate.

Classic examples:

  • Cloud usage consumed this month, invoiced next month
  • Salaries earned but not yet paid (payroll accrual)
  • Utilities consumed before the meter is read
  • Legal/consulting work in progress

Worked Example

It is June 30. Your AWS dashboard shows roughly $8,200 of June usage, but the invoice will only arrive on July 3.

June 30 — Accrue:
   Expense (Cloud / COGS)     +$8,200    → estimated, hits June P&L
   Accrued Expenses           +$8,200    → liability

July 3 — Invoice arrives for $8,347:
   Reclassify accrual → AP, and true-up the difference:
   Expense                      +$147    → small July adjustment
   Accounts Payable           +$8,347
   Accrued Expenses           −$8,200

AP vs. Accrued — the one-line test:

Do you have the invoice? Yes → AP. No → Accrued.

Accounts PayableAccrued Expense
Invoice in hand✅❌
Amountexactestimated
Counterparty termsdefined (due date)not yet defined

2.4 Pay Now vs. Pay Later — The Operational View

From an operator's point of view, every cost entry triggers one of two workflows:

Pay Now

Cash leaves a bank account immediately.

Cost Item created     →  Expense recorded
Withdrawal created    →  Bank balance reduced
Payment status        →  PAID
Liability created     →  none

Pay Later

The expense is recorded; a liability holds the place of cash.

Cost Item created     →  Expense recorded
Payment status        →  UNPAID
Liability type        →  AP       (invoice attached)
                      →  ACCRUED  (no invoice yet)

Worked Example — One Month, Both Flows

Jun 02  SaaS subscription, paid by card          $499    Pay Now   → PAID
Jun 10  Marketing campaign, invoice net-30    $12,000    Pay Later → AP
Jun 30  June AWS usage, invoice pending        $8,200    Pay Later → ACCRUED
                                              -------
June expenses (accrual basis)                 $20,699
June cash out                                    $499
End-of-June liabilities                       $20,200   ($12,000 AP + $8,200 accrued)

A manager looking only at the bank account would think June cost $499. The accrual view shows the truth: $20,699 of economic cost, of which $20,200 is still owed.

2.5 Why Liabilities Must Be Tracked Explicitly

Three practical reasons:

  1. Cash forecasting. The AP aging schedule tells you exactly how much cash leaves in the next 30/60/90 days.
  2. True profitability. Without accruals, months with delayed invoices look artificially profitable.
  3. Audit defensibility. Each liability must trace to either an invoice (AP) or a documented estimate (accrual).

2.6 In Practice — TupicFinance

TupicFinance implements this chapter directly. Every cost item and recurring subscription carries an explicit payment_status (PAID / UNPAID) and, when unpaid, a liability_type of AP or ACCRUED, chosen automatically: attaching an invoice yields AP, ticking "I don't have an invoice yet" yields ACCRUED. Choosing Pay Now requires selecting a bank account and creates the matching withdrawal transaction in the same operation, so the expense, the cash movement, and the liability state can never drift apart. The fields are stored, not computed — a deliberate design choice for auditability that Chapter 06 explains in depth.

share