Connect Planning Data and Actuals

Summary

This guide connects a planning dataset and verifies that its actuals reach the intended scenario-planning model.

Capabilities

You can connect external data sources such as accounting platforms or CSV files, import and refresh actual financial actuals, map to the appropriate model structures (including dimensions and categories), and review the impact of these actuals within planning models for ongoing scenario analysis.

Prerequisites

Before You Start

• Confirm the active workspace.
• Use a role that can connect or import the source and edit the model.
• Identify whether the model needs statements, transaction-category actuals, or invoice actuals.
• Keep one known source period available for verification.

Concepts

Planning models separate forecast and actuals by defined boundaries. Sources may include statements, transaction categories, or invoices, and can be connected directly from supported providers or imported as CSVs. Mapping and dimensions ensure actuals are not only loaded but also classified and structured for accurate scenario planning. Linking and refreshing data imports are distinct from changing any original provider records.

Workflow

1. Choose the Dataset

Open Scenario planning → Data, then select New.

Available datasets include:

• Xero statements
• QuickBooks invoice actuals
• bank-transaction category rollups
• CSV transaction-category actuals
• Stripe invoice actuals

Read the catalog description. A provider connection can exist without a supported planning dataset. Do not select a source marked Coming soon for a current model.

2. Complete the Connection or Import

Follow the source-specific steps.

Connected provider

1. Select the provider.
2. Complete authorization or choose the existing connection.
3. Choose any required accounting method or dataset options.
4. Finish the setup.

CSV import

1. Select CSV import.
2. Upload the supported file.
3. Map the necessary transaction fields.
4. Complete the import.
5. Check the imported period and category values.

Return to Scenario planning → Data after the setup.

3. Confirm the Source

Find the new source under its provider connection.

Confirm:

• the source name
• the dataset type
• the expected connection
• the current status
• the last refresh value

If the source is missing, clear search and filters. Then confirm that the selected provider supplies a planning dataset.

4. Run the First Refresh

Use the source's refresh action.

Wait for the success or failure message. Do not navigate away while you still need the result to diagnose the first setup.

When the refresh fails:

1. Read the error.
2. Check provider authorization.
3. Confirm that the provider or import contains records.
4. Retry the individual source.
5. Use Refresh all only after the source succeeds by itself.

5. Open the Model

1. Select Scenario planning → Models.
2. Open the intended model.
3. Confirm the model name and active scenario.
4. Open model settings.
5. Check the date range and actuals boundary.

The source can refresh successfully while the model still excludes its periods.

6. Import or Link Actuals

Select Import actuals when the model has no imported actuals. Select Refresh actuals when they already exist.

When the model uses a focused source control:

1. Open Sources.
2. Select the statement, transaction-category, or invoice source.
3. Link it to the intended model area.
4. Refresh the source from the model when needed.

A source link changes planning data. It does not edit the original invoice, transaction, or provider statement.

7. Verify a Known Period

Choose one period that you can confirm in the source system.

Compare:

• the period
• the currency
• the category or invoice grouping
• the amount
• the actuals-versus-forecast boundary

Do not validate only the grand total. A total can match while categories or periods are mapped incorrectly.

8. Check Dimensions

When the model uses a dimension:

1. Open Scenario planning → Dimensions.
2. Find the dimension and owning model.
3. Check its members.
4. Return to the model.
5. Confirm that imported values map to the intended members.

Create or rename a member before building formulas that depend on an unclear structure.

9. Recalculate and Review

After actuals are current:

• review formula outputs
• check for missing or error values
• confirm that forecasts begin after actuals
• compare the base and any active scenario
• save a version before a large remapping

Document any manual adjustment separately from the source import.

Ongoing Refresh Routine

Use this sequence when source records change:

1. Refresh the source under Data.
2. Confirm the refresh result.
3. Open the model.
4. Select Refresh actuals or refresh the linked source.
5. Verify one changed period.
6. Review dependent formulas and scenarios.

A recent timestamp is helpful, but representative record verification is the stronger check.

Behavior specification

Troubleshoot

The provider is connected but no planning source exists

Open the planning catalog and confirm that the provider has an available dataset. Some provider connections support other Eigenn features before they support planning data.

Refresh succeeds but values are missing

Check the source date range, model date range, actuals boundary, currency, and mapping. Also confirm that the provider or CSV contains the expected records.

Values appear in the wrong dimension member

Correct the member or source mapping. Do not change the formula to compensate for a classification error.

Refresh all reports several failures

Retry each failed source separately. This identifies which provider connection or dataset needs recovery.

Diagrams

Rendering diagram…

Screenshots

Shown with synthetic data in a local workspace.

Verification

1. After connecting a source and importing actuals, locate the new source in the system and confirm it appears with the correct name, type, connection, and current status. (Expected: The source is visible and correctly listed.)
2. Upon refreshing the source, check for the success or failure message. (Expected: Success or clear failure details are shown.)
3. In the planning model, compare one known period's actual values against those in the original source, confirming period, currency, category, group, and amount. (Expected: All values match with the source system for that period.)
4. For models using dimensions, check that imported actuals map to the correct members. (Expected: Each value appears under the intended dimension member.)
5. After every update, review and confirm that forecast data begins after the actuals boundary and no formulas return errors. (Expected: Forecasts and actuals are separated and calculations complete without error.)
6. On subsequent refreshes, verify at least one changed period aligns with external source records. (Expected: The updated period reflects new data as expected.)

Related

Related Pages

• Planning Data and Dimensions
• Scenario Planning
• Create Your First Planning Model
• Bank Connections
• Reconcile and Categorize Transactions