Accounts Receivable Management for a Small Team: Who Owns Each Step, and What Runs in Slack

Small firms lose money on receivables because the weekly overdue check belongs to nobody, so name one owner and a fixed day before you buy any tool. Make sure payments are recorded before that person reads the list, or Monday's reminders go to customers who already paid. Then sort each step into a scheduled check, a draft someone approves, or a call a person makes. In the QuickBooks 2025 US Small Business Late Payments Report, 56 percent of 2,487 US businesses with up to 100 employees said they were owed money from unpaid invoices, an average of $17.5K each, and 47 percent had some invoices more than 30 days overdue.

The accounts receivable process in plain steps

Published guides agree on the cycle. The Wave guide to accounts receivable management lists six steps: agree the work, price and payment terms; create and send the invoice promptly; track each unpaid invoice's amount and due date; follow up on a reminder schedule; record each payment against the right invoice; and check recorded payments against the bank. The Citi small business guide adds the two ends: the invoice states terms such as net 30, meaning due in 30 days, and uncollectible balances are eventually written off.

Put together, the accounts receivable process for a services firm looks like this:

• Terms. Agreed in the proposal or contract.
• Invoice. Sent the day the work or milestone is done, because the clock only starts when the invoice lands.
• Reminders. Wave's sample timeline: a reminder before the due date, a check on the due date, a follow-up at 7 days overdue, and direct contact at 30 or more days overdue.
• Aging review. Wave groups unpaid invoices into not yet due, up to 30, 31 to 60, 61 to 90 and over 90 days overdue, and advises checking overdue invoices weekly and all unpaid invoices monthly.
• Payment and bank match. Each payment recorded against its invoice, then reconciled.
• Disputes and holds. A client who disagrees with an invoice is a different problem from a client who forgot.
• Write-off. The last resort, with rules attached.

None of those guides puts a name next to each line.

Why receivables slip in a team with no AR clerk

Wave's guide is thorough, and it still never says who should do the weekly review. Citi's guide says sales, customer service and finance should share the credit policy, which is sound advice for a company that has three departments. A 20 person agency has a founder, an operations generalist, and an outside bookkeeper who logs in once a month.

In that setup, the work splits in a predictable way. The founder sends invoices because they own the client relationship. The bookkeeper records payments at month end. Between those two moments, nobody looks. The reminder that should go out at day 7 depends on someone remembering, and the overdue review that Wave recommends weekly happens when cash feels tight, which is usually after the balance has already aged past 30 days.

The steps rarely fail because nobody knows them. They fail because no single person is named for the weekly overdue review, so give that review one owner before you change any tool. A new invoicing app, a payment portal or a reminder template will not fix a review that nobody runs. In the QuickBooks survey, businesses with a higher share of overdue invoices more often reported cash flow problems (50 percent against 34 percent) and less often used accounting software (36 percent against 56 percent). The report treats these as correlations, so read them as a sign that tools help once someone is accountable for looking, not as proof that software fixes late payment.

The same complaint shows up in public threads: a general contractor's evenings spent chasing invoices, the view that chasing slow payers is worth paying for, and how much time and persistence collecting takes.

Who owns each step: an accounts receivable workflow for 5 to 100 people

The cadence column comes from the Wave and Citi guides above; the owner and "who runs it" columns are our recommendation for a team without a dedicated AR person.

Two roles do most of the work. The AR owner is usually the operations generalist: they run the weekly review, approve reminders, and escalate. The account lead is whoever owns the client relationship, because a 45-day overdue invoice from your largest client needs a conversation.

Record payments before you read the overdue list. If the bookkeeper matches payments to the bank only at month end, the list the AR owner opens on Monday still shows invoices customers paid last week, and the first reminder goes to someone who has already paid. Either move payment recording to weekly, ahead of the review, or have the AR owner check the last week of bank deposits against the list before anything is sent. The review is only as accurate as the slowest step that feeds it.

Split every step into one of three kinds before you automate or hire: a check that can run on a schedule, a draft a person approves, or a judgment call that stays with a person. Skip the sort and you either pay hourly for due-date checks a schedule could run, or switch on automatic reminders for everything and send your biggest client the same template again during a billing dispute. The table tells you what to hand to a schedule, what to hand to a person with an approval step, and what never to hand off.

Running the weekly receivables check from Slack

If your team already works in Slack, the scheduled rows of the table can run there. Here is what that looks like with the Kipwise agent, using only what it does today.

