How it works
From actuals export to driver-labeled variance — one session.
Three steps. No new ERP integration. No pivot tables to rebuild. Upload the file your team already produces at month-end — Finwren maps the schema, runs the attribution pass, and returns annotated output before the board deck assembly window closes.
Step 01
Connect your actuals
Upload an ERP export, Excel file, QuickBooks report, or NetSuite subledger pull. Finwren maps the schema automatically — account names, period columns, budget vs. actual columns. Structured or semi-structured input, no reformatting required.
Account,Period,Actual,Budget,Prior_Mo
Net Revenue,Oct-25,4763000,4820000,4701000
Cost of Revenue,Oct-25,1381000,1446000,1390000
Gross Profit,Oct-25,3382000,3374000,3311000
SG&A,Oct-25,1332000,1190000,1156000
R&D,Oct-25,498000,510000,490000
EBITDA,Oct-25,2050000,2184000,2165000
# 6 rows · schema auto-detected · 3 cols mappedStep 02
Finwren maps variance drivers
Line by line, not just totals. Every account that moved versus budget receives a driver label. The one account explaining the majority of the EBITDA variance is surfaced at the top, with the supporting context to validate the driver with the relevant department head.
Variance map — Oct 2025
Step 03
Narrative ready for the deck
Finwren generates annotated narrative sections with the driver labeled, the variance quantified, and the question to surface in the board meeting. Ready to paste into your presentation before the meeting starts.
Questions from FP&A teams before onboarding
Finwren reads Excel (.xlsx), CSV, and standard ERP export formats. QuickBooks P&L reports, NetSuite saved search exports, and Sage income statement exports all work without reformatting. The requirement is a structured file with account identifiers, period, actuals, and budget columns. Finwren detects the column mapping automatically.
No. Finwren is built to run on exports — the flat files and structured reports your team already produces at month-end close. A native ERP connector is available for Enterprise customers who prefer a direct feed, but the Analyst and Team tiers run entirely on uploaded exports. No ERP credentials, no IT change request required to get started.
Finwren uses pattern analysis across the account structure and historical actuals to identify movements that represent a meaningful departure from trend or plan. Driver categories — headcount, accrual timing, volume mix, pricing, one-time items — are assigned based on the accounting context of each account type. The attribution is a starting point for your analysis, not a replacement for it. FP&A judgment on context (seasonality, deliberate plan changes, one-time events) applies on top of the driver output.
No data is stored beyond your active session. When you close the session, your uploaded actuals are not retained. See our Security page for the full data handling policy.
For a standard monthly P&L with 50-200 line items, the variance attribution completes in under 60 seconds. Multi-entity consolidations with 5+ legal entities typically complete in 3-5 minutes.
Yes. The Team tier supports up to 5 data sources and multi-entity consolidation. Enterprise handles unlimited entities with custom consolidation workflows. The variance attribution runs at both the entity level and the consolidated level.