Will it hold up at our scale?
A fair question when up to hundreds of records pass through every day — invoices, orders, delivery notes, documents and postings. SBM wasn’t built for a brochure; it has been running continuously since 2017, grown inside companies that move exactly these volumes.
I’m interestedWhat has run through it since 2017.
No pilot install, no trial run: production systems carrying the daily business.
-
since 2017
In continuous operation
No restart, no migration in between. The same software, in daily use throughout, across version changes and changes in the law.
-
100+
Records per day
Invoices. Orders. Quotes. Delivery notes. Documents. Postings. Up to hundreds a day — not the ten documents of a side business, but daily volumes where lists, search and reporting have to prove themselves.
-
8 figures
Invoiced turnover
The invoice turnover processed through SBM over the years runs into a double-digit million figure — in companies with a high daily document load.
It isn’t only invoices.
Orders, quotes, delivery notes, documents and postings run in the same system. That is where it is decided whether software carries the daily workload — not at the invoice form.
-
Many records, one system
One customer, many documents, different ways to bill: individually, recurring or per project. Line items, costs and receipts stay with their record and still feed one shared report. Project-based billing and order management we build for you as a module.
-
Connecting your own app — built as part of the project
Upstream systems feed data in through an interface built for you. In practice this has carried the transfer of records from a mobile app for years — captured on site, processed in the system, findable at any time.
-
Records and handovers as documents
Captured records become verifiable documents: template, PDF, digital signature, log with checksum. Exactly the route used for handover and acceptance records.
-
Findable without stretching data protection
Everything stays on your own server in the EU country your business sits in. Access follows roles and permissions, and the universal search finds a record even when the keyword sits in a single line item.
When many people work at once.
The point where simple tools fall apart.
-
Invoice numbers are drawn on save
The number is created at the moment of saving, not when the form opens. Whoever saves first gets the next number — an open form blocks no number and tears no gap in the sequence.
-
Everyone sees what they are entitled to
Users, roles and permissions apply at area level. Plus two-factor login via emailed code, a login log and a dashboard of their own for every user.
-
Traceable who did what
System logs record what happened in the system. For documents and signatures there is a separate log with timestamp and checksum.
-
Safety limits instead of a stalled server
Large lists run against configurable ceilings rather than bringing the server to its knees. Need more? Raise the value in the settings.
One invoice, two languages.
For everyone working across borders — who still needs bookkeeping their accountant can read.
The service description appears in your customer’s language, and underneath it the same line in the language of your bookkeeping. The customer understands what they are paying for; your accountant understands what to post. Both on the same document, without a second invoice and without paper shuffling. Don’t need it? Hide the second line and stay in one language.
- Customer language on top, accounting language below
- Or the local language only
- Applies to invoices and delivery notes
- Translate right in the editor (uses an online translation service when you click)
Does that sound like your scale?
Tell us roughly how many documents you handle and where it currently hurts. We’ll give you an honest read on whether SBM fits.
I’m interested