How Budgee reduces forecasts when actuals arrive

When Enable Automatic Forecast Adjustments is turned on, Budgee tries to stop actual transactions and forecasted transactions from both being counted for the same expected activity.

In simple terms, when a real transaction arrives, Budgee looks for forecast-generated transactions in the same category and same month and reduces those first.

It starts with the closest match it can find:

1. same month
2. same category
3. same customer or supplier if possible

If there is still some amount left after that, Budgee then reduces other forecast-generated transactions in that same category and month.

A simple example

Imagine Budgee has forecasted:

• Month: April
• Category: Sales
• Customer: Acme Ltd
• Forecast amount: $1,000

Then a real imported transaction arrives for:

• Month: April
• Category: Sales
• Customer: Acme Ltd
• Actual amount: $700

With automatic forecast adjustments turned on, Budgee reduces the forecast-generated amount from $1,000 to $300.

So instead of showing:

• Actual: $700
• Forecast: $1,000

Budgee shows the remaining forecast as:

That helps avoid double counting.

If the actual is bigger than the forecast

If the real transaction is larger than the matching forecast amount, Budgee reduces that forecast to zero.

It may then try to reduce other forecast-generated transactions in the same month and category.

If there is still some amount left after that, Budgee ignores the remainder. It does not push it into another month or another category.

What Budgee adjusts

Automatic adjustment only reduces forecast-generated transactions.

It does not directly reduce:

• scenario-created future transactions
• manually added future transactions that are not part of forecast generation
• imported repeating transactions from Xero

Those can still appear in forecast views, but they are not the direct target of this adjustment process.

Things to know