When is fiscalization needed for recurring payments?
One thing I often see in subscription businesses is confusion between payment processing, tax calculation, invoicing, and fiscalization.
For recurring payments, fiscalization is not usually about whether you charge with Stripe, Adyen, PayPal, cards, SEPA, or another payment method. It is more about where your company is established, where the customer is located, whether the sale is B2C or B2B, and whether the destination country requires transaction reporting, certified receipts, e-invoicing, or real-time fiscal registration.
In many cases, if you only have a small number of customers in another country and you are below the local registration or reporting limits, you may not need to create a separate local setup. A storefront for that country without fiscalization can be enough, especially when sales are still small.
But when sales grow, or when the destination country requires local fiscalization, the architecture should not become a migration project. Ideally, you should be able to keep the storefront, pricing, tax logic, subscription rules, and payment provider setup, then add the required fiscalization provider to that storefront.
This is one of the things we are building into Azotte : storefront-based subscription operations where fiscalization can be added only where it is actually needed, instead of forcing every country to have the same heavy setup from day one.
My view is simple: do not over-engineer fiscalization too early, but also do not design billing in a way that makes it painful to add later.
Posted Jun 3, 2026, 1:24 PM UTC