Visma and TaxJar integration

What moves between them

The main flow runs from Visma into TaxJar and back. After Visma generates a customer invoice, ml-connector polls Visma for new invoices using the lastModifiedDateTime parameter, extracts the customer, line items, and delivery address, maps the customer's exemption profile, and POSTs the transaction to TaxJar for real-time tax calculation. TaxJar returns calculated tax by rate and jurisdiction and whether nexus is required in each location. ml-connector then creates a journal transaction in Visma with the calculated tax amount and updates the customer record with nexus status. When an invoice is credited, ml-connector sends a refund to TaxJar to adjust the reported transaction, and the refund credit posts back to Visma as a negative journal entry.

How ml-connector handles it

ml-connector stores both the Visma OAuth credentials (client_id, client_secret, tenant_id) and the TaxJar API token encrypted in its database. On the Visma side, it obtains a bearer token from https://connect.visma.com/connect/token using client credentials, includes the ipp-company-id header on every list and read call, and polls the /v1/customers and /v1/sales/invoices endpoints using lastModifiedDateTime to detect new and modified records. For each invoice, it extracts the customer, delivery address, and line items, matches the customer to TaxJar via email or customer ID, and retrieves the customer's exemption type (none, resale, government, etc.) from Visma. It then POSTs the transaction to TaxJar's /v2/taxes endpoint with the addresses, line amounts, and the customer's exemption_type, so TaxJar applies the correct rate. TaxJar responds with the calculated tax per jurisdiction and the nexus_addresses the merchant must register. ml-connector creates a journal transaction in Visma for the calculated tax (posting to a designated tax clearing account), updates the customer's Dimension record with nexus status, and tracks a record of the request and response. If the invoice is later credited in Visma, ml-connector sends a refund to TaxJar, decrementing the reported transaction so tax authorities see the net sale. Refund credits post back to Visma as negative entries on the same clearing account. Rate limits and timeouts are handled with exponential backoff, and every record carries a timestamp and audit link.

A real-world example

A Nordic software company with customers across Scandinavia and the EU sells subscription licenses and uses Visma ERP for invoicing and accounting. Before the integration, the finance team manually looked up sales tax rates for each customer in each country using spreadsheets and TaxJar's rate calculator, applied the rate manually in Visma, and then re-entered each transaction in TaxJar quarterly for compliance filing. This process was error-prone and expensive at month-end when they had to reconcile TaxJar's reported sales against Visma's ledger to find discrepancies. Now, when Visma generates an invoice, TaxJar's tax amount and nexus obligation are calculated automatically, the ledger is updated in real time, and the transactions are already in TaxJar for filing. The company can run a compliance report directly from TaxJar and compare it to Visma's tax clearing account with no rework.

What you can do

• •POST Visma customer invoices to TaxJar for real-time sales tax calculation by jurisdiction and return the calculated tax to Visma for ledger posting.
• •Map Visma customer exemption profiles (resale certificates, government, non-profit) to TaxJar so only taxable customers are taxed.
• •Track nexus status by region so Visma knows where the merchant has tax filing obligations as returned by TaxJar.
• •Report Visma invoice credits to TaxJar as refund transactions to keep reported sales in sync with actual activity.
• •Validate customer addresses against TaxJar and auto-correct incomplete or invalid addresses before tax is calculated.

Questions

Which direction do invoices and tax calculations flow between Visma and TaxJar?

Invoices flow from Visma to TaxJar for tax calculation. TaxJar returns the calculated tax amount, tax rate, and nexus obligations, which ml-connector posts back into Visma as journal entries on a tax clearing account. Invoice credits flow from Visma to TaxJar as refund reports so the state tax filing reflects the net transaction.

How does the integration handle customer exemption profiles?

ml-connector retrieves each customer's exemption type from Visma (resale, government, non-profit, or none) and includes it in the TaxJar tax request. TaxJar applies the appropriate rate rules based on the exemption_type, so customers with a resale certificate are not taxed even if they are in a taxable jurisdiction.

What happens if a customer address is incomplete or TaxJar cannot validate it?

ml-connector uses TaxJar's address validation endpoint to check each address before submitting the tax request. If the address is invalid or incomplete, ml-connector corrects it where possible using the validation response and re-submits. If the address cannot be corrected, the transaction is logged with the error so the finance team can review and fix it in Visma.