Utilities, telecoms providers, insurance companies, and subscription businesses share a billing profile that sets them apart from most other companies: they send very high volumes of invoices, to predominantly private or small-business customers, on a fixed cycle, with a high degree of repetition in the invoice structure. The invoice for a household electricity customer looks almost identical month to month — name, address, period, consumption, tariff, total, payment details.
This billing profile is exactly where eBill delivers the most value. The combination of high volume, consumer audience, and predictable invoice structure makes utilities and subscription billers natural candidates for full eBill automation.
Why high-volume recurring billing fits eBill well
eBill's core advantage is reaching Swiss consumers through their existing e-banking interface. Around 3 million Swiss bank customers are registered eBill payers, covering most of the major retail banks — PostFinance, UBS, Raiffeisen, ZKB, and the cantonal banks. A utility or telecom with a million residential customers can reach a substantial share of them through eBill without asking those customers to install any new software or create any new account.
For recurring billing specifically, eBill also offers a feature that standard invoice delivery does not: standing approval (Dauerfreigabe). A registered payer can instruct their bank to automatically approve and pay all invoices from a specific biller up to a defined amount limit, without individually reviewing each invoice. For a household that receives a monthly electricity invoice of reliably similar amounts, this turns eBill into something close to a direct debit — the invoice arrives, the bank checks it is within the standing approval limit, and it is paid without any action required from the customer.
This dramatically changes the payer experience. Instead of logging into e-banking every month to approve an invoice — which is what drives eBill abandonment among customers who find it too many steps — the process becomes invisible. The bill arrives, it is paid, the customer sees it in their statement. The biller gets paid reliably and on time.
Technical considerations for high-volume senders
Sending a million invoices per month through eBill is a different technical proposition from sending a hundred. A few things matter at scale:
Batch transmission. eBill service providers support batch file transmission for high-volume senders, typically via SFTP or a high-throughput API. The invoice data is prepared and uploaded as a batch file — often a structured XML file containing multiple invoice records — rather than sending individual API calls per invoice. This is far more efficient and avoids rate-limiting issues at send time.
The batch file format varies by service provider, but most follow the SIX eBill sender specification. Your billing system needs to generate the output in the correct format, with the correct payer identifiers (eBill participant IDs or registered IBANs) for each invoice.
Payer registration lookup. Before including a customer in the eBill batch, you need to know whether they are a registered eBill payer. Service providers expose a registration lookup API. For high-volume senders, this lookup is typically done as a batch check run against the customer master database periodically — weekly or monthly — rather than per-invoice at send time. The result is stored against each customer record: eBill-registered, not registered, registration unknown.
Customers who are not registered fall back to your alternative channel — printed invoice, email PDF, or online portal. Your billing system needs to handle this routing automatically.
Status feedback processing. Every invoice sent via eBill generates status events: delivered to the payer's bank, viewed by the payer, approved, rejected, or expired (not acted on within the acceptance period). At high volume, these status events arrive as batch response files on the same SFTP location where you sent the invoices.
Processing status feedback at scale requires a systematic approach: match each response to the original invoice, update invoice status in your billing system, trigger follow-up actions for rejections and expirations (a reminder notification, a fallback delivery to a paper or email channel), and track approval rates as an operational KPI.
Expiry handling. eBill invoices that are not approved within the acceptance period (typically 30–60 days depending on configuration) expire automatically. An expired invoice is not paid — the customer has to contact you to get a replacement. For utilities that have hundreds of thousands of invoices in flight at any time, tracking expiry and following up is not optional. Build expiry handling into your status processing from the start.
Payment terms and amounts
For recurring subscription billing, invoice amounts tend to be stable. For utilities, they fluctuate with consumption — an electricity invoice in winter is higher than in summer, a water invoice varies with household usage. The standing approval feature covers this variability through the configurable amount limit the customer sets.
A customer who sets a CHF 200 standing approval limit will have all invoices up to CHF 200 approved automatically. An invoice above that limit — perhaps after a particularly cold winter — appears as a normal invoice requiring manual approval. Your billing system should generate a notification to the customer when an invoice exceeds their standing approval limit, so they are not surprised to see a pending item in their e-banking.
For split billing — a customer who pays part of a utility bill through a subsidy programme and part directly — the eBill invoice covers the customer's portion only. Coordination with the subsidy scheme is a separate process.
Customer onboarding at scale
The main operational challenge for a large utility or telecom adopting eBill is not the technical integration — it is getting a meaningful share of customers to register. Without a critical mass of registered payers, the efficiency gains are limited.
Proven approaches at scale:
Migration campaigns with an incentive. Offer a one-time discount or prize draw entry for customers who register for eBill by a given date. Utilities have successfully moved 15–25% of their customer base in a single campaign. The ongoing growth rate after a campaign is slower, so a strong initial push matters.
Paper invoice surcharge. Some billers charge a small fee (CHF 1–2 per invoice) for paper delivery and offer eBill as the free alternative. This is a common tactic in telecoms and is effective at shifting customers who are indifferent about the format but price-sensitive.
Online account integration. If your company has a customer portal or app, integrate the eBill registration prompt directly into the account settings flow. Customers who are already logging in to see their usage data are halfway to eBill adoption — they just need the prompt and a clear path to register with their bank.
Bill inserts and QR codes on paper invoices. For customers still receiving paper, include a clear instruction on each invoice: "Register for eBill to receive this invoice digitally in your e-banking — scan this QR code to find out how." Include a QR code linking to a short registration guide specific to the major banks. Make the process obvious.
Reconciliation at scale
The reconciliation side of recurring billing via eBill is simpler than for ad hoc invoicing. When a standing approval is in place, payment arrives reliably and predictably. Your camt.054 processing handles the matching — the payment reference from the eBill invoice comes back in the remittance field, and the invoice is closed automatically.
The main reconciliation complication at high volume is the gap between invoice generation date and payment date. Invoices generated in November may be paid across different value dates in November and December depending on when customers (or standing approvals) trigger payment. Make sure your AR matching logic handles the timing correctly and does not flag late payments that are simply invoices approved at the customer's discretion within the normal acceptance window.
For subscription businesses that need to match payment precisely to a billing period — critical for accurate MRR reporting — using a unique invoice reference per period per customer (rather than a generic subscription identifier) is the cleanest approach. Each eBill invoice carries a distinct reference, each camt.054 credit brings that reference back, and each billing period closes cleanly.