Reference · built on requestOperator by FibricReporting & analysis

Forecast Variance

A closed period's forecast compared to ledger actuals by line, largest contributors named, a variance note and revision proposed.

Request accessPricing ↗

About

The forecast is kept in a spreadsheet and the actuals in the ledger, and the two meet once a month in someone's evening. This operator does the meeting. When a period closes, it reads actuals by account from the ledger: a Profit and Loss report from Xero by period and tracking category, or a SuiteQL query against NetSuite transactions. It reads the forecast for the same period from the Google Sheet or Excel workbook where it is kept, using the account mapping you provide.

For each line it computes the variance and ranks the contributors. It proposes a variance note to the line owner and, where the owner agrees, a revised forecast written to the sheet's next-period cells.

This is a reference listing. It documents what Fibric would read from Forecast Variance and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Profit and Loss rows by period from the Xero Reports endpoint, with periods, timeframe, and tracking category parameters
  • Transaction lines by account and period from NetSuite through the SuiteQL REST query service, paged by limit and offset
  • Budget lines from Xero Budgets and the Budget Summary report, where the forecast is kept in the ledger
  • Forecast cells by line and period from a named range in a Google Sheet, or a worksheet in an Excel workbook
  • The mapping from forecast lines to ledger accounts, and the period close flag you set
  • Prior variance notes and revisions for the same line, so a repeat cause is shown

Proposed actions

  • Target capability: propose a variance note per line naming forecast, actual, variance, and the accounts that contributed most
  • Target capability: propose a forecast revision written to the next period's cells in the sheet, with the old values kept
  • Target capability: propose a question to the line owner where a variance has no contributing account in the mapping
  • Target capability: propose a mapping fix when a ledger account with activity is missing from the forecast mapping

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Xero actuals against a Google Sheet forecast

    Month-end Profit and Loss rows from Xero are matched to the forecast tab by account mapping. Each line's variance and top contributors become one note; the revised cells are written after approval.

    With Xero, Google Sheets

  • NetSuite lines by department

    A SuiteQL query returns posted transaction lines by account and department. Variances are computed per department line and proposed to that department's owner.

    With NetSuite, Microsoft Excel

  • Forecast held in the warehouse

    Where the forecast is a Snowflake table, revisions are proposed as new rows with a version column rather than overwrites, and the note links both versions.

    With Snowflake, Xero

  • Budget kept in the ledger

    If the budget lives in Xero Budgets, the Budget Summary report supplies the forecast side and no spreadsheet is read.

    With Xero

Requirements

  • A ledger connector with period reports or a query interface: Xero, NetSuite, QuickBooks Online, or Sage Intacct
  • A file connector holding the forecast: Google Sheets, Microsoft Excel, or a warehouse table in Snowflake
  • A mapping of forecast lines to ledger accounts, and a named owner per line
  • A close signal per period, so it compares against final rather than partial actuals
Authentication
Read on the ledger's reporting scope, a Google Sheets or Excel scope for the workbook, and the account mapping stored with the deployment.

Limits

  • Xero's Profit and Loss report compares up to 12 periods in one call. Longer histories take more than one call.
  • SuiteQL through REST returns at most 100,000 rows per query and requires the Prefer: transient header.
  • Values are written to sheet cells as literals. Formulas in those cells are replaced, and the old contents are recorded.
  • It reads closed periods only. Mid-period reads are not offered because the actuals are incomplete.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Forecast Variance ↗

Questions and answers

What does a line owner approve?
The variance note for their line, and separately any revision to the forecast. The proposal shows forecast, actual, variance, the contributing accounts, and the cells that would change. The owner can edit the revised number before approving.
What is recorded for each line?
The report or query used, the forecast cells read, the variance, the note sent, and any revision with old and new values, who approved it, and the sheet range returned by the write.
Does it post to the ledger?
No. It reads reports and transactions. It never creates journals, edits budgets in the ledger, or changes the account mapping. Writes go only to the forecast sheet, only after approval, and only to the cells shown.
Ask about Forecast Variance

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy