# Convert invoices by email: how the channel works

- Date: 2026-07-29
- Modified: 2026-08-29
- Reviewed: August 29, 2026
- Reading time: 2 min read

Convert invoice PDFs by email: enable the Enterprise channel, verify senders, choose a format, send attachments, and review the reply.

> Reviewed against Invoice Converter email channel, OASIS UBL 2.1 specification.

The email channel converts genuine PDF invoice attachments and returns validated artifacts in the same thread. It is included with every active Enterprise subscription and suits controlled, low-volume workflows.

## Setup and first conversion

- Start an Enterprise subscription and switch on Email Import in your profile. No approval by our team is needed.
- In the account profile, add and verify every sender address. Choose the reply destination and language.
- Copy an inbox from the profile. The generic inbox needs exactly one subject tag such as [XRechnung], [ZUGFeRD], [EN16931], [UBL], or [CII].
- Send one invoice per email, attached as a genuine PDF. With supporting PDFs such as timesheets, name the invoice in an Invoice file line. Each email uses one conversion unit per format.
- Open the threaded reply and review the issued file plus its HTML validation report.
## Important limits

Only verified senders are processed. The channel accepts genuine PDF attachments, not renamed images. Low-confidence cases and warnings still need human review. Available units must cover the full message before processing begins.

## Email or API?

Use email when a person or mailbox rule benefits from a reply thread. Use the [External API](/en/blog/invoice-conversion-api) when a system needs idempotency, task status, rate-limit information, and explicit downloads.

> **Send a PDF, get the e-invoice back in the thread**
>
> Email Import converts genuine PDF attachments from verified senders and replies with the validated file in the same thread. 1. Turn on Email Import: Email Import is included with every active Enterprise subscription. Enable it in your profile; no manual approval is needed. 2. Verify every sender: Only verified sender addresses are processed. Choose where replies go and in which language. 3. Email the PDF: Send one invoice PDF per email, with up to 8 supporting PDFs such as timesheets. With several PDFs, name the invoice in an Invoice file line. Up to 10 attachments, 10 MB each. The generic inbox needs exactly one format tag in the subject. Each email uses one conversion unit per format. 4. Extracted and validated: The visible PDF content is extracted and checked by the same strict conversion and validation pipeline as the API. 5. The reply arrives in the same thread: It carries the e-invoice and its HTML validation report. The service does not forward the invoice to your customer. 6. Review before you forward it: Low-confidence cases and warnings still need human review. Compare the result with the source before sending it on. Output: XRechnung, ZUGFeRD, EN16931, UBL, CII.

## FAQ

### Can any sender use the address?

No. Each sender must be added and verified in the Enterprise account profile.

### Does the service forward the invoice to my customer?

No. It returns results to the configured sender or collective address. You control the later delivery.

## Official references

- [Invoice Converter email channel](https://www.invoice-converter.com/en/developer-api/email-invoices)
- [OASIS UBL 2.1 specification](https://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html)