QuickBooks Recurring Transaction

The three types behave nothing alike

Choosing a type is the whole configuration. Everything else is scheduling detail, and picking the wrong one is the difference between a bill that goes out on its own and one that sits in a list waiting for you.

Scheduled is the automatic one. Intuit describes it as: "transactions other than invoices can be sent automatically without any changes. Examples include rent payments, loan payments, and depreciation." Notice which examples Intuit reaches for. All three are entries whose amount is known in advance and does not vary, which is exactly the case where nobody needs to look at it before it posts. Notice also the carve-out in Intuit’s own wording, "other than invoices", which is why a scheduled invoice has a separate option for whether QuickBooks emails it. When you create a template you can "choose whether to include unbilled charges, automatically send emails, or mark the transaction to print later".

Reminder is the supervised one. Intuit: templates "are created at regular times, but you need to edit and send them yourself. An example is a utility bill that changes each month." Reach for this when the shape of the transaction repeats but the number does not. The electricity bill arrives every month and is never the same twice, so automating it would just guarantee a wrong figure.

Unscheduled is not really recurrence at all. Intuit: "transactions need to be created and sent each time. Use this to copy a transaction when needed on a case-by-case basis." No dates, no cadence, no reminders. It is a stored starting point you reach for when the situation comes up again, which for irregular work is the honest answer.

One practical consequence follows. A template that never seems to fire is usually a Reminder or an Unscheduled one, doing precisely what it was told.

A template is not a transaction

This is the single most common misunderstanding about recurring transactions, and it produces two opposite complaints from two different people in the same office.

The first is someone who set up a recurring invoice and cannot find the revenue. Nothing is wrong. The template exists, the invoice has not been created yet, and there is nothing to report on because no transaction exists. A template holds no amount that your books recognise.

The second is someone surprised by a transaction they do not remember entering. Also nothing wrong. A Scheduled template fired overnight, as designed. Intuit is specific about when: "Recurring transactions are created on the day scheduled typically between 12:00 am and 5:00 am depending on your time zone." So the entry that appeared before anyone arrived was made by the template, on time.

There is a third case that catches people at period ends, and it comes from a setting rather than a misunderstanding. Templates can be told to run early. Intuit: "You can create transactions (from scheduled recurring templates) for a specified number of days before the actual transaction date," and gives the worked example of entering 10 in "Days in advance to create" for transactions scheduled on the 15th, so "QuickBooks Online will create transactions on the 5th". A template configured that way puts a dated transaction into your file well before its own date, which is useful for approvals and awkward if you are closing a month and did not know it was set.

So when a recurring transaction surprises you, there are only three questions worth asking. Which type is the template, what is its schedule, and how many days in advance is it set to create.

Two systems that both think they own recurrence

Here is the situation that makes this term worth understanding rather than merely defining.

QuickBooks can bill the same customer the same amount every month. So can Stripe, through subscriptions. If you run Stripe for billing and sync the results into QuickBooks, you now have two systems each capable of producing a monthly invoice for the same customer, and neither one knows about the other.

The failure mode is not subtle. A QuickBooks recurring invoice template fires on the first. The synced Stripe invoice for the same customer and the same period arrives separately. Your accounts receivable now shows two invoices for one month of service, your revenue is double counted, and if the QuickBooks template has automatic sending turned on, the customer has been asked to pay twice.

What makes it hard to spot is that both records look correct in isolation. The QuickBooks one was generated by a template somebody set up deliberately. The Stripe one reflects a real invoice a real customer really received. Nothing is malformed. There are simply two of them.

The rule that falls out of this is short. Pick the system that owns recurrence and turn the other one off. If Stripe raises your customer invoices, QuickBooks recurring templates for those customers are the thing to switch off, and QuickBooks goes back to being where the results are recorded rather than a second billing engine running in parallel.

This does not mean abandoning recurring transactions. It means scoping them to entries Stripe never produces. Rent, loan payments, depreciation, recurring journal entries, internal accruals: none of those have a Stripe counterpart, and they are the cases Intuit names for the Scheduled type anyway. The collision is specific to customer-facing invoices, and so is the fix.

The numbering collision underneath it

Duplicated invoices are the visible half of the problem. There is a quieter half sitting under it, and it explains a category of sync error that otherwise looks arbitrary.

QuickBooks holds its own document numbering and will refuse a second document that reuses a number it already has. A recurring template creating invoices directly in QuickBooks is drawing from that same numbering series. Stripe, meanwhile, guarantees its invoice numbers are unique inside Stripe, which says nothing at all about what QuickBooks already holds.

So a template quietly consuming QuickBooks invoice numbers on a schedule is one of the ways a synced invoice can arrive and find its number taken. Nothing about it is visible from the Stripe side, because from Stripe’s point of view the number was unique.

The general treatment of that mismatch, including how Stripe composes its numbers and which field to reconcile on, is a longer subject than this entry, and it is linked below.

When QuickBooks recurrence is still the right answer

It would be a mistake to read the warning above as an argument against the feature. Recurring transactions are the right tool for a large class of entries, and a Stripe-first business still has plenty of them.

The test is whether anything outside QuickBooks is also producing the transaction. If the answer is no, a template is strictly better than typing, because it is faster and it does not make typing mistakes.

That covers most of what a bookkeeper does on a schedule. Fixed supplier bills and rent, loan and lease payments, depreciation and accrual journal entries, internal transfers on a cadence, and any customer invoice you genuinely raise from QuickBooks rather than from Stripe. Intuit names invoices, estimates and expenses among the transaction types you can build templates for, with one exclusion worth knowing: "You can’t turn an existing estimate into a recurring estimate. Create a new recurring estimate from scratch, as described above."

The type still matters within that set. Fixed and predictable goes to Scheduled. Repeating but variable goes to Reminder, so a human sees the number before it goes anywhere. Irregular goes to Unscheduled, which is a template you invoke rather than a schedule that invokes you.