With Xero or QuickBooks Online connected, the agent can look up a contact's outstanding balances, open an invoice and run the aged receivables report, using your own access and only the organisation or company you connected. It says which Xero organisation or QuickBooks company it acted in. It can run a request on a schedule in plain language and post the result in the channel, and it can act when an invoice is created or paid in Xero or QuickBooks, or when a payment comes in on Stripe. It reads the record back with your tools before it posts, rather than acting on the notification alone.

An illustrative example, made up for this article:

Monday 9:00, #finance thread. The AR owner mentions the agent once: "Every Monday at 9, run the aged receivables report from our QuickBooks company and post who owes what in each bucket, oldest first, with links."

The agent posts the first report. The owner replies in the same thread, no new mention needed: "Draft a reminder for the two invoices in 31 to 60." The agent drafts them. The owner edits one line and asks it to add a note to each invoice with the date the reminder went out.

Wednesday. A client pays. Because the owner also asked to be told whenever an invoice is paid, a message lands in the channel and the Monday list is no longer stale.

What stays with people is the same as in the table. The agent creates or updates invoices, records payments or adds notes only when you explicitly ask. In QuickBooks, a sales invoice is posted live rather than as a draft, so check the wording before you ask it to create one. Credit terms, disputes, whether to pause work for a client, and write-offs remain decisions for the founder.

It also has limits you should plan around. Bank reconciliation is not on that list of actions, so your bookkeeper still does the month-end match. A QuickBooks connection is one company, so a firm with two entities reconnects to switch, while each Xero organisation is a separate grant.

The agent costs $10 per user per month with a 3-user minimum. Compare that with an AR clerk whose first month would mostly go on the scheduled rows of the table above. Our aged receivables report guide shows how to read the report the Monday check posts, and the overdue invoice chasing guide covers the reminder step in more depth.

Accounts receivable best practices for a small firm

• Shorter, explicit terms. Citi says businesses that state due dates, credit limits and late fees up front may be less likely to face disputes later. Put the late fee in the contract, not in the third reminder.
• Invoice the same day. Every day between finishing the work and sending the invoice is a day added to your collection time, and no reminder schedule can recover it.
• One number to watch. Invensis recommends monitoring days sales outstanding (DSO), the average number of days it takes to collect after a sale, and Citi says a high DSO signals that collections are taking too long. For a small firm, the trend matters more than the absolute value: if DSO rises three months running while sales are flat, the weekly review is not happening.
• Watch the aging trend, not just the total. Citi advises monitoring aging reports regularly to spot trends that might signal future risk. A total that stays flat can hide a balance moving from 31 to 60 into 61 to 90.
• Several ways to pay. Citi lists ACH, cards and online portals. Fewer steps for the client means fewer excuses.

Disputes, write-offs and the paper trail

The last rows of the table carry a tax rule. IRS Topic 453 on bad debt deductions says a debt becomes worthless when the facts show there is no reasonable expectation of payment, that you must show you took reasonable steps to collect it, and that a business bad debt is deductible only if the amount was included in your gross income in the current or a prior year. Cash-method businesses generally cannot deduct unpaid fees they never reported as income.

Keep a dated record of each reminder and contact for every overdue invoice, because a business bad debt is only deductible once you can show reasonable steps to collect it. Chasing from personal email and phone calls leaves no record where your accountant will look. Log every reminder against the invoice itself, as a note in Xero or QuickBooks, so the trail lives with the invoice. If you run the weekly check in Slack, asking the agent to add a dated note to the invoice when a reminder goes out builds that trail as a side effect. Talk to your accountant before writing anything off; this is a summary of the IRS page, not tax advice.

Disputes need a separate lane. When a client says an invoice is wrong, stop the reminder schedule for that invoice, move it to the founder, and record why. A dispute left in the automatic sequence produces the repeated-template problem described earlier.

How to tell it is working

Give the new setup six weeks, then check three things:

1. The weekly review happened every week. In Slack this is visible: the scheduled report is in the thread with the owner's replies under it. If weeks pass with no reply, ownership has slipped again.
2. The 31 to 60 bucket is shrinking as a share of the total. That is where reminders do the most good; balances older than that need conversations.
3. DSO is flat or falling. Calculate it the same way each month.

If the review runs but balances still age, the problem has moved to your terms or to specific clients, and the founder needs to take it up with them.

When to hire instead

A schedule covers the checks and drafts, and a person still makes the judgment calls. If your 30+ day list is mostly disputes, payment plans and clients who need a call, you need a person, and our guide on whether you need a bookkeeper yet helps you size that hire. Hire for the judgment rows of the table, after the scheduled rows already run.

Pick the AR owner today, and write their name next to "weekly overdue review" in the table above. Then set that review for the same morning every week, whether in your calendar or as a scheduled request in a Slack thread, and run the first one this Monday.