> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/help/quickbooks-integration/actuals-import.md).

# Actuals Import

This article explains how to import historical actuals from QuickBooks Online into a Model Reef model after you have mapped the Chart of Accounts, and how those actuals populate your variables and statements.

You will learn how to:

* Select the import date range and frequency.
* Pull actuals per account, per period.
* See how those actuals become Data Library series and variables.
* Combine historical actuals with forward forecasts.

{% hint style="info" %}
Prerequisites

Before running an actuals import, you should have:

* Connected the model to a QuickBooks company via **Authentication (OAuth)**.
* Run **COA Import** and mapped accounts to variable types, categories and branches.
* Saved those mappings for the model.

Without these, Model Reef cannot correctly interpret QuickBooks account data.
{% endhint %}

***

{% stepper %}
{% step %}

### Choosing the actuals date range

In the QuickBooks integration panel:

* Select **Import Actuals**.
* Choose a **start date** and **end date** for the historical data you want.
* Confirm the **frequency** to match your reporting (usually monthly).

Typical usage:

* For an initial model build, import several years of history.
* For updates, import from the end of the last import up to the current month or last closed period.
  {% endstep %}

{% step %}

### Pulling actuals from QuickBooks

When you run the import, Model Reef:

* Requests trial balance or equivalent account level data from QuickBooks for the selected date range.
* Computes per period values for each mapped account.
* Builds a time series of actuals for each account.

These time series are then written into the Data Library as structured series with consistent units and frequency.

No changes are made in QuickBooks. The integration only reads data in for modelling purposes.
{% endstep %}

{% step %}

### Creating and updating variables from actuals

For each mapped account, Model Reef will either:

* Create a new variable if no variable exists yet for that account mapping.
* Update an existing variable that is already linked to the account.

Each variable will:

* Be placed in the branch chosen during COA mapping.
* Use the variable type mapped from the QuickBooks account type (Revenue, COGS, Opex, Staff, Asset, Liability, Equity, Tax, Dividend).
* Use the mapped categories and subcategories for reporting.
* Reference the Data Library series that now holds the historical actuals.

Once created or updated, these variables immediately feed into:

* P\&L (historical actuals).
* Balance Sheet (opening balances and flows).
* Cashflow Statement and Cashflow Waterfall, via the timing engine.
  {% endstep %}

{% step %}

### Blending historical actuals with forecasts

With historical actuals in place, you can:

* Set a **model start date** and horizon so earlier periods contain actuals.
* Attach **forecast logic** (drivers, growth, seasonality) for periods beyond the imported range.
* Allow Model Reef to blend historical and forward periods for each variable.

A typical pattern is:

* Historical actuals populate from the import start date up to the most recent closed period.
* From that point forward, modelled assumptions drive revenue, costs, assets, liabilities and tax.
* Charts and reports display a continuous series combining both segments.

You can also set up scenarios that start from the same historical base but diverge in their forward assumptions.
{% endstep %}

{% step %}

### Validating imported actuals

After each import, validate that the data matches QuickBooks by:

* Comparing total revenue, key expense lines and net income for a sample month or quarter.
* Checking key Balance Sheet lines such as cash, receivables, payables, loans and equity.
* Looking at the Cashflow Statement and Waterfall to ensure the overall pattern aligns with expectations.

If there are differences, check:

* COA mappings (type, category and branch).
* Date range selection.
* Whether any QuickBooks adjustments were made after your export or front end report generation.

You can adjust mappings and rerun the import for the affected period if needed.
{% endstep %}
{% endstepper %}

***

## Updating actuals over time

To keep your model updated with QuickBooks actuals:

* Periodically rerun **Import Actuals** with a new end date (for example each month after close).
* Model Reef will append new periods and update existing series if QuickBooks history has changed.
* Auto created variables and linked statements will update automatically.

Forecast assumptions remain unchanged unless you decide to revise them in light of the new actuals.

***

## Related articles

* [Farm-Level Working Capital Planning](/use-cases/agriculture-and-primary-production/farm-level-working-capital-planning.md)
* [Build a Forecast Accuracy Tracker](/how-tos/scenarios-and-planning/build-a-forecast-accuracy-tracker.md)
* [Differences vs Ticker Fundamentals Import](/help/importing-from-google-finance-and-yahoo-apis/differences-vs-ticker-fundamentals-import.md)
* [Category Selection](/syntax/variables-syntax/category-selection.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.modelreef.io/help/quickbooks-integration/actuals-import.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.