Does DataFlow Support Multiple Companies and Integrate With Existing Systems?

Updated

Yes to both, with a caveat on the second. DataFlow (Clarity) is built to run any number of companies on a single installation, and its own modules — nominal ledger, trade ledgers, stock, order processing and VAT — all post to one database rather than exchanging files. The site also states that it "plugs into the systems you already run," though it does not name specific third-party products or list integration methods, so you should confirm the exact connectors you need before committing.

Multiple companies on one installation

The product page lists "Any number of companies on one installation" as a core capability. In practice this means you are not buying a separate copy of the software per entity, and the companies share one installation rather than being stitched together from separate systems.

What the page does not spell out is how far data is shared between companies — for example whether customers, products and the chart of accounts can be common across entities or must be maintained per company. If you run several trading companies with overlapping customer lists, that is the first question to put to DataFlow in a demo.

One database keeps trading and accounting in step

The central design claim is that the trading side and the accounting side sit on the same database. The modules page describes each module as posting to "the same integrated database," sharing one set of customers, products and accounts.

That matters because it removes the reconciliation step the site itself identifies as a common problem: orders and invoices in one tool, the ledger in another, with someone re-keying figures at month-end. With a single database, an order, delivery and invoice post as they are raised, and the ledger reflects them without an import step.

The module set, as described on the site:

Area Module What it covers
Accounting Nominal Ledger Chart of accounts, journals, cash book, reconciliation, period close
Trading Trade Ledgers Sales and purchase ledgers, receipts, payments, allocations, statements, aged debt, BACS
Trading Order Processing Quotations, orders, deliveries, invoices, credit notes, works orders
Trading Stock Control Catalogue, movements, layered pricing (description truncated on the page)

VAT is handled within the same system, with HMRC Making Tax Digital described as built in, alongside EC Sales Lists and payment-practices reporting.

Integrating with existing systems

The site's heading "Plugs into the systems you already run" signals that DataFlow expects to sit alongside other software rather than replace everything. However, the supplied page content does not list which systems, which protocols, or whether connections are pre-built or bespoke.

So the honest position is: integration is claimed, specifics are not published in the material available. Before you rely on it, ask for:

  • Named connectors for the systems you actually use (e.g. ecommerce, CRM, payroll, banking feeds).
  • The method — API, file import/export, or a middleware layer — and who maintains it.
  • Direction and timing — real-time or scheduled, one-way or two-way.
  • What still needs manual handling, since the site's own pitch is about avoiding imports and re-keying.

A practical way to decide

If your main pain is that trading and accounts live in separate tools and month-end is a reconciliation exercise, the single-database design is the relevant feature, and multiple companies on one installation is a bonus if you run more than one entity.

If your main requirement is connecting to a specific external platform, treat integration as unconfirmed until you have it in writing. Book a demo and bring a short list of the systems you run and the data you need to move between them; that turns a general claim into a testable answer.

One further note: the page mentions pricing and purchase as signals but publishes no prices or payment terms, so cost and licensing should be raised directly rather than assumed.