Wave Accounts Payable: Bills, Aging, Limits, Workarounds

Wave handles a basic payable workflow — bill entry, vendor records, due-date tracking, aged payables — but it is not a full AP system. In practice, Wave lets you enter bills, assign them to vendors, set due dates, track unpaid amounts in accounts payable automatically, and review aged payables and purchases-by-vendor reports. The limits show up just as quickly: permissions are tied to Wave Pro, those permissions are not highly customizable, recurring bills are not built in, and higher-volume teams still rely on manual workarounds.

Those details are not minor. According to CPA Practice Advisor's report on small-business AP payment challenges, over half of small businesses spend at least four hours each month managing accounts payable, and 38% say keeping track of due dates is their biggest challenge. That is why an honest workflow assessment matters: if your payable process depends on retyping invoice details, checking due dates by hand, and managing exceptions outside the system, the software may still work, but the labor around it grows faster than most teams expect.

How Bills, Vendors, and Due Dates Work in Wave

In Wave, the payable workflow starts in the Bills area under Purchases in the web app and ties each bill to a vendor record. For a small business with a manageable invoice volume, that gives you a workable place to log what you owe, track when it is due, and keep those unpaid amounts sitting in accounts payable until you record the payment.

The day-to-day flow is straightforward. When you enter a bill in Wave, you are filling in the fields that actually drive the rest of the workflow: the vendor, currency, bill date, due date, bill number, notes, plus the line-level details such as expense account, quantity, price, and tax. If your process depends on reference fields like P.O./S.O., that can also matter at entry because it helps connect the bill back to the purchase or job it came from. Entering a bill in Wave is really a question of whether the software captures enough operational detail to keep the books clean without side spreadsheets.

Vendor setup is part of that answer. Wave bills and vendors work together best when each supplier has a consistent record, because the vendor name becomes the anchor for bill history, reporting, and follow-up. That is enough for basic Wave vendor management in a low-complexity environment: you can keep recurring suppliers organized, see which bills belong to whom, and avoid treating every invoice as a one-off transaction. If your team mostly needs a clean vendor list and a reliable place to store bill details, Wave can cover that.

Once saved, a bill sits in accounts payable until payment is posted, so the due date is what separates a current bill from a problem one. That weekly rhythm (record on arrival, monitor, clear on payment) works for an owner-operator or single bookkeeper, but it assumes someone is retyping vendor names, bill numbers, dates, and line details from incoming PDFs — Wave accepts the bill but does not source the data for you.

---

What Wave's Aged Payables and Vendor Reports Actually Tell You

Wave's reporting layer is most useful once you stop asking, "Can I enter bills?" and start asking, "Can I see what is still unpaid, how late it is, and which vendors are driving spend?" For that, the aged payables report is the main visibility tool. A typical Wave accounts payable aging report helps you sort unpaid balances into overdue buckets so you can see what is current, what is slipping, and which obligations need attention first. That matters because AP problems usually show up as missed timing, not missing transactions. If you can spot a growing 30-day or 60-day bucket early, you have a better chance of protecting cash flow and supplier relationships.

The purchases by vendor report answers a different question. Instead of showing aging by due status, it helps you review supplier-level activity over time. For a small business, that is useful when you want to confirm where money is going, compare vendor totals, or sense-check whether one supplier is starting to account for more of your monthly purchasing than expected. A bookkeeper or owner can use that report to support month-end review, vendor conversations, or basic spend analysis without exporting data into a larger reporting stack.

Used together, these reports create a practical weekly review routine. The aged payables report helps you prioritize overdue bills and spot balances that are drifting. The purchases by vendor report helps you see whether spend is concentrating with one supplier or climbing unexpectedly. That is useful for a small team that needs straightforward visibility into liabilities and supplier activity without building a larger reporting stack.

The limit is that the reports do not create workflow control. They show what is outstanding and who it is tied to, but they do not route bills for approval, pause payment, or enforce team rules around exceptions. Someone still has to review the reports, decide what needs follow-up, and act outside the software. If you want a stronger refresher on how to read an accounts payable aging report and fix the underlying data, Wave's reporting can support that habit. It just does not replace the manual follow-up around it.

