Finance module
ASSETS / MODULEAssets
Acquisition through capitalization, custodian assignment, maintenance with real labor/parts/external cost capture, and disposal with computed gain or loss — with self-approval blocked at every governed step.
Acquisition to Maintenance and Disposal
- 01
Capitalize
The asset moves from draft to available — the creator cannot capitalize their own asset.
- 02
Assign custody
A named custodian is assigned, with only one active assignment enforced at a time.
- 03
Maintain
Planned, preventive, or priority maintenance orders capture downtime and real labor/parts/external cost; parts consumption posts a real Stock movement.
- 04
Dispose
Disposal computes gain or loss and is self-approval-blocked, just like capitalization.
What it is
The Vercentlabs Assets module tracks and governs the full lifecycle of physical and equipment assets — acquisition, capitalization, assignment, maintenance, and disposal — with an audit trail on every state change and self-approval blocked at every governed step.
Module atlas / operating conditions
Why Assets becomes difficult in fragments
Unclear custody of equipment
Nobody can say with confidence who currently has a given piece of equipment, or when it changed hands.
Unproven preventive maintenance
Maintenance happens, or doesn't, with no structured record of labor, parts, or cost — so you can't prove a warranty claim or plan a replacement.
Unauditable capitalization and disposal
An asset gets capitalized or disposed of by whoever handled the transaction, with no separation between the person acting and the person approving.
Unmonitored warranty and maintenance windows
Warranty expirations and maintenance-due dates aren't tracked centrally, so windows close unnoticed.
Operating outcomes
What changes when Assets shares one system of record
A defensible chain of custody
Assignment enforces one unique active assignment at a time, so custody is always a clear, current fact.
Maintenance you can actually prove
Planned, preventive, and priority maintenance orders capture downtime hours and real labor, parts, and external cost.
Capitalization and disposal that can't self-approve
The creator of an asset cannot capitalize it themselves, and disposal (with computed gain or loss) is also self-approval-blocked.
A due-window view before it's missed
The dashboard surfaces warranties expiring and maintenance coming due, ahead of time.
Capability architecture
The module, decomposed by operating capability.
6 capability groups organised by the way the product works, not as a flat marketing feature wall.
Asset register & categorization
The core record of what you own and how it's classified.
- 01Structured asset register
- 02Category-based classification
Capitalization
Moving an asset from draft to available, with a governance guard.
- 01Draft-to-available lifecycle
- 02Self-approval blocked — the creator cannot capitalize their own asset
Assignment & custody
Who currently has the asset, enforced as a single source of truth.
- 01Enforced-unique active assignment
Maintenance
Planned and reactive maintenance with real cost capture.
- 01Planned, preventive, and priority maintenance orders
- 02Downtime-hour and labor/parts/external cost capture
- 03Parts consumption posts as a real Stock movement
Disposal
Retiring an asset with a computed, auditable financial outcome.
- 01Computed gain or loss on disposal
- 02Self-approval blocked, same as capitalization
Inspections & transfers
The data model exists; today these are read-only views, not a create workflow — an honest, current limitation.
- 01Inspection and transfer records (read-only today)
Primary operating sequence
A transaction-level view of how work progresses through Assets.
See it work
Acquisition to Maintenance and Disposal
The ordered process a real Assets workflow follows inside Vercentlabs.
Trigger
An asset is acquired, referencing its purchase order and receipt from Procurement.
- Capitalize
The asset moves from draft to available — the creator cannot capitalize their own asset.
- Assign custody
A named custodian is assigned, with only one active assignment enforced at a time.
- Maintain
Planned, preventive, or priority maintenance orders capture downtime and real labor/parts/external cost; parts consumption posts a real Stock movement.
- Dispose
Disposal computes gain or loss and is self-approval-blocked, just like capitalization.
Approvals
- 01Capitalization and disposal both block self-approval by the same person who initiated the action.
Automated actions
- 01Due-window logic for warranties and maintenance
- 02Status-transition guards
Connected modules in this workflow
Outcome
A complete, audit-ready asset history from acquisition through disposal, with every governed step blocked from self-approval.
Operational proof
Assets, documented as an operating system.
Capability architecture
6 groups
Grouped by how the module is actually structured.
Primary operating sequence
Acquisition to Maintenance and Disposal
Rendered above as an ordered process rather than a feature collage.
Connected system
4 modules
Adjacent modules are linked through the operating model on this page.
Business outcome
A defensible chain of custody
Assignment enforces one unique active assignment at a time, so custody is always a clear, current fact.
Ready to see Assets running on your own data?
Book a DemoSystem map
Assets does not operate alone.
The handoffs below are part of the operating model, not decorative cross-sells.
Assets link to their originating purchase order, receipt, and vendor bill — a confirmed, wired connection.
Maintenance parts consumption posts as a real stock movement — a confirmed, wired connection.
Support tickets carry a related-asset reference, so a service issue can be traced to the specific equipment.
Identity fields align with the Accounting fixed-asset subledger but are not FK-joined — see the Accounting module page's Honest Limitations note before assuming a unified depreciation pipeline.
Output register
What Assets tells operators and managers
Total assets, assigned count, in-maintenance count, warranties expiring, net book value, maintenance due
Audience / Facilities/IT managers, finance/asset controllers
Rule register
What the module can run on its own
The dashboard surfaces warranties expiring and maintenance coming due before the window closes.
An asset can't skip lifecycle states out of order.
Enforced structurally on both capitalization and disposal.
Control register
How Assets stays governed
Module-specific controls shown separately from the platform-wide security architecture.
Every lifecycle action — capitalize, assign, maintain, dispose — is independently permissioned.
Every state change is logged and cannot be altered after the fact.
Data access is enforced at the database row level.
What to plan before going live.
- 01
Asset categories and depreciation-relevant classification are set up before migrating the existing register.
- 02
Existing custody assignments are migrated as a starting point, not re-established from scratch.
- 03
Maintenance schedules (preventive intervals) are configured per asset category.
- 04
Assets has no mobile presence today — plan for desktop/browser access, including for maintenance technicians.
Buyer questions
Questions teams ask about Assets
Can the same person who buys an asset also capitalize it?
No — capitalization blocks self-approval, so the creator of the asset record cannot be the one who moves it to available/capitalized status.
Are asset inspections and transfers fully automated today?
The data model exists for both, but no create-function has been found — they're read-only today, not a live create-workflow. This is an honest current limitation, not a planned feature described as shipped.
Is the Assets module connected to Accounting's fixed-asset depreciation?
Identity fields align but the two are not foreign-key joined — they're independent data models. Don't assume a single unified capitalization-to-depreciation pipeline.