Release Notes

Information about future and past API releases

Version releases

We are constantly adding new features to Procountor API. This page has the planned changes in future releases as well as release notes for the current ones. For anyone interested, we recommend subscribing to our mailing list to get notifications about API changes as soon as they become available.

Subscribe to our mailing list

Currently available API versions

Procountor API version diagram

API Path Version Release Date Support Ends
/latest monthly release with no extended support
/supported 22.08 updated to latest numbered version every three months
/v2211 22.11 2022-11-19 mid-Aug 2023
/v2208 22.08 2022-08-20 mid-May 2023
/v2205 22.05 2021-05-22 mid-Feb 2023

You can find the version update schedule from Procountor news and announcements site.

Release notes

Changes highlighted in red are not backwards compatible

Planned changes for the future

  • POST /payments endpoint will require mandatory field invoiceVersion (to be added later) to ensure invoice is correct.

Changes in version 22.11

Endpoints

  • In POST /invoices and PUT /invoices endpoints, for invoice type SALES_INVOICE if invoiceChannel is ELECTRONIC_INVOICE, in addition to name following fields will be required in billingAddress and counterParty > counterPartyAddress
    • street
    • zip
    • city
  • type that wasn't needed in POST /reports/ledgeraccounts has been removed from LedgerAccountsReportRequest.
  • type that wasn't needed in POST /reports/generalledger/{id} has been removed from GeneralLedgerReportRequest.
  • GET /coa endpoint now returns translations for ledgerAccounts in Chart of accounts supported languages, if translations are available.
  • POST /ledgerreceipts with parameter "createReconciliation=true" now correctly rounds decimals in accountingValue that have more than 2 decimals. Receipt is now even after adding reconciliation row.
  • New attachment type REFERENCE_PAYMENT_EVENT has been added to the GET /attachments endpoint to return attachments added to the reference payment transactions/event.
  • Other

    • In API reference documentation, GET /coa now points to the correct Chart of accounts link in Procountor manual.
    • OpenAPI JSON for receiptStatus and receiptType, which had default and enum in wrong places in following models have been corrected. API documentation for those schemas have been also updated.
      • receiptStatus in
        • AccountingReportRequest
        • LedgerAccountsReportRequest
        • GeneralLedgerReportRequest
        • ReportRequest
      • receiptType in
        • AccountingReportRequestOptions
        • LedgerAccountsReportRequestOptions
        • GeneralLedgerReportRequestOptions
        • ReportRequestOptions

    Changes in version 22.10

    Endpoints

    • In POST /invoices, PUT /invoices/{invoiceId} and GET /invoices/{invoiceId} endpoints, comment in invoiceRows now supports up to 512 characters instead of 255.

    Changes in version 22.09

    Endpoints

    • POST /invoices endpoint was fixed so that a new sales invoice can be created successfully even when user has no other right than to create new sales invoice or group invoice.

    Changes in version 22.08

    Endpoints

    • We are introducing new endpoint POST /reports/ledgeraccounts to retrieve ledger accounts accounting report. This new endpoint mimics Procountor UI functionality behind Accounting -> Accounting reports (new) and Accounting report type 'Ledger accounts'. This endpoint has following limitations:
      • Date range (end date - start date) can't be more than 1 year
      • Report is presented in 'every month and total sum' format
      • Comparison data options aren't supported
      • Only handful of presentation options are supported
      • Filtering by dimensions isn't supported
    • In POST /reports/accounting endpoint, transactionValue can now be filtered with comparison symbols ( >,=>,=<, <). For example, '> 210.00'.

    Other

    • Bugs fix included in this version:
      • POST /invoices endpoint now checks if user has right to view the corresponding register if partnerId is given. If user doesn't have the required right, 403 forbidden error is returned with an appropriate error message.
      • When creating sales invoice via endpoint POST /invoices, if partnerId is given but not penaltyPercent, penalty percent is fetched from the business partner's penalInterestRate. If the business partner doesn't have penalInterestRate, sales invoice's penaltyPercent shall be set to 0,00.
      • In POST /invoices endpoint, if partnerId and penaltyPercent are missing, penaltyPercent is set from Management > Company info > Usage settings > 'Collection and penal expense settings', if it's set there. Otherwise, penaltyPercent will be set according to the country's specific general penalty percent.
      • PUT /users endpoint now checks if mobilePhone starts with prefix '+'. If it doesn't, error code 400 is returned.
      • All API requests using Webhooks that receive response transactionIdentifier will include additional confirmationApp field to indicate which application was used to confirm the transaction (FINAGO_KEY or PROCOUNTOR_KEY). In future, Finago Key will be replaced by Procountor Key as a 2-factor authentication application.
      • In POST /reports/generalledger/{id} endpoint ledgerReceiptTransactions doesn't anymore return first row with receiptDate and transactionDescription.
      • ledgerReceiptTransactions returned by POST /reports/generalledger/{id} endpoint now returns vatStatus as integer instead of string.
      • deliveryInstructions in PUT /invoices/{invoiceId}, GET /invoices/{invoiceId} and POST /invoices now supports maximum 255 chars instead of 250.

    Changes in version 22.06

    Endpoints

    • We are introducing new endpoints regarding business partner's default dimensions:
      • GET /businesspartners/{id}/defaults/dimensions to fetch the basic information on default dimensions and their items of a particular business partner.
      • GET /businesspartners/{id}/defaults/dimensions/{dimensionId} to fetch the default dimensions items for a particular business partner.
      • PUT /businesspartners/{id}/defaults/dimensions/{dimensionId} to update the dimension items percents for a particular business partner. The number of items in a dimension is unlimited but the total percent must equal to 100. Since only percent can be updated, new endpoint GET /businesspartners/{id}/defaults/dimensions/{dimensionId} can be called first to fetch the item's other details.
    • We are introducing new endpoint POST /reports/generalledger/{id} to retrieve the general ledger accounting report for a particular ledger account.
      • This endpoint has following limitations:
        • Ledger receipts are sorted by receipt number in DESC order
        • Date range (end date - start date) can't be more than 1 year
        • Filtering by dimensions, balance sheet items, balance sheet items in transactions, ledger accounts, ledger account numbers aren't supported
        • Only handful of presentation options are supported
    • We are introducing new endpoint GET /company/expenses/collectionpenal/settings to fetch the environment's collection and penal expenses settings that is available in Procountor UI under Management > Company Info > Usage settings.

    Other

    Changes in version 22.05

    Endpoints

    • New optional field invoiceOperatorInfo that contains operator and receivingAddress information have been added to InvoiceRow used in the GET /invoices/{invoiceId} endpoint for PURCHASE_INVOICE type.
    • We are introducing new endpoint GET /company/deliveryterms to view list of delivery terms allowed in invoice types PURCHASE_INVOICE, PURCHASE_ORDER, SALES_INVOICE and SALES_ORDER.
    • New optional field deliveryTermsInfo that contains name of the delivery term and municipality have been added to InvoiceRow used in the GET /invoices/{invoiceId}, POST /invoices and PUT /invoices/{invoiceId} endpoints.

    Other

    • API reference page updates:
      • The following resources names have changed
        • from Report to Reports
        • from User to Users
      • At the top of the page (just before the Servers link), OpenAPI JSON links have been added to all supported API versions

    Older release notes

    Older release notes can be found from their own page.

    Old release notes