Pipedrive for US companies with European teams and entities

Start with the structure, one account in three layers

The mistake we are called in to repair most often is a second Pipedrive account for the European team. It feels clean for a month. Then group reporting needs a spreadsheet, a customer who buys in both regions exists twice, and every automation has to be built and maintained in two places.

Keep one account and put the differences in three layers on top of it. The account holds the pipelines, stages and fields everybody shares. The entity layer says which legal entity invoices a deal and in which currency. The country layer drives tax inputs, consent rules, language and ownership. The table below is the whole design in one view.

The US rollout of the same account is covered on the page about Pipedrive implementation in the United States. If you are building both at once, design the shared layer first and the two market layers second. It is the cheapest order.

VAT is one framework, and it still lands in your fields

In the United States the question is nexus: whether your business has enough of a connection to a state to owe sales tax there. Europe replaces that with a different one. VAT is a shared framework across the member states, so the rules travel with you, but the rate is set nationally and the treatment depends on who is buying. Sell across a border to another business and the tax usually shifts to the buyer, provided their VAT number is valid. Sell across a border to consumers and the one-stop-shop regime lets you register in one member state and declare there instead of registering in every country you sell into.

The design decision is the same subtraction we make for sales tax. A rate stored in a CRM field goes stale quietly and nobody finds out until an accountant does. So we keep rates out of Pipedrive and configure the inputs the invoicing chain needs: the buyer's country on the organization, the VAT number in its own field with a validity check rather than free text, a business or consumer flag, and the entity that will invoice. Deal value is the pre-tax amount, always, because forecasting and commission read that number. The cross-border treatment is then a consequence of those fields, not something a rep ticks by hand at the end of the month. Where quotes carry line items, the products catalog has to line up with the invoicing tool before the first record moves.

GDPR, in the terms a US sales team needs

You do not need to read the regulation to run the CRM side of it. You need to answer five practical questions, and the answers become fields and routines.

• Which records are in scope. A country field on every person and organization, required at creation, so you can find everyone in the EU or the UK with one filter.
• On what basis you hold them. A lawful basis and a source on the record, written at intake. A contact imported from a conference list and a contact who asked for a demo are different, and the CRM should say which is which.
• Who processes the data. Pipedrive acts as a processor and offers a standard data processing agreement. Every connected app and automation tool is another processor, and an inventory of them belongs next to your records of processing.
• How long you keep it. A retention rule for prospects that never converted, enforced by a scheduled deletion routine rather than by intention.
• How you answer a request. A way to find every record that belongs to one person, export it and erase it, with the date and outcome logged.

Transfers are the part US teams ask about first. Personal data moving from the EU to the United States needs a recognized mechanism, such as the standard contractual clauses or, for companies that have certified, the EU-US Data Privacy Framework. Which one applies depends on your vendors and your own status, and it is a legal question. We are a CRM firm and not your counsel, so nothing here is legal advice. What we build is the structure that makes your counsel's answer enforceable in the system. The routines are described in our data hygiene guide, and visibility in the permissions guide.

Where the data sits, and who asks about it

European buyers ask two questions in every software review: where does the data live, and is there a data processing agreement. Pipedrive stores EU customer data in the EU and offers a standard processing agreement, and for most companies that closes the subject in an afternoon. Check the current terms for your own account rather than relying on a summary, including ours. Public sector organizations and their suppliers sometimes push further, toward national sovereignty requirements. A mainstream SaaS CRM does not become a national sovereign cloud, and it is better to say that in week one than to discover it in contract review.

Inside your own configuration, two decisions matter most. Make a deliberate choice about email sync, because syncing every mailbox company wide is how private correspondence ends up in a shared system. And set visibility groups that match the org chart instead of good intentions, so a US salesperson does not see European personal data they have no reason to touch.

One pipeline, several languages

This is the part a US team underestimates. Every Pipedrive user picks their own interface language, which solves nothing, because the configuration is shared. Pipelines, stages, field names and automations exist once for everybody. That layer cannot split, and a bilingual attempt at it breeds duplicate fields, and duplicate fields breed reports that disagree with each other.

So we pick one language for the shared layer and write it down as a convention. Any team that crosses a border builds it in English. A team selling only in its own country, in its own language, can build in that language, and in France that is not a preference: a domestic French team handed an English configuration is a team that stops using the CRM. The customer-facing layer is where the movement belongs. A preferred language field on every person and organization, required at creation, templates and quote documents per language, and automations that pick the right version. Budget that template work honestly, because the alternative, a French-speaking customer receiving a Dutch follow-up, costs deals without ever showing up as a complaint. The naming discipline that keeps it manageable is in custom fields that earn their place.

Currencies, price lists and the reporting currency

A European entity usually invoices in euros, pounds or a Nordic currency, and your board reads dollars. Both can be true in one account if you decide three things before the first deal. The deal carries the currency the customer is invoiced in. The company has one reporting currency. And one person owns the exchange rate source and the date it is applied.

