Every release to Biztimize — new features, improvements, fixes, and breaking changes — documented here, for everyone. No marketing gloss.
Further refinements to the Customer Payments page.
Layout, filtering and data-entry improvements on the Customer Payments page, following the ledger statement corrections in the same release train.
A review of the production environment tightened network access, retired components no longer in use, and trimmed the deployed footprint.
Analytics components that were no longer part of the product — and a scheduled refresh job that had never succeeded — have been removed, along with roughly 4 GB of unused machine-learning runtime. Faster deployments, less to go wrong, and nothing you use is affected.
Firewall rules were reconciled against the services actually listening, database access was restricted to the application tier, and repeated authentication failures are now blocked automatically.
A released bill of materials is changed by a change order with a date, an approval and an impact assessment — never by editing the structure underneath the orders already planned against it.
Once a BOM is released, production orders, purchase orders and budgets have been planned against it. Editing it in place changes what those documents were costed on, silently. A released structure is now changed only through an Engineering Change Order.
Before a change is released you can see what it touches: which orders are already open against the affected lines, and a decision recorded per order about what should happen to it.
The BOM endpoints previously required only a signed-in user, so any user of the tenant could create, edit or delete any BOM at any plant. They now require explicit BOM permissions, and two focused roles ship with the feature: BOM Engineer (authors and raises changes) and Engineering Change Approver (approves, releases and decides impact).
Administrators: review role assignments as part of this upgrade so the BOM screens stay available to the people who need them.
Document numbers are now yours to define — prefixes, sequences, resets and per-variant series — without a code change, and without disturbing any number already issued.
One document type can carry several series — by company, branch, or any variant you distinguish — so each stream of documents keeps its own running number.
A variant that could never fire is refused at configuration time rather than discovered later as a gap in the sequence.
Every document type — orders, invoices, receipts, notes, vouchers — can now be given its own numbering rule: prefix and suffix, sequence width, and how and when the counter resets.
Refinements to the Customer Payment screen for faster, clearer receipt entry.
Usability and presentation improvements across the Customer Payment screen so a receipt can be captured and checked against the customer’s open items in fewer steps.
Cheques dated for a future day are now held, tracked and presented as their own instrument instead of being treated as money already in the bank.
A post dated cheque is a promise for a future date, not a receipt today. Post Dated Cheque Management records the instrument when it is taken, holds it until its due date, and carries it through presentation, clearing, dishonour and return — with the accounting following the cheque rather than the calendar.
Product Specification rights can finally be granted to a role, and a reversed vendor payment stops standing in the payables sub-ledger as if it were still live.
The payables sub-ledger knew about cancelled payments but not about reversed ones, so both halves of a reversal landed as debits — the original kept its full debit and the reversal document posted a second one. The payable was relieved twice instead of netting to zero, and the Vendor Ledger screen disagreed with the General Ledger, which was never wrong.
A reversal now posts as a credit under its own transaction type, and the pair nets to nil.
The Product Specifications screen has always hidden its buttons behind permissions, but those permissions did not exist — so no role could hold them and the actions were drawn for tenant administrators only. A user holding the whole Materials Manager role saw the page read-only, with nothing on screen able to explain why.
The style intent workspace gained stronger validation and a clearer queue, so an intent that cannot be projected per size says so.
The BoM Beta style intent pane was reworked: intents are validated as they are built, the queue shows what is ready and what is blocked, and an intent that cannot be projected per size is reported with the reason instead of producing a plausible-looking wrong bill of materials.
Generation from a style intent was reworked so component and consumption derivation is consistent between the wizard and the generated bill of materials.
The HR performance and recruitment setup commands now resolve the named tenant to its own database.
The performance and recruitment setup and check commands did not resolve the tenant passed to them to that tenant’s database, so seeding could act against the wrong one. They now resolve it explicitly.
Candidate records can be created from a resume, and purchase requisitions are raised against a cost center instead of a department.
A purchase requisition is now raised against a cost center rather than a department, so the requirement carries the dimension the spend will actually be reported under. Existing requisitions keep their value under the new field.
Upload a resume — or a batch of them — and the details are extracted for review: name, contact, current employer and designation, notice period, skills and education. Correct anything that needs correcting, then create the candidate record in one step.
Extraction only. No score, no fit percentage, no ranking and no ordering of candidates is produced, and protected characteristics are never extracted — shortlisting stays a decision a person takes.
We run monthly release briefings for customers — what shipped, what changed, what's next. Bring your team.