Accounts Payable for a Small Team: Who Approves Each Bill, and What Runs in Slack

Bills arrive in three inboxes. You approve them from memory and pay when a vendor chases. Then one bill is paid twice, a final notice shows up, and you start drafting a job post for a bookkeeper or AP clerk whose first month would be the same chasing. This guide is for the owner or operations generalist of a 5 to 100 person Slack-first firm. It gives each step of the accounts payable process, from bill arrival to bank match, an owner, a trigger and a verdict, with a copyable bill approval rule, so you can see which steps a weekly check in Slack can run and which ones a person has to keep.

The short answer: one rule, one list, one payer

A workable accounts payable process for a team with no AP clerk has three parts.

1. One approval rule, written down. It says who approves a bill by what they know and how much it is, not by job title.
2. One weekly list. A scheduled check pulls the bills due in the next seven days from your accounting data and posts them in one Slack thread, grouped by the approver the rule names.
3. One payer. Only a weekly bill run pays, and a person releases that payment from the bank. The agent does not pay bills.

Why bills get paid late, twice, or by the wrong person

Most guides describe the process as a pipeline for an accounting department. Stripe's accounts payable guide lists eleven steps, running from a purchase order and a goods receipt through three-way matching and vendor statement reconciliation. It is built for a company with purchasing, receiving and AP teams, and does not say what a one-person team can drop.

Hellobooks, a bookkeeping software vendor writing for small Australian trades teams, describes the pattern that applies to you instead. Bills go to whoever gets the email, one invoice is paid twice, and a final notice arrives for a bill nobody remembered. Its fix is five steps: one inbox for every bill, enter each bill when it arrives, approval by the right person, a weekly bill run, and matching the payment in the bank. Its example is a vendor's illustration, and its dollar thresholds are examples, not rules.

A bill appears whenever a vendor sends it, nobody is told it is waiting, nobody is named as approver, and no date forces a decision. Approval happens when someone looks, usually when the vendor writes again.

The ownership table: from bill arrival to bank match

The table uses Hellobooks' five steps as the skeleton and adds the steps that make a small team safe: a new supplier check, a bank detail change check and a monthly review. The owners are for a made-up 14-person design agency; swap in your own people. The verdicts are a recommendation, based on what the Kipwise agent can read and do (see the Slack section below).

Three of nine steps involve the machine, and none of them runs without a person: someone reads the list, someone presses Approve on a draft, someone fixes the mismatch. The other six depend on knowing the vendor, the work or the bank, which a scheduled check cannot see.

The bill approval rule you can copy

Name the approver by what they know. In Hellobooks' table, regular overheads need no approval if the amount matches last month, materials under $2,000 go to the person who ordered them, and materials of $2,000 and over, subcontractors, and anything unusual or from a new supplier go to the owner. The principle to copy: the person who approves should be the one who knows whether the goods arrived or the work was done.

ApprovalMax, an approval software vendor, adds a design point worth keeping even if you never buy software: tie each rule to a spend level and a decision the business is willing to delegate, then attach people to it. A rule pinned to a job title stops working the day the role changes, and nothing tells you it has. It also says to name a backup approver and a time after which an untouched request escalates.

Here is a rule for the design agency. The $2,000 line and the 7-day window are examples to replace with your own numbers.

1. Recurring overheads (rent, phone, software): no approval if the amount matches last month. Anything different goes to the owner.
2. Freelancers and subcontractors: the project lead who commissioned the work approves, after confirming the work was delivered. The owner approves above $2,000.
3. Everything else under $2,000: the person who ordered it approves.
4. Everything else at $2,000 or more, and any bill from a new supplier: the owner approves.
5. Backup: if an approver has not answered by Thursday noon, the owner is asked to approve or hold.
6. Bank detail changes: never approved from an email. Call the vendor on a number already on file.

What runs in Slack, step by step

The setup is one internal thread, "Bills this week". Mention the Kipwise agent once, and plain replies in that thread continue the conversation. The agent uses your own Xero or QuickBooks access to read outstanding balances, open a bill and run reports, including the aged payables report, for the organisation or company you connected. See the QuickBooks agent and Xero agent pages.

