Contracts, claims and the money, in one system
Every module reads and writes the same records. The dealer, the adjuster and finance always see the same claim, and every dollar it moves is on the ledger.
Issued from a plan, corrected with a reason
Every contract goes through one creation path. It is numbered in your sequence, carries the plan’s coverage, and posts its fund split to the ledger the moment it is issued.
- The customer and vehicle captured in the same pass; a VIN already on file is reused, never duplicated
- Correct, terminate or void, each with a typed reason
- A correction records what the field said before
- A wrong premium is reversed on the ledger and re-posted, so the book lands where it should
Claims with jobs, statuses that mean something
A claim breaks into jobs, and each job into parts, labor, fees and adjustments. Eighteen statuses are defined as data, each with a label written for the dealer, so the person who submitted the claim can read where it stands.
- Coverage checked against the contract’s covered parts; a part paid for life is not paid twice
- Required documents set by amount and category, shown before submission and enforced
- Documents stored privately, checksummed on upload, served by short-lived links
- The claim’s full timeline, with every decision on it
Decisions within limits
Adjusters approve or deny each line with a reason and document every adjustment. Each person’s money authority is configuration, and a claim above it routes to underwriting instead of bouncing between inboxes.
- A claim authorization number issued on authorization
- Routine claims can authorize automatically, never past a hold
- Two adjusters editing one claim are stopped, not silently overwritten
- Authorizations post to the ledger as commitments
Payments that post, a book that reads
A payment is recorded against the claim it settles and posts to the ledger, so a commitment nets to zero as it is paid. The book is aggregated from those entries rather than rebuilt from claims: premium written, claims authorized, claims paid and what is still owed.
- Payments recorded per claim and per payee
- Outstanding commitments visible at any time
- Every figure traceable to the entries behind it
A TPA that runs itself
Create a workspace, invite your team and add your dealers without filing a ticket. Decide which dealer may sell which plan, and author the plans, prices and fund splits they sell.
- Roles and permissions your admins can see and change
- Every permission change written to an audit trail
- A change to a fund split never restates a contract already sold
- Document rules versioned, with every earlier version kept
- A setup checklist that walks a new workspace to its first contract
- New dealers start as not producing, until you open them
What is being built next
Listed so nobody mistakes it for something that ships today.
Repair-order intake
In developmentContracts created from dealer management system feeds and an API, through the same creation path. The pipeline is built; connecting it is next.
Document extraction
In developmentA claim pre-filled from the repair invoice, suggested by AI and confirmed by a person.
Remittance
In developmentDealers settling contract sales, expected against received, line by line.
Reconciliation
In developmentThe ledger matched against insurer statements, with mismatches surfaced instead of allowed.
Portfolio analytics
In developmentLoss ratios and drilldowns per dealer, vehicle segment and product.
More product families
In developmentService contracts, GAP, maintenance and appearance protection. The core is product-generic; lifetime repair is the first product configured on it.
See it on a book like yours
Thirty minutes with the people who build Traxle: a contract issued, a claim authorized, and the ledger behind both.