Visma and AvidXchange integration

What moves between them

Supplier invoices and purchase orders move from Visma to AvidXchange on a schedule you define, feeding the approval workflow. Once payments are executed in AvidXchange, completed payment records flow back to Visma where they are matched against the original purchase orders and invoices for reconciliation. GL accounts and dimensions are synced in both directions so coding in AvidXchange maps correctly back to Visma's chart of accounts.

How ml-connector handles it

ml-connector obtains an OAuth 2.0 bearer token from Visma's Connect endpoint using your client credentials and tenant ID, then presents that token on all Visma API calls. It polls Visma for new and modified invoices and purchase orders using the lastModifiedDateTime query parameter, extracting supplier details, line-item amounts, and GL dimensions from each record. On the AvidXchange side, it uses your partner API credentials to post those invoices and orders into AvidXchange's approval workflow, mapping Visma's suppliers and GL codes to AvidXchange's vendor and dimension tables. After payment execution in AvidXchange, ml-connector pulls completed payment records back to Visma and creates journal transactions for reconciliation, mapped to the original purchase receipts. Because Visma webhooks are one-time delivery only and lack automatic retry, ml-connector relies on polling to ensure no records are missed, with exponential backoff on network errors. The integration tracks the lastModifiedDateTime of each sync cycle so it resumes from where it left off if a connection drops.

A real-world example

A mid-sized manufacturing company uses Visma for accounting and purchasing, and recently deployed AvidXchange to streamline AP approval and gain better payment visibility. Before integration, the AP team exported invoice extracts from Visma, manually entered them into AvidXchange for routing, and then waited for approvals before processing payments. With Visma and AvidXchange connected, new invoices and orders flow automatically from Visma into AvidXchange's approval workflow, eliminating manual data entry. Once payments are approved and executed in AvidXchange, they sync back to Visma automatically for reconciliation against the original purchase orders, cutting the time to close the AP cycle and reducing keying errors.

What you can do

• •Sync supplier invoices and purchase orders from Visma to AvidXchange on a schedule you define.
• •Map Visma GL accounts and cost dimensions to AvidXchange GL codes so invoices code correctly in the approval workflow.
• •Pull completed payments from AvidXchange back to Visma and create reconciliation journal transactions.
• •Handle Visma OAuth 2.0 authentication and AvidXchange partner API credentials, with token refresh on expiry.
• •Poll Visma for new and modified records using lastModifiedDateTime, retrying on network errors.

Questions

Which records move between Visma and AvidXchange?

Supplier invoices, purchase orders, and the vendor and GL dimension reference data move from Visma into AvidXchange for approval routing and payment processing. Once payments are executed in AvidXchange, completed payment records flow back to Visma where they are matched to the original purchase orders and invoices for reconciliation.

How does ml-connector handle Visma's lack of reliable webhooks?

Because Visma webhooks are one-time delivery only and lack automatic retry, ml-connector polls Visma for new and modified records using the lastModifiedDateTime query parameter on each sync cycle. This ensures no invoices or orders are missed, even if a webhook notification is lost.

How are GL accounts and dimensions mapped between the two systems?

ml-connector pulls the GL account and dimension tables from Visma and syncs them to AvidXchange so that when invoices are coded in AvidXchange's approval workflow, the GL codes and dimensions are valid in Visma. Mapping rules match Visma dimension values to corresponding AvidXchange dimensions based on the configuration you provide.