The Monday list. Ask the agent to run a scheduled task every Monday in that thread. Creating it needs your approval once, and later runs do not ask again. The task runs the aged payables report, opens each bill due in the next seven days, and posts one list with vendor, amount and due date, grouped by the approver your written rule names. It says plainly which bills it did not open.

The agent's documentation says it can open a bill. It does not say whether the agent can read a bill's approval status, so in week one ask it about one approved and one unapproved bill. If it cannot tell, the list shows bills due and the approver confirms in the thread.

The Thursday nudge. When an approver has not answered, ask the agent for a reminder. It searches your Gmail, writes a draft, and shows the recipient, subject and message on an Approve or Deny card. Only you can press it, it expires after 30 minutes, and denying it or letting it expire means nothing is sent.

What the check can never do. It cannot know that the freelancer delivered, that the hire company billed four days for three, or that a bank detail change is genuine. Those are the judgements ApprovalMax says to keep with people: whether the goods or services arrived and were worth the price, whether an exception should be granted, and verification of any change to a supplier's bank details.

Why the weekly list matters more in Xero

Xero users have asked for an approver notification since 2012, and Xero's own reply on 22 September 2026 still lists a bill approvals workflow as in development, so until it ships a small team's approval step stalls silently unless a weekly list names each waiting bill and its approver. On Xero's Product Ideas thread, titled "Email or notification when items are Awaiting Approval", the request has 378 votes. A Xero community manager wrote on 5 January 2026 that the new homepage summary of bills awaiting approval "isn't a direct notification" and that more notification controls were not in the short-term roadmap. The same manager wrote on 22 September 2026 that Xero is building a bill approvals workflow that emails an approver when their step becomes active. These are user reports and a vendor's statement of plans, status "In development". This article did not check what QuickBooks does, so test your own setup.

Keep approving and paying apart, even at five people

ApprovalMax says the person who approves a bill should not be the person who releases the money. It also cites the ACFE's Occupational Fraud 2026 report, which found that more than half of occupational fraud cases involved a lack of internal controls or an override of existing ones.

At 14 people you often cannot separate every role. ApprovalMax says pretending to separate them helps nobody and recommends compensating controls: a monthly review of paid invoices against approvals by someone outside AP, alerts on edits after approval, and restricted access to the payment file.

A team too small to separate approving from paying should write down its compensating controls instead of pretending to have separation: one weekly bill run is the only thing that pays, a person outside the approval chain reviews paid bills against approvals monthly, and every bank detail change is confirmed by a call to a number already on file.

Write these three lines into the same document as the approval rule. For the monthly review, pick someone who did not approve the bills, such as a part-time bookkeeper, an adviser or the other founder, and ask for ten minutes comparing last month's payments against the approved list.

The failure to design against: a wrong payment on a wrong list

A small firm's bills process usually breaks when a wrong payment goes out: a duplicate, a bill on hold, a vendor's changed bank account. ApprovalMax adds two more: one commitment arriving as two invoices that each sit under an approval limit, and a bill that changes after approval.

Let the scheduled check read and list only, and keep every write and every payment with a person, because the realistic failure in a bills process is a wrong payment released on a wrong list, and a read-only list can only produce a wrong question. A wrong question costs a minute in the thread, and a wrong payment costs the amount.

In practice:

• Write the scheduled task as "read the aged payables report and list the bills due in seven days", with no instruction to approve, record a payment or change a bill. The agent can write to Xero and QuickBooks when you explicitly ask, but a scheduled run is the wrong place to ask. Do that live, one item at a time, behind a card.
• Release payments from your bank, not from Slack. This article does not claim the agent pays bills, and nothing in the approach needs it to.
• Enter the vendor's own invoice number on every bill. Hellobooks says it is what stops double payments.
• Put a disputed bill on hold instead of leaving it unpaid, as Hellobooks' worked bill run does, so it stays visible.
• If two invoices from one vendor in a week add up to more than your approval line, send both to the higher approver.

A worked example, made up for this article

