Workbook Connect for finance teams
Budgets, actuals, accruals, and the cost-center data behind every report. Your team maintains all of it in Excel, validates it against your own accounts, and commits it straight to the database, every period.
Your numbers land in the warehouse, not in an inbox
Post an accrual or a reclass in Excel and commit. The figure is written live to the same table your reports read, with nothing to email and nothing to re-import.
The whole month lives in spreadsheets, not just budget season
The tables your team touches every period
Most finance work is a fact table keyed to your cost-center and account dimensions. Workbook Connect edits exactly these tables, and the foreign keys are what keep a posting from referencing a center or account that does not exist.
An illustrative data model, not your exact schema.
Work the period in Excel, against the live tables
A period close as you post it
Add accruals and reversals as new rows, edit a reclass in place, and let validation flag anything that does not belong. If any row fails, the commit is blocked and nothing is written until every line passes.
| Status | Cost center | Account | Period | Type | Amount |
|---|---|---|---|---|---|
| New | CC-410 Logistics | 6300 Freight | 2026-05 | Accrual | € 18,400 |
| New | CC-410 Logistics | 6300 Freight | 2026-04 | Reversal | -€ 17,900 |
| Changed | CC-220 Marketing | 6100 Agency fees | 2026-05 | Reclass | € 9,250 |
| Needs fix | CC-105 Sales | 6000 Travel | 2026-05 | Adjustment | € 0 |
| Needs fix | CC-700 IT | 8000 Depreciation | 2026-03 | Adjustment | € 4,120 |
| CC-220 Marketing | 6100 Agency fees | 2026-05 | Actual | € 31,600 |
- Row 4: an Adjustment of € 0 has no effect. The non-zero-amount rule flags it, so the commit is blocked until this row is fixed. Nothing is written until every row passes, then they all commit together.
- Row 5: period 2026-03 is closed. The open-period rule flags it, so the commit is blocked until this row is fixed. Nothing is written until every row passes, then they all commit together.
An illustrative example of the editing workflow, not a product screenshot.
Validated first, then committed in one transaction
Finance teams, answered
Yes. Each analyst opens their own Excel workbook filtered to the cost centers they own, and roles scope who can change which lines. Workbook Connect uses optimistic concurrency, so if two people touched the same FactActuals row, the conflict is flagged on commit instead of one quietly overwriting the other.
A validation rule. You author a rule (for example, Period must be on or after the open month) in the Validation Designer, and it runs in the sheet before any commit for everyone on the connection. If a row is dated to a locked period, the commit is blocked and nothing is written, with the reason attached, so a stray edit never reopens a month you have already closed.
Straight into the table you point at, for example FactActuals, in your own Azure SQL Database, SQL Server, Fabric SQL Database, or Fabric Warehouse. Once every row passes validation, they are written together in one transaction on commit, live, with no CSV to hand to IT and no second copy to reconcile.
No SQL, and only the access you already grant. People sign in with your existing authentication (Entra ID with MFA, a service principal, Windows Integrated, and more), and every read and write honours the database permissions already on their account.
Yes. You can browse and edit any table you have rights to, so the budget, the prior-year actuals, and the current accruals can sit in the same workbook while you build the variance.
Completely. Workbook Connect makes no server-side schema changes. The database stays the single source of truth, IT keeps the tables and permissions, and the table configuration (lookups, filters, primary-key mapping, hidden columns) is shared to the team automatically on connect.
Give finance a faster, cleaner close
Download Workbook Connect free and connect it to your database. Post your next month-end accruals straight to FactActuals from Excel, with every reclass and correction validated in the sheet first and committed in one transaction to the same table reporting reads.