Billing and collections

Updated 9 October 2026

Dana's 61-to-90-day list had nine names on it last month. This month it has fifteen. About half are roll-off accounts that keep swapping containers at the same construction sites; the rest are portable sanitation customers running recurring event service. Dana has one spreadsheet tab for the balances, one email thread per account for the back-and-forth, and no clean way to decide who gets called before the billing cycle closes on Friday.

That is the ordinary shape of collections once a roll-off or portable sanitation company carries more than a handful of overdue accounts. The fix is not a wider spreadsheet. It is a short triage habit: filter the list by age, group accounts that need the same follow-up, batch the send to that group, and log the call where the invoice already lives.

The one-account-at-a-time problem behind that growing list

A single overdue account is easy. The office can open the invoice, check the balance, send a note and move on. The trouble starts once a dozen accounts sit past 60 days at the same time, each in a different email thread, each at a different stage of being chased.

Receivables do not get easier to collect the longer they sit. The value of a receivable declines over time because the likelihood of collection decreases the longer that a receivable is outstanding, which is why an aging schedule assigns a lower expected-collection value to a 90-day balance than to a 10-day one. Experian's own business-credit glossary tracks the same idea from the payer's side: Days Beyond Terms is the average number of days a firm pays its bills past the invoice due date, and a rising DBT across a customer base is an early warning before any single account looks alarming on its own.

Roll-off and portable sanitation accounts carry a specific version of this risk because so much of the work runs through construction and event clients on their own payment cycles. Construction-site customers are historically the slower payers in this kind of account base. Around half of subcontractors, material suppliers and rental companies report that it takes more than 40 days on average to get paid, per Levelset's national survey of construction payment practices. Nationally, late payments affect an average of 22% of B2B receivables in the United States, with about seven out of ten companies reporting at least some late payments.

This is not a niche problem limited to one vertical. The Portable Sanitation Association International counts about 1,200 businesses in the United States that are primarily focused on portable sanitation, alongside the far larger roll-off and dumpster rental side of the industry, and most of those operators bill recurring and event accounts the same way roll-off operators bill recurring container service. A billing admin working a dozen-plus overdue roll-off and portable sanitation accounts at once is not managing an exception; it is a normal month.

The four-step process: sort the list before you touch the phone

Before any account gets a call, sort the list. The order matters more than the speed:

1. Filter by age. Pull every overdue account into its aging bucket: 1 to 30, 31 to 60, 61 to 90 and 91-plus days.
2. Group by action. Inside a bucket, group accounts that need the same next step, such as a second written notice, a call, or a hold on new service.
3. Batch the send. Send one statement run to the whole group instead of drafting the same note a dozen separate times.
4. Log the call. Record what was said and agreed directly against the account, so the next person working that list is not starting from a blank page.

Those four steps do not remove judgment from collections. They remove the twelve open tabs that make judgment slower than it needs to be. The U.S. Small Business Administration makes the same basic point about any receivables process: issue invoices promptly and have a follow-up system for collecting, rather than letting the follow-up happen whenever someone remembers to check a thread.

Filter by age: the four buckets that replace the spreadsheet

An accounts receivable aging report categorizes unpaid invoices by how long they have remained outstanding, grouping them into time buckets so a business can see overdue payments at a glance instead of reading every invoice in order. CRO sorts overdue accounts into four buckets: 1 to 30, 31 to 60, 61 to 90 and 91-plus days. Intuit's own QuickBooks Online support documentation describes the matching Accounts Receivable Aging Summary and Detail reports an operator runs the same way once that operator is on QuickBooks.

CRO gives billing admins at roll-off and portable sanitation companies a collections dashboard that filters overdue accounts into those same four buckets automatically, so the list builds itself instead of someone rebuilding it in a spreadsheet every week.

Group by action with Collections Baskets

Once the buckets exist, the next problem is that not every account in a bucket needs the same thing. A roll-off account that missed one invoice needs a different note than a portable sanitation account that has ignored two statements in a row.

CRO lets a billing admin create a Collections Basket to group and prioritize follow-up by whatever fits the admin's own workflow. For Dana's growing 61-to-90-day list, that means the roll-off accounts waiting on a second notice can sit in one basket while the portable sanitation accounts due for a direct call sit in another, without either group getting lost in the other's thread.

Batch the send, then log the call

CRO reaches a whole basket at once with batch statement sending, instead of opening each account to draft and send the same reminder a dozen separate times. The admin reviews one batch, sends it, and moves to the next basket.

Call notes and status updates then log directly on the invoice screen in CRO, in the same place the balance and the statement history already live. That matters more than it sounds: the next person who opens that account, whether it is Dana again next week or a manager asking for an update, reads what already happened without digging through a separate email thread or asking around the office.

Who to call first inside a basket, and when an account needs to move from a notice to an escalation, stays an operator decision. The dashboard sorts and groups the list; it does not decide which fifteen-name account gets the first phone call on a Friday afternoon.

Where CRO fits in the decision

