Accounts payable vs accounts receivable: managing both without chaos
Written By: Hemanth Aligingi, Senior Executive at Outsource360
Through every quarter of 2025, small businesses in the United States were getting paid faster. Then 2026 turned it around. Most guides on accounts payable vs accounts receivable stop at which one is the asset and which one is the liability, and that's a fine place to start, but it isn't the question this year is asking.
Xero's Small Business Insights for the United States recorded the time small businesses wait to be paid climbing to 29.3 days, with invoices settling around 8.5 days beyond their agreed terms. Aggregated from hundreds of thousands of subscribers, so it isn't a survey of opinions. It's what actually happened to the money.
A few days of slippage sounds survivable. It is, in isolation.
Here's what makes it bite. Nothing moved on the other side. Suppliers didn't extend their terms because your customers got slower. Software renewed on the same date. Contractors invoiced on the same cycle. The rent didn't wait. So the money now arrives later on one side of the business and leaves on exactly the schedule it always did on the other, and the difference has to come from somewhere.
That gap isn't a receivables problem. It isn't a payables problem either.
It's the space between two ledgers that most small businesses run as one job, in one inbox, by one person, usually on a Friday afternoon. And that person is almost never a finance professional. They're a founder, or an operations lead who inherited the bank login, or a part-time bookkeeper working eight hours a week across four clients.
Ask that person what accounts payable is and they'll answer correctly. Ask them which of their customers is furthest past due and how much falls due to suppliers in the next fortnight, and the answer changes shape. It becomes "let me check," then it becomes a spreadsheet nobody has opened since March.
The gap between knowing the definition and running the function is where the chaos lives.
Search the topic and you'll find the definition covered thoroughly. The top result on most days is a well-written piece from a tax software publisher, last updated in April 2023, that explains the difference across eight sections and stops. Another major vendor's guide runs about 1,200 words with a frequently-asked-questions heading and no questions underneath it. Both explain the same thing competently: one is money you owe, the other is money you're owed, one's a liability, one's an asset.
None of them answer the part that keeps people up. How do you run both when you can't split the duties between two people? Which queue do you clean first when both are a mess and you have one clear afternoon? What actually changes when you start selling into the UK or start buying from a small supplier in India?
So this covers both halves. What each ledger is and how a transaction genuinely moves through it, in the first third. Then the operational part: the controls that work at one person, the triage order when both queues are broken, the weekly rhythm that removes most of the noise, what the same two ledgers look like across three markets, and the point at which the job stops being yours.
That's the textbook answer, and it's where most guides finish. What follows is what the two ledgers actually do to each other: the mechanics, the controls, the collision points, and how to run both without either one running you.
On this page
Accounts payable vs accounts receivable: the difference, in one table
Asset or liability? The journal entries that settle the argument
The accounts payable process, in six steps
The accounts receivable process, and where it differs from accounts payable
Reading the two ageing reports side by side
The one-person finance function: controls when you cannot segregate duties
Both queues are a mess. Which one do you fix first?
The cadence that keeps both ledgers clean
Early-payment discounts and late-payment interest: the arithmetic and the law
The same two ledgers, three markets
Who should run accounts payable and accounts receivable as you grow
Where payables and receivables are heading
Accounts payable vs accounts receivable: the difference, in one table
Both accounts describe the same thing from opposite ends of a transaction: work that's been done and money that hasn't moved yet. That symmetry is the whole reason they're easy to confuse. So what separates them in practice, beyond which side of the balance sheet they land on?
What accounts payable actually is, and three things it is not
Accounts payable is a control account in your general ledger that carries the total you owe suppliers for goods and services you've already received but haven't yet paid for. Sitting behind that single number is a sub-ledger: one running balance for every supplier, each made up of individual invoices with individual due dates.
Here's the thing: that structure matters more than the definition. The control account is what appears on your balance sheet (the single figure a lender or an investor reads). The sub-ledger is what you actually work from.
Three things accounts payable is not. It isn't your total expenses, because an expense paid immediately by card never touches the payables ledger at all. It isn't money already spent, since the defining feature is that the cash is still in your account. And it very much isn't the stack of bills sitting unopened in an inbox, because an invoice nobody has recorded doesn't exist in your accounts, however real the obligation is.
That third one causes the most damage. A business with six unrecorded supplier invoices isn't a business with clean payables. It's a business whose liabilities are understated by whatever those six invoices total.
What accounts receivable actually is, and three things it is not
Accounts receivable mirrors it exactly. It's the control account carrying the total your customers owe you for goods or services you've already delivered, with a sub-ledger holding a balance per customer behind it.
It isn't revenue. Revenue is what you earned in a period and lives on the profit and loss statement. Receivables are the portion of that revenue still sitting with the customer, and the two numbers only match if nobody has paid you at all.
It isn't cash, obviously, though the number of businesses that read a healthy receivables balance as a healthy position suggests the distinction needs saying out loud. And it isn't "invoices I've sent." An invoice raised in a Word document, emailed, and never entered into your accounting system isn't a receivable. It's a hope with a reference number.
The side-by-side comparison
Accounts payable | Accounts receivable | |
What it represents | Money you owe suppliers for goods or services already received | Money customers owe you for goods or services already delivered |
Balance sheet classification | Current liability | Current asset |
Normal balance | Credit | Debit |
The document that creates it | A supplier invoice you receive and record | A sales invoice you raise and issue |
Who the counterparty is | Your vendors, suppliers, contractors and service providers | Your customers and clients |
The sub-ledger behind it | One balance per supplier, invoice by invoice | One balance per customer, invoice by invoice |
What ageing measures | How long you've held an invoice past its due date | How long a customer has held your invoice past its due date |
The failure mode when neglected | Late fees, lost discounts, suspended supply, duplicate payments | Silent non-payment, ballooning old balances, eventual write-offs |
The metric that tracks it | Days payable outstanding (DPO) | Days sales outstanding (DSO) |
The mirror principle: your receivable is somebody else's payable
Here's the model worth keeping, because it settles the asset-or-liability confusion permanently and does it in one move.
A single invoice document creates both entries at once. When you invoice a client £8,000, that same piece of paper becomes an £8,000 receivable on your balance sheet and an £8,000 payable on theirs, at the same moment, for the same amount, referencing the same reference number. One transaction, two ledgers, two companies, opposite signs.
Which means the person on the other end of your overdue invoice is running an ageing report too. Your invoice is a line on it. When you chase, you're not asking them to find money so much as asking them to move your line up their payment run.
Think of it this way. Chasing feels adversarial when you picture it as asking for a favour. It stops feeling that way when you picture it as a scheduling request inside a process you understand, because you run the identical process yourself.
And it explains the confusion at the heart of the search query cleanly. People ask whether receivables are an asset or a liability because they've seen the same amount described both ways, in two different conversations, and both were correct. It depends entirely on which end of the invoice you're standing at.
Where each one sits on the balance sheet
Accounts receivable appears under current assets, generally near the top, just after cash and cash equivalents. Accounts payable appears under current liabilities, usually first in that block.
"Current" means expected to settle within twelve months. For almost every small business, both qualify comfortably, since standard commercial terms run 30 to 60 days. A receivable you genuinely expect to collect in three years isn't a current asset, and let's be honest, at that age it's usually not an asset at all.
Both feed working capital, the figure you get by subtracting current liabilities from current assets. That's the number a lender looks at first (and, based on what we've seen, the one most founders have never calculated). It's also why the two ledgers can't sensibly be managed apart: they're two inputs to a single measure of whether the business can meet its obligations over the coming year.
Asset or liability? The journal entries that settle the argument
The asset-or-liability question generates an enormous amount of search traffic and a fair amount of circular explanation. Four journal entries end the debate faster than any paragraph can. Why do they work better? Because they show you the mechanics rather than describing them.
The four journal entries you actually need
When a supplier invoice arrives and you record it: debit the relevant expense account, credit accounts payable. The expense hits your profit and loss immediately, and the obligation parks on your balance sheet.
When you pay that supplier: debit accounts payable, credit cash. The liability clears, the bank balance drops, and your profit and loss doesn't move at all, because the expense was already recognised when the invoice landed.
When you raise a customer invoice: debit accounts receivable, credit revenue. You've earned the income, so it's recognised now, and the amount owed becomes an asset.
When that customer pays: debit cash, credit accounts receivable. The asset converts into money. Revenue, again, doesn't move.
Four entries. Two of them touch your profit and loss, two of them don't (and knowing which is which explains most of the gap between a profitable set of books and an empty bank account).
Why receivables are an asset before the money arrives
Under accrual accounting, you recognise revenue when you've earned it, not when you've been paid. The moment you deliver, you hold a legally enforceable right to collect. That right has value, it's owed to you, and anything owed to you that carries value is an asset. Straightforward enough.
Let's be honest, the consequence feels like a trick the first time it happens to you. You can post a strong, genuinely accurate profit while holding no cash whatsoever. Nothing has gone wrong in the books. The profit is real. It's just currently sitting in other people's bank accounts, which is a different problem from an accounting problem and needs a different fix.
Why payables are a liability before you approve the payment
The mirror holds. Your obligation to a supplier exists the moment you receive the goods or the service, not the moment you get round to approving the invoice.
This is where a specific, common mistake lives. "I haven't approved it yet" doesn't keep an invoice off your balance sheet. Approval is an internal control over payment; it has no bearing on whether the liability exists. An unapproved invoice sitting in an inbox is an unrecorded liability, and a business carrying several of them is reporting a stronger position than it holds.
Our recommendation is short. Record on receipt. Approve separately. They're two different steps (people collapse them constantly, because in a small business the same person does both within about four minutes of each other), and collapsing them is how liabilities go missing.
Accounts payable vs notes payable, and accounts receivable vs revenue
Two boundary questions come up constantly, and most guides skip both. What most people miss is that getting either one wrong misclassifies a balance rather than just misnaming it.
Accounts payable versus notes payable: accounts payable arises from ordinary trade credit, has no formal instrument behind it, and typically carries no interest. Notes payable involves a signed promissory note, usually carries interest, and often runs beyond twelve months. A bank loan is a note payable. A supplier invoice on 30-day terms is accounts payable. When a supplier converts an overdue balance into a formal repayment agreement with interest attached, it moves from one to the other, and it should move on your balance sheet too.
Accounts receivable versus revenue: revenue is an income statement event that measures what you earned in a period. Accounts receivable is the balance sheet consequence, measuring what's still outstanding at a point in time. Revenue for the year might be £400,000 while receivables at 31 December are £48,000. Same business, different questions, no contradiction.
Do payables and receivables exist at all on cash-basis books?
Technically, for tax purposes, no. And this trips up a lot of founders.
Under the cash method, you report income in the tax year you receive it and deduct expenses in the tax year you pay them, which is set out in IRS Publication 538, Accounting Periods and Methods. An unpaid customer invoice generates no taxable income, and an unpaid supplier bill generates no deduction. Neither balance drives what you owe.
Eligibility runs through the gross receipts test. A corporation or partnership generally qualifies for the cash method if average annual gross receipts across the three prior tax years don't exceed an inflation-adjusted threshold, which the Internal Revenue Service set at $32 million for tax years beginning in 2026. Comfortably above where this question usually gets asked.
But (and this is the part that matters operationally) the fact that a receivable doesn't affect your tax return doesn't make it irrelevant. You still need to know who owes you what, and you still need to know what falls due next month, or you're managing the business by bank balance. The normal, sensible small-business position is cash-basis for tax and accrual-style tracking for management. Your accounting software runs both without complaint.
The accounts payable process, in six steps
Most payables failures aren't decisions gone wrong. They're steps that quietly went missing, usually the boring ones near the start. So what does the full sequence actually look like?
The six steps, start to finish
A purchase is authorised before it happens, by someone with the authority to commit the money.
The goods arrive or the service is delivered, and somebody confirms that it actually did.
The supplier invoice is captured and coded to the right expense account and the right period.
The invoice is matched against what was ordered and received, then approved by a named person.
Payment is scheduled into a payment run and released.
The transaction is recorded, the remittance filed, and the supplier balance updated.
Six steps. In a small business, steps one and two are the ones that vanish first (they're the least satisfying, and neither produces a document anyone chases you for), and everything downstream inherits the damage.
The three-way match, and whether a small business needs one
The three-way match is the standard control in the payables world: you cross-check the supplier invoice against the purchase order and the receiving report before paying. All three have to agree on quantity, unit price, total, and the purchase order reference.
What it catches is worth listing, because each item is a real way money leaves a business: duplicate payments, quantities billed above what arrived, unit prices above what was agreed, invoices for goods that never showed up, and payments to suppliers who don't exist.
In practice, though, a full three-way match is overhead most service businesses can't justify. If you don't hold inventory and don't raise purchase orders, you have no receiving report to match against, and building the paperwork to enable the control costs more than the control returns.
The version that works at small scale is a two-way match plus a named approver. Check the invoice against the agreement or the quote, confirm the work was delivered with the person who commissioned it, and have someone other than the person who entered the invoice approve it. That catches most of what the three-way match catches, at a fraction of the process weight.
Worth flagging: the moment you start holding stock, this changes. Inventory is precisely where the three-way match earns its keep.
Approval thresholds a small business can actually operate
Three tiers cover most businesses. Small recurring spend inside an agreed budget gets processed by whoever runs the books, no approval needed. Anything above a set figure needs the founder or the department lead to approve it. Anything above a second, higher figure needs approval before the commitment is made, not after the invoice arrives.
Set the figures at what's genuinely material to you rather than what a textbook suggests, and write them down. An unwritten threshold isn't a control, it's a preference (and preferences bend on a busy Friday).
One rule outranks all three tiers, though. The person who can add a new supplier to the system must not be the person who can release a payment. If those two capabilities sit with one login, every other control you build is decorative, because that combination lets someone create a payee and pay it in the same session. It's also the exact hole that external fraud aims at, which the next section covers in detail.
Where the payables process breaks
Four failures account for most of the money lost, and none of them are exotic.
The duplicate payment. The same invoice arrives twice, once as an emailed PDF and once through a supplier portal, gets entered twice, and gets paid twice. Nobody notices until the supplier mentions a credit (which they sometimes don't, and which is not, strictly, their job to do).
The bill that never got recorded. It went to a personal inbox, or arrived while someone was away, or was filed as "deal with later." The liability exists, the accounts don't show it, and it surfaces as a demand letter.
The subscription nobody approved. A tool bought for a project two years ago, renewing annually on a card, still charging. Most businesses that audit this find at least one, and the ones that find none usually haven't looked properly.
The credit note never applied. The supplier issued it, it was filed, and the next payment went out at the gross amount anyway.
Each of these is caught by the same thing: a fixed weekly review of the payables ageing report by someone who's paying attention. Not clever software. Attention, on a schedule.
The accounts receivable process, and where it differs from accounts payable
Payables and receivables look symmetrical on a balance sheet and behave nothing alike in practice. The difference comes down to control: you decide when to pay a supplier, and you can only influence when a customer pays you. So how does that change the process?
The six steps, start to finish
Credit terms are agreed in writing before any work begins.
The goods are delivered or the service completed, with a record of when.
The invoice is raised in the accounting system and sent to a named person who can actually pay it.
Payment is tracked against the due date, not against a general sense of how long it's been.
Cash received is applied to the specific invoice it settles, not left floating as unallocated.
Anything still outstanding is aged, escalated, and eventually reserved against or written off.
Step five is the one that gets skipped, and skipping it makes the ageing report unreadable within about two months. Worth flagging early, because almost nobody treats it as a real step.
Credit terms are set before the invoice, not after it
The receivables control with the highest return isn't a reminder email. It's a clause agreed before you start work, which is unglamorous and enormously effective.
Four things to settle at the point of sale: the payment window in days, what starts the clock (invoice date, delivery date, or acceptance date, and they're genuinely different), who receives the invoice by name and email, and what happens on the day after it falls due. Get those four agreed in writing and most collection problems never form. Get them vague and you'll spend the next quarter negotiating them retrospectively, from a weaker position, with work already delivered.
That clause is worth revisiting whenever your customer mix changes. Terms you set for a first client three years ago rarely fit the business you're running now.
The escalation ladder, and where it stops being your job
Four rungs, in order. A reminder before the due date, which is administrative and costs no goodwill. A notice on the day it falls due. A direct conversation with a named person at the point where it's meaningfully overdue, by phone rather than email, because email is where these go to be ignored. Then a formal demand referencing your terms and any statutory rights you hold.
Now, here's where it gets interesting. Rung four is where the decision changes character. Up to that point you're chasing. Past it, you're deciding: reserve against the balance, refer it to a collections agency or solicitor, or accept that it's gone. Chasing indefinitely past rung four isn't persistence, it's an unfunded part-time job.
Fair warning: the transition costs money either way. A collections agency typically takes a percentage. Legal action costs more than most overdue small-business invoices are worth. The realistic goal is to reach rung four rarely, by getting the terms right at the start.
Allowance for credit losses, and when to write a debt off
At some point a receivable stops being an asset in any meaningful sense, and the books should say so.
Under United States generally accepted accounting principles, this is governed by the current expected credit loss model in Topic 326, introduced by the Financial Accounting Standards Board in Accounting Standards Update 2016-13 and effective for private companies for fiscal years beginning after 15 December 2022. It replaced the older incurred-loss approach with a forward-looking one: you recognise expected lifetime credit losses when you first record the asset, rather than waiting for evidence that a specific customer has stopped paying.
The terminology shifted with it. The traditional "allowance for doubtful accounts" became an "allowance for credit losses," though the older terms remain acceptable where the disclosure makes clear they represent credit losses.
The practical consequence catches people out. Because the model is forward-looking, receivables that are entirely current can still carry an expected loss. Not every invoice inside terms is worth its full face value, and a business with a history of writing off two percent of billings should be reserving against that pattern rather than acting surprised annually. This is where most first-time preparers go wrong.
The Financial Accounting Standards Board proposed a practical expedient in December 2024 that would simplify this estimate for private companies and certain not-for-profits on current receivables. Treat that as proposed rather than settled, and check its status with your accountant before relying on it.
Writing off is a separate act from reserving. The reserve is an estimate across the whole ledger; the write-off removes a specific balance you've concluded is uncollectable. Do the second one when you've exhausted rung four and not before, because a written-off balance that gets paid creates its own small accounting mess.
Which of the two is genuinely harder to run
Receivables, and not by a small margin.
Payables failure is loud and it arrives fast. A supplier goes unpaid, chases you, then stops shipping. The feedback loop is short, the consequence is visible, and (this is the useful part) the problem announces itself without you having to go looking.
Receivables failure is silent and it compounds. A customer who isn't going to pay you rarely says so. They go quiet, and quiet feels like nothing happening. Meanwhile the balance ages out of the range where it's collectable, and by the time anyone looks properly the invoice is fourteen months old and the contact who commissioned the work has left.
The practical reality is that nothing forces you to look at your receivables. Payables generate incoming pressure. Receivables generate silence. That asymmetry is why the ageing report has to be a scheduled habit rather than a response to something.
Reading the two ageing reports side by side
Both ageing reports are already sitting in your accounting software, generated automatically, and most businesses look at one of them occasionally and the other never. Read together they answer a question neither one answers alone. What question?
What the receivables ageing report tells you in thirty seconds
The report groups every unpaid customer invoice by how long it's been outstanding, in buckets: 0 to 30 days, 31 to 60, 61 to 90, and 90 plus.
Here's what that actually looks like. Read three things and stop. The largest balance in any overdue column, because that's where the recoverable money is concentrated. The oldest balance, because age is the strongest predictor of whether you'll ever see it. And the total sitting in 90 plus, because that column is your realistic write-off exposure.
What you're looking for is movement between the columns. A balance that was in 61 to 90 last month and is in 90 plus this month is telling you the escalation isn't working. Fine to see once. But three months in a row and the process is the problem, not the customer.
What the payables ageing report tells you that the receivables one cannot
The payables ageing report is the forward-looking half of the pair, and it's the one founders skip.
It shows every unpaid supplier invoice with its due date, which means it tells you what's coming rather than what's already gone wrong. Three things it surfaces that nothing else will: obligations falling due inside the next fortnight, early-payment discount windows about to expire, and the supplier you're quietly about to lose because you're 45 days into a 30-day relationship without having mentioned it.
That last one has no equivalent on the receivables side. Your customers won't tell you they're about to fire you either (nobody sends that email), but at least with suppliers the warning sign is a number on a report you already have.
Reading them together: the coverage question
Here's the calculation this article would keep if it had to lose everything else. Two numbers, both from reports you already have, no forecast required.
Take the total falling due to suppliers over the next 30 days from the payables ageing report. Then take the total genuinely collectable from customers over the same window, which means current invoices plus overdue balances you have concrete reason to expect, not the whole receivables balance including the 90-plus column you've been ignoring since spring.
Compare them. If collectable receivables comfortably exceed payables due, you have room. If they're close, you have a scheduling problem and you'll want to know that two weeks early rather than on the morning it bites. If payables due exceed collectable receivables, you have a decision to make now, while you still have options.
This takes about five minutes. It isn't a forecast, and it doesn't try to be one: forecasting properly is a separate discipline. It's a same-page comparison of two reports, run weekly, and it catches the overwhelming majority of problems early enough to do something about them.
Where to find both reports in QuickBooks Online, Xero and Zoho Books
In QuickBooks Online, both live under Reports. Search for "A/R Ageing Summary" and "A/P Ageing Summary," and use the Detail versions when you need to see invoice by invoice rather than customer by customer.
In Xero, they're the Aged Receivables Summary and Aged Payables Summary, reachable from the Business menu and from the Reports section. Xero lets you set the ageing periods, so you can match the buckets to your actual terms rather than accepting the default.
In Zoho Books, look under Reports for Receivables and Payables, where the ageing summary and ageing details reports sit in each group.
Same reports, three interfaces. Whichever you're on, our recommendation is to schedule them into your inbox rather than relying on remembering to run them. A report you have to go and fetch is a report you'll fetch when there's already a problem.
Days sales outstanding and days payable outstanding, in one line each
Days sales outstanding measures the average number of days it takes to collect after a sale. Days payable outstanding measures the average number of days you take to pay suppliers.
Commonly cited practice puts a receivables figure under 30 days in strong territory and 30 to 45 as typical for a business on Net 30 terms, though the range only means anything relative to the terms you actually offer. Someone selling on Net 60 with a 50-day figure is doing well; someone selling on Net 15 with the same number isn't.
Both metrics feed the cash conversion cycle, and the forecast built on top of that cycle. Both live in our cash flow guide rather than here, because this article is about running the two ledgers and that one's about what the numbers coming out of them mean.
The one-person finance function: controls when you cannot segregate duties
Every article on this topic contains a version of the same sentence: the person raising invoices shouldn't be the person paying them. It's correct, it's the foundation of financial control, and it's written for an organisation that employs at least two people in finance. What if you employ one, or none?
The control you structurally cannot have
Segregation of duties works by splitting authorisation, execution and recording across different people, so that committing fraud requires collusion rather than merely opportunity. In payables that means one person sets up suppliers, another enters invoices, a third releases payment. In receivables it means credit approval, billing, collections and reconciliation sit in different hands.
Now count the people in your finance function. If the answer is one, or one part-time bookkeeper working eight hours a week, that control isn't being neglected. It's structurally unavailable.
This is where the standard advice fails, and it's worth being blunt about it. Telling a founder with a single bookkeeper to segregate duties is telling them to hire someone. That may be the right answer eventually (and for a business past a certain size it definitely is), but it isn't the answer this quarter. What follows is what you do instead.
Six controls that work at one person
Control | How it runs | What it catches |
Out-of-band verification of bank-detail changes | Any change to supplier payment details is confirmed by phone, on a number you already held, before the next payment | Payment redirection fraud, the single largest external threat to payables |
A fixed payment run | Payments leave on one named day each week, never ad hoc | Duplicate payments, rushed approvals, unrecorded one-off transfers |
Owner review of the payment file before release | The founder reviews the list of payees and amounts, not the invoices, and takes 10 minutes over it | Unfamiliar payees, unexpected amounts, anything that doesn't belong |
Supplier master-file change alerts | Adding a supplier or changing bank details triggers a notification to someone who isn't the person who made the change | Fictitious vendors, unauthorised changes |
Bank-side payment controls | Dual authorisation above a threshold, or your bank's equivalent verification service | Any single-person payment above the amount you'd notice too late |
Monthly ageing review by an outsider | Your accountant, a non-executive, or your outsourced finance team reads both ageing reports and asks about anything odd | Slow-building problems on both ledgers that nobody inside is looking at |
None of these reconstruct proper segregation. Together they cover most of what segregation was protecting you from, which is the realistic goal.
The supplier bank-detail change rule
If you take one operational rule from this article, take this one.
The Federal Bureau of Investigation's Internet Crime Complaint Center, in its 2025 Internet Crime Report, recorded $3.046 billion in reported business email compromise losses in 2025, second only to investment fraud among reported categories, averaging over $122,000 per complaint. Around 86 percent of those funds moved by wire transfer or ACH. Total reported losses across all internet crime categories reached $20.877 billion, up roughly 26 percent year on year.
Read that per-complaint average again in the context of a small business. $122,000 isn't a bad quarter. For a lot of companies it's the whole cash position, and it leaves in a single afternoon.
And note the mechanism, because it's the reason this belongs in an article about payables rather than an article about cybersecurity. These attacks don't break into anything. They arrive as an email from a real supplier you actually owe money to, referencing a real invoice, saying the bank details have changed. The payment then travels through your normal, functioning payables process. Every control passes, because nothing about the transaction is irregular except the destination.
So the rule, stated as a rule: a change to supplier bank details is verified by voice, on a number you already held before the email arrived, every time, with no exceptions for urgency. Urgency is the tell, not the exception (the pressure to move fast is the attack, not a coincidence around it).
When the same person has to run both anyway
Can one person handle payables and receivables? At small scale, yes, and pretending otherwise helps nobody. It's common, it's often the only affordable option, and plenty of businesses run it for years without incident.
What changes isn't whether one person does the work. It's what you buy instead of segregation.
Don't try to get a second pair of eyes on everything, because you won't sustain it and a control you abandon in week three is worse than one you never started. Get a second pair of eyes on exactly two things: the payment file before it's released, and the 90-plus column of the receivables ageing report each month. The first is where money leaves incorrectly. The second is where money quietly stops arriving.
Ten minutes on the first, ten on the second, once a week and once a month respectively. That's the whole ask, and the person doing it doesn't need to be a finance professional. They need to be someone other than the person who prepared it.
Both queues are a mess. Which one do you fix first?
This is the question people actually have, and nobody publishes an answer to it. You've inherited two ledgers that haven't been maintained properly, you have one clear week, and doing a mediocre job on both is worse than doing a good job on one. So which?
The twenty-minute assessment before you touch anything
Three numbers, pulled from reports you already have. Resist the urge to start fixing before you have them, because the shape of the problem determines the order of the work.
First: the total sitting at 60 days and beyond on the receivables ageing report. Second: the total falling due to suppliers inside the next 14 days. Third, and this one takes the longest: the count of items on both sides that exist in reality but haven't been recorded, which means unopened supplier invoices and work delivered but not yet invoiced.
That third number is the one that decides most cases, and it's the one people skip because it requires going through an inbox rather than running a report. Frankly, this gets overlooked almost every time.
Fix receivables first when, fix payables first when
Go to receivables first when the 90-plus column holds more than a month of operating costs, or when nobody has looked at the ageing report in six weeks or more, or when you have delivered work that was never invoiced at all. That last one is free money and it's more common than it should be.
Go to payables first when a supplier you genuinely depend on is about to stop working with you, or when an early-payment discount window is closing inside the next few days, or when you buy from registered micro or small enterprises in India, where a missed deadline carries a tax consequence rather than a relationship one (covered further down).
When both conditions are live, payables goes first. The reasoning is straightforward: payables problems have hard deadlines attached and receivables problems mostly don't (a supplier has a date, an unpaid customer just has a growing number). An unpaid supplier stops shipping on a date. An uncollected invoice gets slightly harder to collect each week, which is bad but isn't a cliff.
The order of operations for the first week
Record before you chase. Always, and without exception.
You can't triage a queue you haven't finished entering, and every hour spent chasing an incomplete ledger is an hour you'll partly repeat. Get every unrecorded supplier invoice into the system, get every uninvoiced piece of delivered work invoiced, then run both ageing reports fresh. Only then start working the list.
But founders reverse this constantly, because chasing feels productive and data entry doesn't. It's the single most common reason a clean-up takes three weeks instead of one.
Three moves that make it worse
Paying everything at once to clear the decks. It feels decisive and it destroys your position, because you've converted a scheduling problem into a cash problem and given up every payment term you had.
Blanket-chasing every open invoice, including ones that aren't due yet. Customers who aren't late and get chased anyway learn that your reminders are noise, which is expensive to unlearn.
Writing off an old balance to make the report look clean. Before writing anything off, check whether it was invoiced correctly in the first place. A surprising share of ancient receivables are unpaid because the invoice went to the wrong address, or was never sent, or was disputed on a technicality nobody resolved.
The cadence that keeps both ledgers clean
Nearly everything described so far is a recovery operation. The point of running a cadence is to stop needing one. What does that rhythm actually look like across a week?
Rhythm | Payables | Receivables | Time it should take |
Daily | Capture and code every supplier invoice that arrived | Apply every payment received against its invoice | 10 minutes |
Weekly | One payment run on a fixed day, approved before release | One pass down the ageing report, escalate anything newly overdue | 45 minutes |
Monthly | Agree the payables sub-ledger to the control account | Agree the receivables sub-ledger, review the 90-plus column | Part of the close |
Quarterly | Review the supplier master file and open discount terms | Review credit terms by customer, decide deferred write-offs | 1 hour |
Daily: the ten-minute pass
Capture what arrived, code it, and apply any cash received to the invoice it settles. Nothing is decided during this pass and nothing is chased. It's purely about keeping the ledgers current, because every control downstream assumes the data is complete.
Ten minutes, at the same point each day (pick one and stick to it, because a floating habit isn't a habit). Skip it for a fortnight and the weekly pass becomes an afternoon.
Weekly: one payment run, one collections pass
Bottom line: one change removes most of what people mean by chaos. Payments leave on one named day.
Ad-hoc payment is the root of an astonishing amount of trouble. It's how invoices get paid twice, how approval gets skipped because someone's chasing you, how discount windows get missed, and how the person running the books ends up interrupted six times a day by payment requests. Fixing the day fixes all of it at once, and it costs nothing.
The collections pass runs the same week, ideally on a different day. One pass down the receivables ageing report, escalate anything that has newly crossed a due date, and stop. You're not trying to resolve everything, you're trying to make sure nothing ages silently.
Monthly: tie both sub-ledgers back to the general ledger
Once a month, the payables and receivables sub-ledgers have to agree to their control accounts in the general ledger, which is one step inside the wider month-end sequence covered in our monthly close checklist.
Quarterly: the review the cadence misses
Three things drift too slowly for a weekly rhythm to catch. The supplier master file accumulates entries nobody uses and occasionally one nobody recognises. Credit terms granted to customers years ago stop matching their current payment behaviour. And write-off decisions get deferred quarter after quarter, so the receivables report gradually fills with balances everyone privately knows are gone.
An hour, four times a year. If you ask us, it's the least urgent item in this article and one of the highest-return, which is exactly why it never gets done.
Where the two ledgers collide
Some of the worst tangles happen where payables and receivables touch each other, and general guides skip all of them because they're edge cases individually. Collectively they're most of the mess in a real set of books. What are they?
The customer who is also a supplier
This is common in agencies, consultancies and anywhere two businesses trade in both directions. Say you owe them £6,000 and they owe you £9,000.
Mentally netting the two is fine. Netting them in the ledger usually isn't. Under most reporting frameworks, offsetting assets against liabilities requires a legally enforceable right to set off and an intention to settle net, which a casual agreement between two account managers doesn't provide. Book both balances in full, on both ledgers, and if you genuinely want to settle net, document a contra agreement that both parties sign, then post the offset as an explicit transaction with its own trail.
Do it informally and two things break at once: your payables and receivables both understate reality, and neither ageing report reflects what's outstanding.
Credit notes and debit notes, booked to the right ledger
A credit note from a supplier reduces accounts payable. A credit note you issue to a customer reduces accounts receivable. Simple in principle, and routinely booked as income or an expense instead, which overstates both ledgers and leaves phantom balances that never clear.
The tell is a supplier balance that never quite reconciles, or a customer balance stuck at an odd figure that no invoice explains. Nine times out of ten there's a credit note sitting in the wrong place (and it's usually been there since whichever month everyone was busy).
Deposits, prepayments and unapplied cash
Money received before you've delivered anything isn't a receivable and isn't revenue. It's a liability, because you owe the customer either the work or their money back. Money you pay a supplier in advance isn't a payable either, it's a prepaid asset.
Unapplied cash is the everyday version of this problem, and it's the one that does the most quiet damage. A customer pays a round figure covering three invoices, the payment gets recorded against the customer but not against the specific invoices, and from that point the ageing report shows three overdue invoices and a floating credit (all four lines wrong, none of them obviously so). Do that a few times and the report becomes fiction, which is why applying cash properly is a daily step rather than a monthly one.
The disputed invoice nobody closed
A customer queries an invoice. Somebody promises to look into it. Nobody does, the conversation ends, and the invoice sits there ageing while everyone privately assumes someone else is handling it.
This is the most common reason a receivables report stops being trusted, and the fix is a single rule: a dispute is a status, not a silence. Flag it in the system with a date and an owner, set a review date, and if it isn't resolved by then it escalates. An invoice quietly parked in a dispute nobody is working isn't disputed. It's abandoned.
Early-payment discounts and late-payment interest: the arithmetic and the law
Two levers sit at the boundary between the ledgers and the money, and both are widely misunderstood. One is arithmetic that most people never do. The other is a legal right most sellers don't know they hold. Which is worth more?
What a 2/10 net 30 discount is really worth
The terms mean: take 2 percent off if you pay within 10 days, otherwise the full amount is due in 30. It reads like a small saving. It isn't.
Work it through. Paying early costs you 2 percent to save 20 days, and the correct base is what you'd actually pay, so it's 2 divided by 98, or about 2.04 percent. There are 18.25 periods of 20 days in a year, since 365 divided by 20 is 18.25. Multiply: 2.04 percent times 18.25 gives roughly 37 percent on an annualised basis.
Thirty-seven percent. That's the return on paying twenty days early, and it's why the discount is the one payables decision most small businesses get wrong in the expensive direction.
The decision rule follows directly. If your cost of capital sits below that figure, taking the discount creates value, and for almost every business it does, because almost nobody borrows at 37 percent. Even drawing on a credit line at 12 percent to fund early payment leaves you well ahead. The only real constraint is whether you have the cash without creating a worse problem elsewhere, which is exactly what the coverage comparison in section five tells you.
When offering a discount on your own invoices is the wrong move
Now flip it, because the same arithmetic runs in reverse and this is the half that gets missed.
Offer 2/10 net 30 to your own customers and you're giving up roughly 37 percent annualised on every invoice they take you up on. If you're offering it because collections are slow, you're financing your business at 37 percent to solve a process problem, and there is almost always a cheaper fix. Tighter terms, a named invoice recipient, and a working escalation ladder cost nothing.
A discount is a reasonable tool when you're deliberately buying certainty on a large invoice, or when a specific customer's payment behaviour is genuinely worth paying to change. But as a standing offer to compensate for a collections process nobody runs, it's expensive financing with a friendly name.
The United Kingdom: a statutory right most sellers never use
If you sell to businesses or public bodies in the UK, you hold a statutory right to interest on late payment, and it applies automatically. No clause required in your contract.
Under the Late Payment of Commercial Debts (Interest) Act 1998, statutory interest runs at 8 percent above the Bank of England base rate on overdue commercial invoices. On top of the interest you can claim a fixed sum toward recovery costs, and the GOV.UK guidance on late commercial payments sets those at £40 for debts up to £999.99, £70 for debts of £1,000 to £9,999.99, and £100 for debts of £10,000 or more. Reasonable additional recovery costs can also be claimed.
Timing matters too. Where a payment date is agreed, it must usually fall within 30 days for public authorities or 60 days for business-to-business transactions. Absent an agreed date, payment defaults to late 30 days after the customer receives the invoice or 30 days after delivery, whichever is later.
The right covers business-to-business and public-sector debts. It doesn't cover consumers.
Most small suppliers never invoke any of this, usually out of a reasonable worry about the relationship. The better approach, in our view, is that the value is rarely in claiming it and often in citing it. A final demand that references the specific statutory entitlement reads differently from one that asks politely for a third time,
and it costs nothing to send.
The United States and India: what you can actually charge
The United States has no general federal equivalent for private commercial debt. Late fees and interest on ordinary B2B invoices are a matter of contract, which means the clause has to be in your terms before the work starts, and enforceability including any usury ceiling is governed at state level. Different rules apply to federal government payments under prompt-payment legislation, which is a separate regime.
India runs the opposite way, and far harder. Where the supplier is a registered micro or small enterprise, statutory interest applies without needing a contract clause, and the buyer faces a tax consequence as well. That combination is unusual enough to deserve its own treatment, which follows in the next section.
The same two ledgers, three markets
The mechanics of payables and receivables are identical everywhere. Debit, credit, sub-ledger, ageing report. What changes across borders is the deadline, the penalty, and increasingly the format the invoice has to travel in. So what should a founder selling or buying across markets actually know?
Question | United States | United Kingdom | India |
Is there a statutory payment deadline for B2B? | No general federal rule for private commercial debt | Agreed dates usually within 60 days B2B, 30 days for public authorities | 45 days to a registered micro or small enterprise, 15 without a written agreement |
Can you charge late interest without a contract clause? | Generally no, it's contractual and state-governed | Yes, automatically, at base rate plus 8 percent | Yes, to micro and small enterprises, at three times the RBI bank rate, compounded monthly |
Is there a fixed recovery-cost entitlement? | No general entitlement | Yes: £40, £70 or £100 by debt size | Covered within the statutory interest regime |
Does paying late carry a tax consequence? | No | No | Yes, the deduction moves to the year of actual payment |
Is e-invoicing mandatory? | No federal mandate | Planned, with Peppol confirmed as the network | Yes, in force above prescribed turnover thresholds |
What is universal, and what is not
The short answer: the accounting treatment is universal, and almost nothing else is. Payables are a current liability and receivables a current asset in every framework a small business is likely to report under, the journal entries are the same, and the ageing buckets are the same.
Not universal: almost everything that determines behaviour. When payment is legally late, what you can charge when it is, whether being late costs you anything beyond goodwill, and whether an invoice is even valid in the form you send it.
United States
The decisive question in the US is which accounting method you're on, because it determines whether these balances affect your tax at all. Under the cash method, income is reported when received and expenses deducted when paid, so unpaid invoices on either side don't move your tax position. Eligibility runs through the gross receipts test, set at $32 million in average annual gross receipts across the three prior tax years for tax years beginning in 2026.
On late payment, there's no general federal statutory right for private commercial debt. Whatever you can charge, you charge because it's in your contract, and both enforceability and any interest ceiling are state matters. Which makes the terms clause the entire lever: if it isn't written down before the work starts, you don't have it. No amount of firm emailing later creates a right you never wrote down.
United Kingdom
The UK gives suppliers a statutory position that doesn't depend on their contract. Interest on overdue commercial invoices runs at the Bank of England base rate plus 8 percent, with a fixed recovery sum of £40, £70 or £100 depending on the size of the debt, and it applies automatically to business and public-sector debts.
Looking forward, the UK has confirmed Peppol as the core interoperability network for a planned e-invoicing mandate in 2029. That's far enough out not to be urgent and close enough that a business choosing accounting software now should check it can reach a Peppol network when the time comes.
India: the rule that turns late payables into a tax cost
India has the strictest position of the three, and it's the one most likely to surprise a founder buying services from Indian suppliers.
Section 15 of the Micro, Small and Medium Enterprises Development Act 2006 caps payment to a registered micro or small enterprise at 45 days, or 15 days where there's no written agreement. The clock starts from acceptance or deemed acceptance of the goods or services, not from the invoice date, and goods are deemed accepted if no objection is raised within 15 days of delivery.
Then Section 43B(h) of the Income-tax Act 1961, inserted by the Finance Act 2023, attaches a tax consequence. Where that window is breached, the buyer's deduction for the expense is allowed only in the year of actual payment. So an unpaid balance to a micro or small enterprise sitting on your books at 31 March increases your taxable income for that year, and you recover the deduction later. On top of that, statutory interest under the MSMED Act runs at three times the Reserve Bank of India bank rate, compounded monthly.
Here's the second-order effect, and it's genuinely interesting. Stretching payables is a standard lever: pay later, hold cash longer, improve your position. That's how it's taught, and against most suppliers it works. Against a registered micro or small enterprise in India, the same move now costs you a disallowed deduction plus punitive interest. The optimal days-payable figure is no longer one number across your supplier base. It's one number for most suppliers and a hard deadline for a specific, legally defined class of them, which means your payables ledger needs a flag on it identifying which is which. And very few small buyers have built that flag (most only discover the need during their first assessment).
If you're operating across Indian tax rules more broadly, our guide to the 2026-27 business compliance position covers the wider picture.
Selling into the EU from 2026: the e-invoicing wave
If you sell into Europe, the format of your invoice is becoming a legal question rather than a design preference, and the timetable has already started.
Belgium's business-to-business mandate went live on 1 January 2026, using the Peppol network. Poland's KSeF system began on 1 February 2026 for businesses above PLN 200 million turnover and 1 April 2026 for most other VAT-registered firms. France starts on 1 September 2026 for large and mid-sized companies, with every VAT-registered business required to be able to receive electronic invoices from that point. Germany has required all businesses to be able to receive electronic invoices since January 2025, with sending obligations phasing in through 2027 and 2028. Above all of it sits the EU's VAT in the Digital Age package, adopted on 11 March 2025, with digital reporting requirements for cross-border business-to-business transactions scheduled for 1 July 2030 and member states required to align domestic systems by January 2035.
Now, here's where it gets interesting, and it's the part that catches people. Several mandates require businesses to be able to receive electronic invoices before they require them to send. Receiving is a payables obligation. So the first e-invoicing deadline most foreign-selling businesses hit lands on the payables side, not the receivables side (which is the opposite of what almost everyone expects, since
the mandates get reported as an invoicing story).
Who should run accounts payable and accounts receivable as you grow
The two ledgers change hands three or four times over a company's life, and the handovers are usually late because nothing forces them. Payables and receivables degrade quietly (there's no equivalent of a missed payroll to make the problem undeniable). So what actually signals that the current arrangement has run out?
The four ownership models
Model | What it covers | When it fits | What it cannot do |
Founder-run | Both ledgers, in the accounting software, alongside everything else | Pre-revenue to early trading, low invoice volume | Provide any independent review, or survive the founder having a busy month |
Part-time bookkeeper | Recording, reconciliation, ageing reports, payment preparation | Growing businesses with regular volume | Make credit decisions, or hold the customer relationship during collections |
In-house finance hire | Both ledgers plus reporting, with process ownership | Volume that genuinely fills a role, or complexity a generalist can't hold | Segregate duties on its own, since one hire is still one person |
Outsourced finance team | Processing on one or both ledgers, to an agreed cadence | Steady volume, rules-based work, or when you need capacity without headcount | Replace an internal owner, or make judgement calls that belong to you |
The trigger points that say the model has to change
Four signals, all countable, all specific to these two functions.
Invoice volume has outgrown what a weekly payment run absorbs, so payments are leaking back into ad-hoc handling. The 90-plus column on the receivables ageing report has stopped moving, meaning nobody is genuinely working it. A payment went out without a second look, even once. And a supplier deadline has been missed twice, which is the point where it's a process rather than an accident.
Any one of those four is enough. The mistake we see most often is waiting for three of them. The wider decision about whether your books as a whole should move to someone else, and what to watch for when they do, is covered in our guide on when a startup should outsource its bookkeeping.
What automation actually took over, and what it did not
Invoice processing costs have separated sharply. Ardent Partners' State of ePayables research put the average cost to process a single invoice at around $9.40, against roughly $2.78 for the best-performing teams. That gap is the automation dividend, and it's widening rather than closing.
But look at where the automation actually landed. Data capture, coding suggestions, matching, duplicate detection, payment execution: all mechanical, all rules-based, all substantially automatable. What hasn't been automated is deciding which of the twelve exceptions this week actually matters, whether a customer who's gone quiet is having a bad quarter or is about to fail, and whether a supplier's change of bank details is real.
Which produces a second-order effect worth naming. Automation ate the matching, not the judgement. The old version of this job was mostly data entry with occasional decisions. The new version is mostly decisions with occasional data entry, and it's a harder job than the one it replaced, performed in many small businesses by someone hired for the older version. The scarce skill is no longer processing invoices. It's knowing which three of them to look at properly.
Splitting the two functions across an in-house and an outsourced team
For a founder who can't segregate duties internally, there's an option that's often overlooked: hand one ledger out.
Splitting payables and receivables across two organisations reconstructs a meaningful part of what segregation was doing, because the people raising invoices genuinely aren't the people paying them. They're not even in the same company.
If you split one, payables is usually the one to send. It's higher volume, more rules-based, less dependent on relationship judgement, and the exceptions are more clearly defined. Receivables tends to sit better closer to the person who owns the customer relationship, because collections calls are commercial conversations as much as administrative ones, and a chase from someone the customer has never met lands differently.
Team structure matters more than location here. An outsourced payables function following your approval thresholds, running your fixed payment day, and escalating exceptions to you is a control improvement. One that pays whatever arrives is a control you've outsourced away (same arrangement on paper, opposite effect on your risk).
Payables or receivables: which role to hire for first
The general ladder runs bookkeeper, then accountant, then controller, then finance director, and most businesses climb it later than they should. That progression is a separate topic.
Function-specifically, the answer is usually receivables, which surprises people. Payables work is more amenable to being outsourced or automated, because it's rules-based and the exceptions are well defined. Receivables needs someone who can hold a commercial conversation with your customer without damaging the relationship, and who understands the underlying contract well enough to know when a dispute is real.
So if you're hiring one person to do both, a smarter strategy is to hire for the receivables skill set and buy the payables capability. It's easier to add process capacity than to add judgement.
Behind on your books, or scaling past what spreadsheets and one busy afternoon a week can hold? Outsource360's virtual bookkeeping team runs payables and receivables to a fixed cadence, with your approval thresholds and your escalation rules. Explore the service or book a consultation.
Where payables and receivables are heading
Both functions have changed more in the last decade than in the four before it, and the direction of travel is reasonably clear. What should you be building toward?
How the two functions got here
Cloud accounting did the first piece of work, putting a genuine payables and receivables sub-ledger into the hands of businesses that had never employed an accountant. Before that, most small businesses ran a spreadsheet and a bank balance.
Then the rules moved. The Financial Accounting Standards Board issued Accounting Standards Update 2016-13 in 2016, introducing the forward-looking credit loss model that became effective for private companies for fiscal years beginning after 15 December 2022. The 2020 cash shock turned days sales outstanding into a metric that businesses which had never measured it suddenly tracked weekly. India tied payables timing directly to tax deductibility in 2023. And the EU adopted its VAT in the Digital Age package in 2025, setting the timetable for mandatory digital reporting.
Four changes, four directions, one theme. Both ledgers moved from back-office admin to something with rules, deadlines and consequences attached, and they did it inside a decade.
The e-invoicing wall, and what it does to the fix-it-later habit
Belgium went live on 1 January 2026, Poland through February and April 2026, France from September 2026, with EU-wide digital reporting scheduled for July 2030. The practical effect on how work is scheduled is larger than the compliance effect.
When an invoice has to clear a government platform to be valid, a receivables error stops being an internal matter and becomes a compliance failure. You can't quietly reissue it at month-end. Which pulls the work forward: validation that used to happen during the close now has to happen at the point of issue, every time, on every invoice.
For a business used to fixing the ledger monthly, that's a genuine change in operating rhythm. And it's the strongest argument for the daily ten-minute pass described earlier: a habit that looked optional in 2024 becomes the mechanism that keeps you compliant.
Artificial intelligence on both sides of the invoice
Inside the process, machine learning is handling capture, coding and matching at accuracy levels that make manual entry difficult to justify at volume.
Outside it, the same technology is on the other team. The FBI's Internet Crime Complaint Center recorded artificial intelligence as its own category for the first time in the 2025 reporting year, logging 22,364 complaints and roughly $893 million in losses. What that means for payables specifically: the fraudulent supplier email arriving in 2027 will be well written, correctly formatted, contextually accurate about your relationship, and free of every tell people were trained to look for.
So the verification rule gets more important rather than less. A change to supplier bank details is confirmed by voice, on a number you already held. No email will ever be good enough evidence again (because emails are about to get very good, and "it looked legitimate" was never a control anyway).
The three mistakes automation does not fix
Terms that were never agreed in writing. No amount of process improvement recovers a payment date nobody set.
No named approver. Software can route an invoice to a person, and it can't decide who that person should be.
A dispute logged as a silence. An unresolved query that nobody owns will sit in an automated ledger exactly as long as it sat in a manual one, ageing quietly, until someone decides it's their job.
Those three are where the money goes, and all three are decisions rather than tasks. Which is roughly the whole point: software can run the process, but somebody still has to own it.
Frequently asked questions
1. What is the difference between accounts payable and accounts receivable?
Accounts payable is money your business owes suppliers for goods or services already received, recorded as a current liability. Accounts receivable is money customers owe you for goods or services already delivered, recorded as a current asset. They're two views of the same kind of transaction: one where you're the buyer, one where you're the seller.
2. Is accounts payable an asset or a liability?
Accounts payable is a current liability. It represents an obligation to pay somebody else, so it sits on the liabilities side of the balance sheet and carries a credit balance. It becomes a liability the moment you receive the goods or service, not when you approve the invoice or schedule the payment.
3. Is accounts receivable an asset or a liability?
Accounts receivable is a current asset. It represents a legally enforceable right to collect money, which has value to your business, so it sits on the assets side with a debit balance. The same amount is a liability on your customer's balance sheet, which is why the question generates so much confusion.
4. Can the same person handle both accounts payable and accounts receivable?
At small scale, yes, and it's very common. Proper segregation of duties needs at least two people, which many small businesses don't have. Where one person runs both, compensating controls matter: out-of-band verification of any supplier bank-detail change, a fixed payment run, and owner review of the payment file before release.
5. Which comes first, accounts payable or accounts receivable?
Neither. They're parallel processes running in different parts of the business at the same time, one facing suppliers and one facing customers. If you mean which to fix first when both are neglected, the answer depends on your position: payables first when a hard deadline or supplier relationship is at risk, receivables first when old balances have stopped moving.
6. Is invoicing accounts payable or accounts receivable?
It depends on direction. An invoice you raise and send to a customer creates accounts receivable. An invoice you receive from a supplier creates accounts payable. The same document type sits on both ledgers, which is why the terms "billing" and "invoicing" get used ambiguously and are worth qualifying.
7. Where do accounts payable and accounts receivable appear on the balance sheet?
Accounts receivable appears under current assets, usually near the top just after cash. Accounts payable appears under current liabilities, typically first in that section. Both are classified as current because they're expected to settle within twelve months, and both feed the working capital calculation lenders look at.
8. What is an AP ageing report, and how does it differ from an AR ageing report?
Both group unpaid invoices into buckets by age: 0 to 30 days, 31 to 60, 61 to 90, and 90 plus. The receivables version shows who owes you money and how late they are. The payables version shows what you owe and when it falls due, which makes it forward-looking: it warns you about obligations and discount windows before they arrive.
9. Does a small business need a three-way match?
Usually not in full. The three-way match compares purchase order, receiving report and supplier invoice, which requires paperwork most service businesses don't generate. A two-way match plus a named approver catches most of the same errors at far lower process cost. Once you hold inventory, the full three-way match starts earning its keep.
10. Do accounts payable and accounts receivable exist under cash-basis accounting?
Not for tax purposes. Under the cash method you report income when received and deduct expenses when paid, so unpaid invoices on either side don't affect your tax position. You still need to track both for management purposes, though. Most small businesses run cash-basis for tax and accrual-style tracking for decisions.
11. Should I take a 2/10 net 30 early-payment discount?
Almost always, if you have the cash. Paying 20 days early for a 2 percent discount works out at roughly 37 percent annualised, calculated as 2 divided by 98, multiplied by 365 divided by 20. Since almost nobody borrows at 37 percent, the discount creates value even if you draw on a credit line to fund it.
12. Can I legally charge interest on an overdue invoice?
It depends where you are. In the UK, statutory interest applies automatically to overdue commercial invoices at the Bank of England base rate plus 8 percent, plus a fixed recovery sum. In the US, late fees on private commercial debt are contractual and state-governed. In India, statutory interest applies to registered micro and small enterprises without a contract clause.
13. When should an unpaid invoice be written off?
After you've exhausted escalation and concluded the balance is genuinely uncollectable, not merely old. Writing off is separate from reserving: the allowance for credit losses is a forward-looking estimate across the whole ledger under current US accounting standards, while a write-off removes one specific balance. Check first whether the invoice was ever issued correctly.
14. What is the difference between accounts payable and notes payable?
Accounts payable arises from ordinary trade credit, has no formal instrument behind it and usually carries no interest. Notes payable involves a signed promissory note, generally carries interest, and often extends beyond twelve months. A bank loan is a note payable; a supplier invoice on 30-day terms is accounts payable.
15. What is the difference between accounts receivable and revenue?
Revenue measures what you earned during a period and appears on the profit and loss statement. Accounts receivable measures what customers still owe at a specific point in time and appears on the balance sheet. Annual revenue of £400,000 with £48,000 of receivables at year end is perfectly normal, not a contradiction.
16. What happens when a customer is also one of my suppliers?
Record both balances in full on both ledgers. Offsetting them in the accounts generally requires a legally enforceable right of set-off and an intention to settle net, so an informal understanding isn't enough. If you want to settle net, document a contra agreement both parties sign and post the offset as an explicit transaction with its own audit trail.
17. Should I outsource accounts payable, accounts receivable, or both?
If you outsource one, payables is usually the better candidate: higher volume, more rules-based, less dependent on relationship judgement. Receivables tends to sit better with someone close to the customer relationship. Splitting the two across an internal and an external team also reconstructs part of the segregation of duties a small business otherwise can't achieve.
18. Which is harder to manage, accounts payable or accounts receivable?
Receivables, by some distance. Payables failure is loud and fast, because an unpaid supplier chases you and eventually stops shipping. Receivables failure is silent: a customer who won't pay rarely announces it, so the balance ages quietly. Nothing forces you to look at receivables, which is why it needs a scheduled review.
References
Official guidance and regulations
Publication 538, Accounting Periods and Methods. Internal Revenue Service. Cash and accrual methods, and the gross receipts test governing eligibility for the cash method.
Accounting Standards Update 2016-13, Financial Instruments: Credit Losses (Topic 326). Financial Accounting Standards Board, 2016. The current expected credit loss model; effective for private companies for fiscal years beginning after 15 December 2022.
Late commercial payments: charging interest and debt recovery. GOV.UK. Statutory interest, fixed recovery sums, and when a commercial payment becomes late under the Late Payment of Commercial Debts (Interest) Act 1998.
The Micro, Small and Medium Enterprises Development Act, 2006. India Code, Government of India. Section 15: the 45-day and 15-day payment obligation to micro and small enterprises, and the statutory interest that follows a breach.
Section 43B, Income-tax Act 1961. Income Tax Department, Government of India. Clause (h), inserted by the Finance Act 2023: deduction for micro and small enterprise dues allowed only in the year of actual payment where the MSMED Act window is breached.
VAT in the Digital Age (ViDA). European Commission, Directorate-General for Taxation and Customs Union. Package adopted 11 March 2025; digital reporting requirements for cross-border business-to-business transactions from 1 July 2030.
Data and research
2025 Internet Crime Report. Federal Bureau of Investigation, Internet Crime Complaint Center, 2026. Business email compromise losses, per-complaint averages, transfer methods, and the first dedicated artificial intelligence category.
Small Business Insights: United States. Xero, 2026. Time to be paid and days-late figures, aggregated from anonymised subscriber data.
State of ePayables, by Ardent Partners, 2024. Average and best-in-class cost to process a single invoice. Cited from industry summaries of the report; the primary publication is available on request from the publisher.
Product documentation
QuickBooks Online support. Intuit. Ageing report navigation.
Xero Central. Xero. Aged Receivables and Aged Payables reports.
Zoho Books help. Zoho. Receivables and payables reporting.
Disclaimer
This article is for educational and general business information purposes only and does not constitute professional accounting, tax, financial or legal advice. Accounting standards, tax thresholds, statutory payment deadlines, interest entitlements and e-invoicing mandates vary by jurisdiction and by entity type, and they change over time. Figures cited are drawn from the sources linked at first mention and reflect the periods those sources cover. For guidance specific to your situation, consult a qualified professional before acting.
Comments