Printing

All countries

Finland

Sweden

Norway

Denmark

Netherlands

Germany

OTHER

Print is the final fallback delivery method when an invoice cannot be sent as an e-invoice or by email. Maventa evaluates delivery options in the following order:

E-invoice
Email
Print service

To force print delivery, disable all other routes in the invoice sending API. The print service is not enabled by default — it must be activated separately for each company account.

To send an invoice by print, include the recipient’s full postal address in the invoice XML.

Requirements for print delivery:

The sender company has the print service activated
The full postal address of the receiver is included on the invoice
The invoice image meets the technical restrictions

Activating the printing service

To use print as a delivery option, the printing service must be activated separately for the company account. Activation can be done through the API or UI.

Enable the print service using PATCH /v1/company/setting. Under the send_invoice_print block, set the parameter enabled to true.
To disable the printing service, set the enabled parameter to false.
To check the status, use GET /v1/company/settings. The enabled parameter under send_invoice_print indicates whether the service is active (true) or disabled (false).

Maventa applies internal safety limits and alerting on print volumes to help catch unusually high or accidental print sending before it causes problems. These safeguards are monitored internally by Maventa and are not exposed through the API.

Forced print route

You can also force print delivery without explicitly disabling routes. The following XML formats support this natively:

Finvoice: In the SOAP header, use the following:

<eb:To>
  <eb:PartyId>PRINT</eb:PartyId>
  <eb:Role>Receiver</eb:Role>
</eb:To>

If a SOAP header is not an option, use this instead:

<ToIdentifier SchemeID="0037">PRINT</ToIdentifier>
<ToIntermediator>PRINT</ToIntermediator>

TEAPPS:

<NET_SERVICE_ID>PRINT</NET_SERVICE_ID>

The PRINT keyword in the invoice XML is supported mainly for legacy systems that have no way for the sender to choose the delivery channel. For new integrations, control delivery through the API metadata (such as disabled_routes) so the channel is an explicit choice in the integration rather than embedded in the invoice XML.

This mechanism will not be supported forever — plan new integrations around the API metadata approach.

Template

By default, invoices sent through the print service use a Maventa-generated invoice template. This template is optimised for efficient processing, complies with all technical requirements, and is designed to fit the envelopes used by the printing service provider in each country. Customers can personalise this template by adding their company logo (via UI or API).

Examples of Maventa templates for each country are available on the country-specific rules and settings page.

As an alternative, customers may use their own invoice image for all printed invoices or on a per-invoice basis (via UI or API). When using a custom image, Maventa automatically adds a cover sheet with the recipient’s address details. This ensures proper alignment with the envelope window. The cover sheet is counted as an extra page and billed accordingly.

Prints are always double-sided if there is more than one page.

To add a logo to a Maventa-generated invoice image template, use the PATCH /v1/company/setting method with the parameter logos. Note: Most image formats are supported except PDF. JPEG or PNG is recommended. PNG files with transparency are not supported.
To remove an uploaded logo, use the same method as above.
If you want to use your own invoice image for all prints, use PATCH /v1/company/setting and set the parameter send_invoice_print.use_own_pdf to true. To disable it, set the parameter back to false.
If you want to control the use of your own invoice image per invoice, you can do so when sending invoices with the POST /v1/invoices method. Inside print_settings, use the parameter print_own_image (true or false). This setting will override the company-level configuration.

For Peppol BIS 3.0 and other UBL-based invoices, “your own invoice image” is the embedded attachment whose AdditionalDocumentReference carries <cbc:DocumentDescription>CommercialInvoice</cbc:DocumentDescription>. Only that attachment is treated as the invoice image; any other embedded attachment is handled as a regular supporting document. See Peppol BIS 3.0 for the exact XML.

When using your own invoice image, make sure it meets the technical restrictions below.

Technical restrictions of the PDF

All files must be in PDF format and fully self-contained — no dynamic components, and all fonts, images, and other resources must be embedded. All new customers should test their PDF files (all variants of fonts, images, etc.) to verify that the PDFs can be processed. If the PDF contains graphics such as logos, charts, or other images, they must be of good quality.

Keep the top and right margins empty
Do not send any invoice image or attachment with black/dark background
No transparencies
All fonts must be embedded (subset or complete)
All images must be in 250-300dpi. Higher resolution produces little or no quality gain. Lower resolution gives poor quality.
Text should be stored as text (not bitmap)
Recommended size per page is 1024kB, smaller the better
Black / White print: 2bit colors (black and white only), not grayscale.
Colour print: Black text should be in black, not 4-colour
Colour print: All colours must be CMYK
PDF page size needs to be A4 (210 x 297 millimeters)

PDF attachments must be provided without encryption or any form of security restriction. Password-protected files or files with restricted permissions (e.g., preventing printing or content extraction) cannot be processed by the printing service.

Attachment handling

When sending separate PDF attachments for print, the following rules apply:

Up to 3 separate attachments are allowed (maximum of 4 files including the invoice image).
Only PDF format is allowed.
Maximum size per attachment: 50 MB.
Total maximum number of pages: 110.

If these limits are exceeded, all attachments will be discarded. The sender will be notified by email, but the invoice image itself will still be printed.

There is an extra charge per page printed.

Default setting: For Finnish companies, attachment printing is disabled by default. For all other countries, it is enabled. This setting can be adjusted via the API or UI.

Use the PATCH /v1/company/setting to change the setting. Under the send_invoice_print block, set the parameter attachment_print to true to enable attachment printing, or false to disable it.

Error handling

If an invoice cannot be delivered due to an outdated or invalid address, it is returned to the sender’s address. The sender’s address is always included on the Maventa-generated invoice image and on the cover sheet. The return address is taken from the invoice data.

The exception is Norway, where Maventa offers an automated return post handling feature. Invoices are not returned to the sender’s address in this case. Read more on the Norway-specific page.

Maventa validates that a recipient address is provided and all required address fields are present, but does not validate the format or correctness of the address content.