Free assessment

SWISS ELECTRONIC INVOICING

Connecting a Swiss SME to eBill, what the vendors really document

What the eBill connection really demands, program by program, before announcing it to a client.

eBill is the Swiss electronic invoicing channel operated by SIX. A company does not reach it directly; it goes through an approved network partner, whether that partner is its own vendor or a third party. This page establishes who operates what, what sending and receiving each imply separately, what each of the eleven programs we follow documents as of 23 August 2026, and the six points to check before telling an SME that it will send its invoices through eBill.

eBill deposits the invoice in the recipient's e-banking, not in their email inbox

The invoice does not arrive in the recipient's mailbox but in their e-banking portal. According to the vendors' documentation read on 23 August 2026, the recipient must be registered for eBill with a connected bank in order to receive it, and the sender must go through a network partner approved by SIX. That explains the number of contracts and settings to be assembled before the first sending.

The QR-bill follows a different logic. It remains a document, on paper or as a PDF, that the recipient scans or keys in, and it is far more widespread in Swiss tooling. The eleven management programs we follow for the Swiss market all document the QR-bill on sending as of 23 August 2026, whereas only three of them are published by an eBill network partner. An SME switching to eBill therefore keeps the QR-bill for the customers not registered there, and the two channels coexist within the same program.

Sending and receiving are two distinct connections, rarely both at once

Product pages announce eBill without always distinguishing sending from receiving. Sending means depositing your own invoices in the network. Receiving means picking up your suppliers' invoices there in order to process them in creditor accounting. The two functions rest on different contracts and settings, and a vendor's documentation may cover the first without covering the second.

Crésus provides the clearest illustration. Epsitec SA's documentation states that Crésus Invoicing does not allow eBill invoices to be received, whereas sending goes directly from the program, Epsitec SA appearing among the network partners published by SIX. Conversely, Abacus is referenced at SIX for the sending as well as the receiving of electronic documents, and WinBIZ documents both directions, provided an account exists on PostFinance's e-invoicing platform.

The network partner approved by SIX is the only entry point, and it has a name

The eBill network is not open. A company does not plug into it directly; it goes through a network partner, an entity approved by SIX that carries the invoices between the sender's system and the banks. SIX publishes the list of these partners, fifteen entities as of 23 August 2026. Among them figure notably Abacus Research AG, Epsitec SA for Crésus and ePost Service AG for KLARA.

A vendor that itself appears on that list connects its program with no intermediary. The others take a third party's route, and that third party has a name, a contract and a rate card. SelectLine documents an eBill transmission through PostFinance, Infoniqa describes a contract with PostFinance or PayNet coupled with an E-Services licence option, bexio points to a Marketplace application published by iomarket AG, smallinvoice presents eBill sending as a function of its Pingen integration.

This distinction is not theoretical. It decides who you call when an invoice fails to go out, who bills for the service, and what happens on the day the carrier changes its terms. Before settling on a program on the strength of the eBill argument, it is worth asking which route the vendor takes, then checking that name in the list published by SIX rather than in a brochure.

Of eleven programs followed, only three are published by a network partner

As of 23 August 2026, three of the eleven programs we follow for the Swiss market are published by an eBill network partner: Abacus, Crésus and KLARA. Three others document eBill through an external carrier, SelectLine through PostFinance, Infoniqa ONE 200 through a contract with PostFinance or PayNet coupled with the E-Services licence option, WinBIZ through PostFinance's e-invoicing platform. Two go through a third-party integration, bexio through a Marketplace application published by iomarket AG, smallinvoice through its Pingen integration. At Infoniqa, the distinction runs inside the range, the help centre's eBill articles all belonging to ONE 200 and none to ONE 50.

For the last three, the information is missing, or the vendor itself announces that the function is not delivered. Banana Accounting Plus classes automated invoice sending through eBill among the functions not available for the time being. At Odoo, eBill appears in no official source read, the existing building blocks being OCA community modules the vendor does not maintain. Run my Accounts does not figure among the network partners published by SIX and does not document eBill sending on its site.

