Billing Monthly Lawn Maintenance and Seasonal Jobs
· 5 min read
Your maintenance client pays $340 a month for weekly mowing, edging, and blowing. Then April hits and you spread eight yards of mulch, prune the shrubs, and reset the irrigation heads. If you fold that $900 of seasonal work into the same line as the monthly fee, three things happen: the client questions the total, your recurring revenue looks lumpy, and next month they expect the higher number to keep coming. Keep the two streams apart and every one of those problems goes away.
Why the maintenance fee and seasonal work do not belong on the same line
Monthly maintenance is a fixed, recurring commitment. The client already agreed to it, the price does not change week to week, and it should show up as one clean line every cycle. Seasonal work is different. It is scoped once, priced once, and billed once. Spring cleanup, fall leaf removal, mulch installation, aeration, overseeding, irrigation startup and blowout, a one-time tree job: none of these repeat on a schedule, and each carries its own materials and labor.
Mixing them hides information the client wants. When your April invoice jumps from $340 to $1,240 with no breakdown, the client cannot tell what they are paying for, and an approval that should take a day turns into a phone call. Separate the recurring line from the seasonal lines and the invoice explains itself.
Two invoices or one invoice with clear sections
You have two workable options. Send two separate invoices in the same month, one for the flat maintenance fee and one for the seasonal job. Or send a single invoice with the maintenance fee on its own line at the top and each seasonal task itemized below it under a clear heading. Either works. Two invoices keep your recurring revenue reporting clean and let the client route the seasonal one through a different approval if they need to. One invoice means one payment and less to track. Pick based on how your client's accounts payable process handles things, and stay consistent so they know what to expect.
How to structure the recurring maintenance line
Keep it boring and identical every month. One line item: "Monthly lawn maintenance, [month] [year], per service agreement." Same amount, same wording, same terms. Predictability is the point. The client should be able to approve it on sight because nothing changed.
Give the recurring invoices a numbering scheme you can read at a glance, so April's maintenance invoice is obviously distinct from a seasonal one. If you have not settled on a format, the guidance in invoice numbering best practices keeps your books clean when a single client gets several invoices in a month. Set your invoice number format once and let it increment on its own.
Because maintenance repeats, your fastest path is a saved starting point. A landscaping invoice template with the maintenance line already filled in means each month is a copy, a date change, and a send. Building from a blank page every cycle is where errors and delays creep in.
How to itemize seasonal work so it gets approved
Seasonal jobs need detail the maintenance line never does. Break out labor and materials. "8 cu yd hardwood mulch, delivered and installed, $520" and "Shrub pruning, front and side beds, 4 hrs, $260" tell the client exactly what they bought. A single "Spring services, $900" line invites the question you do not want.
Quote seasonal work before you do it. Send a written quote with the scope and price, get it accepted, then the invoice matches what was agreed and there is nothing to argue about. A landscaping estimate template covers the quote side, and JupiterInvoice lets the client accept a quote by typing their name to sign, which gives you a clean record before the crew shows up.
If the client's business requires a purchase order for anything outside the standard contract, the seasonal invoice is where it matters. Maintenance may be covered by a blanket PO while each seasonal job needs its own. If a missing PO number stalls the invoice, you want it stalling on the seasonal line, not holding up your recurring payment too. Keeping them separate protects your steady cash flow when a one-off job hits a procurement snag.
Handling the mid-season change without redoing the invoice
Seasonal work invites changes. The client adds two more beds of mulch, or asks you to skip the pruning, or wants the irrigation blowout moved to a different date. With a static PDF you reissue the whole thing and hope they open the new one.
JupiterInvoice handles this through recipient collaboration. You share a private link, no account needed on the client's side. They can add a PO number or fix their billing entity directly, and you get notified. For anything that changes the money (adding a line, adjusting a price, shifting the due date) they submit a request and you approve or decline it, which creates a new version you can track. When the client is happy they approve the invoice and the version locks. You can see the mechanics in the write-up on versions versus amendments.
A worked example for one April client
Say your client's maintenance is $340 a month, Net 15. In April they also want mulch and a spring cleanup. You send two invoices. The first is the flat $340 maintenance line, identical to March. The second itemizes: mulch materials and install at $520, spring bed cleanup at $210, irrigation startup at $95, for $825 before tax. Each invoice carries its own number and its own PO if the client requires one. Your recurring revenue still reads $340 for April, and the seasonal $825 stands on its own, fully explained.
Set that pattern once and every busy month runs the same way. Create the maintenance invoice from your saved template, itemize the seasonal job on a separate one, and both get approved without a single clarifying email.