Without this workflow
The problem
Extensions do not need hidden runtime access to mutate accounting state unpredictably.
Work faster every day
Guarded FDL extension packages
Add deterministic, permission-bounded product contributions without granting extensions accounting authority.
Customisation should be installable, reversible and inspectable rather than an unrestricted script inside the books.
Release-dependentUse the clean-room FDL package, manifest, inspection and guarded activation direction as it becomes certified.
With Fastbooks
The controlled result
The first certified direction is deliberately limited to deterministic read-only print contributions.
Demonstration sequence
Show the workflow from evidence to outcome.
A feature page should make the user action, product transformation, review decision and accounting consequence visible in order.
- 1Build a supported package
- 2Inspect manifest and permissions
- 3Activate it for one company
- 4Verify deterministic composition and rollback
End on the retained accounting or review outcome, not on a decorative success screen.
Evidence gate
What must be proven before broad advertising.
Implementation is not the same as commercial proof. These checks define what representative validation must support.
- Package integrity and inspection
- Company-scoped activation
- Deterministic read-only print composition
- Backup, restore, upgrade, failure isolation and rollback
Need help getting started?
Message us about installation, business setup, existing data or the first accounting task.
Get setup help on WhatsAppThe message opens directly in WhatsApp. No information is stored on this website.