UBCDATA BRIDGE
HomeIllustrative use case
Illustrative use case

Compare plans with actual results

Bring income and expenses from your accounting systems into a profit and loss report. Data Bridge checks the data and prepares it for comparison with your plan in IBM Planning Analytics or another system.

BASSQLIBM Planning AnalyticsUBC Analytics
HOW THE WORKFLOW RUNS
BASSQLIBM Planning AnalyticsUBC Analytics
01Collect the actuals
02Align the structure
03Review before writing
04Update the model
THE CHALLENGE

What slows the work down

Actuals arrive from different accounting systems, account structures do not match management reporting, and the plan lives elsewhere. Analysts repeatedly assemble files, check periods and rebuild mappings. A changed account or missing cost centre may remain unnoticed until the report is nearly ready.

Finance directors, controllers and analysts across business units.
A PRACTICAL EXAMPLE

Illustrative scenario: a manufacturing group prepares a monthly P&L for several legal entities. The analyst selects an entity and reporting period, reviews prepared actuals, then loads the relevant cube in IBM Planning Analytics or UBC Analytics.

HOW THE WORKFLOW RUNS

From the first step to the right action.

01

Collect the actuals

Read balances or transactions through a configured BAS interface, SQL query or agreed file. Use an authorised Agent connection when the source is inside a private network.

02

Align the structure

Map accounts, cost centres and entities to management reporting categories. Add the selected period and apply agreed calculation rules consistently to every incoming row.

03

Review before writing

Run a simulation and inspect totals and exceptions. Resolve unknown categories or incomplete records before the prepared dataset is written to the planning system.

04

Update the model

Send the result to the appropriate cube using a defined write method. Review the run history and reconcile the loaded totals with the source.

VALUE FOR THE TEAM

Make the work repeatable.

  • Reuse a maintained preparation process instead of rebuilding formulas across multiple reporting workbooks.
  • Make the origin of a management reporting category visible so finance and accounting can review it together.
  • Use period and entity parameters to apply the same controlled workflow during the next close.

Keep control of the result.

  • Restrict source access, available entities and target cube permissions to the operator’s responsibilities.
  • Define how missing mappings, empty values and a repeated load of the same period are handled.
  • Reconcile control totals and investigate partially completed writes before attempting another load.
THE WORKFLOW OUTCOME

Finance gains a repeatable route from accounting actuals to its planning model, with consistent categories and a traceable load history.

Capabilities behind this workflow
FROM IDEA TO WORKING FLOW

Bring your challenge. See a way forward.

Sources, rules and outcomes — let’s build the conversation around your workflow.