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

A team with no AP clerk needs three things: a written rule that names each bill's approver by what that person knows, a weekly list of the bills due in the next seven days grouped by approver, and one person who releases payments from the bank. We recommend letting a scheduled check in Slack build the list and chase the approver, and never letting it approve or pay.
The owner or operations generalist of a 5 to 100 person Slack-first firm usually has bills arriving in three inboxes, approved from memory and paid when a vendor chases. Each step from bill arrival to bank match below gets an owner, a trigger that says it is late and a verdict: Slack check or person.
Five steps cover a small team
Stripe's accounts payable guide lists eleven steps, from a purchase order and a goods receipt to 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 you actually have: bills go to whoever gets the email, one invoice is paid twice, and a final notice arrives for a bill nobody remembered. Its fix has 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 dollar thresholds are examples, as ours are below.
In each of those failures a bill appears whenever the 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.
Who owns each step, from bill arrival to bank match
The table uses Hellobooks' five steps as the skeleton and adds three checks a small team needs: a new supplier check, a bank detail change check and a monthly review. The owners are for a made-up 14-person design agency, so swap in your own people. The verdicts are recommendations based on what the Kipwise agent can read and do (see the Slack section below).
| Step | Owner | Trigger that says it is late | Verdict |
|---|---|---|---|
| One inbox for every bill | Operations lead | A bill reaches someone's personal inbox | Person |
| Enter the bill, with the vendor's invoice number | Operations lead | A bill in the inbox with no matching bill in the accounting tool | Person |
| New supplier check | Owner | A bill from a vendor not yet in the accounting tool | Person |
| Bank detail change check | Owner | Any email asking to change where a vendor is paid | Person |
| Approval by the person who knows the work was done | Approver named by the rule | A bill due in the next 7 days with no approval | Scheduled check lists it, approved draft chases the approver |
| Weekly bill run list | Owner | The list is not posted by the chosen day | Scheduled check |
| Release the payment | Owner | An approved bill is due | Person |
| Match the payment in the bank | Operations lead | A bill you paid still shows as owed | Scheduled check, person fixes it |
| Monthly review of paid bills against approvals | Someone outside the approval chain | No review note by the 5th of the month | Person |
Three of the 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: the person who approves a bill should be the one who knows whether the goods arrived or the work was done. 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.
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.
Here is a rule for the design agency. The $2,000 line and the seven-day window are examples to replace with your own numbers.
- Recurring overheads (rent, phone, software): no approval if the amount matches last month. Anything different goes to the owner.
- Freelancers and subcontractors: the project lead who commissioned the work approves, after confirming the work was delivered. The owner approves above $2,000.
- Everything else under $2,000: the person who ordered it approves.
- Everything else at $2,000 or more, and any bill from a new supplier: the owner approves.
- Backup: if an approver has not answered by Thursday noon, the owner is asked to approve or hold.
- Bank detail changes: never approved from an email. Call the vendor on a number already on file.
Do not try to name every vendor on day one. Tell the Monday list to put any bill this rule does not cover under the owner, in a group of its own. Each bill in that group is a gap in the rule, so add one line for that vendor or category that week. After a month the rule covers the vendors you really have, written from your bills and not from a guess.
What runs in Slack each week
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 judgements stay with people, along with whether an exception should be granted.
Why the weekly list matters more in Xero
Xero users have asked for an email or notification when a bill is awaiting approval, and Xero's Product Ideas page lists a bill approvals workflow that emails the approver when their step becomes active as in development. Its new homepage summary of bills awaiting approval is not a direct notification. Until a notification ships, a small team's approval step stalls silently unless a weekly list names each waiting bill and its approver. This article did not check what QuickBooks does, so test your own setup.
Write the compensating controls for a team too small to separate duties
Approving a bill and releasing the money should be two different decisions, and at 14 people you often cannot staff both. Write down the compensating controls instead of pretending. One weekly bill run is the only thing that pays. Once a month someone outside the approval chain, such as a part-time bookkeeper, an adviser or the other founder, spends ten minutes comparing last month's payments with the approved list. And before a payment leaves, its amount is compared with the approved bill, because a bill edited after approval is what the monthly review exists to catch.
If your bank can require a second user to approve a payment batch, switch it on and make the second user someone who did not approve the bills. That gives a five-person firm separation of duties without a second finance role. Put all of this in the same document as the approval rule.
Keep the scheduled check read-only
The realistic failure in a bills process is a wrong payment released from a wrong list: a duplicate, a bill that should be on hold, a vendor's changed bank account, or one commitment arriving as two invoices that each sit under an approval limit. A read-only list can only produce a wrong question, which costs a minute in the thread. A wrong payment costs the amount. So let the scheduled check read and list, and keep every write and every payment with a person.
- 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. The Kipwise agent does not pay bills, and nothing in this approach needs it to.
- Enter the vendor's own invoice number on every bill. Hellobooks treats it as the thing that 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 week at the design agency
This week is made up. The 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 it has never used. Monday's list sends the software bill through without approval because it matches last month, puts the $1,800 bill with the project lead who commissioned the work, and puts the $3,100 and $950 bills with the owner.
By Thursday noon the project lead has not answered, so the owner asks for a reminder and presses Approve on the draft. 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, calls a number already on file, and hears that the note is not the vendor's. The bill goes on hold. On Friday the owner pays the approved bills from the bank in one run, and the next Monday the check reports every paid bill as cleared.
Run the check, buy approval software or hire
- Run the weekly check first if you have fewer than about 30 bills a month and one or two approvers (a round number, not a benchmark).
- 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. When you compare tools, check whether the approver can approve inside Slack or only gets a notification that sends them to an AP portal.
- 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.
Start this week, and count after four weeks
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.
After four weeks of Monday lists, 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.



