The new Actuals interface follows your close
The new Actuals interface follows the steps of your month-end close, shows first whether your reports can be trusted, and is faster on large volumes. What changed, and what it means for your team.

Day two of the close. You know the report you need exists, because someone showed it to you once. Finding it is another matter.
That was the honest problem with the old Actuals interface. Actuals started as a reconciliation tool. Over the years it grew into much more. Today it is a financial data foundation with financial-native reporting and AR and AP insights. It also gives subledger visibility and an audit trail per transaction. But much of that depth was hard to find. If customers cannot see what a platform does, it may as well not do it.
So we rebuilt the interface. Not to pile on new features, but to make what is already there easy to reach.
The menu is your month-end close
The sidebar now follows the rhythm of a month-end close: import, transformation, reconciliation, reporting and export. These are the steps we see our users take every month. The top-level menu is a short list, in the order you work through it.
We also renamed things where the old words did not fit.
- "Unmatched transactions" is now "Exceptions", the word anyone who has run a close already uses.
- "Ledgers" is now "General Ledger Accounts".
- The old overview page is now called "Reconciliation Overview".
The documentation of the web app lists the old and new names side by side.
The first screen shows what you can trust
When you open the app, you land on an overview. It shows which periods are open and which are closed. Monitoring events that used to sit in separate corners of the product are now in one view. From there, you click straight into the dashboards and reports you need.
The overview also tells you whether a report is usable at all. If something is wrong in the data, you see that first and fix it. You no longer build a report on incorrect or incomplete data without knowing.
Faster on large volumes
Some customers told us the old interface felt slow once their data volumes grew. That was fair. We improved how the frontend talks to the backend and added caching throughout. We also changed how data is requested where needed. In tests with large volumes, the transaction details page performs 40% better.
How we built it
We rebuilt the interface from the ground up on React Router Framework with TypeScript. Backend and frontend are now more closely coupled, which makes development and maintenance faster.
We used AI-assisted tooling, specifically Cursor, to generate new pages and iterate on them. We also used it to review, test and document the code. That is why a small team could rebuild the experience in about two to three months, on schedule. It felt like having many junior colleagues around. That left us free to focus on the decisions and checks with the most impact.
The tooling was used for development only, not for hosting. The platform still runs on our own infrastructure and governance, in line with our SOC 2 Type 2 certification. Speed was the goal. Compliance was never up for negotiation.
What this release is not
This is not a release packed with new features. It is a foundation. The design system, the faster build workflow and the new architecture make future development quicker. AI-driven capabilities are next on our roadmap, and this interface is what makes building them practical. In the coming months, expect updates on native reports and native exports, and on new reconciliation options.
What changes for you
- Your data stays exactly the same. Nothing in your underlying records changes.
- You open the new interface through a link in the current app, and you decide when to switch.
- An in-app tour shows where things live now.
Have you not switched yet? The link is in the app. Start on the overview page and check which of your periods are still open.
In practiceHow many days of your close go to explaining differences?


