Most large finance teams spend too much of the close moving numbers between systems. Actuals sit in the ERP. Consolidation runs in one product. Planning runs in another. Reconciliation, tax, and workforce planning each have their own tool. Every handoff needs an integration, and every integration needs a reconciliation.
OneStream is built to cut that down. This guide explains how it works, from the big idea down to the design choices that matter in a real implementation. We write it for finance leaders, IT leaders, and project sponsors who are evaluating OneStream or preparing to implement it.
1. What OneStream is
The ERP records transactions: invoices, payments, payroll, and journals. SAP, Oracle E-Business Suite, PeopleSoft, and Microsoft Dynamics 365 are common examples. The ERP is the upstream system.
OneStream is the downstream system. It takes actuals from the ERP and uses them for consolidation, close, reporting, planning, budgeting, and forecasting.
OneStream calls itself a CPM platform (Corporate Performance Management). Oracle uses the term EPM (Enterprise Performance Management) for Hyperion. Both describe the same category.
What sets OneStream apart is the single-platform approach. OneStream describes its product as one extensible platform that unifies consolidation, reporting, planning, and analytics in one application. The analyst firm BARC describes it the same way. Compare that with the classic Oracle Hyperion landscape, where HFM handles consolidation, Hyperion Planning and Essbase handle planning, and separate products cover reconciliation, tax, workforce, and capex, connected through tools such as FDMEE and ODI.
Beyond the core consolidation and planning features, the Solution Exchange adds downloadable solutions. OneStream builds over 50 of them, including account reconciliations, transaction matching, tax provision, lease accounting, capital planning, cash planning, and sales planning. Partners and the community add more.
2. How OneStream is built
OneStream uses three tiers. The web tier handles user interaction. The application tier runs the business logic: calculations, consolidation, and rules. The database tier holds the databases.
Users do not install OneStream itself. They connect to it through a client: the OneStream Windows App, a web browser, or the Excel Add-in. The Windows App also includes a built-in Spreadsheet tool that offers functionality similar to the Excel Add-in, without needing Excel installed.
OneStream runs in the cloud on Microsoft Azure or on-premises, and it is the same application in both. The main difference is integration. On-premises, OneStream and the ERP usually share a network. In the cloud, they do not. For that case, OneStream provides the Smart Integration Connector (SIC). A gateway runs inside the company network as a Windows service, connects to the chosen data sources, and opens an outbound, TLS-encrypted connection over port 443. Azure Relay brokers the traffic between the gateway and OneStream in the cloud.
3. Navigation: three areas, controlled by security
The navigation pane has three tabs: OnePlace, Application, and System. Which tabs a user sees depends on their security.
OnePlace is where business users work. They run their workflow, open reports and dashboards, and access shared documents.
Application is where the application is built: workflow, integrations, mappings, dimensions, cubes, reports, forms, and rules. Consultants, developers, and application administrators work here.
System is where system administrators manage the platform: applications, users, groups, security, logs, and environment information.
The Point of View (POV) pane on the right sets which dimension members a user is looking at. We explain dimensions below.
One point we stress with every client: the workflow is not delivered ready-made. The steps users see each month, such as importing the trial balance, reviewing statements, posting journals, and certifying, are designed from the company’s own close process. A small company may have five steps. A large group may have twenty. They are gathered in requirements, written into the design document, and then built.
4. Applications and databases
An application is the container for one OneStream solution: its dimensions, cubes, workflow, rules, reports, and data.
OneStream’s documentation explains that each application has its own dedicated SQL database. A separate framework database holds system-wide security and authentication data, such as users, groups, and roles.
In practice, a production environment runs one live application, sometimes with archived copies kept for reference. Non-production environments often hold several applications at once, for example a fresh copy of production for testing a fix. We always recommend investigating production issues in a copy, never in the live application. In the cloud, environment copies are handled through OneStream support or OneStream’s cloud administration tools.
5. Time: decide it before you build
Time is one of the few decisions in OneStream that cannot be undone.
The time structure is set when the application is created. The standard structure is years, half-years, quarters, and months. A custom time dimension can support weekly or 12/13-period frequencies, and calendars like 4-4-5. OneStream’s documentation states that the time dimension cannot be changed after the application is created. A different time structure means a new application.
So before anyone creates an application, we confirm with the business: Is there a 13th adjustment period? Is planning done weekly? Does any part of the group use a 4-4-5 calendar?
Fiscal years are handled separately, with Time Profiles. A Time Profile aligns the accounting periods with the company’s calendar or fiscal year. The standard profile runs January to December. A company with an April to March year creates a profile where the first period is April. Profiles are assigned to cubes.
This matters for multinationals. If India reports April to March and the US reports January to December, the first period means a different month in each. One design approach is to load each calendar into its own cube with its own Time Profile, then move the data into one main reporting cube, mapping the periods along the way. The same dimensions can be shared across those cubes, so the metadata is not duplicated.
6. Dimensions: what every number means
A number in OneStream means nothing on its own. It needs context: which company, which account, which month, which scenario. Dimensions provide that context.
Excel finds a value by row and column. OneStream finds a value by many dimensions at once. OneStream uses 18 dimension tokens in total:
Entity, Parent, Consolidation, Scenario, Time, View, Account, Flow, Origin, Intercompany, and eight user-defined dimensions, UD1 to UD8.
A short guide to each:
Entity is the organisation structure: legal entities, business units, countries, and regions.
Parent shows which parent an entity rolls up to in the hierarchy being viewed. The same entity can sit under a legal parent and a management parent.
Consolidation holds the steps from local data to the consolidated result, including translation, share, eliminations, adjustments, and the top-level result. It also holds currency members.
Scenario separates Actual, Budget, Forecast, and other data sets.
Time combines year and period in one member, such as 2026M1.
View controls how values are shown, such as periodic or year-to-date.
Account holds the chart of accounts, plus statistical and driver accounts.
Flow tracks balance sheet movements: opening balance, increases, decreases, and closing balance.
Origin shows how data arrived: imported, entered in a form, or posted as an adjustment.
Intercompany identifies the partner entity in transactions within the group, so they can be eliminated.
UD1 to UD8 are free for the business to use: department, product, project, region, or anything else needed for analysis.
Not every dimension can be configured in the same way. OneStream’s documentation lists Origin and View as system-defined and not editable. This has real design effects. For example, if the business wants to split adjustments into corporate, regional, and elimination types, those categories cannot go into Origin. They go into a UD dimension instead.
Two more points for design teams. A dimension is the category, and members are the values inside it. “Product” is a dimension. “Laptop” is a member. Also, an application can hold several dimensions of one type, such as consolidation accounts and planning accounts, and each cube is assigned the one it needs.
7. Data units: why scope drives performance
OneStream processes data in blocks called data units. The documentation describes the data unit as the unit OneStream uses to load, clear, calculate, store, and lock data.
The cube data unit is defined by Cube, Entity, Parent, Consolidation, Scenario, and Time. It is the level where calculation, translation, and consolidation run. Workflow data units add Account, and optionally one user-defined dimension, to narrow the scope for loading, clearing, and locking.
For an enterprise, this is not just theory. Business rules that target a well-defined data unit run faster than rules that sweep large parts of the database. And when many users load data at the same time, a finer workflow data unit lets each team load and lock its own slice without waiting on others.
8. Consolidation in plain terms
Consolidation turns many company-level results into one group result. In OneStream, the Consolidation dimension holds each step.
Data starts in the entity’s local currency. It is translated into the parent’s currency. The share that belongs to the parent is calculated. Intercompany transactions are eliminated, because money moving between two group companies is not group income. Adjustments can be posted along the way. The final group number sits at the top.
A simple way to put it: consolidation moves data from the local level to the top.
9. Foreign exchange rates
When an entity’s currency differs from its parent’s, its numbers are translated using FX rates.
OneStream’s documentation lists four rate types: Average Rate, Opening Rate, Closing Rate, and Historical Rate. Rates are held in a central system location that all cubes reference, not inside each cube.
As standard accounting practice, income statement accounts are usually translated at an average rate, because they build up over the period. Balance sheet accounts are usually translated at the closing rate, because they represent a balance at a point in time.
Planning teams often need their own rate sets, such as a budget rate or a forecast rate, because future rates are estimates. These are added as custom rate types.
Rates can be entered manually, submitted from Excel through the Excel Add-in, or loaded from a CSV file through the Load/Extract tool. For large groups, file-based loading is the practical choice.
One expectation to set with finance early: local-currency totals should tie between the ERP and OneStream, but translated totals may not. The ERP often translates each transaction at a daily rate. OneStream translates monthly totals at average or closing rates. The difference is a normal part of currency translation, not an error.
10. Building metadata
Members are built in the Dimension Library. A hierarchy defines how data rolls up, for example business units into countries, countries into regions, and regions into the group.
The same member can appear in more than one hierarchy, such as a legal structure and a management structure, without creating a duplicate. It is one member with several relationships. Member names must be unique across the application.
For bulk work, the Grid View lets teams review and update many members at once, and export them to Excel.
Two rules we apply on every project:
Do not delete members that hold history. OneStream does not allow deleting a member that has data. When a business unit closes, it is marked as no longer in use, and its history stays reportable.
Metadata is never finished. When the ERP adds a new account, company, or business unit, OneStream needs the matching member before the data can load. This needs a clear handoff between the ERP team and the OneStream team.
11. Design decisions to make early
From our experience as implementers, these decisions shape everything that follows:
The time structure, including any weekly, 13-period, or 4-4-5 needs, before the application is created.
The fiscal calendars in the group, and the Time Profiles and cubes they need.
What each UD dimension is used for, and naming conventions for every dimension, agreed with the business and written into the design document.
The FX source, the rate types for actuals and for planning, and how rates are loaded each month.
The monthly workflow steps, based on the real close calendar.
Environments, copies, and who owns the database work in an on-premises setup.
Getting these right at the start is far cheaper than changing them later.
Key points
OneStream takes actuals from the ERP and runs consolidation, planning, and reporting on one platform.
It has three tiers, connects through the Windows App, browser, or Excel Add-in, and runs in the cloud or on-premises.
OnePlace is for business users, Application for builders, and System for administrators.
Each application has its own database. The time structure cannot change after creation.
Every number is stored across 18 dimension tokens. Data units define how data is processed.
FX rates are stored centrally and translate local results into the reporting currency.
Frequently asked questions
Is OneStream an ERP?
No. The ERP records transactions. OneStream uses that data for consolidation, planning, and reporting.
Can we change the calendar after go-live?
The time structure cannot be changed after the application is created. Fiscal-year alignment is handled through Time Profiles.
How many dimensions does OneStream have?
OneStream uses 18 dimension tokens, including eight user-defined dimensions, UD1 to UD8.
Why do translated numbers differ from the ERP?
The ERP often translates at daily rates. OneStream translates monthly totals at average or closing rates. Local-currency totals should still tie.
Does OneStream need a separate integration tool for a cloud deployment?
OneStream provides the Smart Integration Connector to reach data sources inside the company network from the cloud.