Jirav Automated Month-End Variance Report to Sheets
At month-end, WebRun opens Jirav, reads the latest close actuals and budget figures for each account or cost centre, computes the variance and percentage deviation, and writes a structured variance table to a designated Google Sheets tab so the finance team can begin their close review immediately.
How can I automatically generate a month-end actuals vs budget variance report from Jirav into Google Sheets?
At month-end, WebRun opens Jirav, reads the close actuals and budget figures for every account and cost centre, computes the dollar variance and percentage deviation, and writes a structured table to a dedicated Google Sheets tab. The finance team arrives to a ready-to-review close report with materiality flags already applied.
- Month-end variance table is ready in Google Sheets before the finance team starts their day
- No manual export or copy-paste from Jirav at close
- Materiality flags highlight the lines that need attention first
- One tab per month keeps the full close history intact
Built for FP and A teams · finance controllers · CFOs · accounting teams · financial planning analysts
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.jirav.comin a real browser with your saved login - no setup, no API keys. -
1
Jirav - read month-end close actuals and budget figures
jirav.com
WebRun opens Jirav to read month-end close actuals and budget figures. - Open Jirav and navigate to the month-end close reporting section
- Select the just-closed period and load actuals for each account and cost centre
- Retrieve the corresponding budget figures for the same period
- Calculate the dollar variance and percentage deviation for each line
- Flag lines where variance exceeds the materiality threshold configured for the automation
Done when Every account and cost centre has an actuals figure, a budget figure, a dollar variance, and a percentage deviation for the closed month.
-
2
Google Sheets - receive the variance table for close review
google.com
WebRun opens Google Sheets to receive the variance table for close review. - Open the designated month-end variance Google Sheet
- Write the variance table to the named tab for the closed month, including account, actuals, budget, dollar variance, and percentage deviation columns
- Apply conditional formatting to highlight lines above the materiality threshold
- Stamp the sheet with the run date and the period covered
Done when The variance table for the closed month is written to Google Sheets and ready for finance team review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it overwrite previous months' data in Google Sheets?
No. WebRun writes each month's variance table to its own named tab, so prior close periods remain intact. The sheet grows one tab per month, giving you a full historical record without any overwriting.
Which accounts or cost centres does it include in the variance table?
WebRun pulls every account and cost centre visible in your Jirav month-end close view for the period. You can configure a materiality threshold at setup so small variances are included but flagged separately from material ones.
What if the month-end close in Jirav is not finalised when the automation runs?
WebRun reads whatever actuals are available in Jirav at run time. If you run month-end close on a fixed date, schedule this automation to fire the morning after that date so the figures are stable and the variance table reflects the final close.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.