Without those three, a dashboard moves with the market instead of with the pipeline, and the forecast changes between Monday and Friday for reasons nobody in sales can explain. Price lists follow the same logic: one product catalog, a price per currency, and the legal entity that sells it. That is also the moment to look at the forecast definition, because currency is where forecasts quietly disagree.

E-invoicing arrives country by country

Structured e-invoicing is being made mandatory in one European country after another, each on its own timetable, with the Peppol network as the common layer underneath. Belgium is the concrete case: structured e-invoicing between VAT-registered businesses has been mandatory there since 1 January 2026, over Peppol. Other countries are moving the same way on their own schedules. There is no federal equivalent in the United States, where a PDF attached to an email is still normal, so a US company opening a European entity tends to meet this after the CRM is built rather than before.

The rule for the CRM project is short and it does not bend. Pipedrive is not a Peppol Access Point and it is not an invoicing package. Pipedrive supplies the deal data. The invoicing package builds the structured invoice. The Access Point sends it. That means the deal to invoice link has to end at a package that is genuinely connected, and a custom invoice generator bolted onto the CRM is not one. Get that decision made in the blueprint, because moving the invoicing endpoint after go-live means rebuilding the handoff, the product mapping and every template that hangs off it.

The books are local, and there are a lot of them

In the United States the accounting answer is usually QuickBooks, with NetSuite taking over once a business adds entities, inventory or revenue recognition. Europe has no equivalent single answer, and this is the difference that costs the most budget when it is discovered late. The Netherlands runs on Exact Online and Moneybird, with AFAS upmarket. The United Kingdom belongs to Xero, with Sage and QuickBooks alongside it. German companies invoice from tools such as Lexoffice or sevdesk, which then feed the tax adviser's DATEV environment. France works with Pennylane, Sellsy and Axonaut. The Nordics split four ways again: Fortnox and Visma in Sweden, e-conomic in Denmark, Tripletex and PowerOffice in Norway, Netvisor and Procountor in Finland.

A group selling in several European countries therefore runs one CRM account above several accounting environments, one per legal entity, with the handoff routed by the country field. The integration boundary stays identical whichever package sits on the other side. Pipedrive owns the opportunity: contact, products quoted, value, close date, forecast. The accounting package owns the invoice: tax calculated, payment status, credit notes. Push one way on win, read payment status back onto the deal as a read only field, and match on the accounting customer ID written onto the organization rather than on the company name, which drifts. Getting that mapping to hold across a border is where the work sits, and it is work we do with a small, boring automation or purpose-built middleware around whichever package you already run.

Working across the Atlantic

Two practical differences show up in the first month. The first is time. Eastern time and central Europe overlap in the US morning, and Pacific time and Europe barely overlap at all. Build the follow-up rules, the lead routing and the meeting hours around that overlap instead of around head office. Our own time zone guidance for US teams is on the United States page, and the same logic applies in reverse.

The second is outreach. The US model for email is largely opt-out under CAN-SPAM. Several European countries require prior consent even for business email, with Germany the usual example, and the rules for calls and texts differ again. A campaign template that works in Texas cannot be pointed at Berlin by changing the language. Store the consent state per person and per channel, and let the automation read it before it sends, as we describe in the outbound guide.

Where we publish in your own language

For three markets we do not write in English at all, because the buyers there do not read the language of the decision in English. That is where the depth lives, and it goes further than an English overview can.

• pipedrive-implementatie.be: Belgium, in Dutch and in French. The two language communities, the Peppol mandate, the local invoicing chain and the partner question.
• pipedriveimplementatie.nl: the Netherlands, in Dutch. Exact Online and Moneybird, migration routes, the privacy expectations Dutch buyers actually raise.
• pipedrive-implementatiepartner.nl: also Dutch, and specifically about choosing an implementation partner rather than about the tool.

The honest half of that list is what is missing from it. For the United Kingdom, France, Germany and the Nordics we work in English, and there is no site in the local language and no local delivery team. English is no obstacle in the UK or the Nordics. In Germany and France it can be, and a domestic team that needs German or French workshops and documentation should say so on the first call. We would rather tell you we are the wrong partner than find it out together in month three. The general framework for that decision is in how to choose an implementation partner and the implementation cost guide.

Who we are, and when not to call us

PipeDriven is powered by Sales Surge, and Sales Surge works out of the Netherlands. We are a Pipedrive Platinum Partner and a top 8 Pipedrive partner worldwide as of July 2026. We build the CRM, the migration and the integrations, and where the standard product stops we build the missing part ourselves rather than hand you a list of things it cannot do. That includes European work: we are in the same time zone as your European team, and you can see how a project runs on how we work and what clients say on the reviews page. More about the firm is at www.sales-surge.io.

The honest boundary: you do not need us if you sell in one country, in one currency, from one entity, in one language, with a mainstream accounting package. That is a week of careful configuration and Pipedrive's own onboarding will get you most of the way. Call us when the borders start multiplying. Several entities with several invoicing chains, a migration carrying history you cannot afford to lose, a language line running through the middle of the sales team, or an integration nobody sells off the shelf.

Last reviewed: October 2026.