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
Most partners need no Billing API. The transaction report attached to the Maventa invoice is the normal way to rebill your customers. It lists the transactions of each of your customers, with the unit price and the line sum. See Transaction report.
Use the Billing API version 2 if Maventa invoices you for your customers’ transactions and you want your billed counts during the month or in your own system. Your vendor_api_key setting decides who is invoiced, as described in Basis for billing. The Billing API returns counts and no prices. Call GET /api/billing/v2/reports/billing_company_transactions/available first, and read a month only after that call reports it.
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.