Month-end numbers, without the rekeying.
Most of the time in a close goes on the data, not the accounting: pulling it from several systems, reshaping it, reconciling it by hand. We build the collection and the movement so your team can spend the month on the numbers that need judgement.
Which problem do you have?
No system holds the data, so you ask people for it
Headcount, local adjustments, intercompany confirmations, the figures behind a KPI: every period the same request goes round the entities and the answers come back in every shape. That is a collection problem. ONESOURCE DataFlow gives every entity one template, with validation and controls, rolled forward each period, and reports across all of it from one place.
ONESOURCE DataFlow →A system holds the data, but in the wrong shape or place
Trial balances in three ERP formats, adjustments kept in a separate file, expense postings that need matching and grouping before anyone can summarise them. That is a movement problem, and integration is the answer: Alteryx workflows map, check and publish the data between systems, with every step visible and nothing rekeyed.
Alteryx for tax and finance →Often it is both. The collection feeds the integration, and we build the two to work together.
Is it worth a conversation?
- 1Month-end numbers are pulled from more than one system and put together by hand
- 2The same adjustments and the same mapping are redone in Excel every month
- 3Reconciliations are worked line by line, and the exceptions are found last
- 4A summary goes to the board that nobody can trace back to its postings
- 5One person knows how the spreadsheet works, and the close waits for them
A yes to any of them is worth a conversation. If a system can already give you the data in the shape you need, you do not need us for this, and we would tell you so.
Built once, run every period
Four finance examples in Alteryx: a monthly income statement for every company, an expense analysis with the contras taken out, a VAT reconciliation across two ledgers, and one master trial balance from three ERPs. Each is silent with the steps captioned on screen, and each has its own page you can send on.
Every entity on one template
One example of a DataFlow collection. The example shown is a tax one, a corporation tax disallowables analysis, because that is where the video comes from; the shape is the same for anything a finance team currently emails a spreadsheet for and then types up.
How we implement DataFlowFinance data management: questions we are asked
Do we need to replace a system?
No. The tools we use sit alongside your ERP and your reporting tools. Alteryx moves and shapes data between systems you already have, and ONESOURCE DataFlow collects what no system holds. Nothing is replaced.
Do we need both DataFlow and Alteryx?
Often not. If the problem is collecting data from people, DataFlow on its own may be enough. If the problem is data that exists but is in the wrong shape or the wrong place, Alteryx on its own may be enough. Where both problems exist, the two work together, and we tell you which you need after a short conversation.
Who runs it afterwards?
Your team. Every workflow and template is documented and handed over running, with training on your own set-up, so it does not depend on us or on one person in your team.
Which problem is yours?
Tell us where the time goes in your close today. We will say which of the two it is, or whether it is neither.