Bill pay software for bookkeepers lets you enter, approve and pay a client's bills from one place, while the money still leaves the client's own bank account. Choose it on four things: an approval flow the client controls, clear permissions for staff, the payment methods vendors expect, and records that match each client's bank statement line by line.
What should bill pay software do in a bookkeeping practice?
Bill pay software should take a client's bill from arrival to payment with a record at every step: captured, coded, approved, paid and cleared. For a bookkeeper the core value is control without custody. You prepare payments, the client approves them, and the funds move from the client's account, never through yours.
That last point shapes the whole choice. A bookkeeper who pays bills from a client's account is trusted with money, and the software has to make that trust checkable. Every payment should show who entered it, who approved it and when it left the bank. If a client ever questions a payment, you want the answer on one screen, not in a pile of emails.
The steps a bill passes through, and what to look for at each:
- Capture. The bill arrives by email, upload or photo. The tool should read the vendor, amount and due date, and keep the original document.
- Coding. The bill gets an expense account, so it lands correctly in the client's ledger.
- Approval. The client, or someone they name, says yes.
- Payment. The money goes out on a chosen date by a chosen method.
- Clearing. The payment shows up on the client's bank statement and is matched.
Steps 1 to 4 are where vendors compete. Step 5 is where bookkeepers spend their time, and the tool's records decide how easy it is.
If you are building a new practice and deciding whether to offer bill pay at all, treat it as a separate service with its own fee and its own risk. The guide on how to start a bookkeeping business step by step helps define which services to launch with.
Approval flows in bill pay software
An approval flow is the set of rules that decides who must say yes before a bill is paid. For bookkeepers, the client should always hold the final approval, even when you prepare everything. Good software lets that rule vary by client and by amount, and records every approval with a name and a time.
Approval rules worth testing:
- Single approver. The owner approves every bill. Simple, and right for most small clients.
- Thresholds. Bills under a set amount are approved by an office manager; larger ones need the owner.
- Two approvers. Some clients with two owners or a board want two people on large payments.
- Recurring approval. A fixed monthly bill such as rent may be approved once for the year, with the tool paying it each month.
Check how approval reaches the client. An approval request by email with a one-tap approve on a phone gets answered. One that needs a login to a dashboard tends to sit there until a vendor calls about a late payment.
Also check what happens when a bill changes after approval. If you edit the amount or the date, the approval should reset. A tool that lets an approved bill be edited and paid without a new approval quietly removes the control you bought it for.
Client access and permissions for bill payments
Permissions in bill pay software decide who can enter bills, who can approve them, who can change bank details and who can only look. Set them per client and per person. The rule to protect is that nobody at your firm can both add a new vendor's bank account and approve a payment to it.
That separation is the most important control in bill pay. A fraudulent change to a vendor's bank details, often sent by email that looks like it came from the vendor, is a common way businesses lose money. If one person can change the details and pay, there is no second check. Look for a tool that sends a notice to the client when vendor bank details change, and that holds payments to that vendor until the change is confirmed.
A sensible split for a small firm:
| Role | Enter bills | Code bills | Approve | Change vendor bank details | View history |
|---|---|---|---|---|---|
| Junior bookkeeper | Yes | Yes | No | No | Yes |
| Senior bookkeeper | Yes | Yes | No | Request only | Yes |
| Client owner | Optional | No | Yes | Confirm | Yes |
| Client office manager | Yes | No | Under threshold | No | Yes |
Clients should also be able to see everything at any time without asking you. A monthly summary of bills paid, coming due and waiting for approval is a natural item for the client's report. The comparison of client reporting software for bookkeepers covers how to present that each month.
Ask too about which devices staff can use. Many bill pay tools run in a browser, but some features, such as printing checks on blank stock, may need a particular setup. If your team works on Macs, the guide to bookkeeping software for Mac lists what to confirm before buying.
Which payment methods should bill pay software support?
Bill pay software should support the methods a client's vendors already accept, which for most small businesses means bank transfer by ACH, paper check and sometimes card. The method matters to bookkeepers because each one clears differently. A check can sit uncashed for weeks; an ACH transfer usually clears within a few business days.
What each method means for the books:
- ACH bank transfer. Usually low cost or free, and predictable. The statement line normally appears a short time after the payment date, with a description that names the bill pay provider and often the vendor.
- Paper check. Mailed by the provider or printed by you. The payment is scheduled on one date but clears whenever the vendor deposits it, which can be weeks later or never.
- Card. Some providers pay vendors by card, which moves the payment onto the client's card statement instead of the bank statement.
- Virtual card. Some vendors accept a one-time card number by email, which then appears as a card transaction.
Ask how each method appears on the client's statement. Some providers pull the total of several bills from the client's account in one debit, then pay vendors separately. Others debit each bill on its own. The first makes the bank statement shorter but harder to match; the second makes every line traceable.
Also ask about timing. If the provider debits the client's account on the payment date but the vendor receives funds days later, there is a gap where the money has left the client but has not reached the vendor. That gap matters at month end.
Matching bill payments to the client's bank statement
Matching means tying each payment from the bill pay tool to the line it produced on the client's bank statement. It is how you prove each bill was paid once, for the right amount, from the right account. The work is easy when each payment produces one statement line with a clear description, and slow when payments are bundled.
The table below is an example of four bill payments for one client in March and the bank statement lines they produced. The vendors, dates and amounts are made up for illustration.
| Bill | Method | Scheduled | Amount | Statement line | Statement date | Matched? |
|---|---|---|---|---|---|---|
| Office rent | ACH | Mar 1 | 2,400.00 | BILLPAY ACH LANDLORD LLC | Mar 3 | Yes |
| Cleaning service | ACH | Mar 10 | 380.00 | BILLPAY ACH SPARKLE CLEAN | Mar 12 | Yes |
| Equipment repair | Check | Mar 15 | 615.00 | CHECK 1048 | Apr 2 | Not in March |
| Software subscription | Card | Mar 20 | 99.00 | (card statement) | Mar 20 | On card statement |
Read the table for what it teaches. The ACH payments land two days after their scheduled date, so a March 31 payment would land in April. The check was scheduled in March but cleared in April, so it is an outstanding check at March month end. The card payment never touches the bank statement at all.
A good routine each month:
- Export the bill pay tool's payment list for the period.
- Convert the client's bank and card statements into transaction lines.
- Match each payment by amount, then confirm by date and description.
- List anything unmatched: uncleared checks, payments that failed, and bank lines with no bill.
- Carry uncleared checks forward and check them again next month.
Step 2 is where statement work comes in. Converting each client's statements into clean lines, with opening and closing balances checked, makes the matching quick. AutoBankConvert batch-converts statements for every client and holds back any statement whose transactions do not add up to its closing balance. The overview of bank statement processing software for a practice sets out what to look for in that step.
When a bookkeeper should not run a client's bill pay
A bookkeeper should not run a client's bill pay when the client will not approve payments promptly, when the client wants you to approve on their behalf, or when the firm has no second person to separate duties. In each case the control that makes bill pay safe is missing, and the risk sits with you.
Situations to decline or postpone:
- The client wants you to approve. If you both prepare and approve, any mistake or fraud is yours alone. Keep approval with the client.
- The client never answers. Bills will go late, vendors will call you, and you will be blamed.
- You work alone and the client is large. Without a second person, the separation of entering and approving cannot exist inside your firm, so the client must hold it.
- The client's cash is tight. Choosing which bills to pay when money is short is a business decision, not a bookkeeping task.
- Your engagement letter does not cover it. Paying bills is a service with real liability. Put it in writing, with a fee, before you start.
When bill pay does fit, keep the client in charge of approval and keep your records tight enough that every payment can be traced to the statement. If converting those statements is the slow part, get started with AutoBankConvert and run one client's month through it.