Profit and loss statement changes for small business books: live view, job level margin, automatic entries

The profit and loss statement itself has not changed. Revenue less costs, in an order that has been settled for a century. What is changing is when it exists, who reads it, and how much of it is produced by rules nobody has looked at recently.

This page describes those structural changes and what each one asks of the person keeping the books: the closing routine, the coding behind job margin, and the automatic entries that keep running until somebody audits them.

What to take away

From a monthly event to a standing view

Bank feeds, captured invoices and automatic postings mean a statement can be produced at any moment. QuickBooks Online and Xero both build their reports straight from the bank feed, so a running view of income and expenses is there without waiting for a month end, and most other cloud ledgers now work the same way.

Roughly right is the problem. A statement produced on the fourteenth contains none of the invoices that will arrive for work already done, none of this month's share of the annual costs, and no stock movement. It reads as a period that is going well because half of the period's costs have not been keyed yet.

The habit worth building has two tiers: a live view for cash and for spotting obvious errors, and a closed statement produced once after cut-off, which decisions come from. Naming which one you are looking at removes most of the harm.

The closing routine that makes the closed statement trustworthy is the same set of steps every month, and the bookkeeping foundations guide covers the bookkeeping behind them.

What the closing routine covers

Margin gets cut finer

Tracking fields on transactions — Xero's tracking categories, the projects and classes in QuickBooks Online, the dimensions in larger ledgers — have made it easy to ask what a single job, customer, site or product line contributed. That question used to require a separate exercise and now it is a report.

The gain is real. The risk is that the answer is only as good as the coding, and job level coding is where small businesses are weakest. A cost coded to the general overhead account because nobody knew which job it belonged to does not appear as missing. It appears as a job that looks more profitable than it was.

Two disciplines make finer margin safe. Give every tracked dimension a written definition, kept with the chart of accounts, so two people code the same cost the same way. And reconcile the sum of the parts to the whole: the job margins added together, plus unallocated costs, must equal the statement.

Revenue and billing separate

Subscription and retainer billing has made the invoice date a poor guide to when income was earned. Systems bill annually, monthly, or on a usage count, and the earning happens on its own schedule.

What this does to the statement is push work into the deferred income calculation. Money billed in advance sits as a liability and releases into revenue as the service is delivered. The rule behind that release is not a matter of preference: under ASC 606, Revenue from Contracts with Customers, revenue is recognized as the performance obligation is satisfied, not when the invoice is issued. When that release is a schedule inside a billing system rather than an entry a bookkeeper makes, the statement depends on a mechanism nobody in the business can see.

The check is worth building into the month: does deferred income on the balance sheet equal the amount still owed in service? If not, the revenue figure is wrong in a way the revenue recording guide explains.

Advance payments are also handled differently under different accounting methods. IRS Publication 538, Accounting Periods and Methods, sets out the periods and methods available; sections 446 and 451 of the Internal Revenue Code govern the choice of method and when advance payments are included in income; and a business that changes its method generally must file Form 3115.

Costs allocate themselves

Recurring journals, automatic prepayment releases and rules that split a cost across departments all reduce keying. They also produce entries every month that nobody decided this month.

A prepayment schedule set up two years ago keeps releasing after the policy has been canceled. A rule splitting rent between two sites keeps splitting after one closed. The entries are neat, dated correctly and wrong.

The countermeasure is dull and works: once a year, list every automatic entry the ledger makes, name what each is for and who agreed it, and delete anything nobody can justify. An automatic entry with no owner is a standing instruction from a former employee.

In QuickBooks Online these templates sit in the recurring transactions list, in Xero the repeating invoices and bills are the equivalent, and mid-market ledgers such as Sage Intacct keep recurring journals with a next run date against each one.

The reader changes

More statements are now read by machines: a lender's system, an application form that pulls figures directly, a platform assessing an advance. Anyone about to be read that way is better off knowing what the routes to business funding actually weigh before the figures are pulled. These readers take the numbers as given and cannot ask what a line means.

This raises the cost of a loose account structure. A cost sitting in the wrong group has always been sloppy; it now feeds a decision without a human noticing. Consistency between periods matters more for the same reason, since an automated read compares this year with last year and calls a coding change a trend.

None of that changes the accounting. It changes how much a coding decision can cost, and how the same entries land on the balance sheet that gets read alongside it.

What is not changing

Common questions