Accounts receivable is ripe for automation: recurring invoices, payment reminders, online payments, and fee categorization. Done well, your team spends time on exceptions and relationships—not copy-paste. Done poorly, you send wrong invoices at scale and spend the next quarter apologizing.

Meridian’s design principle is simple: automate the mechanical, require humans for the consequential.

What you should automate

Recurring billing

Retainers, subscriptions, and maintenance contracts are perfect candidates. Set the cadence, amount, payment terms, and tax treatment once. Meridian generates drafts or auto-sends based on your preference. Many teams auto-send only after the first successful cycle.

Reminders

Polite, predictable reminders outperform heroic collection emails. Configure sequences: 3 days before due, on due date, 7 days late, 21 days late. Escalate tone carefully; escalate ownership clearly.

Payment application

When a customer pays online, the payment should post to the correct invoice automatically. Partial payments should leave a clear remaining balance—not a mystery deposit.

Dunning for cards

Failed card charges on subscriptions need retries and customer notification. Coordinate with your payment processor’s smart retries, then reflect status in AR so the ledger matches reality.

What should stay human

  • First invoice to a new customer. Confirm billing contact, PO, and tax status.
  • Credits and write-offs. These affect revenue integrity; require approval.
  • Disputed invoices. Pause reminders; assign an owner.
  • Revenue recognition judgments. Schedules can automate the math after humans define the arrangement.
  • One-off project invoices with complex milestones. Templates help; blind autosend does not.
If you would not sign the invoice yourself, do not let a schedule send it unsupervised.

A practical automation ladder

  1. Level 0: Manual invoices, manual reminders. Fine for very low volume.
  2. Level 1: Templates + saved payment terms. Still manual send.
  3. Level 2: Recurring drafts; human reviews and sends.
  4. Level 3: Recurring auto-send for trusted contracts; reminders on.
  5. Level 4: Online payments + auto-application + aging alerts to Slack.
  6. Level 5: CRM/billing sync for usage or seats—with reconciling reports each week.

Most Meridian Growth customers thrive at Levels 3–4. Jumping to Level 5 without reconciling reports is how books drift from the product database.

Controls that keep automation safe

  • Approval thresholds: invoices over a set amount need a second set of eyes.
  • Customer hold flags: stop autosend when a dispute or credit risk flag is on.
  • Audit trail: who changed the recurring schedule, when, and from what.
  • Period awareness: do not let backdated autosends quietly rewrite a locked month.
  • Tax and currency checks: validate before the first send of a new template.

Metrics worth watching

Automation is working if these improve without a spike in credit notes:

  • Days sales outstanding (DSO)
  • % of invoices paid online
  • Reminder-to-payment conversion
  • Credit note rate (should stay flat or fall)
  • Unapplied cash balance (should stay near zero)

How Meridian implements the line

Recurring invoices can draft or send. Reminders are configurable. Payments from Stripe and partners auto-apply when references match—and land in review when they do not. Credits, write-offs, and schedule edits are permissioned. Everything is logged.

We will keep building automation. We will not build a button that “just invoices everyone somehow.” Clarity beats cleverness in the ledger.

Explore invoicing features → · See AR automation in a demo →