Anyone coordinate regularly with accountants abroad? How do you manage it?
Options
CrossBorderCFO
Registered Posts: 1 New contributor 🐸
Bit of a process question rather than anything technical.
Some cross-border work is moving under me at the moment, and I've been doing walkthroughs of how we currently handle communication with local accountants in Italy, France and a few other countries. It's not great, everyone's doing their best in English, but things get lost. Terms get used slightly differently locally, a figure or treatment gets described in a way that doesn't quite match what we'd expect, and a lot of it ends up as a long email chain that nobody could easily explain to an auditor afterwards.
Trying to work out whether this is just normal and everyone copes the same way, or whether other firms have actually got a decent system for it.
- Anyone got bilingual staff specifically for this, or does it fall to whoever happens to speak the language?
- Any tools beyond Google Translate or DeepL that actually help with the accounting side of it?
- Is it the language that's the problem, or more that local rules and terminology don't map cleanly onto what you're used to?
- Has it ever genuinely caused an issue, something that came up in an audit or a dispute?
Would be good to hear how others handle it day to day. Thanks!
Some cross-border work is moving under me at the moment, and I've been doing walkthroughs of how we currently handle communication with local accountants in Italy, France and a few other countries. It's not great, everyone's doing their best in English, but things get lost. Terms get used slightly differently locally, a figure or treatment gets described in a way that doesn't quite match what we'd expect, and a lot of it ends up as a long email chain that nobody could easily explain to an auditor afterwards.
Trying to work out whether this is just normal and everyone copes the same way, or whether other firms have actually got a decent system for it.
- Anyone got bilingual staff specifically for this, or does it fall to whoever happens to speak the language?
- Any tools beyond Google Translate or DeepL that actually help with the accounting side of it?
- Is it the language that's the problem, or more that local rules and terminology don't map cleanly onto what you're used to?
- Has it ever genuinely caused an issue, something that came up in an audit or a dispute?
Would be good to hear how others handle it day to day. Thanks!
0
Comments
-
test0
-
Hi, this is completely normal — and yes, it is usually the mapping, not the language, that causes the real problems. A fluent conversation can still hide a different accounting treatment, and that is what an auditor will pick up later.
The fix that works best in my experience is a chart of accounts mapping table, agreed once and then reused. One row per local account, with five columns: local code, local label, English label, the UK nominal code it maps to, and the treatment. Do not let anyone translate a term on the fly in an email — if it is not in the table, it gets added to the table first, with the local accountant confirming it. That one habit removes most of the "we thought it meant X" errors.
Here is why it matters, with a small example. Take an Italian supplier invoice for €10,000 plus 22% IVA, €2,200, so €12,200 in total. If someone reads the total and books the whole €12,200 as an expense, the cost is overstated by €2,200 and the recoverable VAT is missed entirely. The correct booking is €10,000 expense and €2,200 input VAT, and the mapping table is what stops the €12,200 version from happening. The same thing happens with prepayments: a French "charges constatées d'avance" balance of €6,000 booked as an expense in the month would understate profit by €6,000 that month. The numbers are not large in either case — the point is that the error is invisible until someone reconciles it.
On your other questions: bilingual staff help, but they are not a system on their own — the person who speaks Italian still needs the mapping table, or they become a single point of failure when they are on holiday. For tools, machine translation such as DeepL is fine for a first draft of an email, but I would not use it as the record for anything with a number or a legal term in it. Keep the original document, keep the translation next to it, and keep a short decision log: date, document, what was decided, and who confirmed it. Then a long email chain becomes a one-page file an auditor can actually follow.
And on deadlines: agree one monthly close pack, in one template, with the same cut-off date for every country, stated in local time. Most cross-border friction I have seen is not a language gap at all — it is three different versions of "month end" arriving in three different formats.0