Localisation · 2022

Quick Facts

• Industry: Global diversified holding company
• Role: Senior Consultant
• Impact: A solution implemented on top of the RCM (Account Reconciliation) and TXM (Transaction Matching) marketplace solutions to translate them into local culture format, so accountants in every region work in their own local conventions rather than a single US default.

---

Overview

The client is a global firm with accountants working from different regions, running OneStream's RCM (Reconciliation Control Manager / Account Reconciliation) and TXM (Transaction Matching) marketplace solutions. Out of the box, the solutions presented everything in a US-default culture format rather than each region's local conventions. I implemented a solution to translate the RCM and TXM marketplace solutions into local culture format, so the application works correctly for accountants in every region.

The Problem

The RCM and TXM marketplace solutions are mature, but for a global firm the culture handling fell short:

• Culture format wasn't local. The solutions presented dates, numbers, and currency in a single US-default culture rather than each region's local culture format.
• It applied the same way everywhere. There was no per-region awareness — the culture format didn't follow the region the user actually worked in.

The Solution

I built a solution on top of the existing RCM and TXM marketplace solutions — not a fork, and no change to the core marketplace solutions. It translates them into local culture format so each region's conventions are applied correctly, making the application workable for a global finance team rather than just a US-default one.

Results

Learnings

What worked. Implementing it as a layer on top of the RCM and TXM marketplace solutions rather than modifying them — the core solutions kept their behaviour, and the local-culture-format translation sat cleanly above, so nothing in the marketplace solutions had to be forked.