What’s planned
Where Soldi stands today, what’s scheduled next, and what it isn’t going to do.
Where it stands
The ledger is done and its math is tested.
Entries are immutable, posting happens only on the server, and every report ties out. Current work is the everyday business workflow around the ledger, plus what a company with departments needs.
Planned work
What’s being built
Grouped by theme, in the order we plan to do them. There are no dates, and nothing on this page is a delivery commitment. The order can change if a customer gives us a good reason.
-
In progress
Roles that match an org chart
Soldi has four fixed roles. That works when everyone who touches the books is trusted with all of it, and not much beyond that. Today posting, voiding, reconciling and closing a period all fall under one permission, and an auditor expects four separate ones.
- Granular permissions, replacing the four fixed roles
- Approval steps and spending limits set as permissions
- Segregation of duties between who posts and who approves
- An audit trail that records before and after values along with the action
-
Next
Accounting dimensions
Every Soldi report today is company-wide, because a ledger entry records its account but not its department, class, location or project. Companies past about twenty people ask for this first. It’s scheduled early for a structural reason: entries are immutable, so adding the field once real data exists would mean rebuilding that data.
- Department, class, location and project on every ledger entry
- Segment reporting: profit and loss by department or region
- Budgets set and tracked per dimension
- Job and project costing built on the same field
-
Next
Starting from books you already have
A company that’s already in business can’t switch to Soldi unless it can bring its existing trial balance along. This work covers the first hour of using it.
- Opening balance import, so a company can start mid-year
- Invoice delivery, with a record of what was sent
- Year-end close and retained-earnings roll-forward
- Recurring invoices and journals on a shared schedule engine
-
Later
Scale and integration
The current row limits on registers and reports were sized for a first version, and they’re documented. The plan is to remove them before a large customer’s data shows up. Integration comes after that, since other systems need a way to read from and write to the books.
- Removing the row limits on registers and reports
- A public API, with rate limiting, and webhooks
- Multi-currency, and consolidation across subsidiaries
- Fixed assets and depreciation runs
- SSO, SCIM provisioning and MFA policy
Out of scope
Not on the roadmap
If you need one of these, Soldi isn’t the right product for you.
-
Payroll
Payroll is its own product, with different regulations in every country. Soldi books the journal entries a payroll system produces, but it doesn’t run payroll.
-
Inventory costing
That belongs with the lifecycle and manufacturing data in Ciclo.
-
A bookkeeping service
Soldi is software. It doesn’t come with an accountant, and it won’t file anything for you.
How this is maintained
Every item above is tracked in our own issue tracker, and this page is rewritten from it. Open bugs and security work are left off. Those stay in the tracker until they’re closed.
Want more detail on something here, or to know where it stands? Write to dmoore@
Next
Bring Soldi into your company
Ask about onboarding your organization, moving existing records over, or a demo.