Date and number formats in international business writing cause more genuine confusion than most writers expect. A date written as 04/05/26 means April 5 to an American reader, May 4 to a British one, and something ambiguous to everyone else. A number like 1.000 means one thousand in the UK but one (to three decimal places) in Germany. These aren't edge cases. They're everyday errors that slip through proofreading and land on desks where they do real damage.
Why date formats cause so many problems
The core issue is that three major date conventions are in widespread use simultaneously. The United States uses month-day-year (MM/DD/YY). Most of Europe and Australia uses day-month-year (DD/MM/YY). And the ISO 8601 standard, which is the international format used in contracts, data systems, and technical documents, runs year-month-day (YYYY-MM-DD).
When you write 06/07/2026, a reader in Chicago sees June 7. A reader in Amsterdam sees July 6. Neither is wrong by their own convention. Both are reading your document incorrectly relative to what you meant.
The fix is straightforward: write the month as a word or abbreviation whenever there is any international audience at all. "7 June 2026" or "June 7, 2026" removes the ambiguity completely. For technical documents, contracts, or anything stored in a database, ISO 8601 gives you 2026-06-07, which is unambiguous and sortable.
Note that "7 June 2026" (day first, no comma) follows British and Australian style, while "June 7, 2026" (month first, comma after the day) follows US style. Either works for an international audience as long as the month appears as text. The date line in a business letter follows the same logic: spell out the month and remove the guesswork.
Commas in dates and the ordinal suffix question
US style adds a comma between the day and year when the month comes first: "June 7, 2026." It also adds a comma after the year when the date appears mid-sentence: "The contract signed on June 7, 2026, takes effect immediately." Omitting that second comma is a common oversight. The article on commas in dates covers the placement rules in detail.
Ordinal suffixes (1st, 2nd, 3rd, 4th) appear frequently in British writing but are less common in American date style and are entirely absent from ISO format. In international documents, skip them. "14 September" reads clearly to every English-speaking audience. "14th September" is fine but slightly formal and British-coded. "September 14th" is informal in most style guides and worth avoiding in contracts or official letters.
Number formats: decimals, thousands, and currency
Number formatting is where international confusion gets expensive. The decimal separator and the thousands separator are swapped between English-speaking countries and most of continental Europe.
- UK / US / Australia: a period marks the decimal (3.14) and a comma marks thousands (1,000,000).
- Germany / France / much of Europe and Latin America: a comma marks the decimal (3,14) and a period or space marks thousands (1.000.000 or 1 000 000).
If your document goes to a multilingual team or an international client, the safest approach is to use a thin space (or no separator at all for numbers under 10,000) for thousands, and to spell out the decimal convention in a document preamble or footnote for any figure where confusion could be costly. For financial documents, writing "EUR 1 250 000,00" versus "EUR 1,250,000.00" signals immediately which convention the writer is working in.
The International Bureau of Weights and Measures (BIPM) recommends a space as the thousands separator in scientific and technical writing precisely because it avoids the comma/period conflict. That convention is worth adopting in any document with a genuinely multinational readership.
Currency symbols and placement
Currency symbols don't behave the same way across languages, even when the currency is the same. In English, the symbol precedes the amount with no space: $1,200 or £450. In many European languages, the symbol follows the amount, sometimes with a space: 1.200 € or 450 £. When writing for a mixed audience, spelling out the currency name or code is less ambiguous. "USD 1,200" or "1,200 US dollars" works for every reader.
Three-letter ISO currency codes (USD, GBP, EUR, JPY, AUD) are universally understood in business contexts. Use them when there's any risk of confusion, particularly when the same symbol applies to multiple currencies. The dollar sign ($) applies to the US dollar, the Canadian dollar, the Australian dollar, the Singapore dollar, and several others. In an international contract, "$500" is imprecise. "USD 500" is not.
Percentages, telephone numbers, and units of measurement
Percentages are relatively safe. The % symbol is universal. The only question is whether to leave a space before it: "15%" (standard in English) versus "15 %" (standard in many European style guides and in ISO 31-0). For documents distributed across both audiences, either is defensible. Pick one and stick with it across the document.
Telephone numbers are genuinely tricky. The international format uses a plus sign and the country code, then the number in groups that vary by country: +44 20 7946 0958 for a UK number, +1 415 555 0123 for a US one. If your document includes contact numbers for an international audience, always lead with the plus sign and country code. A reader in Seoul can't call a UK number written as "020 7946 0958" without knowing to replace the leading zero with +44.
Units of measurement introduce a different kind of ambiguity. Most of the world uses metric. The United States uses US customary units. When writing for an international audience, include both where practical: "the package weighs 5 kg (11 lb)" removes the guessing. In purely technical or scientific documents aimed at non-US audiences, metric only is standard and expected.
Time formats: 12-hour vs 24-hour
The 12-hour clock with AM and PM is standard in the US and parts of the UK. The 24-hour clock is standard in most of Europe, the military, aviation, medicine, and logistics worldwide. For business documents with an international readership, 24-hour format removes any ambiguity: "14:30" is unambiguous in a way that "2:30 PM" technically isn't if the reader isn't certain which time zone you're in.
If you're coordinating across time zones, state the zone explicitly. "14:30 CET" or "09:00 EST" gives the reader what they need. For global coordination, UTC is the cleanest reference point: "15:00 UTC." The article on writing AM and PM correctly covers the formatting conventions in more detail for English-language documents.
A practical rule for international documents
The overarching principle is this: any format that depends on the reader sharing your local convention is a format that will eventually fail. Dates with numeric months, ambiguous separators in large numbers, and bare currency symbols all require the reader to guess your convention. In a global business context, that guess costs time or money.
Write the month as text. Use ISO 8601 for databases and technical records. Use ISO currency codes rather than symbols when there's a mixed audience. State time zones explicitly. And if your organisation sends documents to more than one country regularly, a one-page internal style note covering these conventions takes 30 minutes to write and prevents months of confusion.