Every claim, from the service bay to the final decision.
VMS runs warranty the way you already do: your claim types, your own fields and lifecycle, connected to the ERP you already run.
Your claim types are configuration, not code.
A standard warranty claim, a recall claim and a goodwill claim can behave completely differently, with no custom development. Each claim type decides how its claims are created, what can change on them and what they must carry.
Created the right way
Allow manual claims, claims from a template or claims from a recall campaign, per claim type. Any other route is refused.
Locked where it matters
Lock the header or the claim lines once a claim exists, choose which kinds of line can be added, and whether quantities and values can change.
Templates narrow, never widen
A reusable repair brings standard codes, lines and prices. It can tighten a claim type's rules, never open up what the type has locked.
Add your own data and your own process.
Every warranty operation records things a standard model does not, and each one decides claims its own way. In VMS both are settings and published policies, not a software release.
Your own fields
Add claim and vehicle fields (text, numbers, yes/no, dates) and maintain the defect codes, cause codes and statuses behind every dropdown.
Rules by role, status and type
Make any field editable, required, locked or hidden by role and status, and narrow it further per claim type. Every rule is enforced on the server.
A lifecycle you define
The lifecycle engine runs a versioned policy for every claim: your rule checks, your calculations and calls to your systems, with the result deciding the next status. Every step is recorded.
Connected to the systems you already run.
Parts and prices already live in your ERP, and your finance system already pays claims. VMS works with them, so nobody keys data in twice.
Parts and prices from your catalogue
Users search your ERP's catalogue while adding a claim line. A claim keeps the price it was raised with, even if the catalogue changes later.
Your systems inside the lifecycle
Lifecycle steps call your systems over HTTP or OData, read the answer back and move the claim on, with no copying between screens.
Events as things change
Claim and vehicle changes are sent to your systems as events, with a delivery log. A traffic view shows exactly what was sent and what came back.
Your data stays yours, including the way out.
Each customer has its own database, not rows in a shared table. Nothing about VMS makes leaving hard.
Kept per customer
Your own database with its own database role, and your files stored under your own customer identifier, all hosted in the Sydney region.
Backed up continuously
Daily full backups and a change log shipped every 60 seconds make it possible to restore any minute of the last 10 days, into a separate copy.
A clean exit
On request you get your database as a standard PostgreSQL backup and a complete dump of your files, or both destroyed. Reading them needs nothing from VMS.
See VMS on your own claim types.
Tell us how warranty runs in your organisation today. We will walk through it in VMS: your claim types, your fields and your lifecycle.