Fintax Support Limited

Odoo ERP Services in Europe

European businesses deploying Odoo ERP need configuration for IFRS accounting, multi-jurisdiction EU VAT with OSS reporting, GDPR-compliant data handling, and multi-language interfaces across member states.

Europe
EU Member State Tax Authorities Compliant
10 Specialized Services

European businesses deploying Odoo ERP need configuration for IFRS accounting, multi-jurisdiction EU VAT with OSS reporting, GDPR-compliant data handling, and multi-language interfaces across member states. Fintax Support Limited implements Odoo for European companies and groups, setting up VAT tax codes per member state, OSS sales tracking, and intercompany modules for transfer pricing. We deploy on EU-hosted cloud infrastructure ensuring GDPR data residency requirements.

Odoo ERP services in Europe

Regulatory Framework

Odoo deployments in Europe must implement GDPR technical measures including data encryption, access controls, right-to-erasure workflows, and data processing agreements with subprocessors. VAT modules must handle varying rates across 27 EU member states and OSS reporting for cross-border B2C sales exceeding EUR 10,000.

EU Member State Tax Authorities

Our Odoo ERP Services in Europe

Odoo Implementation for Multi-Country EU Operations

Deploy Odoo ERP from discovery through go-live with a phased rollout designed for businesses operating across multiple EU member states. We configure Accounting, Sales, Inventory, and HR modules on Odoo Enterprise β€” hosted on EU data centres β€” with country-specific localisations, fiscal positions, and multi-company structures mapped to your cross-border operational workflows from day one.

Multi-company EU architecture

Separate legal entities for DE, NL, FR, and IT configured under a consolidated Odoo instance with inter-company rules.

Legacy ERP migration

Historical transactions, open balances, and customer records migrated from SAP, DATEV, or local accounting tools with trial balance validation.

Country localisation scoping

Odoo Enterprise localisation modules selected per entity β€” German SKR03, French PCG, Dutch RGS, and Italian civil code charts.

EU data residency compliance

Production instances hosted on EU cloud infrastructure with GDPR-aligned access controls and audit logging from deployment.

How It Works

1

Discovery and entity mapping

Document legal entities, VAT registrations, payroll jurisdictions, and cross-border workflows across EU operating countries.

2

Multi-company system design

Configure Odoo companies, fiscal positions, inter-company rules, and country localisation modules per approved architecture.

3

Data migration and UAT

Migrate historical data per entity, validate trial balance tie-outs, and run user acceptance testing across country teams.

4

Phased go-live and hypercare

Roll out by entity or module with EU timezone hypercare support during the first 30 days of production operations.

Our end-to-end Odoo implementation follows a structured methodology tailored to multi-country EU businesses β€” from single-group manufacturers with warehouses in Germany, the Netherlands, and Poland to service companies with entities in France and Italy. We evaluate Odoo Enterprise localisation modules per jurisdiction: German SKR03 chart of accounts with DATEV export, French Plan Comptable GΓ©nΓ©ral with bulletins de paie, Dutch RGS with vakantiegeld accruals, and Italian civil code with TFR provisions. Multi-company architecture uses inter-company transaction rules so stock transfers between DE and NL warehouses post automatically to both entities' general ledgers. Fiscal positions handle intra-EU B2B reverse charge, OSS eCommerce VAT, and third-country import scenarios without manual tax reclassification. Deployments run on EU-hosted infrastructure β€” Frankfurt, Amsterdam, or Paris regions β€” for GDPR data residency and low-latency access across member states. Data migration from SAP Business One, Microsoft Dynamics, or country-specific tools includes chart of accounts mapping, open AR/AP balances, and inventory valuations validated against last filed corporate tax returns. Phased rollouts typically span 12 to 20 weeks, starting with Accounting and Inventory in the primary entity before adding payroll, CRM, and eCommerce connectors across remaining countries.

Common Questions

Multi-Country VAT Configuration

Configure Odoo VAT with country-specific tax rates, fiscal positions, and intra-EU reverse charge rules across your operating member states. Multi-country VAT setup in Odoo handles domestic rates, OSS eCommerce reporting, EC Sales Lists, and Intrastat declarations β€” ensuring quarterly and monthly filings reconcile with general ledger tax accounts in each jurisdiction.

Country VAT rate mapping

