One Transaction, Several Accounting Clocks

Part 13 of 16 · Behind the Buy Button

The bank statement is only one clock

eComm Inc can receive books before an invoice, pay for software before using it, and commit to a machine before it is built. If I begin and end with cash, I miss much of the relationship.

Accounting asks what assets, liabilities, income and expenses should be recognized under the applicable policy. Payment asks what cash moved and which obligation it discharged. These questions interact without sharing one universal date.

The accounting-clock cheat sheet

Example	Assumed recognition in this teaching model	Cash can happen
Books controlled before invoice	Inventory and accrued obligation	Later
Maintenance already performed	Service expense and accrued obligation	Later
Software paid before service	Prepaid asset, then expense over service	Earlier
Machine advance	Supplier advance, later applied to acquisition	Before delivery
Machine ready for intended use	In-service asset treatment under policy	Before or after readiness

These are simplified assumptions, not a complete accounting manual. Oracle's receipt-accounting overview illustrates how receipts and subsequent invoice activity can be linked without making invoice arrival the sole trigger.

Two small journal illustrations

Return to the 58 books eComm Inc controls at $20 each. Ignoring tax, freight and later adjustments, the assumed entry is:

Simplified receipt entry	Debit	Credit
Inventory	$1,160	—
Accrued supplier obligation	—	$1,160

When the resolved invoice is processed, the system must clear or reclassify the accrual consistently with its policy. It must not record another 58 books merely because a document arrived.

For the $12,000 software prepayment, the initial entry in our example is a debit to prepaid service and a credit to cash. After one month of evenly provided service, $1,000 moves from prepaid service to expense. Cash does not leave again when the monthly expense is recognized.

Debits and credits here show the balancing logic; they are not recommendations for a particular company's chart of accounts or treatment.

Stocks and flows need dates

An accounts-payable balance is a stock at a point in time. Annual purchases and cash spending are flows over a period. Comparing them can be useful, but adding them without a defined purpose is not.

Here is a deliberately small public reference panel, separate from eComm Inc's fiction. Amazon's 2025 Form 10-K reports the following amounts:

Reported measure	Amount	Measurement
Purchases of property and equipment	$131.819 billion	FY2025 cash outflow
PPE sale proceeds and incentives	$3.499 billion	FY2025 cash inflow
Accounts payable	$121.909 billion	December 31, 2025 balance
PPE acquired but not yet paid	$27.0 billion	Included in that payable balance

$131.819 billion − $3.499 billion = $128.320 billion is a defined net of those two cash-flow lines. The $27.0 billion must not be added again to accounts payable. These are dated reported figures, not October 2026 balances or eComm Inc assumptions. The anchors are the consolidated cash-flow and balance-sheet tables and Note 3's unpaid-equipment disclosure.

A commitment schedule is not all future spending

A future order, a recognized liability, an asset balance and a forecast answer different questions. An obligation disclosure also has a defined scope. An excluded variable purchase is not necessarily zero future expenditure.

For eComm Inc, I would keep a bridge from approved commitments to performance, recognized obligations, payments and remaining exposure. For equipment, I would add readiness and expected productive use. That bridge helps explain why spending rose before output did, or why cash remained temporarily strong despite a large unpaid acquisition.

A consolidated company's payable balance may also include several purchasing populations. Using it as though it were exclusively merchandise financing can distort a retail-specific days-payable calculation. The denominator and numerator need to describe compatible activity.

What this changes for the reader

Maya needs to distinguish her customer owing money from cash arriving. eComm Inc's operators need to report work performed even when the invoice is late. Accountants need evidence and a policy-based conclusion rather than a status borrowed from the payment queue.

Investors should ask what moved between the clocks before interpreting a single ratio. A large capital outflow does not prove productive capacity is already available. A small cash outflow does not prove the business incurred little cost.

From the customer's side, I can make a simpler version of the same distinction. Placing my book order, being charged, receiving the book and receiving a refund are separate events. Understanding the business begins by refusing to make one stand in for all the others.

Continue the series

Previous: Now eComm Inc Is the Seller. Next: A System That Can Remember Why. Return to the introduction and cheat sheet.

Evidence and method: public references were checked on October 18, 2026. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.