Where Permissions and Approvals Start to Matter

Permissions barely matter when one person handles every bill. The friction starts when payable work gets shared across an owner, outside bookkeeper, office manager, or controller. At that point, the question is not just whether bills can be recorded. It is whether the right people can see, enter, review, and act on them without creating control gaps.

In Wave, collaborator permissions are tied to Wave Pro, and the structure is not especially granular. That matters because small finance teams often want more than simple shared access. They want one person to enter bills, another to review vendor details, and someone else to approve payment timing. Wave Pro gives some improvement in visibility and role separation, but it does not create the kind of highly customizable permission model that supports layered AP control.

Whether Wave supports bill approvals depends on what you mean by approval. Collaborator controls are not the same as a true approval workflow. A real bill approval process usually means a bill can move through defined checkpoints before payment, with clear accountability over who reviewed it, who approved it, and whether exceptions were flagged. In Wave, the control is lighter. Teams can share work more easily than they can in a purely owner-only setup, but they should not assume that means they now have formal bill approvals in place.

Operationally, this shows up in common day-to-day scenarios. A staff member may be able to enter vendor bills, but the business still needs an external process to confirm the amount, coding, due date, or payment authorization. If two people touch payables, the team may gain convenience, yet still rely on email, chat, or verbal signoff to decide what actually gets paid. That can be workable for a low-volume business, but it is different from having approvals built into the AP workflow itself.

---

The Operational Gaps That Create Extra AP Work

Once the basic bill workflow is in place, the remaining friction usually shows up in three places: the lack of recurring bills in Wave, lightweight approval controls, and the lack of a native document-intake workflow for supplier invoices.

The recurring-bill issue matters more than it first appears. If you pay the same landlord, software vendor, or utility provider every month, you still need a repeatable way to get each bill into the system accurately and on time. Without true recurring bills, teams often fall back to calendar reminders, copied entries, or manual re-entry. That can be manageable for a very small business with a handful of invoices, but it becomes harder to control as volume grows and due dates start stacking up across vendors.

Approval depth is another breakpoint. Wave works best when one person handles most payable tasks or when review is informal. Once you need clearer separation between the person entering bills and the person approving payment, shallow controls create extra coordination outside the software. Teams end up relying on email threads, chat messages, or spreadsheet trackers to confirm what has been reviewed, which weakens the audit trail and adds more admin work around the payable workflow.

The biggest operational gap, though, is document capture. Wave does not give you a native high-volume process for taking supplier PDFs, scanned invoices, or mixed-format billing documents and turning them into clean bill data at scale. That means someone still has to create the structured data first, usually by reading each invoice and keying vendor names, invoice numbers, dates, totals, and line details by hand before the bill can even be saved.

Wave Connect can help in a narrower way. If you already have invoice data in a structured spreadsheet, it can help move that data into Wave more efficiently. But it does not read PDFs, extract fields from invoice images, or solve the document-to-data step by itself. In practice, that means Wave Connect is useful after the data has been cleaned and organized, not before.

For teams dealing with supplier PDFs, this is usually where the admin cost starts to climb. At low volume, a bookkeeper can absorb a few extra minutes per bill. At higher volume, those minutes turn into hours of rekeying, more opportunities for miskeyed amounts or due dates, and more delay between receiving an invoice and getting it into the payable queue. The broader workflow question is how to automate Wave invoice data entry before bills are posted, not whether Wave can store a bill after it already exists.

Invoice Data Extraction addresses that upstream step by turning supplier invoices into structured Excel, CSV, or JSON output through a prompt-based workflow, giving teams cleaner data for Wave bill entry or Wave Connect import. That is a different job from accounting storage. Wave handles the bill once it exists; the upstream layer handles turning incoming documents into usable data. Teams that are working from supplier PDFs and want a more detailed handoff can use the companion guide on how to import PDF supplier invoices into Wave without retyping.

The practical rule: low volume, one operator, and minimal approvals usually means Wave is enough. Rising invoice count, shared ownership, off-system approvals, and repeated PDF rekeying usually mean you need more structure upstream. Teams that are already feeling that strain can see how small businesses automate invoice entry before approval and payment for a deeper look at that next layer.