Standard, reduced, and super-reduced rates configured per member state β€” DE 19%/7%, FR 20%/5.5%, NL 21%/9%, IT 22%/10%.

Fiscal positions automation

Intra-EU B2B reverse charge, export zero-rating, and OSS eCommerce rules applied automatically via fiscal positions.

EC Sales List and Intrastat

Cross-border supply tracking with EC Sales List and Intrastat report generation from Odoo transaction data.

Multi-entity VAT reconciliation

Per-company VAT return boxes reconciled against Odoo trial balance before submission to national tax authorities.

How It Works

1

VAT registration and scheme review

Confirm VAT numbers, MOSS/OSS obligations, and filing calendars for each EU entity and operating jurisdiction.

2

Tax and fiscal position setup

Map VAT rates to products and accounts, configure fiscal positions for intra-EU, domestic, and third-country scenarios.

3

Cross-border reporting configuration

Enable EC Sales List, Intrastat, and OSS return templates per entity with automated data extraction from Odoo.

4

Return testing and team training

Reconcile first VAT period against Odoo records, validate fiscal position behaviour on test transactions, and train finance teams.

EU VAT compliance requires precise handling of domestic rates, intra-Community supplies, and fiscal positions that reclassify tax automatically based on partner country and VAT number validation via VIES. Odoo fiscal positions map B2B intra-EU transactions to reverse charge accounts β€” shifting VAT liability from supplier to customer without manual journal adjustments. OSS eCommerce configuration applies destination-country VAT rates on B2C distance sales above the €10,000 threshold, with quarterly OSS returns generated from Odoo eCommerce order data. We configure country-specific tax reports: German UStVA, French CA3/CA12, Dutch BTW-aangifte, and Italian LIPE β€” each reconciled against Odoo VAT summary accounts before filing. EC Sales Lists aggregate cross-border B2B supplies by customer VAT number for monthly or quarterly submission. Intrastat declarations for goods movements between DE, NL, and PL warehouses track statistical value and commodity codes from Odoo delivery orders. Fiscal positions also handle post-Brexit GB imports, triangular transactions, and call-off stock arrangements per EU VAT Directive guidance.

Common Questions

SEPA Payment Integration

Integrate Odoo Accounting with SEPA Credit Transfer (SCT) and SEPA Direct Debit (SDD) workflows using ISO 20022 pain.001 and pain.008 file formats. SEPA payment integration in Odoo automates supplier batch payments, customer direct debit collections, and bank reconciliation across EUR accounts held with European banking partners.

SEPA SCT batch payments

Supplier payment batches exported as pain.001 XML files for upload to your bank's SEPA Credit Transfer portal.

SEPA SDD collections

Customer direct debit mandates managed in Odoo with pain.008 collection files generated per SDD Core scheme rules.

IBAN and mandate validation

IBAN format checks, mandate reference tracking, and creditor identifier (CI) configuration per SEPA scheme requirements.

Multi-entity bank reconciliation

EUR bank statement imports reconciled against SCT payments and SDD collections per company entity in Odoo.

How It Works

1

Banking and scheme review

Confirm SEPA participant status, creditor identifiers, IBAN accounts, and bank file format requirements per entity.

2

Payment method configuration

Configure SCT outbound and SDD inbound payment methods in Odoo with pain.001 and pain.008 export templates.

3

Mandate and vendor setup

Register SDD mandates on customer records, validate vendor IBANs, and configure payment approval workflows.

4

Payment run testing and go-live

Process test SCT and SDD batches, validate bank acceptance, and reconcile first production payment run in Odoo.

SEPA payment integration eliminates manual bank portal entry for EUR supplier payments and customer collections across EU entities. Odoo generates pain.001 XML files for SCT batch payments β€” aggregating approved vendor bills into a single file uploaded to your bank's corporate banking portal for same-day or next-day settlement. SEPA Direct Debit collections use pain.008 format under the SDD Core scheme, with mandate references, creditor identifiers, and sequence type (FRST, RCUR, OOFF, FNAL) tracked on customer records in Odoo. We configure IBAN validation on partner bank accounts, payment date scheduling aligned with D+1 SCT settlement cycles, and multi-entity payment batches where each company exports separate pain.001 files from its own EUR bank account. Bank statement imports via CAMT.053 reconcile SCT outflows and SDD inflows against Odoo payment records automatically. Payment approval workflows enforce dual-authorisation on batches exceeding configured thresholds β€” meeting internal control requirements for cross-border EUR disbursements to suppliers in DE, NL, FR, and PL.

