Why are bills showing up in my P&L without going through accounts payable?

Why are bills showing up in my P&L without going through accounts payable?

Short answer. Because they are being recorded at the moment of payment rather than the moment they are owed. Card charges and ACH payments categorized straight from the bank feed skip accounts payable entirely. The expense still lands in the P&L, so nothing looks broken, but your AP balance stops representing what you actually owe and you lose the ability to see cash before it leaves.

What is accounts payable actually for?

It exists to separate two events that happen at different times: incurring an obligation and paying it.

A vendor sends an invoice on the 3rd with 30 day terms. You owe the money on the 3rd. You pay it on the 30th. Accounts payable is what holds that obligation for 27 days so the business can see it.

Skip the bill entry and both events collapse into one. The expense appears on the 30th, the day the money moved. On a cash basis that is technically defensible. On an accrual basis it is wrong, and more importantly it means that for 27 days the business had a $14,000 commitment that appeared nowhere.

The purpose is not bookkeeping tidiness. It is knowing what is coming before it arrives.

How do bills end up bypassing it?

Four routes, and most businesses have at least two running simultaneously.

Card and ACH payments categorized from the bank feed. This is the biggest one by volume. Software subscriptions, ad spend, contractor payments, freight. The charge appears in the feed, someone assigns it to an expense account, and it posts. No bill was ever entered because the payment happened automatically. The vendor relationship never touches AP at all.

Bill pay tools that post their own entries. Many payment platforms write directly to expense accounts rather than clearing an AP balance. Convenient, and it works fine until you try to reconcile what you owe against what the accounting system thinks you owe.

Checks written directly. Someone needs to pay a vendor, writes a check, and codes it to an expense. Fast, and it leaves no obligation record behind.

Owner or manager purchases. A card in someone's pocket buying materials, meals, or supplies. These almost never route through AP, and in most small businesses nobody expects them to.

None of these are mistakes exactly. Each one is somebody choosing speed. The problem is cumulative rather than individual.

What does this look like when it has been running a while?

A construction services business doing about $6M in revenue had $340,000 in annual vendor spend. The AP aging report showed $12,000 outstanding.

The actual amount owed at that moment was closer to $58,000.

The gap was not fraud or error. It was structure. Only two vendors, the two who mailed paper invoices with terms, were ever entered as bills. Everything else, roughly 80 percent of vendor spend, was recorded when the payment cleared. Subcontractors paid by ACH, material suppliers on card, equipment rental on autopay.

Every dollar was in the P&L. Nothing was missing from the income statement. But the AP balance was describing two vendors out of forty, and the owner had been using it to answer the question of what he owed.

He was making payroll decisions on a number that covered five percent of his obligations.

What does the bypass actually cost?

Four costs, and they compound.

Cash forecasting stops working. The whole point of AP is forward visibility. If obligations only appear when they are paid, there is no forward view at all, only a record of the past. A business cannot answer whether it can afford something next month if it cannot see what is already committed.

Expenses land in the wrong period. A $22,000 invoice dated March 28 with 30 day terms, paid April 27, posts to April. March understates cost, April overstates it. If March also happens to be the month you closed a large project, margin on that project looks better than it was, and the true cost arrives in a month with no matching revenue.

Duplicate payments become invisible. Accounts payable is the control that catches paying the same invoice twice. Without a bill record to mark as paid, the only defense is somebody remembering. In a business paying forty vendors, that fails eventually, and duplicate payments are among the hardest overpayments to recover.

Terms and discounts get left on the table. Vendors offering two percent for payment within ten days are common in trades and wholesale. Capturing that requires knowing an invoice exists and when the window closes. On $340,000 of spend, even partial capture is several thousand dollars a year that simply does not happen when there is nothing tracking due dates.

How do you tell how bad it is?

Two checks, under an hour.

Compare AP to actual spend. Take total vendor spend for a full year from the P&L, then look at your average AP balance. If a business spends $340,000 a year on 30 day terms, a rough expectation is somewhere near a month of spend sitting in AP at any time, so $25,000 to $30,000. If the actual balance is $12,000, most spend is bypassing. This is crude and it is enough to tell you whether you have a problem.

Count vendors in AP versus vendors in the P&L. Run a vendor list from your expense detail and compare it to the vendors who have ever had a bill entered. In the case above it was two out of forty. That ratio is the answer, and it takes ten minutes to produce.

If both checks come back clean, the process is working and you can stop. They rarely do.

What should actually go through AP?

Not everything, and this is where most cleanup attempts fail. A rule requiring every transaction to be entered as a bill collapses within a month because nobody is entering a bill for a $12 domain renewal.

The workable rule has three parts.

