28-day billing for roll-off rentals
A 28-day billing cycle bills every four weeks rather than on a calendar month. Thirteen of those cycles fit in a year where twelve calendar months do, which is where the convention gets its reputation. It is a trade convention rather than a rule, and it interacts awkwardly with a business whose real unit of work is the pull.
Informational only. Informational only, not legal advice. Federal rules are quoted from the regulations as published; state and local rules sit on top of them and vary. Confirm your own position with the agency named before you rely on it.
Reviewed August 2026
Verify with the offices named on the permit and licensing pages this guide draws on.
What a 28-day cycle is
A 28-day cycle is a fixed four-week billing period. Instead of invoicing on the first of each month, the invoice falls every 28 days from a start date, which means it moves around the calendar rather than sitting still on it.
The convention is described in the trade as common in portable sanitation and dumpster rental, and both the software vendors serving those trades and operators themselves discuss it as an established practice. It is not written into any regulation, no agency requires it, and nothing prevents an operator from billing on calendar months instead.
Because it is a convention rather than a rule, the only thing that makes it binding between you and a customer is the rental agreement. That is worth stating in plain terms in the agreement itself, since a customer who expects twelve invoices a year and receives thirteen has a legitimate complaint about the disclosure even where the pricing was fair.
Where the thirteenth cycle comes from
The arithmetic is the whole story. Thirteen cycles of 28 days is 364 days, one day short of a common year. Twelve calendar months is 365. So a rental billed every 28 days generates thirteen invoices in the same span that produces twelve monthly ones.
Stated as a benefit, that is an extra billing period per unit per year at the same headline rate. Stated as an obligation, it is an extra charge the customer did not expect if nobody told them the cycle was four weeks rather than a month. Both descriptions are accurate, and which one a customer uses depends entirely on how clearly it was explained before they signed.
The other half of the arithmetic is drift. A cycle that is 28 days long starts a day or two earlier each calendar month, so invoice dates walk backwards through the year. Over twelve months an invoice that began in the first week of the month ends up in the last week of a different month.
Roll-off is priced per pull, not per period
The complication is that this convention comes from trades where the billable unit is a period. A unit on site for a month is a month of service, and a period-based cycle fits that shape naturally.
Roll-off does not have that shape. The unit of work is the pull: the delivery, the exchange, the final haul. Those are events, and they are priced as events, often with disposal charged by weight on top. The rental period exists alongside them, usually as an allowance of days included in the pull price, with rent accruing after that allowance runs out.
So a roll-off invoice generally carries two different kinds of line. Event lines that happen when they happen, and period lines that accrue while the box sits. A billing cycle governs only the second kind, which is why importing a period convention wholesale from a period-based trade does not fit without thought.
Where the two shapes collide
The collision happens at the cycle boundary. A box delivered midway through a cycle, hauled midway through the next one, and never exchanged in between produces a rental line that belongs to neither cycle cleanly, and a customer looking at two invoices for one job.
It also shows up in reconciliation. If pulls are event-priced and rent is cycle-priced, then revenue per job is split across invoices whose dates have nothing to do with the job. Working out whether a particular job made money means reassembling it from pieces that were never filed together.
And it shows up at close. Cycle boundaries that drift do not align with month ends, so month-to-month comparisons stop being like-for-like: some months contain one cycle boundary and some contain two, which moves revenue between periods for reasons that have nothing to do with the work performed.
Whichever convention you use, the cycle length, the start date, the included days on a pull, and the rate that accrues after them should be stated in plain terms in the rental agreement. The dispute this prevents is not really about the money.
Permit durations do not respect billing cycles either
There is a third clock running on the same job, and it belongs to the city. Permit durations are set by the issuing agency and they match neither calendar months nor 28-day cycles.
San Diego’s traffic control permit for a storage container or dumpster is valid up to 7 days, with extensions requiring City Engineer approval and additional fees, and its published pricing splits by category: a temporary storage container is priced per week with a one-week maximum, while a dumpster is priced per month. In New York City a construction debris container permit runs up to 90 days tied to an active buildings department permit, while a bulk item refuse container permit runs up to 5 consecutive days. Philadelphia issues its private dumpster license as lifetime with no renewal and its public right-of-way license annually with late fees past 60 days.
Three clocks on one job is the operational reality: the pull, the billing cycle and the permit. They are all worth tracking separately, because expiry on the third one is the only one with an enforcement consequence attached.
Making the convention work rather than fighting it
Two things make a 28-day cycle behave. The first is disclosure: name the cycle length and the number of cycles in a year in the agreement, in words a customer will read the same way you do. The second is separation: keep event revenue and period revenue as distinct lines so that a job can be reassembled later without guesswork.
The 28-day billing calendar on this site lays the cycles out against the calendar so the boundaries and the drift are visible in advance rather than discovered at close. Knowing which months carry two boundaries is most of what makes the convention manageable.
And if it does not suit your operation, nothing requires it. Calendar-month billing is a legitimate choice, and so is billing rent only after an included-days allowance expires. The convention is a tool from a neighboring trade, not an obligation this one inherited.
What this guide does not settle
Each of these is a thing this page does not answer. They are listed rather than smoothed over, because a gap you can see is worth more than a sentence that reads as though there is none.
- How widely the 28-day convention is actually used in roll-off specifically. It is described as a trade convention in secondary sources rather than measured, and no adoption figure was verified for this page.
- Any figure for what the convention does to annual revenue. That depends on your rates, your included-days allowances and how long boxes sit, all of which are yours.
- Permit durations and fees in metros where no agency page carried them. Ask the issuing office named on the metro page.
Frequently asked questions
What is 28-day billing and why does the trade use it?
It is a fixed four-week billing period rather than a calendar month. Thirteen cycles of 28 days is 364 days, so a rental billed this way produces thirteen invoices in the span that produces twelve monthly ones. It is a trade convention rather than a rule, and it comes from period-priced trades.
Does 28-day billing make sense for roll-off?
It fits the rental half of the job and not the pull half. Roll-off revenue is mostly event-priced, so a period cycle governs only the rent that accrues while a box sits. Keeping event lines and period lines separate is what makes either convention workable.
How do I explain a 28-day cycle to a customer?
State the cycle length, the start date, the included days on a pull and the rate that accrues afterward, in the rental agreement and in plain words. A customer who expects twelve invoices and receives thirteen has a disclosure complaint even when the pricing was fair.
Sources, and what each one returned
Every claim above traces to one of these. Where a source is marked as one we could not open, nothing on this page rests on it: it is listed so you can try it yourself, and the note says what our request got back.
Where to go next
The rules are the easy half
Knowing what an agency requires is one thing. Proving, months later, that a box was dropped, swapped and collected on the days you invoiced for is the part that actually costs operators money. SwapProof is being built for that record. It is not open yet — the waitlist is where you hear first.