Common Questions

Multi-Language & Multi-Currency Setup

Configure Odoo with EUR as group reporting currency alongside local currencies and full multi-language support for EU teams operating across member states. Multi-language and multi-currency setup in Odoo handles ECB exchange rate feeds, translated user interfaces, and consolidated financial reporting in EUR for group management accounts.

EU language localisation

User interfaces, reports, and document templates translated in DE, FR, NL, IT, PL, and EN for cross-border teams.

EUR and local currency setup

Entity base currencies β€” EUR, PLN, GBP β€” with ECB daily rate feeds and automated exchange difference posting.

Consolidated EUR reporting

Group management accounts in EUR with entity-level trial balances translated at closing rates.

Unrealised gain/loss revaluation

Month-end revaluation of open foreign currency balances with automated journal entries per entity.

How It Works

1

Language and currency review

Identify user language preferences, entity base currencies, and group reporting currency requirements across EU operations.

2

Localisation and rate feed setup

Install language packs, configure ECB exchange rate feeds, and set entity base currencies with translation rules.

3

Document template translation

Translate invoice, quotation, and delivery order templates per entity language with correct VAT label localisation.

4

Consolidation testing and validation

Process test transactions in multiple currencies, validate EUR consolidation reports, and confirm language switching per user.

EU businesses operating across member states need Odoo configured for both linguistic and monetary diversity. We install language packs for German, French, Dutch, Italian, Polish, and English β€” allowing each user to operate in their preferred language while sharing a single database. Entity base currencies reflect local registration: EUR for DE, NL, FR, and IT entities, PLN for Polish operations, with EUR as group consolidation currency. ECB daily exchange rate feeds update automatically, with manual override capability for locked-period adjustments. Customer invoices and supplier bills raised in foreign currencies convert at transaction date rates, with realised exchange differences posted on payment receipt under local GAAP rules. Month-end revaluation runs on open foreign currency receivables and payables per entity, posting unrealised gains and losses before management accounts close. Consolidated EUR reporting translates entity trial balances at closing rates for group P&L and balance sheet dashboards. Document templates β€” invoices, delivery notes, purchase orders β€” are translated per entity with country-specific VAT labels, legal footnotes, and payment terms in the local language.

Common Questions

Country-Specific Payroll Configuration

Configure Odoo Payroll with country-specific localisation modules covering German Lohnsteuer, French bulletins de paie, Dutch vakantiegeld, and Italian TFR provisions. Accurate multi-country payroll in Odoo posts journal entries to each entity's general ledger and supports statutory filing workflows aligned with national social security and tax authority requirements.

German Lohnsteuer setup

Income tax calculated per ELStAM data with Lohnsteuerklassen I–VI, SolidaritΓ€tszuschlag, and Kirchensteuer deductions.

French bulletins de paie

Payslip templates compliant with French labour code requirements including cotisations sociales and net Γ  payer.

Dutch vakantiegeld accrual

Holiday allowance accrued at 8% of gross salary with May payout scheduling and loonheffing withholding.

Italian TFR provisions

Trattamento di fine rapporto accrued monthly with severance liability posted to Odoo general ledger.

How It Works

1

Payroll jurisdiction mapping

Document employee assignments, social security registrations, and payroll provider relationships per EU entity.

2

Country payroll module configuration

Configure l10n_de_hr_payroll, l10n_fr_hr_payroll, l10n_nl_hr_payroll, and l10n_it_hr_payroll modules per entity.

3

Salary structure and GL mapping

Define salary rules, deduction types, and chart of accounts mapping for payroll journal entries per country.

4

Payroll run testing and go-live

Process test payroll runs, validate payslips against national calculators, and go live with first production pay period.

