You've finished the invoice, attached the PDF, clicked Send, and moved on to the next job. Two days later the client writes to say they never received anything. Or worse, they pay into an account that someone changed in a manipulated email. That's exactly the moment you realize that sending invoices by email isn't just a minor side step, but a real part of your cash flow.

Especially as a Swiss freelancer or sole proprietor, you know the temptation to keep the process as lean as possible. That often works, until a document lands in spam, a client disputes delivery, or questions about account details start coming in. Email remains a practical entry-level channel, but only when dispatch, filing, and security logic work cleanly together.

Why sending invoices by email deserves more attention

A typical Tuesday at a small Swiss sole proprietorship often looks like this. The work is done, the invoice is ready as a PDF, and dispatch goes out quickly between two appointments. Then the waiting begins, and that's exactly where the problems appear that nobody took seriously at the start.

The email may never arrive because it gets stuck in spam. Or the client can't find the invoice anymore because it gets buried in an overflowing inbox. In more delicate cases, the recipient even claims they saw a different account number than the one you sent.

Rule of thumb: The simpler the dispatch channel, the more important discipline in the process becomes. Without clear filing, unambiguous naming, and clean delivery, a convenient email quickly turns into an unnecessary back-and-forth issue.

The email route isn't wrong, though. It's just often set up too imprecisely. In Germany, according to a Bitkom study, 99% of companies send invoices by email, 55% already use e-invoices for dispatch, and only 45% receive e-invoices in machine-readable format, which nicely illustrates the transition from simple PDF dispatch to structured e-invoicing Bitkom study on e-invoice reception. Exactly this intermediate state is also noticeable in everyday Swiss life, especially among self-employed people with lots of PDF invoices and little ERP automation.

Anyone who sends invoices by email doesn't just protect themselves from lost receivables. They also protect their reputation. A clean process comes across to clients as calmer, more reliable, and significantly more professional.

Legal foundations for sending invoices by email in Switzerland

The first important point is simple: invoices by email are generally possible, as long as the invoice contains all mandatory information and authenticity and integrity are preserved. In Switzerland, the approach is handled pragmatically, and a PDF by email remains a common standard for many small businesses. What matters isn't the medium alone, but whether the content is correct, traceable, and archived.

Developments in Germany help as a frame of reference. There, invoices have been allowed to be sent electronically since July 1, 2011, provided mandatory information, authenticity, and integrity are secured technical guide to electronic invoices. Since January 1, 2025, an invoice in Germany only counts as an e-invoice if it is issued, transmitted, and received in a structured electronic format, and a simple PDF no longer qualifies Federal Ministry of Finance FAQ on e-invoicing. For Swiss freelancers, this is mainly relevant as a market signal, not as a direct adoption of the rules.

Consent, format, and archiving

In a B2B context, the recipient's consent to electronic dispatch is a central point when invoices are sent classically by email as a PDF notes on sending invoices by email. For structured e-invoices, expectations shift because the ability to receive digital formats is increasingly assumed. In Switzerland, it's therefore worth clarifying early with new clients which channel they prefer and how their accounting department prefers to process invoices.

Archiving must not be treated as a side issue either. Electronic invoices must be filed so they remain verifiable, and VAT-compliant retention is central for the FTA. Anyone who sends invoices by email should keep the sent version, the proof of dispatch, and the associated receipts together.

You can also find a practical overview of the legal foundations for Swiss freelancers at Magic Heidi for Swiss freelancers, if you want to think about invoices, filing, and everyday practicality together.

How to build a professional invoice email

The invoice itself is only one part of the message. The rest determines whether the client recognizes it immediately or mentally files it away as an ordinary email. A clear subject line, a brief greeting, and a clean attachment noticeably reduce follow-up questions, especially for recurring work.

Subject and text must be unambiguous

A good subject line names the invoice and a reference the client can immediately assign. For example, a phrasing like Invoice 1023 dated 15.05.2024 works much better than a vague title like "Documents". In the email body you don't need long explanations, just the note that the invoice is attached, plus a short thank-you and a way to reach you with questions.

Invoices don't belong in the body text of the email. The attachment is the document; the email is just the clean cover card.

Avoid writing sensitive data or long payment details directly into the message. The PDF is the place for the actual invoice, not the email window. This is particularly helpful with foreign-currency clients or platform clients, because otherwise the message quickly becomes cluttered.

Templates that prove themselves in everyday use

For dispatch, a simple structure is often enough:

• Subject: Invoice 1023 dated 15.05.2024
• Salutation: Hello Ms. Meier
• Short text: Please find attached the invoice for my work from last month.
• Note: If you have any questions about line items or the amount, you can reach me directly by replying to this email.

For the filename, a scheme that makes client and date immediately visible helps, such as Invoice-1023-Mustermann-2024-05-15.pdf. It looks unspectacular, but saves the recipient search work. If you want to keep your signature equally tidy, you can use a simple AI email signature template as a starting point if your signature isn't consistently structured yet.

Deliverability and security when sending invoices

The biggest weakness of email dispatch rarely lies in the PDF itself, but in delivery and manipulation. An invoice that never reaches the client or gets stuck in spam does you no good. That's why it's worth having your own invoicing address, ideally as a separate mailbox without forwarding and without mixing it with private use.

