Golden Horizons
CAPABILITY · OPS & BACK-OFFICE
Accounts Receivable Automation
Overdue invoices get chased on a tone-appropriate cadence without owner involvement.
Audit this workflow →What it does
Monitors your accounting system for overdue invoices. Sends escalating reminder messages by email and SMS in your brand voice. Stops automatically on payment. Logs every touchpoint and reports DSO trend to the owner weekly.
Most small businesses don't have a collections problem. They have an awkwardness problem. The invoice goes out, 30 days pass, nothing comes back, and nobody makes the call. The owner doesn't want to bruise the relationship, and the front desk never signed up to play bad guy. So the money sits, the invoice ages, and by the time someone finally follows up, usually at 60 or 90 days when the cash squeeze gets loud, the conversation is harder than it would have been at day four.
Receivables that nobody actively manages turn into a slow bleed. A contractor carrying $40,000 in unpaid draws across three jobs isn't broke. He's waiting. A property manager running twelve net-30 tenants at a 40% on-time rate isn't undercapitalized. She's unorganized. The money exists. The follow-up doesn't.
The Invoice Chaser runs a four-stage reminder cadence tied to your actual due dates: a friendly confirmation at three days past due, a firmer nudge at seven, a direct statement of concern at fourteen, and a formal past-due notice at thirty. Every message goes out in your brand voice, never a generic collections template. Tone escalates gradually rather than jumping to demand, because the goal is payment from a client who stays a client, not a check from someone who never comes back. The system sends by email first, flips to SMS if email goes unanswered, and stops the moment a payment posts in your accounting system. No chasing a client who already paid.
Every outbound message logs with timestamp, channel, and delivery status. The owner gets a weekly DSO snapshot showing which invoices moved, which are aging, and which have gone quiet long enough to warrant a direct conversation. That escalation flag is where the system hands off. Disputed invoices, clients asking for payment plans, and accounts that have gone silent for forty-five days get surfaced to the owner with full contact history attached, so the human conversation starts with context instead of confusion.
Golden Horizons wires this directly into QuickBooks, Xero, or Wave. No manual exports, no spreadsheet tracking, nobody remembering to check the AR aging report on Fridays. The accounting system stays the source of truth, and the chaser runs off it automatically.
Use cases
- A commercial laundry company on net-45 hotel contracts carried heavy outstanding AR because the owner handled follow-up personally, which meant inconsistently. After connecting to QuickBooks, the 7-day and 14-day reminders moved two of three hotel clients to consistent on-time payment.
- A two-partner CPA firm on a net-60 client base had always treated follow-up as the admin's job, but the admin had no script and no authority. Invoice Chaser gave the firm a documented cadence, gentle at 7 days past due, direct at 21, formal at 45, and the admin's only job became reviewing.
- A residential GC running three active builds was chasing retainage and draw payments on different timelines per job. Invoice Chaser tracked each draw separately, sent reminders tied to contract milestones rather than calendar dates, and flagged the client who went quiet at 30 days.
- A dental practice collecting patient balances after insurance adjudication kept losing money on small co-pays because staff felt awkward calling about $80. Invoice Chaser handled the first two touchpoints, surfacing only accounts over $300 still unpaid at 30 days for a staff call.
- A property management company with 22 residential units tracked rent arrears by hand in a spreadsheet. After connecting to their Wave account, Invoice Chaser ran the 3-day, 7-day, and 14-day cadence automatically and cut the owner's monthly follow-up work from roughly four hours to under one.
What’s included
- Fixed scope with written acceptance criteria before any build starts
- Customization layer for your brand voice and business rules
- Clean handover with documented runbook and live training
- Monthly ROI report for three months post-delivery
- Source code delivered to your GitHub on handover
What’s NOT included
- Third-party API subscription costs (billed to your accounts)
- Data migration from legacy systems
- Ongoing infrastructure costs after handover
How clients use this
Fixed-scope build with clean handover, documented ownership, and optional support for monitoring, maintenance, and minor changes.
Part of
Used in: Law Firms , Real Estate Agents , Construction Firms
Questions Invoice Chaser clients ask
Can we control how firm the tone gets? We don't want to alienate long-term clients.
Yes. Tone calibration is part of the build, not an afterthought. Before we go live, we draft all four cadence messages with you and get your sign-off on each one. The 3-day message stays deliberately light, a friendly heads-up and nothing more. Tone sharpens at 7 and 14 days, and the 30-day message reads formal but never hostile. You can also configure exceptions: a VIP client list that gets a softer track, or accounts where the 30-day escalation skips the automated message entirely and just flags the owner for a personal call. The system chases the invoice, but you decide how hard.
What happens when a client responds saying the invoice is disputed or they want a payment plan?
Any reply by email or SMS pauses the automated cadence on that invoice and creates an escalation flag in the weekly owner report. We don't try to resolve disputes or negotiate payment plans programmatically, because that's a human conversation. What the system does is hand the owner a complete contact log when the conversation happens: which messages went out, when, on what channel, and what the client responded. The owner walks in with full context instead of reconstructing it from memory. If the client agrees to a payment plan, the owner logs the arrangement and sets a manual follow-up date, and the chaser can optionally resume on the remaining balance once a partial payment posts.
Which accounting systems does Invoice Chaser connect to, and how does it know when payment posts?
We connect to QuickBooks Online, Xero, and Wave through their official APIs. No CSV imports, no manual syncing. The integration listens for payment events in real time, so when a payment posts and the invoice closes out as paid, the chaser stops immediately on that invoice. There's no lag and no risk of reminding someone who already paid. The weekly DSO report pulls from the same accounting data, so the numbers the owner sees match the books. Running a different system? We scope that during the audit call. Most cloud-based accounting platforms with an API can be connected, though build time may extend slightly depending on integration complexity.
Are there any legal considerations for automated payment reminders, especially for B2C clients?
For B2B collections, meaning business clients, commercial accounts, and professional services, standard reminder cadences are generally straightforward. B2C is different. When you're collecting from individual consumers, the FDCPA (Fair Debt Collection Practices Act) sets rules around communication frequency, timing, and required disclosures, though the Act primarily applies to third-party debt collectors rather than original creditors collecting their own debts. Several states layer on their own consumer protection rules that can reach original creditors too. We flag this during scoping: if your client base is mostly individual consumers and balances run significant, we'll recommend your attorney review the message templates before go-live. The build can carry required disclosures as static footers on the appropriate messages. We're engineers, not lawyers, so the compliance sign-off stays with your counsel.
How long does it take to see AR days actually improve after the build ships?
The cadence starts running on the first invoice that hits its due date after go-live, so the system works from day one. Whether that moves your DSO depends on your baseline. Businesses with no existing follow-up at all, where invoices get sent and then passively waited on, tend to see a material shift in the first billing cycle, simply because clients who would have waited to be asked are now being asked on a schedule. Businesses that already ran informal follow-up tend to see the gain show up in the 30-to-60-day bucket, where the consistent cadence replaces the inconsistent human one. We pull a baseline DSO snapshot before go-live and track against it monthly after launch. That's how we know the system is working, not just running.