How to prepare business software for a second country

Open a sheet and write one row per country. Add the legal entity that will trade there, the bank account, the currency it settles in and the tax registration it needs. Most gaps hide in the entity column, because a branch and a subsidiary issue different invoices. That is the first pass.

Next, list the documents. Nothing here needs code yet. Sales invoice, credit note, delivery note, purchase order, payslip, customer statement and contract all change shape between countries. A short line beside each says who sees it, customer, tax office or auditor.

Finally, list the systems. Accounts package, CRM, warehouse tool, payroll service and website each hold a piece of the picture. Write down which of them stores a country, a currency or a tax code today. Write it all down.

Software cannot decide what the law requires. Ask early. Your accountant, tax adviser and local counsel can. Take the sheet to them and ask what each document must carry, which numbers must run unbroken and how long records must be kept.

Ask about timing too. Some countries want invoices reported soon after issue, others at period end; a late rule found after launch costs far more than a question asked in week one. One late rule can undo a launch.

Record each answer with the date and the adviser’s name. The trail stays. When a rule changes, you can see which settings depended on it.

A regional profile is one saved bundle of settings. It holds the currency, the date order, the number format, the address layout, the tax rule table, the document templates and the language. Switching a customer to a profile changes all of them together. Think of it as a bundle.

This beats scattered fixes. One place, one fix. Without profiles, a developer edits an invoice template for Germany, then separately edits a report for Spain, and nobody remembers which; with profiles, the rule sits in one place.

Keep the home country as a profile as well. It forces you to see which behaviour was assumed rather than chosen, such as a fiscal year starting in April or a comma used as a thousands mark. Nothing is hidden then.

Existing customers need a country, a currency and a tax status before they can use a profile. Blanks are common. Export the customer list and look at the blanks; many older records have a free-text address and no country code at all.

Time zones need the same care. A shift ending at midnight in one city lands on the next date in another, and a due date can slip a day. Store timestamps in one standard zone and show them in local time. Dates drift quietly.

If your current setup was built around one country, plan the migration as a separate task. Treat it as its own job. Fixed assumptions are often buried in formulas and printed forms.

Switch on the new profile for a pilot group, such as one customer, one branch or one product line. Raise real invoices, run a month-end and let the local adviser read the output. Keep the home market untouched while this happens. Start the pilot small.

Define what a good pilot looks like before it starts. Agree the finish line first. For example, a customer’s accounts team accepts the invoice without a query, the bank reconciles the payment, and the tax return draws from the same data.

Then widen the release. Write the lessons into the checklist and use it for country three; Your next step is simple: finish the country sheet this week and send it to your adviser. Then repeat.