Currencies, VAT and sales tax, invoice formats, languages, data location and privacy records for business software that serves several countries
Software has to change for each country. Currency tables, VAT and sales tax codes, invoice layouts, translation files, storage regions and consent records are built as configuration that your team can edit without code changes. The legal question stays with your adviser.
- Rules are set up as configuration your team can change
- Legal and tax conclusions stay with your own advisers
- No software makes a company compliant in any country
Companies that began in one market and now invoice, ship or hire abroad need this, as do businesses on software built around one country’s tax paperwork. We work remotely, by video call and shared screen, with customers in many countries and time zones, and we keep a written record of each decision. Engineering and documentation are our part. The rules come from you and your advisers.
Where Single-Country Software Breaks Across Borders
One Currency Hard-Wired Into Every Screen
Quotes and ledgers assume one currency. A foreign sale gets keyed in at whatever rate someone looked up that morning, and the amount the customer actually agreed to disappears from the record.
Tax Logic Written Into the Code
A typed-in rate stays locked in code. Every new country and every rate change becomes a ticket in a developer’s queue, and the finance team waits for a release to fix a single rate.
Invoices That Look Wrong to a Foreign Customer
Customers reject these invoices. A tax number in the wrong place, a missing legal line or a swapped day and month sends the invoice back, and payment waits for the reissue.
Names and Addresses That Do Not Fit
Forms demand a state and a fixed-length postcode. They also split every name into first and last, so customers in other countries type filler text into the boxes just to reach the next screen.
Dates and Times That Disagree
03/04 is two different days. Delivery dates read differently by country, and support hours, reminders and cut-off times drift whenever the system only knows a single time zone.
Customer Data Stored in the Wrong Place
One regional database holds everyone’s records. Some customers, contracts and sector rules expect personal data to stay in a stated region, yet nobody has written down where each table, backup and log copy sits.
No Record of Who Agreed to What
Consent lives in too many places. Marketing consent, accepted terms and privacy notices sit in web forms, spreadsheets and inboxes, so a customer’s request to see what you hold takes weeks to assemble.
Going international is rarely one big change. It is a long list of small assumptions, each fine in the home market, that stop holding the day a second country arrives.
Configure Each Country as Settings, Not as Special Cases in Code
Work begins with a list of every country you trade in, sell to or hire from, and the documents each one expects. Each country gets a profile. A profile holds currency, tax treatment, document layouts, language, number and date formats and storage region, and your finance team maintains it directly. Developers return only for new behaviour.
A Profile for Every Country
Each country is one named profile. Currency, tax codes, number formats, address fields and invoice templates sit together, so adding a country means adding a profile instead of editing the application.
Amounts Kept in Their Original Currency
The original amount is never overwritten. Each transaction stores the agreed amount, the rate used and the reporting-currency value, so revaluation and reports can be rerun later without guessing what was first charged.
Privacy Records Built Into the Data
Answers come from the system. Consent, notice versions, deletion requests and access history are stored against the person and the region, so nobody rebuilds the answer from old email threads.
What Changes When Software Handles Several Countries Properly
Focus on business value before discussing technology.
Sales Recorded in the Currency Agreed
The customer sees their own currency. Finance reads three figures on one invoice line, quote or ledger entry: the original amount, the rate applied and the value in the reporting currency.
Tax Treatment Chosen by Setting
Rates are settings, not code. VAT and sales tax codes attach to products and customers through configured rules, and a rate change becomes a dated update that the finance team makes alone.
Invoices That Customers Accept First Time
Fewer invoices bounce back. Each region has a layout carrying the legal lines, tax numbers and wording your adviser confirmed, so the customer’s accounts department can book the document on first receipt.
Screens and Messages in the Reader’s Language
Pages follow the reader’s language. Customer-facing pages, emails and PDFs appear in the language the customer chose, and right-to-left scripts such as Arabic and Hebrew mirror the layout, tables and page numbering correctly.
Data Held Where You Said It Would Be
Storage region is a recorded fact. Storage region, backup region and the vendors involved are recorded for each type of record, so a customer’s question gets answered with a page rather than a search.
Consent and Requests Traceable by Person
Every consent has a source. What a person agreed to, when, in which language and from which form is stored, and requests to see or erase data follow a written path with a log.
What Global Compliance and Localisation Work Includes
Everything required from operational discovery to production deployment and long-term maintenance.
Country and Document Discovery
We start with a country list. For each market you sell into, buy from or employ in, we list the documents customers, banks and tax offices ask for, then mark the gaps in today’s software.
Multi-Currency Design
Yen and pound sales round differently. Price lists, quotes, invoices, receipts and ledgers carry the transaction currency, the rate source and the reporting currency, with a rounding rule agreed for each one.
VAT and Sales Tax Configuration
Tax codes, inclusive and exclusive pricing, reverse-charge handling and exemptions are built as dated rules in a table, and your adviser confirms each one before release. Nothing goes live unconfirmed.
Invoice and Tax Document Formats
Each region gets its own layout with the tax numbers, legal wording, numbering series and credit note treatment your adviser specifies, and sample PDFs are approved before first use.
Language and Right-to-Left Support
Translators never touch code. Interface text, emails, PDFs and notifications live in message files, and Arabic and Hebrew layouts are mirrored and checked on real documents rather than on screen mock-ups.
Dates, Numbers, Names and Addresses
Address forms ask only for local fields. Date order, decimal and thousand separators, phone formats, postal codes and name fields follow the customer’s region, so a Japanese customer never meets a mandatory state box.
Time Zone Handling
Stored once, shown locally. Timestamps are stored in one reference zone and shown in the viewer’s zone, while scheduled jobs, reminders, cut-off times and support hours are each tied to an explicit zone.
Data Location and Hosting Review
We map where each record lives. The map covers every copy, backup and vendor and shows what a regional database would change, and the findings go to your adviser, who decides what the business needs.
Privacy Records and Consent
Reviews start from these records. Consent, notices, withdrawals and access or erasure requests are recorded per person with date, source and region, which gives GDPR, UK GDPR and CCPA reviews something concrete to read.
Retention and Audit Trails
Nobody edits the log that describes them. Retention periods set by your adviser run as scheduled jobs, and audit logs record who viewed, changed or exported each record.
Sector Rules Review Support
The conclusion stays with your adviser. Where a rule such as HIPAA may touch the business, we produce the technical facts your adviser needs, covering access control, logging, hosting and every vendor that handles records.
Migrating a Single-Country Setup
Existing data is carried over. A setup built around one country’s tax invoices, local currency ledgers and formats is converted to a multi-country structure, and every migrated balance is reconciled against the old books.
Where Multi-Country Setup Work Is Typically Needed
Real-world business processes we configure and automate.
Exporter Invoicing in Three Currencies
A manufacturer quotes in dollars, euros and pounds from one price list built in a single currency, using a manual conversion sheet. Separate price lists, stored rates and region-specific invoices replace that sheet, and receipts post against the currency of the invoice they settle.
Online Seller Crossing Into the European Union
A web shop that starts shipping to several EU member states needs tax calculated by destination, so rules attach to the delivery country and invoices carry the required lines. Order exports feed the accountant’s filings.
Clinic Group Adding a Second Country
Patient records sit in one region. A clinic group adding a second country has its notes, access logs and hosting reviewed with its adviser against health privacy rules, and records are then separated by country.
Software Company Selling Subscriptions Abroad
The product bills monthly in one currency. Buyers then choose their currency at checkout, tax is collected by buyer location, receipts arrive in the buyer’s language and every signup writes a consent record.
Franchise Network With Regional Operators
Operators share one billing system. Each operator gets its own tax profile, language, opening hours and time zone, while head office reads consolidated figures in a single reporting currency across all countries.
Business Moving From a Single-Country Configuration
A subsidiary opens overseas. A company that ran on local tax invoices and one-currency ledgers adds a second legal entity, a separate chart of accounts and a tax profile, and inter-company entries stay apart.
Is This Service Right for Your Business?
We partner with established businesses that have outgrown manual processes and want reliable systems.
Companies Selling Into Several Countries
Exporters, online retailers and service firms that invoice in more than one currency, or collect tax in more than one place, need those settings inside the software.
Businesses With Staff or Operators Abroad
Teams span time zones and languages. They need schedules, notices and screens that make sense to the person reading them, whether a shift lead abroad or a planner at head office.
Firms Answering Customer Data Questionnaires
Questionnaires arrive before contracts do. Larger buyers ask where data is stored, who can reach it and how long it is kept, and answering accurately depends on having the record to hand.
Owners Whose Software Was Built for One Country
Single-country packages hard-code their assumptions. Packages with one country’s tax, address style and invoice layout baked in usually need rework before a second market can be served.
Health, Finance and Education Providers
The tax settings are yours to confirm: we propose them, your accountant approves them. Health, finance and education organisations that hold sensitive personal records benefit from technical facts, laid out in an order their adviser can review without hunting through systems.
Small Firms Selling Abroad Occasionally
Occasional exporters may need little. A business with a handful of overseas customers may need only one extra currency, a tax setting and a clean invoice, and the assessment says so.
Enterprise Capabilities in Plain Business Terms
Regional Profiles
A new country is one new record. Each record holds currency, tax rules, number formats, language, time zone and document layouts, so a country can be added without touching the application code.
Multi-Currency Ledgers
Gains and losses post to named accounts. Each ledger entry keeps the transaction amount, the exchange rate with its source and the reporting value, so settlement differences are visible rather than buried in a rounding line.
Dated Tax Rules
Old invoices keep their old rules. Rates, exemptions and reverse-charge treatment carry start and end dates, so a document issued last year still shows the rule that applied on the day it was issued.
Document Templates by Region
Credit notes get their own layout. Invoices, receipts and statements use region-specific templates with the numbering series and mandatory wording for that country, held as files finance can preview before release.
Translation Management
Missing translations never reach customers. Text for screens, emails and documents sits in files a translator can edit, and a missing string is flagged before release instead of being discovered by a customer.
Right-to-Left Rendering
Mixed text is the hard part. Layouts, tables and PDFs mirror for Arabic, Hebrew and similar scripts, and embedded numbers, product codes and brand names are tested on printed output.
Locale-Aware Formats
The customer’s region decides the display. Dates, numbers, currencies, phone numbers and postal addresses are shown and validated according to that region, not the server’s locale.
Time Zone Scheduling
Every job names its zone. Jobs, reminders and cut-offs run in an explicit zone, so a seasonal clock change never moves an appointment or a billing run.
Regional Data Storage
Hosting region is a setting. Record types can be stored in a chosen region with backups placed to match, and the whole arrangement is written up so your adviser can review it.
Consent and Notice Records
History is never rewritten. Each person’s consents, withdrawals and notice versions are stored with date, source, language and region, so you can show what they saw and agreed to at signup.
Subject Request Workflow
Requests are logged and assigned. Access, correction and erasure requests are tracked to completion, with identity checks and a note of exactly what was produced or removed recorded against each one.
Audit and Retention Controls
Logs show who opened or exported what. Retention jobs remove or archive records on the schedule your adviser sets, and each run produces a report listing what it removed and when.
Our Structured 6-Step Delivery Process
A transparent path from your first conversation to a reliable production release.
- 01
Country and Document Inventory
Everything starts with an inventory. We list countries, entities, currencies, document types and systems in play, and the client provides sample invoices and customer paperwork from each market.
- 02
Gap Review Against Your Adviser’s Requirements
Open questions are marked as theirs. We check current software against what your tax and legal advisers say each country needs, and the client provides those requirements in writing.
- 03
Regional Profile Design
The structure comes first. We draw up the profile layout, price lists, tax rule tables and document templates for agreement, and the client provides decisions on reporting currency, rounding and numbering series.
- 04
Build and Translate
Everything is built in a test environment. Profiles, document layouts, formats and translated text are built there, and the client provides translators or reviewers who read each language involved.
- 05
Migration and Parallel Checks
Old and new run side by side. Existing records are converted and sample transactions run through both setups, and the client’s accountant compares totals and signs off every difference.
- 06
Release, Records and Review Dates
Regions go live one at a time. Setting changes are documented for each region, and the client names an internal owner and a calendar date to revisit rates, templates and retention.
What You Receive Upon Project Completion
Everything required to run, maintain, and expand your software without vendor lock-in.
Connects With the Systems You Already Rely On
We build bridges between your software so you don't have to replace functional existing tools.
Accounting and ERP
- Zoho Books
- Odoo
- Xero
- QuickBooks Online
- Custom ledger exports
Sales Tax and Rate Services
- Exchange rate feeds
- Tax calculation services
- VAT number validation
- Address validation services
Payments and Commerce
- Stripe
- PayPal
- Shopify
- WooCommerce
- Regional payment methods
Hosting and Storage
- AWS regions
- Azure regions
- Google Cloud regions
- Regional backup storage
Language and Messaging
- Translation management tools
- Email delivery services
- WhatsApp Business Platform
- PDF generation engines
Selected for Reliability, Speed, and Longevity
Technology chosen to match your operational scale and long-term maintainability.
Localisation
Money and Tax
Documents
Privacy and Records
Hosting
Why Business Owners Choose GullySystem
Settings Your Finance Team Can Change
Finance should not queue behind developers. A new rate or a changed invoice line should be edited by the people who understand the rule, so settings are built for the finance team to maintain.
Your Adviser Decides, We Build
We do not interpret tax or privacy law. Your advisers confirm what each country needs, and we turn their written requirements into working configuration that can be tested against sample transactions.
Compliance Is Not a Product
No tool or certificate makes a company compliant. What a business can show is working controls and a record of decisions with the reasons behind them, which is the evidence a reviewer actually asks for.
Original Amounts Always Kept
An overwritten amount is gone for good. Converted figures can always be recalculated, so every transaction stores what was actually charged, the rate that was applied and the date that rate was taken.
Real Documents, Not Screenshots
Problems show up on paper first. Right-to-left layouts, long German compound words and Japanese names are tested on printed invoices, because overflowing columns and clipped characters rarely appear on a screen.
Remote Work Across Time Zones
Sessions run by video call. We schedule across your working hours with shared screens and written follow-up, and every decision is kept in writing so the next reviewer can read the reasons.
Flexible Engagement Options
Choose an engagement model that matches your operational scope, budget, and timeline.
Localisation Assessment
This is the smallest first step. Country inventory, document samples and a gap report on today’s software come first, and the result stands alone so you can decide what to build and in what order.
Regional Setup Implementation
Your existing system can stay. Currency, tax rules, templates, formats, languages and records are configured in the system you already use or in a new one, with the finance team trained to maintain them.
Localisation in a New Build
Design comes before data. Multi-country behaviour is built into screens, data and documents from the first sprint, whereas adding it later means converting records that are already in use.
Ongoing Regional Upkeep
Rates change and countries get added. Rate and template updates, new countries, translation changes, retention checks and access reviews are handled on a regular cycle that you agree in advance.
Frequently Asked Questions
Straightforward answers to the questions owners ask before getting started.
Can you make our business compliant in other countries?
Compliance is a legal conclusion. It is drawn by your advisers from decisions only the business can make, so we configure the software to their rules and record what was set and why.
Do you give tax or legal advice on VAT or sales tax?
Tax advice is not ours to give.
Which privacy rules do you work with?
Reviews under GDPR, UK GDPR and CCPA ask for consent history, access logs, hosting facts and deletion paths, and we build those records. Applicability is your adviser’s call.
What about health or financial sector rules such as HIPAA?
We never claim that HIPAA or comparable sector rules are met, because the legal reading of each control belongs to your own adviser. We supply the technical facts. These cover who can open which records, what is logged, where data is hosted, which vendors touch it and how long each record is kept.
Does our data have to be stored in a particular country?
Ask your adviser first. Residency turns on your sector rules and your contracts, so we write down where each record type is stored and what running a regional database would involve.
How do you handle currencies and exchange rates?
Every transaction keeps three figures. These are the amount agreed, the rate used with its source and the reporting-currency value, with rates arriving from a feed or being entered by finance. Settlement gains and losses go to accounts you name.
Can invoices be produced in Arabic or other right-to-left languages?
Yes, and we check printed output. Layouts, tables and PDFs are mirrored, numbers and product codes are checked on paper, and a native reader on your side should review the sample before approval.
Do you provide the translations?
We manage the files, not the wording. Wording should come from a reviewer who knows your trade and the language, and we can work with translators you already use or help you brief new ones.
We run on a single-country configuration today. Can it be extended?
Usually yes, with some restructuring. Local-currency ledgers, home-country tax invoices and local address fields are restructured into profiles, with the home country kept as one profile among several, and existing records are reconciled with your accountant.
Do you have an office or staff in our country?
No, we work fully remotely. We work with customers worldwide by video call, shared screen and messaging, and local advisers such as your accountant and lawyer confirm what applies where you trade.
How long does a multi-country setup take?
Timing depends on the scope. Scope grows with the number of countries, with how much of the software already separates settings from code and with how much data must be migrated. A timeline follows the assessment.
How much does this cost?
The price moves with regions and document types, with how much is built instead of configured, and with any data migration in scope. A figure follows discovery.
We only sell abroad occasionally. Is this worth doing?
Possibly only in part. A few overseas customers may need only one extra currency, a tax setting and a corrected invoice layout, and the assessment says plainly when more is not needed.
Read before you decide.
Practical notes on the questions this service raises, not product marketing.
How to prepare business software for a second country
A plan for opening a second market: list entities, currencies and documents, check gaps with advisers, build regional profiles, release one region at a time.
Where to store customer data: what to map and ask your adviser
Map every record type, copy, backup and vendor by region, then take the right questions to your adviser and contracts before moving data to a new region.
Why foreign customers send your invoices back for correction
Why an overseas accounts team bounces an invoice, from tax number placement to credit note numbering, and how region layouts with approved samples stop it.
Why online orders abroad get taxed at the wrong rate
Wrong VAT and sales tax on web orders usually trace to typed-in rates, billing address logic, mixed pricing and unchecked VAT numbers. Here is each fix.
Let’s Build the Right Software for Your Business
Tell us about your current operational challenge, spreadsheet bottleneck, or software requirement. An experienced engineer will review your workflow and reply within one business day.
- No obligation consultation
- Senior engineer reviews your brief
- Your operational details stay 100% confidential
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirementsRelated Practices & Services
Data Protection and Privacy Readiness
Data mapping, consent records, roles and retention rules form the engineering groundwork that overseas privacy reviews and customer data questionnaires both depend on.
GST and E-Invoice Compliance Engineering
A single-country tax setup is often the starting point, with its invoice formats and returns data that must be carried into the multi-country structure.
ERP and CRM Implementation
Ledgers, entities, price lists and customer records are set up so that several countries can share one system, each with its own chart of accounts where needed.
Data Migration and Spreadsheet Replacement
Existing records move into a new structure. Totals are reconciled before and after the cut-over, so the accountant can compare ledgers line by line and sign off each difference.