ROUTE OF ACCESS TO THE eBill NETWORK, SIX EXAMPLESDirect eBill network partner at SIX, sending and receivingROUTE OF ACCESS TO THE eBill NETWORK, SIX EXAMPLESDirecteBill network partner at SIX, sending and receiving

VENDOR DOCUMENTATION AND LIST OF SIX NETWORK PARTNERS, READ ON 23.08.2026

These findings hold for the day of reading and for the public documentation. A vendor may have delivered a function without having written it up, or have written it in a single language, which is nothing anecdotal when a vendor's commercial site exists only in German. The absence of proof is not the proof of absence, and verification is done with the vendor, version by version, before committing to a client.

The cost of eBill reads on three lines, never on a program's price page

The first line is the subscription or licence option that opens the function in the program, like the E-Services option at Infoniqa. The second is the connection itself, Crésus's documentation mentioning registration fees of CHF 20. The third is the price per invoice transmitted, 20 centimes excluding VAT per sending at Crésus as of 23 August 2026. None of these three lines appears on a vendor's general price page.

For vendors that go through a third party, the second and third lines belong to that third party and follow its rate card, not the vendor's. The eBill application on the bexio Marketplace is chargeable on top of the subscription, and the carrier's amounts do not appear in the vendor documentation read. An eBill budget is therefore built from the real volume of invoices addressed to recipients actually registered, and not from a comparison of monthly subscriptions.

eBill is not Peppol, and the difference plays out on your recipients

The two networks are often confused. Peppol is an international network used notably to invoice administrations and European principals; eBill is a Swiss network that deposits the invoice in the payer's e-banking. An eBill connection therefore does not cover a Peppol requirement. Among the eleven programs we follow, Odoo is the only one that acts itself as a Peppol access point, Switzerland figuring among the countries eligible for registration.

Abacus documents Peppol through its partner Descartes STEPcom, and Abacus Research AG does not figure in the OpenPeppol list of Certified Service Providers. For bexio, Crésus, WinBIZ, KLARA, Infoniqa and smallinvoice, no Peppol presence is documented in the sources read on 23 August 2026. The right question to put to an SME is therefore not whether it wants electronic invoicing, but who its recipients are and what they require.

Six checks before promising eBill to a client

These points are checked in order, because each one can stop the project before the next.

The third point often comes as a surprise. Crésus's documentation makes eBill sending conditional on an active QR-IBAN, on an entry in the commercial register and on a sending contract, and KLARA states for its part that the QR-IBAN is mandatory for eBill sending. A sole proprietorship not entered in the commercial register can therefore find itself blocked after having chosen its program, for a reason that is not technical at all.

ORDER OF THE FIRST FOUR CHECKSIDENTIFY THE ROUTE1Native,carrier orthird-party applicationSENDING CONTRACT2Signed with thenetwork partnerQR-IBAN AND REGISTER3QR-IBAN active,entry in thecommercialregisterSHARE OF THEREGISTEREDRECIPIENTS4How many of yourcustomers reallyreceive through eBillORDER OF THE FIRST FOUR CHECKSIDENTIFY THE ROUTE1Native, carrier or third-party applicationSENDING CONTRACT2Signed with the network partnerQR-IBAN AND REGISTER3QR-IBAN active, entry in the commercial registerSHARE OF REGISTERED RECIPIENTS4How many of your customers really receive through eBill

SENDING PREREQUISITES DOCUMENTED BY Crésus AND KLARA, READ ON 23.08.2026; ORDER PROPOSED BY LYVIA

The last point rarely arises at the moment of installation. An eBill connection lives in a contract between the company, its network partner and its bank. It does not automatically follow a change of management software, and taking it over is prepared like the rest of the migration, which we set out on our page about changing management software.

  • Which route the program connects by: native, carrier or third-party application
  • Who signs the sending contract, and with which entity
  • Whether the QR-IBAN is active and the company entered in the commercial register
  • What share of the recipients is really registered for eBill
  • Whether the receiving of supplier invoices is covered, or only the sending
  • What becomes of the flow on the day of a change of program