What actually goes wrong in everyday life

Spam filters often work silently in the background. The email is out there, but nobody in the company checks the quarantine folder or a second mailbox. Even more often I see invoices running through personal mailboxes that later can't be cleanly filed or traced.

Important: If you send invoices by email, you need a fixed channel, a uniform format, and clear responsibility. Without these three points, the process remains vulnerable.

For practical dispatch, that means not leaving delivery to chance. Encrypted transmission, access controls, and a clear deletion and authorization concept are part of the minimum, as also described in a technical guide to electronic invoices. For solo businesses, this is less an IT topic than a question of orderliness. Anyone using a single invoicing mailbox reduces mix-ups and notices sooner when deliveries fail to arrive.

The assurance "it's been sent" isn't enough in everyday life. More sensible is a workflow where, after dispatch, you can trace where the invoice went, who has access, and where the email lands if it isn't delivered directly. That's exactly where improvised dispatch separates from a robust workflow.

Manipulated account details are the real problem

The most delicate point is often not the dispatch itself, but the manipulation of account details in transit or in the mailbox. Transport encryption protects the email on its way, but not against changes to the content if someone is already sitting in the mailbox or the invoice is intercepted along the way notes on manipulated invoices by email. For Swiss small businesses, this remains relevant because phishing, social engineering, and fraudulent communication attacks continue to be real risks.

The practical damage usually arises quietly. A changed account often only becomes noticeable when payment is missing or the client asks. Anyone sending invoices by email should therefore not spread account details repeatedly in free email texts, but set up dispatch so that recipients can cleanly match sender, invoice, and payment details. A clear internal check before the email goes out also helps. You can find further notes on access, protective measures, and the secure handling of invoice data in the Magic Heidi security overview, if you want to think through your workflow together with filing and permissions.

From a data protection perspective, this is no side issue either. A professional commentary points out that sending invoices by simple email without adequate technical protective measures can create a liability risk under Art. 82 GDPR if third parties redirect payments to a wrong account data protection and e-invoicing. That doesn't mean every invoice email is risky. It means you should work with a clean process for account details and delivery, rather than relying on habit.

QR invoice and e-invoice as alternatives to PDF by email

The PDF by email is convenient, but not always the cleanest solution. The QR invoice reduces the effort of payment matching because the reference comes along in structured form and both accounting and payment recipients have less manual reconciliation to do. The true e-invoice goes a step further, because structured data can be processed directly by machines.

Comparison of invoice dispatch methods

The Swiss QR invoice is often the best compromise in everyday life if you want to work without a big ERP. Anyone whose invoices involve lots of repetition or frequent payment questions saves noticeable time with a structured reference. Magic Heidi creates QR invoices directly from the application and supports exactly this pragmatic path, without you having to switch to complicated accounting logic.

When which method makes sense

For small projects with low volume, PDF by email is often sufficient, as long as dispatch and archiving are clean. As soon as incoming payments become erratic, the client regularly asks questions, or you want to simplify payment reconciliation, the QR invoice is the more obvious solution. The structured e-invoice pays off more where both sides are digitally mature enough to process the exchange truly automatically.

If you still feel uncertain about QR invoices, creating QR invoices with Magic Heidi offers a direct entry into the Swiss standard, without first having to plan a whole system change.

Archiving and automation for your invoice workflow

Sending invoices is only half the work. The other half is clean filing, so that you don't have to piece together emails when questions arise, at year-end closing, or during an audit. For the Swiss solo business, what counts above all is that outgoing and incoming invoices are treated the same way, i.e., filed traceably, completely, and in an audit-proof manner.

How the workflow stays auditable

Set up a clear scheme for sent invoices. The email, the PDF, and the payment reference belong together, so you can find the context immediately later. The same principle applies to incoming receipts, just in the other direction. A dedicated invoicing mailbox is still the cleanest starting point for this, because it maintains the separation between personal correspondence and accounting documents.

Automation pays off above all where manual steps repeat constantly. A statistic from Sevdesk shows that in 2024 only 46% of companies used invoices automatically from their ERP system BFS on invoice automation. That shows how many processes still run semi-manually. Exactly in this in-between space lie most of the small efficiency gains, not in large enterprise projects.

What's worthwhile for solo self-employed people

• Collect incoming invoices centrally: One mailbox, no scattered forwarding.
• Archive attachments directly: Don't piece them together later from the mail archive.
• Limit access: Anyone working on invoices needs clearly defined access.
• Automate bank reconciliation: Connect transactions with invoices and expenses faster.
• Import receipts via scan or email: This saves sorting work and reduces transfer errors.

The best automation is the one that shortens your daily work without you losing track.

Magic Heidi covers exactly this practical area, with QR invoices, AI-supported receipt capture, CSV import for bank statements, and receipt import via email forwarding. For freelancers and sole proprietors, that's often the more sensible path than a heavy ERP, because the workflow stays simple and still remains cleanly documented.

Invoice dispatch, archiving, and accounting have to fit together in everyday life. As soon as you keep emails, PDFs, payment references, and receipts in one place, the risk of gaps during follow-up questions or later reconciliation drops significantly.