Your subscription business runs on ReCharge, renewals fire automatically every month, and your customers never think twice about it, until one asks for a VAT-compliant invoice on their third renewal and you realize you’ve never actually generated one. Recurring billing solves the payment problem beautifully. It doesn’t solve the invoicing problem at all.
That gap catches a lot of subscription sellers off guard, especially once they cross into markets where a compliant invoice isn’t optional. Here’s what ReCharge actually handles, what it doesn’t, and how invoicing fits into a subscription order’s lifecycle on Shopify.
What ReCharge Does, and Doesn’t, Handle on Its Own
ReCharge is genuinely good at the thing it was built for. It’s just not built for the thing merchants often assume it covers.
ReCharge manages billing; it doesn’t generate compliant invoices
ReCharge’s core job is charging the customer’s saved payment method on schedule and keeping the subscription itself, frequency, quantity, pause/skip status, in sync. It handles the transaction. What it doesn’t produce is a tax-compliant invoice showing your VAT or GST breakdown, your business registration details, and a sequential invoice number tied to that specific charge.
Where the gap shows up for VAT/GST-registered sellers
If you’re VAT or GST registered and selling to EU, UK, or Australian customers, every charge, including every single renewal, is technically a taxable supply that should have a compliant invoice behind it. Sellers who assume ReCharge’s payment confirmation email counts as that invoice usually discover the gap either when a business customer asks for a proper VAT invoice, or when their own accountant flags it during a VAT return.
What Triggers an Invoice on a Subscription Order?
The mechanics matter here, because “subscription order” isn’t one single event, it’s several different order types that each need to be invoiced correctly.
The first (initial) order vs. recurring renewal charges
The customer’s first subscription purchase creates a standard Shopify order, the same as any one-time purchase. Each subsequent renewal ReCharge processes also creates its own Shopify order, meaning your invoicing needs to trigger separately, and correctly, on that renewal order too, not just once at signup.
Paused, skipped, or failed-payment cycles
A paused or skipped subscription cycle doesn’t generate a charge, so there’s nothing to invoice, but a failed payment is different. If ReCharge retries a failed charge and it eventually succeeds, that successful charge is the one that needs an invoice, not the failed attempt. Getting this sequencing wrong is a common source of either missing invoices or duplicate ones.
Prepaid vs. pay-as-you-go subscription models
Prepaid subscriptions, where a customer pays upfront for three or six months of deliveries, need a single invoice covering that full prepaid amount at the time of purchase, not one invoice per future delivery. Pay-as-you-go models need a fresh invoice on every individual charge. Confusing the two models leads to either invoicing prepaid customers repeatedly for something they’ve already paid for, or under-invoicing pay-as-you-go customers by treating renewals as if they don’t need their own document.
Mid-cycle plan changes and upgrades
A subscriber who upgrades their plan mid-cycle, adds a product to an existing subscription, or changes their delivery frequency typically triggers a prorated charge from ReCharge reflecting that change. This prorated amount is its own distinct transaction and needs its own invoice, separate from the regular scheduled renewal, treating it as part of the next normal renewal, rather than the mid-cycle event it actually was, will show the wrong date and the wrong amount on the resulting record.
Do You Need a New VAT-Compliant Invoice on Every Renewal?
This is the question most subscription sellers actually want answered, and the honest answer is: usually yes, in most VAT/GST jurisdictions.
In most VAT and GST jurisdictions, yes, every recurring charge is a separate taxable supply and needs its own compliant invoice, even if the product and price never change between renewals. The invoice doesn’t need to look different each time, but it does need to exist as its own document with its own invoice number and its own transaction date.
Why yes, in most VAT/GST jurisdictions
Tax authorities generally treat each periodic charge as a distinct supply of goods or services, occurring on the date the charge is processed, not the date the customer originally subscribed. That means the invoice date, the tax rate applied (which can change if VAT rates are updated), and the invoice number all need to reflect that specific renewal, not the original signup.
Keeping the customer’s VAT-exemption or B2B status consistent across renewals
If a customer was validated as a VAT-exempt B2B buyer at signup, that status needs to carry through to every renewal invoice automatically. A common failure mode is a customer’s exemption status being captured correctly on order one, then silently dropped on renewal three because the renewal order wasn’t checked against the same customer record.
Setting Up InvoiceForge for ReCharge Orders
Here’s the part that actually matters operationally: because ReCharge’s recurring charges create standard Shopify orders, not some separate, hidden order type, any invoicing app that reads Shopify’s order data, including InvoiceForge, can generate an invoice from them the same way it would for any other order.
Order data ReCharge passes through to Shopify
When ReCharge processes a renewal, the resulting Shopify order carries the standard order fields, line items, customer, billing and shipping addresses, and the charge amount, the same structure InvoiceForge already reads for one-time orders. There’s no separate ReCharge-specific data format your invoicing setup needs to learn.
What InvoiceForge needs from that order to generate a correct invoice
For InvoiceForge to generate an accurate invoice on a renewal, the order needs correct tax-rate information and, for B2B customers, the same validated VAT/exemption status that applied at signup. Since this data lives on the Shopify order and customer record rather than inside ReCharge itself, keeping customer records accurate in Shopify, not just in ReCharge’s subscriber dashboard, is what keeps renewal invoices correct automatically.
Confirm your specific setup before going live
Every subscription program has its own quirks, trial periods, one-time setup fees bundled with the first charge, mixed prepaid-and-recurring product lines. Before relying on automatic invoicing across a full subscriber base, it’s worth generating and checking a handful of renewal invoices manually against what you’d expect, rather than assuming the first live renewal will be correct without a test pass.
A Quick-Start Checklist for Subscription Sellers
Getting this right from day one avoids a much messier cleanup once you’ve got hundreds of active subscribers.
Testing your first few renewal invoices manually
Before your subscription program scales, walk through at least one full renewal cycle end to end: confirm the renewal order appears correctly in Shopify, confirm InvoiceForge generates an invoice from it with the right tax treatment, and confirm a VAT-exempt test customer’s status carries through correctly. This is a 20-minute check that catches problems before they’ve compounded across dozens of renewals.
What to watch for during a subscriber’s first 90 days
The first three renewal cycles are where most subscription-invoicing problems surface, a rate change, a mid-cycle address update, or a failed-then-retried payment. Spot-checking invoices during this window for a new subscriber cohort is a cheap way to catch a systemic issue before it’s affected months of renewals.
Watching for tax rate changes mid-subscription
VAT and GST rates do occasionally change, and a subscriber who signed up under one rate might renew under a different one months later if a rate change took effect in between. Since each renewal is its own taxable supply, the invoice needs to reflect the rate in effect on the date of that specific charge, not the rate that applied when the customer originally subscribed. This is subtle enough to miss unless you’re specifically checking for it after any rate change affecting your business.
Subscriptions solve the “get paid automatically” problem. They don’t automatically solve the “produce a compliant invoice for every one of those payments” problem, that’s a separate piece of infrastructure that has to be built on top, whether that’s through your invoicing app reading standard order data correctly or through manual intervention on every renewal. Given how quickly renewals compound, the automatic route is the only one that scales past a handful of subscribers.
If you’re running VAT or GST-registered subscription sales through ReCharge and want to see how invoice generation lines up with your renewal cycle, InvoiceForge’s automatic invoice reminder and generation workflow is a useful place to start, the same order-triggered logic that handles reminders on one-time orders applies to recurring ones.