Accounts Receivable | Recurring Invoices

Recurring billing that survives a price change mid-cycle.

Schedule recurring invoices monthly, quarterly or annually. Each cycle raises a fresh invoice with the sales tax treatment applied as at the network and by email where they are not. A price change, a pause or an upgrade landing mid-period is prorated rather than argued about. Payment follow-ups fire automatically if it goes unpaid past the due date.

Start free trial Book a demo

What the system does

Capability, input, output.

Capability	Input	Output
Recurring schedule	Customer + frequency + duration + price	Cycle plan with auto-trigger
Fresh invoice per cycle	Recurring invoice + GSP	A new tax invoice each cycle, not a copy of the last one
Multi-channel delivery	Customer contact preferences	Delivered over the network or by email, with the receipt tracked
Escalation pricing	Annual escalation %	Auto-revised price on the schedule
Pause / resume	Customer hold flag	Cycle paused without losing the schedule
Follow-up integration	Unpaid invoice past due date	Tone-aware reminder cadence

Recurring schedule

Input

Customer + frequency + duration + price

Output

Cycle plan with auto-trigger
Fresh invoice per cycle

Input

Recurring invoice + GSP

Output

A new tax invoice each cycle, not a copy of the last one
Multi-channel delivery

Input

Customer contact preferences

Output

Delivered over the network or by email, with the receipt tracked
Escalation pricing

Input

Annual escalation %

Output

Auto-revised price on the schedule
Pause / resume

Input

Customer hold flag

Output

Cycle paused without losing the schedule
Follow-up integration

Input

Unpaid invoice past due date

Output

Tone-aware reminder cadence

Compliance + integrations

Recurring billing, GST-correct every cycle.

Each cycle raises a genuinely new invoice, with the rating, the currency and the customer's belonging status re-applied from the master rather than inherited from the last one. It sounds pedantic until a customer restructures mid-year and every subsequent invoice quietly carries the old treatment.

Regulations we work within

Rule 48(4) (e-Invoice)

A fresh tax invoice raised each cycle, rated from the current customer record.
Section 31 + Rule 46

Mandatory invoice fields validated each cycle.
Section 13(3), CGST Act

Time of supply for continuous supplies handled per the rule.

Connects to

Email delivery Delivery per cycle
Email Templated invoice delivery
Email gateway Per-customer delivery preference

Recurring Invoices FAQ

What buyers ask.

What about annual price escalation?

Configurable per contract. Set the escalation % (or absolute amount), the trigger (anniversary date, FY start), and the cap. The system applies the new price from the next cycle and notifies the customer in the invoice itself.

A customer wants to pause for 2 cycles. How?

Pause flag at the customer or contract level with a resume date. The pause is captured in the audit trail. Cycles during the pause window are skipped; the schedule resumes on the configured date without losing the cadence.

Different recurring schedule per customer?

Yes. Each customer or contract has its own schedule, pricing, currency and delivery preference. Bulk-edit available for global changes; individual override for VIPs.

How does this play with subscription accounting under ASC 606?

Recurring invoices feed the deferred and accrued revenue accounting under ASC 606. Performance obligations are tracked at the line, revenue is recognised across the service period rather than at the invoice, and the deferred balance updates each cycle. The invoice date and the revenue date are different things, and keeping them separate is what stops an annual prepayment landing as one month's revenue.

Related features

Schedule one recurring invoice. Watch it run.

Connect one customer, set a monthly cycle, free. The first invoice raises on the cycle date, goes out on whichever path that customer is on, and the follow-up fires if it goes unpaid.