Skip to content

The OneStream implementation partner UK groups hire at a fixed price, after we survey the data model.

Constancia, an EPM consultancy, is an official OneStream (EPM software) partner based in the UK. We survey the data model before we quote, and the price is then fixed.

OneStream at a glance

Covers
Planning, financial close and consolidation, reporting and analytics.
Data in
Direct integration to Oracle, SAP, Microsoft, IBM, Infor, Workday, Databricks and Snowflake.
Our record
58 implementations over 35 years.
  • FedRAMP Rev. 5
  • ISO 27001:2022
  • SOC 1
  • SOC 2
  • GDPR

A OneStream implementation partner designs the data model, builds the consolidation and the planning on it and proves the new close against the old one. Constancia does that work for multi-entity groups with a date in the diary, and the build price is fixed after the survey.

Reads
The consolidation as it runs, every ledger that feeds it and the workbooks that finish the numbers.
Builds
Consolidation, planning and reporting on dimensions designed for the group as it reports now.
Proves
A parallel close beside the old one until the difference between them reaches zero.

A OneStream implementation is a build on top of a data model, and that model sets the price.

A OneStream implementation puts a group's close, consolidation, planning and reporting on 1 data model, for a finance team with a date it cannot move. The configuration is the visible half, and the data model underneath it decides how long the configuration takes.

Constancia has completed 58 OneStream implementations over 35 years, and the certified consultants who survey your model are the people who build on it. Nobody joins after the contract to learn your environment on your budget.

Where 9 entities close on 3 ERPs, the third ERP usually exports at a different grain from the other 2. Our survey finds that before the price is written, so the change order for it never exists.

Every OneStream build we do follows the same 6 steps, starting with the survey.

The order stays the same on every engagement, whatever the group is coming from. The 6 steps are what a group buys, and the configuration at the end is the smallest of them.

  1. 01

    Survey the estate

    We sit through a close and read the consolidation you run, the ledgers that feed it and the workbooks that finish the numbers.

  2. 02

    Name the risks

    Every finding goes into a written risk list with a named owner and a place in the build sequence.

  3. 03

    Fix the price

    The quote is written after the survey and carries every risk on the list, so a surprise in a ledger is already priced.

  4. 04

    Design the model

    The entities, accounts, periods and hierarchies are designed for the group as it stands, with the next acquisition allowed for.

  5. 05

    Build and prove

    We reconcile the new close against the old one in 4 layers, local currency, translated, eliminated and consolidated, until the difference is zero.

  6. 06

    Hand over

    Your team runs the system from go-live, with the documentation and the traceability written while the work happened.

The survey is a separate piece of work with its own written output, and the price that follows it holds.

Every group we implement OneStream for has these 4 things in common.

  1. 01

    Several entities and more than 1 ledger

    The group closes in 2 or more ERPs and assembles the group numbers afterwards, in a legacy consolidation or a workbook.

  2. 02

    A dated event in the diary

    An IPO, an integration, an audit clock or a board mandate for AI sets the date the build works back from.

  3. 03

    A legacy consolidation with a sunset date

    A consolidation in HFM, BPC or IBM Controller still produces the group numbers, with spreadsheets grown around it.

  4. 04

    Somebody to own it afterwards

    A named person in finance will run the system after go-live, so the documentation is written for them and for nobody else.

A single-entity business with 1 ledger and a straightforward close does not need a build of this size.

5 routes lead into OneStream, and 1 structural join decides each of them.

The platform move is the shorter half of every route. The right-hand column is the half that sets the timeline, and the survey reads it first.

The 5 routes into OneStream, with the object that moves and the structural join that sets the timeline on each.
What movesThe join that decides the route
Oracle HFMThe consolidation rules, the hierarchies and the history from Hyperion (Oracle's legacy EPM suite).A dimension in a mature HFM estate carries years of restructuring, and each hierarchy is read for what it was for before it is rebuilt.
SAP BPCThe consolidation, and usually the planning that grew into the same model.The plan and the consolidation are separated in the design, because OneStream holds them on 1 model with different rules.
Oracle FCCSA cloud consolidation, with planning and reporting in separate Oracle applications.The group decides whether it wants its applications separate or on 1 model, because both platforms are cloud.
IBM TM1Planning cubes, the rules attached to them and the reports built on top.Each rule is read and sorted into kept, rewritten or dropped before any cube is rebuilt.
AnaplanThe planning model, its lists and its modules.The statutory close ran in another system, so the consolidation is designed on OneStream and the plan moves beside it.

See more on our

Subscribe on YouTube
  • Latest episode

    How an EPM implementation works, and why the software comes last

Every Sunday, 6am

The Sunday Close.

Our weekly newsletter on AI in finance.
Yours to enjoy with your Sunday morning coffee.

  • AI in finance observations from Alex (CEO) and Brad (COO)
  • Newest video from our YouTube channel
  • AI in finance trends we have spotted each week

Tell us the date you are working to.

The people who would do the work read every message and reply inside 2 working days.