AutoInvoice offers electronic invoicing and document transfer services. There are two APIs that can be used for connecting to AutoInvoice, REST and SOAP.
Potential application ideas include:
AutoInvoice offers various selection of services and different ways to access them. Here’s guidance for how to decide and define what you want from your integration.
The integration scope impacts what AutoInvoice services you integrate to. The scope defines what are the key functionalities and capabilities users will have in the service.
Things to consider when defining the scope:
Sending, receiving or both?
Will your customers be using AutoInvoice to send or to receive electronic documents or for both.
B2B / B2C invoicing?
Do your customers have needs for consumer invoicing. AutoInvoice has different consumer invoicing options between the market areas, delivering to bank network or mobile application depending on country.
What are the services your customers want to activate? We have different services that support the invoicing flow, such as printing and scan service as well as help to bring customers added value such as Receivables Management and Supplier Activation. See Services & Networks part in Integration guide for more information.
Currently there are some features that are not supported with both SOAP and REST APIs, which may require integration to use both. We are working to support all functions available via SOAP API also via the REST API, and most of the new functionalities will be only available through REST. Integration guide will tell which features are supported by which APIs.
You can get started with your integration by just couple of API methods. With more effort you can make a fully integrated solution.
The integration level impacts effort to integrate as well as how the service is used. For example will the users access AutoInvoice UI or will all actions take place within your ERP system.
Integration levels from level 1 to level 3 are shown on the picture below. The level 3 is offering the best functionality and performance of the service, but usually also requires the most integration effort.
In level 1, invoice sending and receiving takes place through API but email and web UI are used to handle errors, to monitor invoices and to manage companies and settings.
When the level of integration goes up the automation increases. In level 3, all actions from invoice sending, receiving and monitoring to the error handling and companies management are handled through the API.
The level should be chosen based on the integrators needs and the grade of automation required. It is also good to note that you can start from a level and continue to deepen the integration over time.
Interested to know more about the electronic invoicing?
Here’s our quick guide to the basics of electronic invoicing and document exchange.
An electronic invoice or order document is a document that is exchanged over a network between two or more independent financial systems requiring no human interference.
Electronical invoicing and ordering (or e-invoicing and e-ordering) means that business documents such as invoices, credit notes, catalogues,orders and order responses are distributed between the supplier and the buyer in a structured, electronical format.
Electronic documents are an easy and effective way to deliver data between the trading partners.
With electronic document exchange it is possible to change the traditionally paper-heavy manual processing of documents into a faster, more automated process and this way create signficant savings in cost and time.
Electronic document exchange also enables to have increased level of integration between the supplier and the buyer, as well as between organization’s own accounting software and other business systems.
Electronic invoicing and ordering infrastructure consists of operators that connect suppliers and buyers referred as end customers. When an end customer sends an e-document, his/her operator routes it to receiver.
AutoInvoice e-invoicing works based on trying to find the best possible route for the document. If receiver cannot be reached through e-invoicing network,invoice can be sent as email or to printing services and delivered as a paper mail. This allows reaching of all customers through a single API.
There are different formats that are accepted as ways to structure the data for the electronic documents such as invoice. E-document can be data in structured Electronic Data Interchange (EDI) or XML format, or structured data issued using standard web-based forms.
AutoInvoice and e-document formats
AutoInvoice e-invoicing supports XML based standard formats and automatically converts the invoices from one format to another when needed. The service supports a wide range of different e-invoicing formats including international ones like PEPPOLBIS, formats for software houses like VismaXML and LiinosXML, and national formats like Finvoice, TeApps (FI), Svefaktura (SE) and SI-UBL (NL). If you are downloading invoices please check that your financial system can handle at least one of the formats that AutoInvoice has support for. For e-ordering AutoInvoice uses Peppol formats.
Learn more about invoice formats:
E-document networks enable trading partners to exchange standards-based electronic documents between each other over a common network. The networks can be open or point to point connections between different operators.
In addition to operator point-to-point connections AutoInvoice enables connection to the open European e-delivery network Peppol. Peppol is part EU’s initiative to move document exchange between economic operators to standardised electronic form and to lower the barrier for cross-border trading. Peppol has expanded from EU to a global network, including for example Singapore.
Users are connected to the Peppol network over Access Points. AutoInvoice is a certified Peppol Access Point provider. This means that through AutoInvoice you can register companies to Peppol network for receiving electronic documents and send electronic documents to other Peppol recipients. You can read more about Peppol here.
How to register to Peppol via AutoInvoice is explained in our integration guide.
Documents are routed based on the recipient and operator/network information. Depending on how the document is delivered, this address can be the electronic invoice address (EIA), email or postal address. If no address is given AutoInvoice can try to fill in the information based on the recipient’s business ID and information in AutoInvoice Finder. The finder uses information from different sources, like national registers for e-invoice addresses. The default order in which invoices are sent is e-invoice, email, print. In AutoInvoice there are also possibilities for customized routing, i.e. disabling routes or changing their order.