Industry · Global business

Custom apps for organisations operating worldwide.

We build for companies that outgrew their Dutch headquarters long ago: multinationals with production sites on three continents, scale-ups whose customer base is growing faster than their teams, and B2B exporters that need to deliver across the EU, the US, Asia and Latin America from a single codebase. Multi-currency, multi-language, multi-region — and always with code ownership resting with your organisation, not with us.

Target groupMultinational with Dutch HQ
Target groupInternational scale-up
Target groupB2B exporter
Target groupCross-border service provider

The Netherlands as a hub for global business.

~€720bn
Dutch goods exports per year, in euros
~250.000
Dutch exporting companies
~30%
Share of GDP from foreign trade
~5.500
Foreign headquarters in the Netherlands

Source: CBS Internationaliseringsmonitor, NFIA annual report, Eurostat.

Standard software breaks as soon as it crosses a border.

An organisation operating within the Netherlands can get a long way with a standard ERP, CRM and HR package. But as soon as you open a second site in Germany, enter a joint venture in Singapore, or ship daily via Schiphol cargo to Brazil, India and the US, every standard system breaks in a handful of predictable places. Multi-currency reporting falters once you need quarterly consolidation with intercompany transactions, multi-language support stays limited to a handful of interface languages and becomes unusable in countries with right-to-left scripts, and cross-border data transfers immediately come under pressure from GDPR, CCPA, LGPD and POPIA all at once — and that is only the privacy side.

A Dutch multinational that must genuinely comply with both the CSRD and the US SEC climate-disclosure rules for the first time sees its ESG team quadruple within a few months. A scale-up with customers in seven countries discovers that VAT, sales tax, GST and VAT each have their own rules, and that the standard expense tool forces employees in Tokyo to scan yen receipts in an interface that only rounds to euro figures. And an exporter of high-tech machinery — think semiconductor suppliers in the ASML chain — has to deal with export control rules (dual-use licences), customs UCC codes, HS classifications and sanctions lists that differ for every destination country and that no standard package can handle without customisation.

In practice, global businesses respond to this with a patchwork: SAP or Oracle for the financial core, Workday or SuccessFactors for HR, Salesforce for customer contact, a middleware layer of their own in Java or .NET, and a growing number of point solutions per region. The core functionality works, but every new region means a new subproject, every compliance change a new migration, and every attempt to get management information from three continents into a single view ends in a Power BI report that is out of date again after a quarter.

A custom app solves this differently: your business logic sits at the centre, and the region-specific exceptions wrap around it as configuration, and instead of six separate SaaS tools, an employee in São Paulo, Rotterdam, Singapore and San Francisco gets the same core experience with region-adapted data. We build that layer on top of Appfront's app service and integrate it with your existing ERP, CRM and HR stack. For companies that deliver a multi-region platform to international customers themselves, we draw on our multi-tenant platform approach. For the B2B delivery context, with customer onboarding, contract flows and per-region SLAs, we build on the logic of a custom B2B app.

Software that fits every form of global business.

A dedicated flow, dedicated integrations and dedicated compliance requirements for each type of international organisation. Below, for each profile, is what we typically build — from multinational to exporter.

Multinational with Dutch HQ

The focus here is on consolidation, governance and internal portals for global teams. A Dutch head office with locations on several continents faces the same questions: how do I get consistent management information from eight ERP implementations, how do I roll out a single employee app to ten thousand employees spread across twenty time zones, and how do I make sure our CSRD reporting is as robust as our SEC disclosure? In that context, a custom layer on top of the existing systems is not a replacement, but the orchestration layer the group steers by.

Our module set for multinationals typically builds on a multi-region data layer that pulls financial, operational and HR data from the various locations into a standardised model, with FX conversion at the time of the transaction and separate reports for IFRS, US GAAP and local GAAP. On top of that, we build an employee app for global teams — payslips, leave requests, onboarding, training tracker, internal mobility — in all relevant languages, with region-specific compliance flags and an interface that works equally well for a factory worker in India and a trader in London. For the board and the risk function, we deliver consolidation dashboards that drill down to KPI level per region and work hands-on with CSRD/SFDR data rather than relying on an after-the-fact export.

