Document Exchange

In addition to invoices, Maventa supports the exchange of other trading documents via Peppol networks.

Companies and government organizations are increasingly interested in full procurement automation. eOrdering automates the purchase-to-pay process and provides benefits across different teams and the organization as a whole, including:

• Streamlined processes
• Improved supplier relationships
• Increased visibility and control

Automation of ordering, such as using structured catalogues as the basis for orders, simplifies information exchange and benefits all parties in the procurement chain. Steps like approvals, order picking, and invoicing can be automated, improving efficiency and reducing errors.

Peppol BIS ordering.

All the document types and profile versions in Peppol

Documents endpoints

Document sending

Documents are sent by uploading a document file in XML format along with the required parameters in the API call:

Use POST /v1/documents to send a document. The call returns a document ID.

Parameters:

• File
• Referencing
• Something

Use GET /v1/documents/{id} to check the status of a sent document, to see whether it was delivered successfully or failed. You can also use webhooks to receive real time notifications of document status changes.

Document receiving

To receive documents, register first the company as document receiver, like this.

Documents are received by listing new incoming documents in Maventa and then downloading the document and attachments into the financial system. List and download documents

Use GET /v1/documents with params direction=RECEIVED, received_at_start, and received_at_end to get list of documents available for download. It is possible to use the param fields to limit the amount of data returned on the response.
Use GET /v1/documents/{id} to download the document
Use PATCH /v1/documents/{id} to markd the document status to ‘CONFIRMED_DELIVERY’ after downloading the document. Only when the document is in ‘CONFIRMED_DELIVERY’ status, the downloading process is considered to be completed by the system.

Receiving ordering and other document types

The receiving of ordering and other document types can also be enabled using this endpoint. In these cases it’s also required to specify the desired profile version (profile_version) in the request. Note: Make sure the system integrating is able to process the requested profile version. See Document receiving for details.

Example request:

{ “network”:”PEPPOL”, “profiles”:[“INVOICE_RESPONSE”], “profile_version”:”PEPPOLBIS30” }

Supported profiles and versions:

REMINDER PEPPOLBIS30, EHF30 FI, NO, SE, DK, NL INVOICE_RESPONSE PEPPOLBIS30 FI, NO, SE, DK, NL, BE MESSAGE_LEVEL_RESPONSE PEPPOLBIS30 FI, NO, SE, DK, NL, BE INVOICE DEPRECATED: Use INVOICE_AND_CREDIT_NOTE CREDIT_NOTE DEPRECATED: Use INVOICE_AND_CREDIT_NOTE

EHF30 is a Norwegian national format and should be preferred for Norwegian customers.

UNKNOWN, INVOICE, CREDIT_NOTE, ORDER, ORDER_RESPONSE, CATALOGUE, CATALOGUE_RESPONSE, SELF_BILLING_INVOICE, DESPATCH_ADVICE, RECEIPT, VOUCHER, BANK_FILE, REMINDER, SCAN, INVOICE_RESPONSE, MESSAGE_LEVEL_RESPONSE, EXPRESSION_OF_INTEREST_REQUEST, EXPRESSION_OF_INTEREST_RESPONSE, TENDER_STATUS_REQUEST, CALL_FOR_TENDERS, TENDER, TENDER_RECEIPT, ORDER_CHANGE, ORDER_CANCELLATION, SELF_BILLING_CREDIT_NOTE