EU payroll requires jurisdiction-specific handling that Odoo Enterprise localisation modules address per country. German payroll configures Lohnsteuer per ELStAM electronic tax data with Steuerklassen I through VI, SolidaritΓ€tszuschlag, and Kirchensteuer where applicable β€” posting employer and employee Sozialversicherung contributions to DE entity GL accounts. French bulletins de paie are generated with mandatory cotisations sociales lines, net imposable, and net Γ  payer per Code du travail formatting requirements. Dutch payroll accrues vakantiegeld at 8% of gross annual salary with May payout scheduling, loonheffing withholding, and pension premium calculations per Wet op de loonbelasting. Italian TFR (Trattamento di fine rapporto) accrues monthly at approximately 7.41% of gross salary plus revaluation, with severance liability tracked on employee records and posted to provision accounts. We configure salary structures, pay schedules, and GL account mappings per entity so payroll journals reconcile with social security filings β€” DEUV for Germany, DSN for France, loonaangifte for the Netherlands, and UniEmens for Italy.

Common Questions

Inventory & Warehouse Management (Multi-Location EU)

Deploy Odoo Inventory for multi-warehouse EU fulfilment across DE, NL, and PL locations with real-time stock tracking, lot and serial number traceability, and automated COGS posting per entity. Multi-location inventory in Odoo supports inter-warehouse transfers, Intrastat reporting, and consolidated group stock visibility for cross-border supply chain operations.

Multi-warehouse DE/NL/PL network

Stock tracked across German, Dutch, and Polish warehouses with inter-warehouse transfer workflows and route rules.

Cross-border receiving and shipping

Purchase receipt, pick-pack-ship, and delivery order workflows with Intrastat data captured on EU transfers.

Entity-level COGS posting

FIFO or average cost valuation with automated COGS entries posted to the correct entity general ledger.

Group stock visibility

Consolidated inventory reports across all EU warehouse locations with reorder rules and demand forecasting.

How It Works

1

Warehouse network design

Define warehouse locations in DE, NL, and PL, internal routes, storage zones, and picking strategies for EU fulfilment.

2

Product and costing configuration

Set up products with lot/serial tracking, units of measure, barcodes, and costing method per entity policy.

3

Inter-warehouse workflow setup

Configure transfer routes between DE, NL, and PL warehouses with Intrastat fields and inter-company billing rules.

4

Go-live and cycle count programme

Launch inventory operations with initial stock load per warehouse, barcode deployment, and recurring cycle count schedule.

Odoo Inventory provides EU businesses with real-time stock visibility across warehouse networks spanning Germany, the Netherlands, and Poland. We configure warehouse locations per entity β€” DE warehouse under the German company, NL hub under the Dutch entity, PL distribution centre under the Polish company β€” with inter-warehouse transfer routes that trigger inter-company billing and Intrastat declarations automatically. Costing methods β€” FIFO or weighted average β€” are set per entity to match local GAAP requirements, with automated COGS entries posting when delivery orders are validated in each jurisdiction. Lot and serial number tracking supports EU product safety regulations, electronics warranty management, and recall traceability across borders. Reorder rules with lead time and safety stock calculations prevent stockouts during peak EU retail seasons β€” accounting for cross-border transit times between DE, NL, and PL locations. Barcode scanning via Odoo Mobile accelerates receiving and picking in warehouse operations. Cycle count schedules maintain inventory accuracy above 98% per location β€” the threshold most EU auditors expect before relying on perpetual inventory records in statutory accounts.

Common Questions

CRM & Sales Pipeline Setup

Implement Odoo CRM with EU sales stages, automated lead routing by territory, quotation workflows with multi-country VAT, and commission tracking integrated directly to Accounting. A configured CRM pipeline gives cross-border sales teams visibility into revenue forecasts that feed group management reporting and entity-level tax planning.

Territory-based lead routing

Leads assigned automatically by country, language, or product line across DE, FR, NL, IT, and PL sales teams.

Multi-country quotation flow

Quotes convert to sales orders with fiscal position VAT calculation and automatic invoice generation on delivery.

Pipeline forecasting dashboards

Pipeline value, win rate, and weighted forecast reports in EUR for group management and entity-level planning.

Multi-language CRM interface

Sales teams operate in local language with translated email templates and quotation documents per market.

How It Works

1

Sales process mapping

Document EU sales workflow β€” lead sources, qualification criteria, stages, and handoff points β€” before CRM configuration.

2

Pipeline and automation setup

Configure CRM stages, territory-based lead assignment, email templates, and activity schedules per sales team.

3

Quotation and pricing integration

Connect CRM to Sales module with price lists, discount rules, fiscal positions, and approval workflows for quotes.

4

Team training and dashboard launch

