Finance
Landing first- A ledger, invoicing, and the period close a controller can actually trust
- A jurisdiction-aware tax engine that plugs into the tax service you already use
- Multi-currency for operations that transact across borders
Administrative Systems Paid add-ons · Mostly on the 2027 roadmap
The back office, as an add-on.
DLBD Technologies is building the back-office systems a regulated operation needs — finance, procurement, sales, HR, reporting — as paid add-ons to the operational products, not as standalone applications. Each one plugs the back office into what the floor and the lab already do. Mostly on the 2027 roadmap.
Why add-ons, not standalone
The point is the connection to the batch, not another disconnected ledger.
A finance system that does not know which lot the invoice covers is what you already have. A sales module that cannot fire the batch to make what it just sold is another spreadsheet by another name. These are add-ons because their whole value is that the batch record, the released lot, and the accounting entry are one story — not three copies. If you do not run a DLBD operational product, you have no use for the back-office add-ons; if you do, they turn on beside what you already run.
What is coming
The add-ons, grouped by function.
Each add-on extends the operational products you already run and inherits the same signing controls, audit trail, and roles. Posting the month carries the same weight as releasing a batch.
Receivables, payables, cash, assets
Next- A real customer ledger behind lab invoicing, with credit control and collections
- Vendor bills matched against what your warehouse actually received
- Bank reconciliation and payment runs without the spreadsheet handoff
- A fixed-asset register that stops living in a separate file
Procurement
Later in 2027- Requisitions with budget checks, quote comparisons, and contracts
- The full path from asking for something to paying the invoice for it
Sales
Later in 2027- Quotes, price lists, sales orders, back-orders, rebates
- The order-to-production trigger: a sales order either draws from released stock or fires the batch to make it — no phone call between sales and the floor
- One commercial customer, shared by the lab, by sales, and by finance
CRM connection
Later in 2027- A first-class connection to the CRM you already use — closed-won deals land as draft sales orders
- A built-in pipeline is deferred; we would rather integrate cleanly than reinvent the CRM
People and projects
Later in 2027- Employees, time, leave, and performance, with a clean handoff to your payroll provider
- A lightweight project spine for method development, stability studies, and any services arm
Planning and reporting
Later in 2027- A short-horizon plan that nets demand against what is on the shelf and what is on order
- Consolidated reporting that spans the whole operation without a one-off SQL job every time
One platform
The books, the batch record, and the released lot are one story.
Every back-office system uses the same sign-in, audit trail, signing controls, and approvals that the floor and the lab already do. Posting a period carries the same weight as releasing a batch. There is one system of record for the whole operation.
On the roadmap, not in the demo.
The back-office add-ons are being built in phases through 2027 and require at least one DLBD operational product. If your evaluation depends on one, tell us which — we can share when it lands and what it will look like.