For multinationals, the value lies in standardisation without centralisation: one architecture, one design system, one identity layer, but local changes remain possible without completely blowing up group IT governance.

  • Multi-region data layerEU/US/APAC consolidation, FX at transaction time, IFRS and US GAAP side by side.
  • Global employee appTwenty languages, RTL support, region-specific flows, mobile-first.
  • CSRD/SFDR dashboardData points at transaction and invoice level, audit trail per disclosure.
  • SSO across all regionsOne identity provider, MFA-aware for international travel.

The global business apps we typically build.

The world of global business is broader than one type of client, and that shows in the kinds of apps we deliver. For one company, the focus is a multi-currency, multi-language client portal where clients in fifteen countries log in at the same time, see their invoices in local currency, read contracts in their own language and handle support requests in their own time zone. A portal like this calls for ICU MessageFormat as the basis for i18n, right-to-left support for Arabic, Hebrew and Persian users, an exchange-rate pipeline (Open Exchange Rates or your own feed from the central bank), and a payment layer that can handle Mollie or Stripe for European countries, Adyen and local schemes for APAC, and ACH and wires for the US without headaches.

For another group of clients, it is an employee app for global teams: a single environment in which an employee in Rotterdam, a production worker in Poland, a sales rep in Brazil and an engineer in Bangalore get the same core experience — payslips in the right language and currency, leave requests in line with local labour rules, a training tracker with country-specific content. Under the hood, that means role setup per country, a design system that works in ten languages without breaking the pixel grids, and a notification layer that takes religious holidays per region into account. For companies that serve their international clients through their own tenant architecture, the same approach builds on our multi-tenant platform approach.

A third category is cross-border compliance dashboards, which have grown rapidly in scope over the past few years. A Dutch listed company faces CSRD for its EU reporting, SFDR for financial products with sustainability claims, and the EU Taxonomy for classifying activities, and in the same cycle it needs an SEC filing if it is also listed in the US. We don't build these dashboards as an after-the-fact report, but as a hands-on environment where ESG data is pulled in at transaction and invoice level, and where the audit trail for each disclosure can be traced back to an individual purchase invoice or HR change. The foundations come straight from our CSRD/ESG reporting software approach.

For exporters and logistics organisations, we increasingly build supply-chain track-and-trace and customs flows: shipments traceable from the Dutch warehouse or the Schiphol cargo hub all the way to the final destination, with automatic HS code classification, integrations with the EU Customs Single Window and local customs APIs, and sanctions list screening at order confirmation. For high-tech exporters in the semiconductor and machine-building chain, export control comes on top: classification under the Dual-Use Regulation, list assessment per destination country and end-use statements. Where compliance complexity runs deeper, this often connects to an enterprise software project as the reference architecture.

A fifth group of apps centres on expense management, travel flows and customer onboarding for international travel and cross-border KYC/KYB. Employees in São Paulo, Tokyo or Lagos scan local receipts, the system rounds to the correct sub-unit, links to the local corporate card and passes it on to the group accounting system, where the amount is converted at the FX rate on the transaction date. Customer onboarding for international B2B service providers runs on KYC and KYB with UBO rules per jurisdiction, sanctions list screening across EU, US and UN lists, and contract flows with local jurisdiction provisions and language variants. For the B2B context of such apps, we often start from our page on building a B2B app.

The common thread: the software accounts for the reality of operating worldwide, rather than exporting a Dutch product with a few extra languages bolted on. We build vendor-independent: a future IT partner of your group, or a successor in the CIO's seat, can take over the code, data and hosting without Appfront becoming indispensable through tokens, certificates or credentials. An international company shouldn't be locked into a tool as soon as it makes an acquisition, closes a branch or its reporting regime fundamentally changes.

Compliance that works across six jurisdictions at once.

An internationally operating company rarely works under a single legal regime. From the first sprint, we build within the framework of EU privacy law, international data transfer instruments, regional equivalents and the relevant export and trade rules.

