Visma and Pipedrive integration

What moves between them

Suppliers from Visma flow into Pipedrive as organizations. Visma supplier invoices are read periodically and appended as notes or activities on the corresponding Pipedrive organization. Visma customers and their invoices flow into Pipedrive deals and persons, with invoice totals and dates visible to the sales team. The sync runs on a schedule you configure, typically daily or after each Visma invoice post. Reference data such as customer status and payment terms align in both directions where supported by Pipedrive custom fields.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Visma side it uses OAuth2 client credentials with the tenant-specific company ID to obtain bearer tokens, and it polls the Visma API for supplier and invoice updates using lastModifiedDateTime as a delta marker so only new and changed records are fetched. On the Pipedrive side it either uses OAuth2 with token refresh or API token auth, and it handles the HMAC-SHA256 signature verification on inbound webhooks. When a new Visma supplier is detected, ml-connector creates or updates a Pipedrive organization with the supplier name and code; when a Visma customer invoice is created, ml-connector creates or links a Pipedrive deal and appends the invoice details as a note or linked activity. Pipedrive's custom fields and opaque field hashes are resolved via field definition queries so invoice amounts and due dates land in the right fields. Rate limits on both sides are respected with exponential backoff on 429 responses.

A real-world example

A regional B2B service company uses Visma.net for accounting and supplier invoice management, and Pipedrive for customer pipeline tracking. Before the integration, the sales team received no visibility into customer payment patterns or invoice history in Pipedrive; they tracked balances in spreadsheets and emails from finance. With Visma and Pipedrive connected, each customer invoice automatically appears as a note on the deal in Pipedrive, and the sales team can see at a glance which customers have open invoices, who is paying late, and what products they ordered. This reduces the need for finance to chase sales for customer payment context, and sales can factor payment history into renewal or expansion conversations.

What you can do

• •Sync Visma suppliers to Pipedrive organizations, keeping vendor master data visible in your CRM.
• •Post Visma customer invoices as notes or activities on Pipedrive deals, giving sales full financial visibility.
• •Map Visma customer records to Pipedrive persons, aligning customer master data across both systems.
• •Handle Visma OAuth2 client credentials and Pipedrive webhook signature verification automatically.
• •Poll Visma for invoice updates on a schedule you control, with exponential backoff on rate limits.

Questions

Which direction does data move between Visma and Pipedrive?

The main flow is from Visma into Pipedrive. Suppliers become organizations, customer invoices appear as deal notes or activities, and customer records become persons in Pipedrive. Pipedrive is a CRM and has no native invoices or GL accounts, so financial data flows one direction only. Reference data such as customer status and terms can be aligned in both directions via custom fields.

How does ml-connector handle Visma's webhook limitations?

Visma webhooks have one-time delivery and no automatic retry, and they must be enabled at the company level for each entity. ml-connector uses polling with lastModifiedDateTime as a fallback to ensure no invoice or supplier record is missed, and it can also listen for Visma webhooks where they are enabled to accelerate the sync.

Does ml-connector resolve Pipedrive's custom field hashes?

Yes. Pipedrive custom fields are exposed as opaque hashes in the API response, so ml-connector queries the field definition endpoints (/v1/dealFields, /v1/personFields, etc.) to map invoice amount and due date fields to the correct custom field IDs before writing to Pipedrive.