Train sales teams on Odoo CRM, deploy KPI dashboards, and integrate with marketing automation if applicable.

Odoo CRM replaces standalone tools for EU businesses that want sales data flowing directly into Accounting without manual re-entry across entities. We configure pipeline stages matching your sales process β€” lead, qualified, proposal, negotiation, won/lost β€” with probability percentages for weighted revenue forecasting in EUR. Automated lead assignment routes inbound leads by territory: DACH region to German reps, Benelux to Dutch team, Southern Europe to Italian and French reps. Quotation workflows generate branded PDF quotes in the customer's language with VAT calculated via fiscal positions β€” domestic rates, intra-EU reverse charge, or OSS eCommerce rates as applicable. Quotes convert to sales orders on customer approval and trigger invoice creation on delivery validation, posting revenue to the correct entity. Commission tracking rules calculate rep commissions on confirmed orders, posting accruals to Odoo Accounting per entity. Gmail and Outlook integrations log emails and calendar events against CRM records automatically. Pipeline forecast reports give directors visibility into expected revenue by country and month β€” data useful for group cash flow planning and entity-level corporate tax provisioning.

Common Questions

eCommerce Integration

Connect EU eCommerce platforms β€” Shopify, WooCommerce, and Amazon EU marketplaces β€” to Odoo for automated order import, inventory synchronisation, and OSS VAT-compliant revenue reconciliation. Multi-channel eCommerce integration eliminates manual data entry, ensures fiscal position VAT posts correctly per destination country, and produces clean revenue records for national tax authority reporting.

Shopify and WooCommerce sync

Orders, products, customers, and inventory synced bidirectionally via REST API with multi-store EU configuration.

Amazon EU marketplace integration

Amazon DE, FR, IT, ES, and NL orders imported via SP-API with FBA inventory and settlement report reconciliation.

Multi-channel inventory sync

Stock levels updated across all EU sales channels from Odoo warehouse locations in DE, NL, and PL.

OSS VAT on eCommerce orders

Destination-country VAT applied via fiscal positions on imported orders for OSS quarterly return compliance.

How It Works

1

Channel and product mapping

Map products, SKUs, and variant attributes between Odoo and each EU eCommerce platform with pricing rules per market.

2

Connector installation and configuration

Install Shopify, WooCommerce, and Amazon SP-API connectors with credentials, webhooks, and sync schedules.

3

Order and VAT workflow testing

Test order import, fulfilment export, inventory sync, and OSS fiscal position VAT calculation across all channels.

4

Go-live and reconciliation setup

Enable live sync, configure payment settlement reconciliation, and train team on multi-channel EU order management.

EU eCommerce businesses selling across multiple marketplaces need unified order and inventory management in Odoo to avoid overselling, manual entry errors, and OSS VAT compliance gaps. Shopify and WooCommerce integrations import orders with line items, customer data, and shipping details β€” triggering Odoo delivery orders from the correct DE, NL, or PL warehouse with fiscal position VAT at destination-country rates for B2C OSS-eligible sales. Amazon SP-API syncs EU marketplace orders β€” DE, FR, IT, ES, NL β€” with FBA inventory levels and settlement reports including fee breakdowns for accurate net revenue recording per entity. Multi-channel inventory updates prevent overselling β€” when stock changes in Odoo from a warehouse receipt or inter-warehouse transfer, all connected channels update simultaneously. Platform fees, FBA charges, refunds, and chargebacks post to separate GL accounts for accurate entity-level P&L and corporate tax reporting. OSS eCommerce VAT is applied via fiscal positions on imported B2C orders, with quarterly OSS return data extracted from Odoo sales reports by destination country.

Common Questions

GDPR-Compliant Data Handling Setup

Configure Odoo with GDPR-aligned data handling controls covering personal data retention, right to erasure under Article 17, and records of processing under Article 30. GDPR-compliant setup in Odoo ensures EU customer, employee, and partner data is managed with appropriate access controls, audit trails, and data subject request workflows.

Article 17 right to erasure

Data anonymisation workflows for customer and contact records when erasure requests are received under GDPR.

Article 30 processing records

Documentation of personal data categories, processing purposes, and retention periods maintained per GDPR requirements.

Role-based access controls

User groups and record rules restrict personal data visibility β€” HR records isolated from sales and warehouse teams.

