The working surface
The invoice canvas keeps the full document connected to editing controls. Mobile views focus on the page, an adjustment or layout controls so the screen remains usable.
ISH COMMERCIAL OS / SYSTEM ARCHITECTURE
A business overview of the current system: where you work, how assistance reaches the right record, and how a reviewed invoice becomes a document.
Select a part of the diagram to read its role. This overview describes the application design; it is not an independent security certification or a guarantee of every production configuration.
The invoice canvas keeps the full document connected to editing controls. Mobile views focus on the page, an adjustment or layout controls so the screen remains usable.
The application checks the requested action and the current document. Price adjustments require the appropriate scope and reason. Version checks help prevent an old proposal from replacing newer work.
Customers, projects, quotations and invoices preserve the business context. An accepted quotation provides the starting point for a draft invoice.
Material specification, units, supplier, region and dates make pricing evidence useful. Invoice selling prices and future cost updates are separate decisions. Regional coverage and calibration remain part of the release validation work.
Lerato receives the active invoice context and can inspect the saved record. Proposed changes pass through application controls and a review step. Model output is not treated as an approved supplier quotation.
Review the actual PDF before issue. Document protection preserves issued content; a later cost-book update is not an instruction to rewrite an issued invoice.
LOOKING AHEAD
The retail rollout is being prepared around company onboarding, reusable training and clearly scoped support. Customer provisioning, operational validation and the final retail offer must be completed before general availability.
Share architecture feedback ↗