To deliver an e-invoice AutoInvoice uses the electronic invoicing address and the operator code of the recipient. If only recipient’s e-invoice address or organization number is given AutoInvoice does a lookup to find the rest of the information.
The recipient information can be given as
If both are used, the information in the metadata overrides information in the XML.
Please note that specifying the operator code affects routing so it should only be given when the sender knows this information.
The default order to route an invoice is
E-invoice is tried first, and email and print are used as fallbacks.
If only recipient’s e-invoice address or organization number are given, and no valid electronic route can be found the fallback routes are automatically tried.
The fallback routes are NOT used if invoice has been sent to specific electronic route. The specific route means that in sending both electronic invoice address (EIA) and operator information are given (e.g. 0192:123456789, PEPPOL). In this case invoice is sent directly to specific route and no other routes are searched or tried. The system considers that the invoice is meant to be send as an e-invoice to that specific address and the sender would like to know if that e-invoice route fails.
Disabling routes specifically is also possible in the sending API call.
If you want to find out if a company can receive electronic invoices through AutoInvoice or through external operators before the send, you can use API method:
to find out recipient’s invoicing information. The search can be done using indentifiers such as company name, company organization number or business ID, VAT code or e-invoice address (e.g. EDI, OVT, EAN, GLN)