Anything with payment terms goes through AP. If the vendor gave you time to pay, that is an obligation and it belongs in the system that tracks obligations. This is the core of the rule and it covers the transactions that actually matter.

Anything above a threshold goes through AP even if paid immediately. Pick a number that fits the business, often somewhere between $500 and $2,500. Below it, the visibility is not worth the entry time. Above it, you want the record.

Recurring autopay gets a standing schedule rather than individual bills. Software subscriptions, rent, insurance. These do not need bill entry, but they do need to appear in a forward view. A simple recurring commitments list solves it without creating data entry.

Everything else, the small card purchases, stays on the bank feed. That is not a compromise. It is the correct treatment for transactions where the obligation and the payment genuinely are the same event.

How do you fix it without redoing the year?

Start forward, not backward. Historical cleanup here produces very little value, because the expenses are already recorded and the P&L is broadly right. What is broken is the forward view, and the forward view only exists going ahead.

Write the threshold rule down and tell whoever pays vendors. This is most of the fix. It is a policy change, not a system change.

Enter open obligations as of today. Every unpaid invoice currently sitting in someone's inbox or on a desk gets entered as a bill. This takes an afternoon and it immediately makes AP meaningful, because from that moment the balance is real.

Add a month-end accrual step. At close, ask what work was performed or goods received that has not been invoiced yet. This is the piece that catches the subcontractor who bills late, and it is what makes accrual reporting honest rather than nominal.

Reconcile AP to a vendor statement quarterly. Pick your three largest vendors and request statements. Comparing their record to yours catches both duplicates and missing bills, and it takes about twenty minutes per vendor.

How does this affect job costing?

For any business that bills by project, this is where the bypass does the most damage, and it is usually the reason someone finally investigates.

Job costing depends on every cost reaching the right job. A bill entered through accounts payable carries a job or customer assignment. A charge categorized from the bank feed usually does not, because the feed shows a vendor name and an amount and nothing about which project consumed it.

So the material invoice for the Harrison job gets coded to Materials Expense with no job attached. It is in the P&L. It is not in the job.

The result is job profitability that reads high across the board while total company margin reads low, and nobody can reconcile the two. Each individual project looks fine. The company does not. That gap is the unassigned cost sitting in the P&L with no home.

It also arrives late. A subcontractor invoice recorded when paid rather than when the work was performed lands weeks after the job closed. By the time the cost appears, the job has already been reported as complete and profitable, and revising it means going back to a number someone already acted on.

The practical test takes ten minutes: total the costs assigned to jobs for a period and compare that to total cost of revenue on the P&L. If assigned costs are meaningfully lower, the difference is what is escaping, and it is almost always arriving through the bank feed rather than through AP.

Why does this go unnoticed?

Because the income statement looks fine.

Every dollar of expense is present and coded. The P&L totals correctly. The bank reconciles. Nothing anyone reads regularly is wrong, so no alarm goes off.

The failure shows up somewhere else entirely: in a cash conversation. The owner asks whether he can afford a piece of equipment, looks at the bank balance and the AP report, does the arithmetic, and gets a confident answer built on a number describing five percent of what he owes.

That is the pattern. The books are not wrong. The books are just not answering the question being asked of them, and nobody noticed the mismatch because the report has the right title.

Common questions

Is this a problem if I report on a cash basis for tax? Your return is unaffected. Your ability to manage the business is not. Cash basis for filing and accrual visibility for decisions is a normal and worthwhile combination.

What if my vendors do not send invoices? Then the obligation still exists and someone has to record it. For subcontractors and trades, the trigger is usually work completed rather than an invoice received, which is exactly what the month-end accrual step catches.

Does a bill pay platform fix this automatically? Only if it is configured to post to accounts payable rather than straight to expense. Many default to the simpler behavior. Check where the entries actually land before assuming.

How far back should I clean up? Generally not at all. Enter what is currently open and move forward. Recreating historical bills for expenses already recorded correctly adds work without adding information.

What is a healthy AP balance? Roughly one payment cycle of vendor spend, so about a month of purchases on 30 day terms. Much lower usually means bypass. Much higher usually means slow payment, which is a different conversation.

Who should own this? Whoever pays vendors, with the threshold rule written down rather than held in memory. The most common failure is a rule that exists only in the bookkeeper's head and leaves when they do.

What about employee expense reimbursements? Treat them like any other obligation above your threshold. An employee who fronted $1,800 for materials is a creditor until reimbursed, and that belongs in the forward view. Small out of pocket items can stay on the reimbursement report without an individual bill entry.

---

FynScale is a boutique AI consulting firm for accounting and finance. AI speed. Human judgment.