What is planned
Where Soldi stands today, the work that is scheduled next, and the things it is deliberately not going to do.
Where it stands
The ledger is done and the arithmetic is tested: entries are immutable, posting is server-side only, and every report ties out.
What is being built now is the ordinary business workflow around that ledger, and the depth a company with departments needs.
Planned work
What is being built
Grouped by theme and ordered by intent. These are horizons, not dates — nothing on this page is a delivery commitment, and the order can change when a customer gives us a reason to change it.
-
In progress
Roles that match an org chart
Soldi ships with four fixed roles, which is enough for a company where everyone who touches the books is trusted with all of them. Beyond that it is too blunt: posting, voiding, reconciling and closing a period are one permission today, and an auditor expects them to be four.
- Granular permissions, replacing the four fixed roles
- Approval steps and spend limits expressed as permissions
- Segregation of duties between who posts and who approves
- An audit trail that records the before and after, not just the action
-
Next
Accounting dimensions
Every report Soldi produces today is company-wide, because a ledger entry knows its account but not its department, class, location or project. This is the first question an organisation past about twenty people asks, and it is being taken next rather than later for a structural reason: entries are immutable, so adding the field after real data exists means a rebuild rather than an update.
- 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 product that cannot accept an existing trial balance cannot be adopted by a company that already trades. This group is about the first hour of use rather than the hundredth.
- Opening balance import, so a real company can start mid-year
- Invoice delivery, with the record of what was actually sent
- Year-end close and retained-earnings roll-forward
- Recurring invoices and journals on a shared schedule engine
-
Later
Scale and integration
The current register and report ceilings were sized for a first version and are documented as such. Removing them is scheduled before a large customer’s data arrives rather than after. The integration surface follows, because a system of record that cannot be integrated with is not one.
- Removal of the register and reporting row ceilings
- 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
Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, Soldi is not the product for it.
-
Payroll
A different product with a different regulatory surface in every country. Soldi books the journal a payroll system produces; it does not run payroll.
-
Inventory costing
Belongs with lifecycle and manufacturing data, which lives in Ciclo.
-
A bookkeeping service
Soldi is software. It does not come with an accountant, and it does not file on your behalf.
How this is maintained
Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.
Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.
Next
Bring Soldi into your company
Ask about onboarding an organisation, migrating existing records, or a demonstration.