Recurring Invoices in Invoice Master: Scheduled Drafts, Not Autopilot

“Automated recurring invoicing” can mean at least three different things: generate a draft, send a finished invoice, or charge a saved payment method. Invoice Master implements the first. On the scheduled date, it creates a new invoice draft and advances the schedule. You review and deliver that document yourself.

That is less autonomous than subscription billing, and often safer for retainers or repeat services whose quantities, contacts, or tax context can change.

Product check, July 12, 2026: The current scheduler does not automatically email the customer, create a Stripe payment link, attach files, or charge a payment method.

What a recurring configuration stores

A recurring invoice record contains:

• sender and recipient details;
• recurring line items;
• invoice footnotes;
• a recurrence interval using days, weeks, months, or years plus an integer step;
• the next issue date; and
• payment terms, either due on receipt or a net number of days.

When the date arrives, Invoice Master uses that configuration to create a draft invoice and calculates its due date from the stored payment terms. It then advances the next issue date and notifies the owner about the generated draft.

Seeded demo recurring configurations. Dates and amounts are examples, not customer schedules.

You create and edit the recurring configuration separately. A generated record is a saved application draft, unlike browser-local draft recovery. There is no current “turn this invoice into a recurring template” command, end-date field, pause switch, or automatic attachment carryover. Delete or edit the configuration when the commercial arrangement changes.

Choose recurring work that is genuinely repeatable

Good candidates have a stable customer, cadence, description, and price: a monthly retainer, maintenance fee, membership invoice, or regular service allowance. Usage-based work, changing expenses, milestone billing, and variable taxes need more review.

Write the line item so it remains meaningful when copied into a future draft. Include the period or service name, but avoid hard-coding a calendar month that will become stale. The generated draft can be edited before sending.

Review every generated draft

Use a short review sequence:

1. Confirm the customer is still active and the billing entity has not changed.
2. Check the service period, quantity, rate, tax, and currency.
3. Confirm the issue and due dates.
4. Update purchase-order or project references.
5. Add any one-off adjustment supported by the invoice form.
6. Preview the customer-facing PDF or public view.
7. Create a Premium Stripe link if appropriate.
8. Deliver the invoice through the chosen route.

The schedule saves re-entry. It does not replace acceptance, tax review, or delivery.

How Basic limits affect generation

The backend applies the normal monthly invoice-creation entitlement to scheduled drafts. Basic allows five invoices per month. If a Basic organization has reached that limit when a recurring schedule runs, the invoice is skipped, the next issue date advances, and an owner notification is queued.

This is why “five recurring invoices per month” is an inaccurate description. The limit is on invoices created during the month, whether created manually or by a recurring schedule. Premium bypasses that invoice-count limit.

Review skipped-generation notices promptly. Because the next date advances, waiting until the following cycle can leave a genuine billing period unissued.

Pair recurring drafts with Premium collection tools

After review, a Premium user can send the invoice by email and create a Stripe-hosted payment link. Premium dunning can schedule owner or customer email stages after the due date; the late-payment reminder sequence shows where automation should yield to a person. Those are separate actions:

• recurring scheduling creates the draft;
• document delivery sends or shares it;
• a Stripe link offers hosted checkout; and
• dunning follows an eligible unpaid invoice after its due date.

Keeping those transitions separate makes mistakes easier to catch. It also means Invoice Master is not a card-on-file subscription engine.

Monthly controls

• Compare expected recurring drafts with drafts actually created.
• Investigate skipped-generation notifications.
• Review old configurations whose customer or price changed.
• Confirm generated drafts were delivered, not merely created.
• Check that payment links belong to the current invoice.
• Reconcile paid status to payment history.

Recurring schedules reduce repetitive typing. The human review is not a failure of automation; it is the control that keeps a repeated mistake from becoming a monthly one.