GDPR & cross-border data transfers

SCCs, EU-US Data Privacy Framework, BCRs

Every data flow that leaves the EU falls under Schrems II case law. We build apps in which data transfer instruments such as Standard Contractual Clauses, Binding Corporate Rules and, for the US, the EU-US Data Privacy Framework are explicitly visible in the architecture: for each dataset you can look up who is responsible, which transfer mechanism is used and which additional safeguards (encryption, pseudonymisation, access control) have been applied. Sub-processor registers and standard DPIA templates are part of delivery, not a later update.

GDPR / CCPA / LGPD / POPIA

Regional equivalents as first-class citizens

The California Consumer Privacy Act, Brazil's LGPD, South Africa's POPIA, Singapore's PDPA, Australia's Privacy Act: every region has its own privacy regime, with subtly different definitions, rights and notification deadlines. We build a single privacy engine that applies the right consent text, data subject request flow and retention policy for each region, with a unified audit log for the group DPO and region-specific views for the local privacy officer. That includes the Code on Privacy of Communications where it applies regionally.

Export control, Customs UCC & HS classification

Dual-use, customs and global tariffs

For exporters of high-tech machinery, semiconductor components and software with cryptography, EU Regulation 2021/821 on dual-use goods applies. When an order is created, our apps automatically flag its dual-use list status, the sanctions list position of the destination country and the required end-use statement. On the customs side, the Union Customs Code governs procedures within the EU, while HS classification determines the tariff and import rules per destination country worldwide. We build automated HS classification, integration with the EU Customs Single Window and integrations with the local customs APIs of your main trading partners (US CBP, Brazil Receita Federal, UK HMRC, Singapore Customs), with a digital file per shipment that is traceable to the original commercial invoice.

CSRD / SFDR / EU Taxonomy

ESG reporting with an audit trail down to the transaction

The CSRD obliges a growing group of companies to report in detail on their environmental, social and governance performance. SFDR does the same for financial products that make sustainability claims, and the EU Taxonomy classifies the underlying activities. We build ESG reporting as a data layer on top of your existing finance and HR systems, with data points at transaction level and an audit trail that traces each reported KPI back to a source purchase invoice or HR change. For groups with multiple CSRD-reporting entities, we support entity-level and consolidated reporting side by side.

EU AI Act & international AI regimes

Responsible AI in a global rollout

The EU AI Act has extraterritorial effect for companies that offer AI systems on the European market. At the same time, the US, the UK and Brazil are developing their own AI regimes. For each AI application in the app, we map the risk classification, document the governance, and build in disclosure and transparency flows where needed. Our guiding principle is that AI models processing personal data from multiple jurisdictions comply with the strictest applicable rules, not an average of them.

Ownership & code handover

The code and the data stay with your organisation

We deliver the code in a repository managed by your group, one that continues to exist without Appfront. No mandatory licences, no hidden hosting lock-ins, no compulsory maintenance contract. When a global group makes an acquisition, restructures a regional subsidiary or gets a new CIO, the software should simply go along with it. We can take care of hosting and maintenance, but that is your choice.

Seamlessly connected to the international enterprise stack.

We integrate with the systems your group already works with, from the ERP core to the local tax engine, from payment providers to logistics partners. No migration of the entire stack: our app complements it and rarely replaces anything.

SAP / Oracle
Multi-region ERP core
Workday / SuccessFactors
Global HR & payroll
Salesforce / Dynamics
CRM and service
Vertex / Avalara
Cross-border tax engine
Open Exchange Rates
Multi-currency FX
Stripe / Adyen / Mollie
Global payments
Cloudflare / Fastly
Global CDN & security
AWS / Azure / GCP
Multi-region cloud
EU Customs Single Window
Customs integration
Okta / Azure AD / Ping
Identity & SSO
DocuSign / OneSpan
eIDAS & e-signatures
OneTrust / Cookiebot
Multi-region consent

Standard integrations, no project-specific connections.

