Skip to main content
The Swiss QR-bill add-on adds the Swiss payment part, with the QR code that your customers scan in their banking app, to every document an automation creates. The payment part goes on an extra last A4 page, at the bottom as the standard describes, so your template needs no blank space for it. It works with every template type (Google Docs, Word and PDF) and every way you create documents. You can use it alone or together with the e-invoice add-on. With both add-ons on, one PDF carries the e-invoice data and the QR-bill page. Before a document is created, DocsAutomator checks the QR-bill against the Swiss QR-bill standard (IBAN, reference check digits, amount, field lengths and allowed characters). When something is wrong, nothing is created or sent, and the run names what to fix.

Turn on the add-on

  1. Open Settings, then Add-ons.
  2. Switch on Swiss QR-bill. Only owners and admins can do this.
  3. Click Settings next to the add-on and enter your seller details.
The add-on is off until you switch it on. Automations without a QR-bill do not change.

Seller details

The seller details are the account holder on every payment part. The QR-bill has its own seller details, separate from the e-invoice seller, so a change in one never changes the other. If you used the e-invoice before, the QR-bill page shows your e-invoice seller with the note “Copied from your e-invoice seller. Until you save, changes there also change the QR-bill.” Click Save seller details to keep them as the QR-bill’s own. Until then, your QR-bills keep using the e-invoice seller.
QR-bill seller details in Settings, filled in from the e-invoice seller, with the note Copied from your e-invoice seller and the Save seller details button

QR-IBAN

A QR-IBAN is a separate account number that your bank gives you with its QR reference service. You need it only for the QR reference type. Enter it under QR-IBAN on the same settings page.

Seller for one automation

An automation can use a different seller for its QR-bill. Open Use a different seller for this automation in the automation’s Account card. Each field takes a fixed text or a field of your data source.
  • With a legal name: the automation uses another company, and nothing comes from Settings. Fill in its postcode and city, and its IBAN. With the QR reference type, enter its QR-IBAN instead (the row appears when QR reference is chosen). The workspace QR-IBAN is never used for another company, because it belongs to your account. Without one, the run stops with “Add the QR-IBAN for this seller, or choose another reference type.”
  • Without a legal name: the automation keeps your company and changes single fields only. Empty fields show the value from Settings in grey and use it, including the workspace QR-IBAN, unless you change the IBAN.
Account card of an automation with one changed field: the city Bern, while the other fields show the Settings values in grey
Account card with another company, Tenant AG, and the QR reference type: empty fields read Not set for this seller, and the QR-IBAN row asks for this seller's QR-IBAN
The e-invoice seller of the same automation does not change the QR-bill.

Set up an automation

Open an automation and find its Swiss QR-bill section. Fill in the parts below, then switch on Add a QR-bill. Most fields suggest a match from your data by name, or from the automation’s e-invoice setup.

Payment

  • Currency: CHF or EUR. When the automation also creates an e-invoice, the currency is EUR, the currency of the e-invoice.
  • Amount: the field that holds the invoice total. Leave it empty to let the payer enter the amount, for example for donations. When the automation also creates an e-invoice, leave it empty: the QR-bill then uses the e-invoice amount due, which is the gross total minus any amount already paid. A mapped amount must equal that amount due.
  • Fully paid invoices: when the e-invoice amount due is 0, there is nothing to pay, so the document gets no QR-bill page. The document is still created.

Reference

The message is optional free text of up to 140 characters, for example the invoice number. Your customer sees it in the banking app.

Payer

The payer’s name, street and number, postcode, city and country are optional. Leave them empty to let the payer enter their name and address. When you map any of them, the name, postcode and city are needed. An empty country means Switzerland (CH).

Language

The payment part uses the language of the automation’s locale: German, French, Italian or English. Other locales use English.

Test document

Create a test document from the section. The result of the checks shows in the section, and nothing is sent. Scan the QR code with your banking app to see what your customer sees. In test mode the QR-bill page carries the test watermark, like the rest of the document.

Checks and messages

Every check runs before the document is created. When one fails, no file is created, stored or sent, and the run fails with the message QR-bill not created: followed by the first problem, plus the number and text of any further problems. In the text below, ... stands for the value from your data.

Seller details and account

Amount and currency

Reference and message

Payer

Every text field

Line breaks and repeated spaces in your data become one space, so they never fail a check.

Rare messages

  • The QR-bill could not be built from this data (...). The data passed our checks but not the library that draws the payment part. Contact support with the message.
  • The QR-bill page cannot be added to this PDF (...). The finished PDF could not be read, for example a merged PDF that is damaged. Check the merged files, or contact support.

API and integrations

The QR-bill needs no extra request fields: it reads the fields you map in the automation, also from API, Zapier, Make and n8n requests. A successful response carries "qrBill": { "ok": true }, and the PDF at pdfUrl has the payment part on its last page. A failed check answers with status 400, the message above and "code": "QR_BILL_INVALID".

Settings that combine with the QR-bill

  • E-invoice (ZUGFeRD): the QR-bill page is added first, then the e-invoice data and the PDF/A-3 conversion. One PDF carries both, and it passes the official ZUGFeRD and PDF/A checks with the extra page. With XRechnung, the PDF gets the QR-bill page and the XML file is unchanged. The QR-bill uses its own seller, and the e-invoice’s amount due and EUR. A fully paid invoice gets no QR-bill page.
  • Merge PDFs: the QR-bill page is the last page, after the merged PDFs.
  • Signing and acceptance: the QR-bill page is part of the document your recipient signs or accepts.
Last modified on October 27, 2026