CRO Collections is built for one specific setup: an operator who runs customers and invoices inside CRO without a QuickBooks connection. That operator gets the aging dashboard, Collections Baskets, batch statement sending and invoice-screen call notes described above, all inside CRO.

An operator whose invoices and customers sync to QuickBooks Online or QuickBooks Desktop works overdue accounts inside QuickBooks instead, using its own accounts receivable aging report there. The two do not combine into a shared collections view; a customer does not get CRO's collections dashboard and a live QuickBooks sync at the same time. That is a real boundary, not a missing feature on either side, and it is worth knowing before a QuickBooks shop builds a workflow around a dashboard it will not be using.

CRO's QuickBooks Online and Desktop integration is a separate, real feature: it keeps invoices and customers aligned for billing so entries do not have to be created twice. That sync is about billing data matching between the two systems, not about running the collections dashboard on top of a QuickBooks-connected account. Keeping those two facts distinct is the difference between a workflow that fits an operator's setup and one that promises a combined view nobody actually gets.

What clearing the list is worth in office time

The one-tab-per-account routine costs real time, and it adds up faster than it looks once the list passes a dozen accounts. Assume a billing admin spends about 12 minutes per account working the old way: finding the spreadsheet row, opening the right email thread, confirming the current balance and drafting a note, compared with about 3 minutes per account once the accounts are already filtered into a bucket, grouped into a basket and ready for a batch send, a reduction of roughly 9 minutes per account.

For a 61-to-90-day list of a dozen accounts, that is about 108 minutes, or 1.8 hours, saved on a single weekly pass. At the median wage for bookkeeping, accounting and auditing clerks, $24.36 an hour as of May 2025 according to the Bureau of Labor Statistics, that pass is worth roughly $44 in office time. Run weekly across a year, the same bucket-and-basket habit is worth close to $2,280 in office time, before counting a single invoice that gets paid sooner because the follow-up happened on time instead of three weeks late. The minutes per account, the account count and the cadence are assumptions for this example; substitute your own numbers to size the effect for your office.

The stakes behind that time are not abstract for small operators. More than half of small employer firms cited uneven cash flows, 51%, as a financial challenge in the Federal Reserve Banks' 2024 Small Business Credit Survey, and a roll-off or portable sanitation shop with a dozen-plus accounts sitting past 60 days is carrying exactly that kind of unevenness on its own books.

Questions to test in a collections walkthrough

Ask for a walkthrough using a real overdue list rather than a clean sample account. A dozen accounts split between roll-off and portable sanitation, spread across two or three aging buckets, is a fair test.

• Can the admin filter the whole customer base into the four aging buckets without exporting anything to a spreadsheet?
• Can accounts in the same bucket be grouped into a basket by a reason the admin chooses, not a fixed category?
• Does a batch send reach every account in a basket in one action, with each statement showing that account's own balance?
• Does a call note or status update save directly on the invoice screen, visible to the next person who opens that account?
• If the business has a live QuickBooks connection, does the walkthrough say plainly that collections then runs in QuickBooks, rather than promising both?

A billing admin should leave that walkthrough knowing exactly which system owns collections for their setup, not assuming CRO's dashboard sits on top of a QuickBooks sync it does not support.

Ready to see the aging buckets and Collections Baskets on your own overdue list?

Frequently asked questions

Sources

1. RapidWorks, CRO product page, reviewed 9 October 2026.
2. RapidWorks, How to Manage Subscription and Recurring Waste Collection Accounts, reviewed 9 October 2026.
3. RapidWorks, How to Reduce Days-to-Invoice in Roll-Off Operations, reviewed 9 October 2026.
4. Corporate Finance Institute, Accounts Receivable Aging, reviewed 9 October 2026.
5. Intuit QuickBooks, Run an accounts receivable aging report, updated 5 August 2026, reviewed 9 October 2026.
6. National Association of Credit Management, Commercial Collections: An Overview, reviewed 9 October 2026.
7. Experian, Days Beyond Terms (DBT) glossary, reviewed 9 October 2026.
8. Atradius, B2B Payment Practices Trends in the US 2026, published 10 September 2026, reviewed 9 October 2026.
9. Levelset, Construction Payment Speed: Winners and Losers, updated 18 April 2023, reviewed 9 October 2026.
10. U.S. Small Business Administration, How Net 30 Accounts Help Conserve Business Cash Flow, reviewed 9 October 2026.
11. U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Bookkeeping, Accounting, and Auditing Clerks, May 2025, reviewed 9 October 2026.
12. Federal Reserve Banks, 2024 Small Business Credit Survey, key insights, published 27 March 2025, reviewed 9 October 2026.
13. Portable Sanitation Association International, Portable Sanitation 101, reviewed 9 October 2026.

About the author

Ellery Curran, Marketing Specialist, RapidWorks

Ellery Curran works in marketing at RapidWorks, a software company that serves waste, septic, and heavy equipment operations businesses. She focuses on content that helps operators evaluate and adopt field service technology.