Where these answers come from

Every fact on this page can be checked at the source. The links open directly the website of the vendor or body concerned.

SURVEY OF 23.08.2026

Frequently asked questions

how do I send an eBill invoice from my program?

It all depends on the route your program takes. If it is published by a SIX network partner, like Crésus or KLARA, sending goes from the program once the sending contract is signed and the QR-IBAN is active. If it goes through a carrier, the procedure depends on the carrier. WinBIZ assumes an account and settings on PostFinance's e-invoicing platform, whereas SelectLine's help documents a transmission through PostFinance without the client needing a PostFinance account. At Infoniqa, sending additionally assumes the E-Services licence option.

eBill from bexio, is it possible?

Not natively in the sources read on 23 August 2026. The vendor's communication points to a Marketplace application published by iomarket AG, chargeable on top of the bexio subscription. The QR-bill, for its part, is generated natively from bexio, with automatic reconciliation of payments. Concretely, the eBill route adds a provider, a contract and a cost line to your invoicing chain, and it changes the contact to call on the day an invoice fails to go out.

how do I check for myself what a vendor announces?

Three official registers are enough to settle most discussions. SIX publishes the list of its eBill network partners on eBill.ch, Swissdec publishes the list of certified payroll programs on Swissdec.ch, with the manufacturer's name, the exact product and the certificate number, and OpenPeppol publishes its Certified Service Providers on Peppol.org. The three addresses figure in our sources. A name that appears in an official register can be checked in a few minutes; a mention on a product page cannot be checked.

eBill receiving is not documented for my program, how do I process my supplier invoices?

Through the QR-bill, which is the best-covered channel on the creditor side in the documentation read on 23 August 2026. SelectLine documents reading supplier QR-bills into open items, Infoniqa the scanning of supplier QR-bills, WinBIZ the QR-bill on sending as on receiving, and Crésus the processing of invoices received. It is not the same flow as eBill, since the document remains a paper to scan, but it avoids re-entry.

is a QR-IBAN needed to send through eBill?

In the documentation read, yes. The QR-IBAN is obtained from your bank and is not to be confused with the ordinary IBAN: the structure of the number and the type of reference differ. KLARA moreover documents three configurable QR-bill variants, without QR, with a Creditor reference, and QR-IBAN with a QRR reference, and it is the third that eBill sending assumes. If your bank has never allocated you a QR-IBAN, that is the first call to make.

I invoice a client in France or in Germany, is eBill enough?

No, eBill is a Swiss channel that deposits the invoice in the payer's e-banking. For a European principal, the question bears on formats and on Peppol. SelectLine documents electronic invoices on output in the XRechnung and ZUGFeRD formats. Abacus supports Factur-X and UBL, automatically validates incoming invoices against EN 16931, and goes through its partner Descartes STEPcom for Peppol. Ask your client which format it requires before choosing the technical route.

does smallinvoice send eBill invoices?

The vendor presents eBill sending as a function of its Pingen integration, and Lourens Systems, the publisher of smallinvoice, does not figure among the fifteen network partners published by SIX as of 23 August 2026. The product is moreover designed to work with a fiduciary, with direct accounting exports to Banana, Infoniqa ONE 50 and Topal. If eBill is a selection criterion, it is the Pingen route that must be costed, not the smallinvoice subscription.

my program is not connected to eBill, what should I do?

Three routes exist. Wait for the vendor to document the function, with no date announced to this day. Check with an approved carrier whether it accepts a file deposit from your program, which assumes checking the formats accepted on both sides. Or change tool, a decision never taken for eBill alone. In every case, the check starts with the number of your customers actually registered for eBill.

Where to go next

Check your eBill route before making it an announcement

We read through your invoicing chain, the program in place, the documented connection route, the sending contract and the volume of recipients concerned, then we tell you what the vendors' documentation allows to be established and what remains to be checked with the carrier. We sell no licences. A first exchange with no commitment.