DataFlow runs sales, purchases, stock, accounts and VAT in a single database. Postings happen automatically as you process documents, so there is no import step between your trading system and your accounts — and no month-end reconciliation between two systems.
Sales, purchases, stock, accounts and VAT in one database
Multi-company on a single installation
Approvals, customisation and B2B integration built in
When an order and stock system is wired to a separate accounts package, the two are only ever as current as the last import.
Two systems held together by imports
An order and stock system pushes figures into Sage or Xero on a schedule, so the accounts are a copy of trading rather than the same record — and every import is a chance for the two to diverge.
The same data keyed twice
Customers, products and prices are set up in one system and re-keyed in the other, so a change in one place has to be remembered in the other, and the two drift apart over time.
Month-end spent reconciling two systems
Before the numbers can be trusted, someone has to reconcile the trading system against the accounts package — an exercise that only exists because the data lives in two places.
Every new need is another bolt-on
Approvals, EDI, multi-company, custom fields — each arrives as a separate add-on with its own licence and its own integration to maintain, so the stack grows more fragile with every requirement.
Overview
One database, built as one system.
Trading and accounts are the same record, not two copies kept in step.
One integrated database for trading and accounts
Sales, purchases, stock, accounts and VAT in the same database. Postings happen automatically as you process documents — no import step.
Onedatabase behind every module
Autopostings as you trade
Any number of companies on a single installation
Any number of companies on a single installation. Consolidation and inter-company processing built in.
Anynumber of companies
Groupconsolidation included
Approval chains with authority limits per user and module
Configurable per user, per group and per module. A monetary limit beyond which a document escalates for approval.
Per userand per module limits
Escalatesabove the set limit
Customisable down to the individual customer
User-defined fields and customer-specific EDI variants. Per-customer installer builds where they are needed.
Userdefined fields
Per customerEDI and builds
EDI, cXML PunchOut and Open Banking as first-class integrations
EDI, cXML PunchOut and Open Banking are first-class integrations. Part of the platform, not a third-party add-on.
EDIand cXML PunchOut
Open Bankingbuilt in
What sets it apart
The differences that matter, in depth.
Each differentiator has its own page — the detail behind the headline.
How is DataFlow different from an order system wired to Sage or Xero?
DataFlow holds sales, purchases, stock, accounts and VAT in one database, so postings happen automatically as you process documents. There is no import between a trading system and a separate accounts package, and no reconciliation between the two.
Can it run more than one company?
Yes. Any number of companies run on a single installation, with consolidation and inter-company processing included rather than added on.
How do approvals work?
Approval chains are configurable per user, per group and per module, each with a monetary limit. A document beyond that limit escalates up the chain for approval.
How far can it be customised?
Down to the individual customer — user-defined fields, customer-specific EDI variants and per-customer installer builds where they are needed.
