Skip to content

Bookkeeping · Daily Workflows · Brief · Intro level

Recurring transactions: what to automate and what never to

Rent, subscriptions, and loan payments belong on autopilot; revenue and variable costs never do. How to set up recurring templates safely, and the quarterly audit that keeps them honest.

By The Carryforward Desk3 min read · June 25, 2026

Automation in bookkeeping has one safe use: transactions that are identical every time. Rent, insurance premiums, software subscriptions, loan payments — same vendor, same amount, same account, every month — belong on recurring templates or auto-confirming bank rules. Everything that varies, and all revenue, stays manual. The dividing line is not convenience; it is whether a machine repeating last month's decision can ever be wrong. When it can, it eventually will be — monthly, silently, with confidence.

The dividing line

The test for each candidate: could next month's transaction differ from this month's in any way that matters?

Automate freelyNever automate
Rent (fixed lease amount)Any deposit or customer payment
Insurance premiumsSales and revenue entries
Software subscriptionsVariable vendors (Amazon, contractors, fuel)
Loan and lease paymentsPayroll-adjacent items that vary with hours
Bank and merchant fees (rule-suggested)Anything split between business and personal
Depreciation and other fixed monthly journalsTransfers whose amounts vary

The right-hand column shares one trait: each instance requires a decision. A deposit might be a payment to apply against an invoice, a transfer, a vendor refund, or an owner contribution — and a rule that stamps everything "Sales" will double-count revenue while your aging report insists paid customers are delinquent. That is why the categorization system bans income rules outright: match first, categorize by hand, every week.

Setting up the safe ones

  1. List every fixed monthly and annual obligation from the last three months of statements — most businesses find eight to fifteen.
  2. Create a recurring template for each: vendor, account, amount, schedule, and a memo stating what it is ("Suite 240 rent per lease dated 2025-03-01").
  3. Set templates for bills to post the bill, not the payment — the payment still gets matched from the bank feed, keeping the AP workflow's two-event structure intact.
  4. For card-charged subscriptions, use bank rules on the card feed set to auto-confirm only where the amount is genuinely fixed; set everything else to suggest.
  5. Include fixed month-end journals — depreciation is the classic, per your schedule from the depreciation primer — so the close starts pre-posted.

The quarterly audit

Once a quarter, open the full list of recurring templates and rules and interrogate it:

  1. Does each template match a live obligation? Kill anything tied to an ended lease, a cancelled subscription, or a paid-off loan.
  2. Does the amount still match reality? Compare each against the latest statement; update price changes with a dated memo.
  3. Can you explain every rule? A rule you cannot explain gets deleted — it is doing something, and you do not know what.
  4. Should anything new join the list? A vendor you have hand-coded identically for three straight months is a candidate.

Done this way, automation buys you what it should: the fixed half of your books posts itself, and your weekly attention concentrates where judgment actually lives — the deposits, the variable spending, and the uncategorized queue on its way to zero.

Frequently asked questions

Which bookkeeping transactions are safe to automate?
Fixed, identical-every-time items: rent, insurance, software subscriptions, loan payments, and bank fees. The test is that amount, account, and vendor never vary. Automate them as recurring templates or auto-confirmed bank rules, and month-end review becomes a scan instead of data entry.
Why shouldn't I automate recording revenue?
Because every deposit needs a human decision: is it a payment against an invoice, a transfer, a refund, an owner contribution, or new income? An automation cannot tell, and each wrong guess double-counts revenue or strands an open invoice. Deposits get matched, one at a time, every week.
How often should I review my recurring transactions and bank rules?
Quarterly. List every recurring template and auto-rule, confirm each still matches a live obligation at the current amount, and delete anything you cannot explain. Zombie recurrences — posting rent for a lease that ended, or a subscription price that changed — corrupt books with perfect regularity until someone looks.

Keep reading