A 14-person design agency has bills of $240 for design software, $1,800 from a freelance illustrator, $3,100 from a stock photo and print supplier, and $950 from a vendor the agency has never used.

Monday's list shows four bills. The software bill matches last month, so it needs no approval. The $1,800 freelancer bill goes to the project lead who commissioned the work, and the $3,100 bill and the $950 new-supplier bill go to the owner.

By Thursday noon the project lead has not answered. The owner asks for a reminder, the agent shows the draft on an Approve card, and the owner presses it. The project lead confirms the illustration was delivered. The new supplier's invoice includes a note asking to pay a different account from the one on the vendor's website. The owner does not approve it from the email. The owner calls a number already on file, and in this made-up case the vendor says the note is not theirs. The bill is put on hold. On Friday the owner pays the approved bills from the bank in one run. On the next Monday the check reports every paid bill as cleared.

When to hire, buy software, or run the check first

None of the sources opened for this article addresses a team with no AP clerk directly. Stripe's guide assumes an AP department. ApprovalMax sells approval software that sits between your accounting system and payments. ClearFeed's comparison of Slack invoice approval tools says that with some tools "Slack is little more than a notification channel, and approvers still have to open an AP portal". ClearFeed is itself a vendor, so treat it as a map of the category.

Recommendation:

1. Run the weekly check first if you have fewer than about 30 bills a month and one or two approvers (a round number picked for this article, not a benchmark).
2. Buy approval software if the rule needs many approvers, thresholds by cost centre, purchase order matching or an audit log you must show someone. A Slack thread is not an audit trail.
3. Hire if the "person" steps still take more time than you have after a month. The guide on whether you need a bookkeeper yet walks through that decision, and chasing overdue invoices from Slack covers the customer-side loop.

The Kipwise agent costs $10 per user per month, or $108 per user per year, with a minimum of 3 users. Each user's $10 includes $5 of personal credit that resets monthly, with $2 per user of shared team credit behind it. The install-only trial is $2 for 7 days; saving a card without being charged, or being on a paid Slack plan, unlocks a $10, 14-day trial. Watch credit use in the first month. Current terms are on the Kipwise pricing page.

Verify it works

Run a four-week pilot and keep four numbers.

• Bills paid without a named approver. The target is zero. Check against the Monday lists.
• Bills paid twice or after a hold. The target is zero.
• Bills that reached the due date unapproved. This should fall as the Thursday nudge runs.
• Paid bills the Monday check still shows as owed. Each is a bank match to fix, and a sign the match step is not happening.

For money coming in, see accounts receivable for a small team; paid bills feed the month-end close checklist.

What to do next

Today, write the six-line approval rule with your own names and dollar line, and paste it into a new Slack thread called "Bills this week". Add the day of the weekly bill run and the name of the monthly reviewer. If Xero or QuickBooks is connected to the Kipwise agent, ask it for the aged payables report for the next seven days in that thread and see which bills have no approver yet.

References

• Hellobooks: Accounts payable process for small teams, a bills workflow: five small-team steps, approver table, weekly bill run, bank detail controls (vendor, 2026-09-24).
• ApprovalMax: Accounts payable approval process, how to design it properly: approving versus releasing, compensating controls, judgements to keep with people (vendor).
• Stripe: The accounts payable process, an essential guide: the eleven-step enterprise flow.
• Xero Product Ideas: Email or notification when items are Awaiting Approval: user requests and Xero's 2026 responses.
• ClearFeed: Best solutions for Slack-based invoice approval workflows: the Slack invoice approval landscape (vendor, 2026-09-30).
• Kipwise: QuickBooks agent: reading bills and the aged payables report.
• Kipwise: Xero agent: reading bills and the aged payables report.
• Kipwise: Pricing: seat price, credit and trial.
• Kipwise: Accounts receivable management for a small team: the receivables cycle.
• Kipwise: Do you need a bookkeeper yet: the hire decision.
• Kipwise: How to chase overdue invoices from Slack without hiring a bookkeeping VA: the customer-side chase loop.
• Kipwise: Month-end close checklist in Slack: where paid bills feed the close.