Use case · Finance controller
The monthly close, without the fragile workbook
A controller’s know-how is often locked in workbooks only they understand. Livia turns the database part into an app, and leaves Excel what it does best.
Today
Each month: exports from the accounting system, payroll and the bank, reworked with formulas and fragile macros, consolidated, then turned into dashboards and reports for management.
The workbooks break when a column changes, one person understands them, and the same work is done again by hand every month.
With Livia
- The exports are imported into real tables, from CSV or Excel files, with their columns matched to fields before anything is written.
- The rework rules are written once, as a script, and run on each month’s data from a button.
- Reference data kept by hand, such as cost centres, allocation keys and budgets, becomes tables with entry screens and rights, instead of hidden tabs.
- Consistency checks run on a schedule and send the gaps by e-mail.
- Reports go to the management committee as PDF files, and Excel workbooks to the people who want to play with the numbers.
- A new rework is described in plain words: Livia writes the script, the controller tries it on last month’s data, then keeps it.
- The data stays on the controller’s computer, if they want.
They don’t leave Excel. They stop using it as their database.
When the budget comes round, the same approach opens to the managers.
The budget campaignDescribe your own to Livia
Download Livia Studio, and tell Livia what you track today in a workbook. The trial lasts 14 days and needs no card.
Download Livia Studio