We have standardised the integrations mentioned above across multiple global business projects. For a new project, we set up the integration using the same abstraction layer, which means fewer bugs, a faster turnaround, and your own tech team can manage it themselves if we step out. The integration layer is a mappable adapter: if your group moves from SAP S/4HANA to Oracle Fusion next year, or from Workday to SuccessFactors, that is a configuration change in the adapter, not a rebuild.

For specific group software, such as a Java middleware of your own, a proprietary tax engine built by a local subsidiary, or a legacy mainframe connection with EDI messages to customs authorities, we build case by case. For groups that sell a multi-region product layer to international customers themselves, we work from our multi-tenant platform approach; for the B2B delivery framework, from our custom B2B app; and for ESG components, from our CSRD/ESG reporting approach.

One key difference from the large SaaS suites: with us, the API credentials, OAuth tokens and data flows belong to your group. We configure and build, but we don't make Appfront indispensable through the tokens. If your group changes supplier or a private-equity owner decides to restructure, no hidden costs keep running in the background.

From regional audit to global go-live in clear steps.

A global business app project has its own rhythm: more alignment with regional business owners, more interaction with compliance and tax teams, more cutover rounds. Five phases you will recognise from any international rollout.

01 · Audit

Regional mapping

A workshop with IT, finance, tax, HR and the regional managing directors of the main locations. Outcome: current systems mapped per region, compliance requirements identified, data flows documented.

02 · Design

Scope per region and lifecycle

For each region: which flows go into the app, which integrations take priority (ERP, HR, tax, payments), which compliance regimes apply, and which flows belong in a later release.

03 · Build

Short sprints, demo per region

Every sprint we deliver a working flow that the regional business owners test. The first working flow is live after just a few sprints, often in a single pilot region before we widen the scope.

04 · Cutover

Pilot in one country or location

One country first, for example the Netherlands and Belgium, then a second region, then APAC or LATAM. Each rollout comes with a training programme for the local team, onboarding material for new employees, and a handover to your local application management.

05 · Maintenance

Continuously evolving with you

Whenever there is a change in legislation in any of the regions, a new GDPR guideline, or a change in trade agreements or customs procedures, we adapt the app. Fixed monthly price, first-line support within the same working day in EU time, and an escalation path for the relevant time zones.

Working in a sector where precision is not optional.

CBS Internationalisation Monitor

"Dutch companies with production or service sites in multiple regions report that digitising compliance and consolidation processes is one of their most important investment themes in the coming years."

NFIA & Holland International Trade

"The Netherlands' position as a hub for foreign headquarters stands or falls with digital infrastructure that remains workable across jurisdictions, from tax compliance to privacy equivalence."

European Union Customs Single Window

"Standardised digitisation of customs processes between member states and trading partners is a prerequisite for the European competitive position of industrial sectors with international supply chains."

Answers for the organisation scaling globally.

The questions we hear most from CIOs, international operations managers and group CFOs.

