22 currencies
The UK finance team was supporting transactions across a wide range of EMEA currencies.
Customer story
From European Multi-Currency to Tailored Finance in the UAE: Why DataFlow Stayed the Choice Across Markets
From 22 currencies in Europe to AED reporting, UAE VAT and bespoke commission workflows, DataFlow adapted around each business.
“The team that supported the software was the key for me. Once we started working with Darius and his team, that convinced me we had made the right choice.”
The starting point
JCB needed more than basic multi-currency.
In the late 1990s, JCB International’s European operation was expanding across EMEA from its UK headquarters. The finance team was working across 22 currencies, while its existing Sage Line 50 setup could handle foreign currency in the cash book but not across the nominal, sales and purchase ledgers.
For Vas and the accounts team, that meant journals and manual currency work at a time when new branches and subsidiaries were adding further local reporting requirements. The business needed a system that could manage those currencies through the ledgers and still consolidate the European operation into sterling.
Ledger limitations
Foreign currency functionality did not extend across the full nominal, sales and purchase ledger structure.
Manual journals
Currency handling created repetitive accounting work that grew as the operation expanded.
Sterling consolidation
Local operations still had to roll into the UK-headquartered accounts in sterling.
Why DataFlow
The capability fit. So did the way the team worked.
JCB reviewed a range of financial systems, including larger enterprise platforms. The requirement was clear: support 22 currencies across the ledgers, meet the needs of a growing European operation and do it without the cost and slower change cycles of a much larger supplier.
DataFlow matched the core accounting capability Vas had seen in the larger alternative at roughly one-third of the cost. Just as important, its smaller specialist team could discuss and implement changes quickly — a major advantage for an operation adding currencies, entities and new reporting requirements.
Multi-base currency
Parallel currency records and reporting addressed the core finance requirement.
Mid-range cost
JCB could get the required capability without moving to a much more expensive enterprise platform.
Direct access
A smaller team meant requirements could be discussed with people close to the product.
Room to adapt
The system could be configured around JCB’s acquiring operation and existing processes.
“What I saw in the other system, DataFlow was able to do at one-third of the cost. Because the team was smaller, we could activate changes much more quickly.”
Proof at JCB
The first implementation proved the decision.
From initial evaluation through configuration, the project took around six months. The detailed work happened before go-live, so Vas recalls the live implementation itself taking about two days. DataFlow was configured around JCB’s acquiring operation, linked to its existing invoicing process and extended to support reporting through Excel.
The value was also visible when requirements changed unexpectedly. When a currency devaluation created a digit-length problem the system could not initially accept, Vas raised an urgent call and DataFlow produced a solution within 24 hours.
10 days
finance time saved every month The original JCB case study recorded two working days a week saved on currency conversion, plus another two days during month-end closure.
Two-day go-live
Detailed preparation allowed the live installation to be completed quickly.
24-hour response
An urgent currency-format issue was addressed by the following day.
Invoice integration
DataFlow enabled integration of inter company invoicing operations.
Excel reporting
ODBC links gave the finance team practical access to DataFlow data for reporting.
“By installing DataFlow, we eradicated the manual currency conversion processes. On this one process alone, the company saved two working days per week and another two days during month-end closure.”
The next test
Why DataFlow was chosen again.
That is where this story moves beyond JCB. By the time Vas left in 2016, he had seen DataFlow handle new currencies, changing reporting needs, integrations and urgent accounting changes. His next roles gave him the opportunity to make the choice again.
He selected DataFlow for another UK business and, after moving to the UAE, implemented it for two companies he supported there. The later businesses were different from JCB, but the reason for returning to DataFlow was the same: he already knew the system could be adapted around the requirement rather than forcing the finance process into a fixed model.
The first decision
22 currencies, European reporting and a need to remove manual conversion work.
Chosen again
Vas selected DataFlow for another UK business based on his earlier experience.
A different test
Two UAE companies brought new currency, VAT, commission and integration requirements.
“With DataFlow, whatever I needed to do across the different companies could be configured around my requirements. It made my work much easier and helped the businesses I supported too.”
DataFlow in the UAE
New country. New currency. New rules.
The UAE implementations were not copies of the JCB setup. Reporting was required in dirhams, while most transactions were entered in sterling or euros. Soon after implementation, UAE VAT was introduced, creating another local requirement that had not existed when the systems were first configured.
The two companies also needed more specialised workflows. DataFlow was configured for commission calculations, bank uploads and an integration with Microsoft Dynamics CRM so information needed for commission processing could move into the accounting system.
AED reporting
Reports could be produced in dirhams while the underlying transactions were largely in sterling and euros.
UAE VAT
The system was amended when local VAT requirements arrived after implementation.
Commission logic
Bespoke calculations supported the companies’ specific commission workflows.
Dynamics CRM
CRM information could feed the accounting process used to calculate commissions.
“It made my life a lot simpler operating the system. The reporting was easy, and I was able to deliver what they wanted in the format they wanted it.”
Why DataFlow remained the choice
The constant was the support behind the software.
For Vas, product capability explains the first selection. The support experience explains the repeat selections. Once JCB was live, he had direct access to people who understood the system, the accounting requirement and the practical impact when something needed to change.
That pattern continued across later implementations. He valued knowing that a request would be picked up, discussed and followed through rather than disappearing into a large support queue. It is the point he returned to most strongly when explaining why DataFlow remained his choice across different businesses.
Direct contact
Requirements could be discussed with people who knew the product in detail.
Fast response
Urgent operational issues were treated as real business problems to solve.
Product knowledge
Long-serving team members retained knowledge of earlier implementations and customisations.
Practical change
New reporting, tax and integration needs could be assessed and implemented around the business.
Clarity today
The relationship continued on a simpler setup.
Vas later used Clarity in a standalone company for much simpler accounting than the customised DataFlow installations he had managed before. His use has focused on the core ledgers, cash book, profit and loss and balance-sheet reporting. He described it as extremely easy to operate, while also making clear that he had not used Clarity deeply enough to assess more complex workflows such as stock or bespoke development.
The verdict
Start with the requirement. Then look at DataFlow.
Vas does not recommend choosing an accounting system on name alone. His advice is to begin with what the business actually needs. For organisations that require multi-currency accounting, tailored reporting, integrations or responsive customisation, his own experience has made DataFlow an option he would put on the shortlist.
10/10 recommendation
“It’s obviously 10 from my point of view. I would say to any company: have a look at DataFlow, because it provides what you require. If you need customisation, it is a lot cheaper than the large enterprise systems.”
Trusted by UK trading and accounting businesses
Bannerman Company Ltd
Take the next step
See how DataFlow could fit your finance requirements.
Talk through your currencies, reporting, integrations or bespoke workflows with a team that understands accounting.
Thank you
Your request has been received.
More customer stories
Other businesses running on DataFlow.
Principal AccountingBringing warehouse operations and accounting into one flexible ERP.
Read the story- Star Cargo Group
From seven companies to a £140m group, on the same finance system.
Read the story - Core Products
How Core Products put DataFlow at the centre of e-commerce and distribution
Read the story