techone --guide=international
IT Partner for Companies with International Operations
Your ERP is managed by a team on the other side of the world. You are in Prague or Vienna. Do you know how it is configured and who has access to what?
What Typically Goes Wrong in International IT Environments
Companies with subsidiaries or a parent company abroad face IT challenges that purely local firms never encounter. It is not just a language barrier. It is a combination of distance, conflicting legislation, and systems that are not integrated with each other.
Remote Vendor with No Local Context
ERP was implemented by a remote team in a different time zone. They know the platform but not EU legislation. Support runs through a ticketing system with hours of delay. Contacts rotate every few months.
Different Legislations in One System
GDPR for the EU subsidiary. Local VAT rules. Local chart of accounts. Reporting for central management in a format the local system does not produce. These are separate configurations, not just translations.
Access Rights and Segregation of Duties
SoD is the principle that no single employee should have access to all steps of one process: whoever creates a purchase order must not approve it themselves. Who sees payroll data? Who has access to financial results before closing? Unclear permissions are a security risk and a problem during audits.
Reporting to Central Management
The parent company needs consolidated results. The local system reports in a local format. The gap is typically bridged with Excel: manually, with errors and delays.
No Ongoing Support After Go-Live
The implementation is done, the team disbanded. Who maintains the system? Who applies legislative changes? Who trains new employees? Without an ongoing partner, the system ages.
Institutional Knowledge Gap
An IT consultant who does not know the client environment works slower and makes more mistakes. Every handover costs time and introduces risk.
How an Audit and Implementation Takeover Works
A company inherits an ERP from its parent or a previous vendor with no documentation. The system "works", but no one knows exactly how. An audit reveals what is correct, what is missing and what needs fixing.
Audit of Configuration and Data Structure
We go through the configuration: chart of accounts, dimensions, master data, templates. We look for inconsistencies, duplicate records and settings that do not meet local legislation.
Mapping Processes vs. How ERP Actually Works
How the company operates and how ERP records it are often two different things. We document the current state, not how it was designed to work. The gap between specification and reality is the basis for a remediation plan.
Review and Remediation of Access Rights
We review who has access to what. We configure Segregation of Duties based on actual roles in the company. We remove access that no one needs or should have.
Setting Up Reporting for Central Management
We define the report structure the parent company needs. We configure automated outputs or Power BI connectivity so that reporting no longer goes through Excel.
Documentation and Knowledge Transfer
We document everything. Key configuration, reasons behind decisions, local configuration specifics. Documentation is the foundation for ongoing support and onboarding new people.
Azure and D365 for Multi-Site Companies
Cloud removes dependency on local infrastructure. Dynamics 365 Business Central as a cloud solution gives all subsidiaries access to the same data, the same system version and the same security standards.
Centralised Access from Anywhere
Prague, Bratislava, Vienna, London. Each subsidiary works in the same system via browser or app. No VPN tunnel to a local server.
Multi-Entity in D365
Each legal entity has its own accounting and configuration. They share common master data: customers, vendors, items. Intercompany transactions (automatic records of receivables and payables between subsidiaries) handle consolidation without manual entry.
Security and Compliance
Microsoft certifications cover ISO 27001, SOC 2, GDPR. Data is stored in EU datacentres when legislation requires it. Regular security updates without manual intervention.
Automatic Updates
D365 BC receives two major updates per year. Legislative changes (VAT, Intrastat, local reporting) are part of the standard update. No reliance on local server infrastructure for updates or patching.
What Having an IT Partner in the EU Actually Means
An EU IT partner is not just about time zones. It is about knowing the context, the legislation and how local businesses actually operate.
Available During Business Hours
Problem at 9 AM in Prague? Your partner is online, not five hours behind you. For urgent situations, this is not a minor detail.
European Legislation Expertise
EU VAT, Intrastat, GDPR, local accounting standards. A partner who does not know these must consult a specialist for every change. That makes things slower and more expensive.
Ongoing Collaboration, Not a One-Off Project
The partner knows the history of decisions and why things are configured the way they are. That context builds over years and cannot be handed over in a document.
Communication Without Barriers
English, German, Czech, Slovak. No misunderstandings in technical terminology. Shared understanding of how businesses operate in Central Europe.
Who Benefits from an EU IT Partner
Not every company with international operations needs to change IT partners. Here are the situations where it makes sense.
Good fit
- ERP managed by a distant vendor where support is not working
- System inherited from parent company without documentation
- Reporting to foreign management still goes through Excel
- Adding subsidiaries or acquisitions in the EU
- Facing GDPR audit or compliance review and do not know where to start
- New CIO or IT director needs to assess the current state
Not a priority yet
- Company does not have ERP yet or is just selecting one
- Operations are purely local with no international ties
- Existing vendor is working well and the relationship is established
- Company is in growth phase and IT stabilisation comes later
| Situation | Symptom | Root Cause |
|---|---|---|
| Remote vendor | Support takes days, not hours | Time difference, contact rotation, missing context |
| Legislation | Manual VAT or Intrastat corrections | Local configuration does not match current rules |
| Access rights | Everyone sees everything or no one knows what they can do | SoD not configured during implementation |
| Reporting | Excel consolidation before every close | ERP has no structure for central reporting |
| Documentation | Key person left and know-how was lost | Implementation was never documented |
Frequently Asked Questions
How long does an implementation audit take?
It depends on system scope and availability of documentation. A basic audit (configuration, access rights, key processes) for a mid-size company takes 2-3 weeks. Without documentation and with complex processes, plan for 4-6 weeks. The output is a written report with prioritised recommendations.
Can we take over a system from another vendor without disrupting operations?
Yes. The takeover is gradual. First comes audit and documentation, then access to the environment, then parallel collaboration with the original vendor during handover. Operations continue without interruption. The overlap period with the previous vendor typically runs 1-2 months.
Can a holding company or multi-site business run one shared ERP?
Each legal entity (subsidiary) has its own company in D365. They share customer and vendor master data but have separate accounting and configuration. Intercompany transactions automate invoicing between subsidiaries. Consolidation is handled through D365 or Power BI.
What happens to our data if Microsoft changes its terms?
Your data in D365 belongs to you. It can be exported at any time in standard formats (Excel, API). Microsoft has contractual obligations regarding data availability even after subscription ends. Your data is in standard formats throughout, there is no proprietary lock-in.
Do we need a separate ERP for each subsidiary or one shared system?
It depends on complexity and legislation. A single D365 tenant with multiple companies (entities) is typically simpler and less expensive. But if subsidiaries have fundamentally different processes or are in countries with non-standard legislation, a separate system with a data connection may make sense.
How do we handle GDPR for D365 with data across different countries?
Cloud D365 stores data in Microsoft EU datacentres by default for EU customers. GDPR compliance is covered by Microsoft contracts (DPA). The key is to configure which data is personal, who has access and how to process deletion requests. We address this during implementation or audit.
What is Segregation of Duties (SoD) in ERP and why does it matter?
Segregation of Duties (SoD) is the principle that no single employee should have access to all steps of one process. Whoever creates a purchase order must not approve it themselves. In ERP, SoD is enforced through role-based permissions. Without proper SoD, there is a security risk and problems during internal or external audits.
Have an ERP and need it properly configured?
We will review your situation and tell you what is needed. No commitment.
Free consultation