What types of global business apps do you build?
Mainly multi-currency and multi-language customer portals, employee apps for global teams, cross-border KYC/KYB onboarding, supply chain track and trace with customs integration, expense management for international travel, cross-border compliance dashboards (CSRD, SFDR, EU Taxonomy, SOX alignment), and customs and trade finance modules for exporters. We work with multinationals headquartered in the Netherlands, international scale-ups, B2B exporters in industry and high tech, and cross-border service providers. For the service layer of a single, clearly defined app, see also our app development.
How do you handle multi-currency and multi-language?
For multi-currency, we work with an exchange-rate pipeline (Open Exchange Rates, the ECB feed or your own feed from the central bank) and a data model that stores the source, booking and reporting currency for each transaction. That makes quarterly consolidation correct and supports recalculation when IFRS rules change. For multi-language, we use ICU MessageFormat with right-to-left support for Arabic, Hebrew and Persian users, and a translation workflow with fallback languages so a Mongolian customer never lands on an empty screen.
How do you handle cross-border data transfers?
Every data flow that leaves the EU falls under the GDPR requirements for cross-border transfers. We explicitly implement the instruments the supervisory authority accepts: Standard Contractual Clauses for regular third countries, Binding Corporate Rules for intra-group transfers, and for the US the EU-US Data Privacy Framework via a certified US recipient. For each dataset, we document which instrument applies and which additional safeguards (encryption, pseudonymisation, strict access control) have been applied. For groups with data flows to the US, UK, Switzerland, Singapore, Brazil or South Africa, we provide the relevant DPIA building blocks for each region.
How do you handle cross-border CSRD reporting?
We build CSRD reporting as a data layer on top of existing financial and HR systems, not as an after-the-fact export. For each CSRD data point, we define which source table or source system supplies the value, with an audit trail down to transaction and invoice level. For groups with multiple CSRD-reporting entities, we support per-entity and consolidated reporting side by side, with alignment to SFDR for financial products and to the EU Taxonomy for classifying activities. For the details of such a project, we often work from our CSRD/ESG reporting software approach.
Do you work with multi-region cloud?
Yes. For most international projects, the app runs across multiple AWS, Azure or GCP regions at the same time: an EU region for European users (Frankfurt, Amsterdam or Dublin), a US region for North America, and an APAC region for the Asian user base (Singapore, Sydney or Tokyo). For customers who want data sovereignty (French HDS, German BSI C5, Italian AgID), we set up data residency explicitly. For the performance layer, we use Cloudflare or Fastly as a global CDN.
How do you handle export control, sanctions lists and MFA for international travel?
For exporters of high-tech machinery, semiconductor components and software with cryptography, the EU Dual-Use Regulation 2021/821 applies. We build dual-use list classification into order creation: sanctions list checks, end-use statements and licence tracking are standard parts of it. For MFA, we work with a travel-aware identity layer: users can mark a travel plan so that login attempts from announced regions are handled with a second-factor prompt, while unusual patterns trigger additional checks. For the B2B context of such flows, we often draw on our custom B2B app.
Do we keep ownership of the code and the data?
Yes. We deliver the code in a repository managed by your group, with OAuth credentials, hosting credentials and database ownership in your name. If you switch supplier, your group makes an acquisition or divests a regional subsidiary, there are no hidden costs running in the background and a successor can continue the project without Appfront.
What does a global business app cost?
A multi-currency customer portal for a single Dutch exporter is a very different project from a global employee app for a multinational with tens of thousands of staff, or a cross-border compliance dashboard that has to meet SOX, CSRD and SFDR requirements at the same time. We work with a fixed sprint budget and, after the planning phase, give you a concrete price for the complete build, including integrations and compliance work. What we often do: start with one clearly scoped flow for one region and only broaden once it works.
Can you build for a Schiphol cargo, supply chain or scale-up context?
Yes. For logistics organisations around Schiphol cargo, exporters with daily shipments via the Rotterdam port terminals and agritech players handling perishable goods, we build supply chain track-and-trace environments with automatic HS classification, EU Customs Single Window submission and integrations with local customs systems. For scale-ups growing internationally, we more often build on a SaaS stack and deliver custom work in the areas where growth hurts: typically cross-border customer onboarding, multi-currency invoicing and an employee app that scales with international teams. Our experience with the multi-tenant platform approach gives us a strong starting point here.
Do you work with enterprise security and SSO?
Yes. For global business organisations, we work with enterprise identity providers as standard: Okta, Azure AD/Entra ID, Ping or your own IdP. SSO across all regions, MFA for all users and SCIM provisioning from the HR system are standard. For clients with an ISO 27001, SOC 2 or local equivalent requirement, we supply the evidence for our part of the stack. For the wider enterprise context, we work from our enterprise software track.
Fabian van Dijk · Business developer
Talk about global business apps, multi-region rollouts and cross-border compliance. Email fabian.vandijk@appfront.nl.

Talk to us about your international rollout.

A half-hour introduction with a CIO, a group CFO, an international operations manager or a regional managing director. We listen, ask questions and give an initial direction. No obligation.

Edit content