How ServiceTiket LeaseOps Works
Follow one asset from operating-model discovery and procurement through receipt, finance review, placement, verification, payments and end-term action.
Define the operating model
Map the organisation, roles, controls, master data and system boundaries before configuring the workflow.
Organisation and roles
- Entities, divisions, regions, branches and locations
- Finance, procurement, operations, audit and partner responsibilities
- Role-based access and approval authority
Master records
- Asset classes, models and identification rules
- Lessors, vendors, customers, outlets and locations
- Agreement, document and status requirements
Capability boundary
- Confirm what is standard, configured or integration-dependent
- Document custom and unavailable requirements
- Agree finance, tax, legal and accounting responsibilities
Approve and acquire
Carry an approved business requirement into lessor, vendor, order, invoice and delivery records.
Requirement and approval
- Asset, quantity, specification, business purpose and destination
- Budget and approval checks according to the configured process
- Time-stamped decisions and supporting evidence
Commercial records
- Lessor, vendor, PO, invoice and agreed rental terms
- Payment frequency, dates, deposits, options and supporting documents
- Customer-specific fields reviewed during implementation
Receive and register
Connect commercial records to what was physically delivered and accepted.
Delivery evidence
- GRN or receipt reference, delivery date and destination
- Quantity, serial numbers, condition, photos and acceptance
- Exceptions for shortages, damage or mismatched identity
Asset registration
- Asset or ERP number, model, acquisition type and lifecycle status
- Initial location, custodian and evidence
- Relationship to lease, lessor, invoice and schedule
Review finance inputs and records
Finance confirms policy decisions before configured schedules and reports become part of the controlled record.
Approved inputs
- Commencement, payment timing, discount rate and other policy inputs
- Source and approver retained for each controlled decision
- Ind AS 116 is the primary India context
Finance records
- Lease register, liability, ROU, payment and expense records
- Asset-level versions where required and configured
- Schedules compared with invoices and recorded payments
Place, move and verify
Keep the lease and asset record connected as equipment moves through distributed operations.
Placement and custody
- Customer, outlet, user, department or operational location
- Acceptance, agreement, custodian and current status
- Approved movement and receipt history
Field verification
- QR or barcode identification and expected asset population
- Location, condition, photos, checklist and signature where configured
- Exceptions assigned, reviewed and closed
Control changes and end term
Route each change through assessment, approval, execution and evidence.
In-life events
- Payment changes, modifications, exchanges and location movements
- Affected assets, dates, documents and approvals
- Previous and revised states retained for review
End-term actions
- Renew, return, recover, re-rent, purchase, buyout or retire
- Condition, location, commercial terms and accountable owner
- Completion evidence and final record status
Outputs and integration
- Dashboards, reports, exports and APIs according to agreed scope
- Interfaces and control totals validated during implementation
- Exceptions and reconciliation remain visible
Map One Real Asset Through the Workflow
Bring an anonymised schedule, asset register, GRN or audit record. We will shape the demonstration around the hand-offs your teams actually manage.
Request a Workflow Review