Enter your credentials to Maventa testing environment, to authenticate and try things out with the Swagger UI. This will fetch a Bearer token using OAuth2 with the endpoint POST https://ax-stage.maventa.com/oauth2/token. The token is stored in your browser's session storage (cleared when you close the tab) and used in Swagger calls done from this documentation website. The token is valid for 1 hour.

Never use your production credentials here. This is only for testing the Maventa test environment in the Swagger UI.
All None
eui global company lookup document:receive document:send invoice:receive invoice:send company:read company:write validate receivables:assignments analysis billing:reports partner:invoice_delivery_actions partner:lookups partner:takeovers partner:lyanthe_scan_service fi_bank_message:send fi_bank_message:receive
Cancel Sign In
Get started Integration Guide Services and Networks API Specification Tutorials Changelogs
Search
Getting started Invoice sending Invoice sending Consumer Invoicing Printing Email Invoicing Invoice Receiving Invoice Receiving Scanning Country Specific Denmark Finland Germany Norway Sweden Document Exchange Document Exchange Peppol Network Invoicing formats Invoicing formats Validation Peppol BIS 3.0 Finvoice 3.0 Account Management Companies and Settings Billing

Billing

Partner and Maventa agree about the way the end customers (users of partner’s software) are invoiced for their transactions and use of Maventa services.

Basis for billing

Billing is transaction based. All transactions are billed based on the partner vendor_api_key that is provided on the API calls or in some cases stored in the company details. Based on the vendor_api_key setting the transactions can be billed from the key owner (partner) or from the end customer directly.

Billing is partner specific meaning that same transaction is only billed once from a partner and you can refetch invoices to same partner’s other systems without additional cost. If a customer receives invoices into different partners’ products, i.e. uses multiple ERPs from different partners to receive invoices at the same time, each partner will be billed separately for the invoice they have received into their system.

Partner billing

We recommend all our Partners to fetch transaction reports using our Billing API. Using Billing API is not tied to Maventa’s billing time and it allows billing / transaction review automatically at any time of the month.

Current quarter’s data is kept until the 15th of the first month of the next quarter.

API endpoint /api/billing/v2/reports/billing_company_transactions returns transaction counts that are assigned to the authenticated billing company (partner). The endpoint contains transactions for the current and previous month.

The exact amount to be invoiced for the previous month will be checked on the 1st working day of the following month 14:00 EET (A day before Maventa’s actual invoicing).

For example March transactions are ready to be fetched 3.4.2023 14:00 EET, which is the 1st working day of April.

Transaction report

All Maventa invoices are attached with a transaction report that contains all the transacations that are billed in the invoice.

The transaction report contains the following information of the transactions:

Header Value
BillingCompanyID unique identifier of the invoiced company in Maventa billing system
BillingCompanyName name of the invoiced company in Maventa billing system
BillingCompanyOrganizationIdentifier business ID of the invoiced company in Maventa billing system
TargetCompanyID unique identifier of the company who has performed the transaction
TargetCompanyName name of the company who has performed the transaction
TargetCompanyOrganizationIdentifier business ID of the company who has performed the transaction
MaventaProduct name of the transaction
InvoicingProductCode product information on the invoice
DimensionItemSoftware name of the software used to perform the transaction
NumberOfActions number of transaction
ActionOriginTime first day of each invoiced month
UnitNetPrice unit price of transaction
LineNetSum total line amount

See example transaction report: FIX_PENDING_EXAMPLE

Note that the structure of this report is based on a real life example, but the data in the report is made-up.

Back to top