Automating accounts receivable for RealGreen companies, politely

You can automate most of your accounts-receivable follow-up without torching a single customer relationship. The recipe: pull aging balances from RealGreen nightly, send tone-graded reminders (friendly at 30 days with a one-tap pay link, firmer at 45–60, a final notice before service hold at 90), stop the sequence the moment payment lands, and offer autopay in every touch. Done right, it pulls tens of thousands of dollars forward each season. And it's genuinely more polite than what most offices do today, which is months of silence followed by one awkward phone call.

How does automated AR work with RealGreen?

Every night, invoice and aging data syncs from RealGreen into your automation platform, and each account is sorted into a bucket: current, 30, 60, or 90+ days. Each bucket maps to a step in a reminder sequence, and a payment removes the account from the sequence. Your office does nothing: no exporting aging reports, no mail-merge, no call list. That's the same nightly-replication architecture behind our RealGreen automations, running on a workflow engine connected through HighLevel.

One honest mechanical detail: "stops instantly on payment" has two speeds. A payment made through the reminder's pay link stops the sequence immediately, because the platform sees it happen. A check recorded at the office in RealGreen stops it at the next nightly sync. In practice a reminder almost never crosses a payment by more than a day, and the reminder copy should acknowledge the possibility anyway ("if you've already paid, please disregard").

What should each reminder actually say?

The tone should be graded to the age of the balance, because a customer 30 days out is almost always disorganized, not unwilling, while a customer at 90 days needs to hear a consequence. Here's the sequence we recommend for residential accounts:

Aging bucket	Channel	Tone	Call to action
30 days	Email + text	Friendly: "this probably just slipped by"	One-tap pay link, plus an autopay offer
45 days	Text	Direct: exact balance, exact date	Pay link, or reply to arrange a payment date
60 days	Email + letter	Firm: account needs attention to keep service on schedule	Pay link, autopay offer, office callback option
90 days	Letter + call task for the office	Final notice: service hold pending	Pay in full or talk to a human this week

Every touch carries a one-tap pay link, every touch offers autopay, and the whole sequence halts on payment. Four to six touches over roughly 60 days is plenty: past that you're adding annoyance, not cash.

Why does polite beat aggressive?

Because these aren't strangers who stiffed you: they're active customers you plan to service again next round. The goal is payment and renewal. An aggressive first touch might collect one $85 invoice while quietly canceling a $600-a-year program; that's a terrible trade. The polite version converts the most common cause of late payment (a paper invoice lost on a kitchen counter) into a ten-second phone tap. Most customers experience a friendly text with a pay link as a convenience, not a collections action. Save the firm tone for the accounts that have ignored three friendly ones; by then it's earned, and it still arrives with a payment option instead of just a threat.

What suppression rules keep this from backfiring?

One rule above all: no upsell marketing to past-due accounts. The moment an account enters the AR sequence, it should be suppressed from every other campaign: aeration offers, referral asks, review requests, and especially pre-pay invitations (asking someone to prepay next season while you're dunning them for this one reads as either tone-deaf or desperate). Collections messages are exempt from marketing frequency caps but capped on their own schedule. And because everything reads from one synced dataset, a payment lifts the suppression everywhere at once: the customer who pays on Tuesday can get the spring upsell on Wednesday. The full guardrail framework is in our ten-automations guide.

What's the permanent fix?

Autopay. Reminders accelerate this season's cash; autopay enrollment deletes the problem from future seasons, which is why every single touch in the sequence should offer it: "never think about this again" is a genuinely attractive pitch to the exact person who keeps forgetting to pay. The math is structural: if 1,200 of your customers are invoice-billed and even 15% enroll over a season, that's 180 accounts that will never appear on an aging report again. Autopay does add one new chore, recovering declined cards, which is worth automating from day one. Each reminder cycle you run without an autopay offer is a wasted at-bat with the very customers most likely to want it. The enrollment playbook itself is in our autopay adoption guide.

What is this worth in cash?

An illustrative example, plug in your own numbers. Say you're running a $120,000-a-month book and, at season peak, $80,000 is sitting in 30-plus-day AR. If automated reminders accelerate a quarter of it, that's $20,000 pulled forward: cash in April instead of June, when you're covering payroll and materials for the busiest stretch of the year. Add the quieter wins: fewer write-offs (if automation saves even 1% of the book from going uncollectable, that's another $1,200 a month), and the office hours returned: dozens of awkward calls a month replaced by a queue of the handful that truly need a human. No new customers, no ad spend; just faster collection of money you already earned.

When should you NOT automate a past-due account?

Three cases belong with a human, not a sequence. Billing disputes: if a customer says the application never happened or the price is wrong, automation just repeats the demand louder: pull the account out and have someone call. Known hardship: a longtime customer going through a job loss or illness deserves a conversation and a payment plan, not escalating texts; keep a manual exclusion list the office can add to in seconds. Commercial accounts on net terms: a net-30 invoice at 30 days isn't late, and an HOA's AP department doesn't respond to friendly texts: run commercial AR on its own calendar keyed to the contract. The automation should make these exceptions easy: one tag in the system routes an account to a human and silences the robots.

Frequently asked questions

Will automated payment reminders make customers cancel?

Rarely, if the tone is graded to the age of the balance. Most late payers are disorganized, not unwilling: a friendly text with a one-tap pay link reads as convenience, not collections. The cancellations to worry about come from the aggressive version: a cold demand letter as the first touch, or an upsell pitch landing while the customer is being dunned.

How does the sequence know when someone has paid?

Two ways. Payments made through the reminder's pay link stop the sequence instantly, because the automation platform sees them directly. Payments recorded in RealGreen at the office (a mailed check, a card over the phone) stop it at the next nightly sync. In practice that means a reminder almost never crosses a payment by more than a day.

Should I add late fees to the automation?

That's a policy decision, not an automation decision. The sequence enforces whatever your terms already say: if you charge late fees, mention them at 60 days; if you don't, don't invent them in a text message. Many residential lawn companies find the service-hold consequence works better than fees, because the customer wants the next round done.

What about commercial accounts on net-30 terms?

Exclude them from the residential sequence entirely. A commercial invoice at 30 days isn't late: it's on time under net terms, and their AP department doesn't respond to friendly texts anyway. Run commercial AR on its own calendar keyed to the agreed terms, and route anything genuinely overdue to a human who knows the account.

How many touches is too many?

A reasonable residential sequence is four to six touches spread across roughly 60 days: one or two per aging bucket. More than that adds annoyance faster than it adds cash. The bigger win isn't more messages; it's the autopay offer inside each one, which removes the account from next season's aging report entirely.

The takeaway: the money in your aging report was already earned: collecting it faster is the cheapest revenue you'll ever generate. A tone-graded sequence with a pay link in every message, suppression rules that pause the selling, and an autopay offer at every turn gets you paid and keeps the customer. Both, not either.

Start this month

1. Pull your RealGreen aging report and total the 30/60/90 buckets: that's the size of the prize.
2. Write the four reminder messages (30/45/60/90) and grade the tone honestly; read each one as if it were arriving on your own phone.
3. Get invoice and aging data syncing nightly so buckets update without office work.
4. Turn on the suppression rule first: no upsell or pre-pay marketing to any past-due account.
5. Add the autopay offer to every touch: including the paper ones.
6. Create the human-routing tag for disputes, hardship, and commercial accounts before the first message sends.