Resolve tie out or data discrepancy issues

When fetched data doesn’t match your source system or expected values, work through the steps below in order.

Most discrepancies are caused by stale data.
Before reviewing the spreadsheet setup or dimension configuration, confirm Cube has your latest source data.

Step 1: Confirm Your Source Data Is Current

This is the most common cause of tie-out issues.

Before troubleshooting your spreadsheet or Workspace configuration, verify that Cube has imported the latest data from your source system.

Check Your Last Import Date

In the Workspace, navigate to Integrations. The most recent import date appears next to each source system integration.

If your source data changed after the last import—or if a period recently closed—run a new import for the affected periods before continuing. In many cases, this fully resolves the discrepancy.

Opening balance discrepancies
If opening balances are incorrect, re-importing a single period may not resolve the issue.

Re-import all affected periods sequentially so each period’s closing balance correctly rolls forward into the next period’s opening balance. For example:

• Jan-24 - Dec-24
• Jan-25 - Dec-25
• Jan-26 - Dec-26

Start with the earliest affected period and work forward chronologically.

If your source data is current and discrepancies remain, continue to the next step.

Step 2: Validate Your Spreadsheet Setup

Cube uses the dimension member names in your spreadsheet rows and columns to locate data during fetches. If any values don’t exactly match the dimension members in your Workspace, fetch results may be incomplete or incorrect.

Run Validate

In the Spreadsheet App:

1. Select Analyze
2. Select Validate

Cube will identify any dimension members it can’t recognize.

Common Issues To Check

• Typos or extra spaces in dimension member names
• Time values auto-formatted as dates in Excel or Google Sheets
  • Example: Jan-25 converted to January 25, 2026
  • To prevent this, prefix the value with a single quote: 'Jan-25
• Hidden rows or columns unintentionally included in the fetch range

After correcting any issues, fetch again and confirm whether the values now tie out.

Step 3: Review Filters and Hierarchies

Unexpected fetch values are often caused by filter selections or hierarchy changes.

Confirm Filter Selections

For dimensions used as filters instead of rows or columns, verify the selected dimension members include the data you expect.

For example, if you’re filtering on “All Departments,” confirm all Department dimension members are nested beneath that parent. Any members outside the hierarchy won’t be included in the rollup.

Review Hierarchy Changes

If dimension members were recently moved or re-parented, verify they’re still grouped correctly.

Hierarchy changes affect rollups and may shift aggregated values unexpectedly.

Confirm Scenario and Time Selections

Verify that your fetch is using the correct:

• Scenario
• Time period

Fetching a parent time dimension (such as a full year) instead of a leaf period (such as a month) will return aggregated totals.

Step 4: Review Dimension Configuration in the Workspace

If your spreadsheet setup looks correct, review the underlying dimension configuration in the Workspace.

Verify Dimension Mapping

Navigate to your source system mapping page and confirm dimension members are mapped to the correct Cube dimensions.

Pay close attention to:

• Newly added source-system members
• Members automatically mapped to a Clearing Account
• Scheduled import mapping rules

If new dimension members are routed to a Clearing Account by default, remap them to the correct destination and re-import the affected periods.

Check Clearing Accounts

If you use a Clearing Account as a default mapping target:

1. Fetch all full-year time dimensions for that account
2. Review whether unexpected values appear there

If data was incorrectly mapped:

1. Correct the mappings
2. Re-import the affected periods

Review Time Rollup Settings

Dimensions configured with No time rollup won’t aggregate across periods.

If values look correct monthly but incorrect quarterly or yearly, review the time rollup setting for the affected dimension.

Recalculate Formulas or Tags

If formulas or tags are involved:

1. Navigate to the affected dimension in the Workspace
2. Select Recalculate

Manual recalculation is required after formula changes.

Step 5: Check for Duplicate Published Values

If values appear higher than expected and you’ve published data to Cube, duplicate published entries may be the cause.

Check for Duplicates

1. In the Workspace, open Data Exporter
2. Filter for the affected dimension members
3. Review the exported data for duplicate entries

If duplicates exist:

1. Remove the duplicate row or column from your spreadsheet range
2. Re-publish the corrected data to overwrite the duplicate values

Step 6: Use Drilldown To Trace the Source Data

If the discrepancy still isn’t clear, use Drilldown in the Spreadsheet App.

Drilldown shows the underlying source-system line items contributing to a fetched value, helping you identify exactly where the discrepancy originates.

Still Need Help?

If you’ve completed the steps above and the discrepancy remains, contact Support and include:

• The affected periods and dimension members
• The expected value and the actual value
• The date of the most recent import
• A screenshot of the Drilldown results, if available
• Open a Cube Access Window

This information helps Support investigate the issue more quickly.