EU data residency hosting

Production instances hosted on EU cloud infrastructure with encryption at rest and in transit configured.

How It Works

1

Data inventory and mapping

Identify personal data fields across CRM, HR, Accounting, and eCommerce modules with processing purpose documentation.

2

Access control configuration

Configure user groups, record rules, and field-level restrictions to limit personal data access per role.

3

Retention and erasure workflows

Set data retention policies, configure anonymisation procedures for Article 17 requests, and document Article 30 records.

4

Audit logging and team training

Enable access audit trails, train data handlers on GDPR procedures, and establish data subject request response workflows.

GDPR compliance in Odoo requires deliberate configuration beyond default settings β€” particularly for businesses processing personal data across multiple EU jurisdictions. We configure role-based access controls so warehouse staff cannot view employee HR records, sales reps see only their assigned contacts, and payroll data is restricted to authorised HR administrators. Article 17 right to erasure workflows anonymise customer and contact records on approved requests β€” replacing personal identifiers with pseudonymised placeholders while preserving transactional integrity for accounting and tax audit requirements. Article 30 records of processing document each personal data category stored in Odoo β€” CRM contacts, employee records, portal users, eCommerce customers β€” with processing purpose, legal basis, retention period, and recipient categories. Data retention policies automate archival of inactive CRM leads and expired employee records after configured periods. EU data residency is enforced through hosting on Frankfurt, Amsterdam, or Paris cloud regions with TLS encryption in transit and database encryption at rest. Audit logging tracks access to sensitive personal data fields, supporting GDPR accountability obligations and Data Protection Authority inquiry responses.

Common Questions

Odoo Training, Support & Maintenance

Provide EU timezone support, role-based user training on Odoo 17/18, and managed version upgrades that keep your ERP current without disrupting accounting periods across member states. Post-go-live assistance covers multi-entity month-end close workflows, VAT filing season readiness, and ongoing configuration as your EU operations scale.

Role-based user training

Training sessions tailored to accounting, sales, warehouse, and management roles on Odoo 17/18 in local languages.

EU timezone support desk

Email and ticket-based support during CET business hours with SLA response times for critical accounting issues.

Multi-entity access rights

User groups and record rules configured per role and entity β€” accounting lock dates enforced for non-admin users.

Managed version upgrades

Odoo version upgrades tested in staging before production deployment between fiscal periods across all entities.

How It Works

1

Training needs assessment

Identify user roles, language preferences, skill levels, and priority workflows for customised training curriculum.

2

Role-based training delivery

Conduct live or recorded training sessions for accounting, sales, warehouse, and admin users per entity and language.

3

Support desk activation

Launch EU timezone support channel with documented SLAs, escalation paths, and knowledge base access.

4

Ongoing maintenance and upgrades

Schedule monthly health checks, apply security patches, and plan version upgrades between accounting periods.

Successful Odoo adoption across EU entities depends on trained users and reliable post-go-live support β€” not just initial configuration. We deliver role-based training on Odoo 17/18 covering multi-entity accounting month-end close, VAT return preparation, SEPA payment batch processing, sales order workflows, warehouse barcode operations, and management dashboard navigation β€” in German, French, Dutch, Italian, or English as required. Access rights are configured per user group and entity: accountants receive full accounting access with lock date enforcement, sales reps see only their pipeline and quotes, and warehouse staff access inventory modules without financial data visibility. EU timezone support operates via ticket system with defined SLAs β€” critical accounting period issues covering month-end close, payroll runs, and VAT filing deadlines receive priority response during CET business hours. Managed version upgrades are tested in staging environments before production deployment, scheduled between fiscal periods to avoid disrupting national tax authority submission workflows. Monthly health checks review database performance, backup integrity, user access audits, GDPR compliance controls, and localisation module compatibility across all configured EU entities.

Common Questions

Frequently Asked Questions

Get Started

Fill out the form below and our team will get back to you within 24 hours.

Plan Your Odoo Implementation

Help us understand your systems and goals in Europe so we can design the right Odoo rollout.

Modules Interested In (optional)

Deployment Preference (optional)

Not sure which Odoo ERP service you need?

Our Europe team can assess your requirements and recommend the right approach. Book a free 30-minute consultation.

Need Odoo ERP Support in Europe?

Contact our Europe team for expert assistance.