Ask an OEM's channel finance team what "claims" means and you get a list, not a word: scheme claims, quarterly rebate claims, damage-in-transit claims, freight reimbursements, price-difference claims, return credits — each with its own spreadsheet, its own inbox, and its own backlog the dealers keep score of. Warranty gets a system; everything else gets email, and the email queue is where dealer trust goes to age. Dealer claim management software exists to give the everything-else a system too, and xMatix does it with one structural idea: a claim is not a form a dealer fills — it is a computation over transactions that already happened, with the evidence attached and the settlement posting to the same ledger the dealer account lives on.
One claims machinery, every claim type
Under xMatix, the commercial claim types run on shared machinery rather than parallel projects: trade-scheme settlements, quantity-purchase and slab rebates, cashback, contract price differences and sale-return credits are each generated by the claims engine on its own schedule, sweeping the source records that earned them — order lines, returns, despatches, scheme accruals. Every type inherits the same batching, the same approval framework, the same notifications and the same settlement path into the ledger, so the finance team learns one claims process and the run history of every type lands on one jobs screen with its errors inspectable.
Generated from transactions, not typed from memory
The reason claim season is fight season is that most claims are reconstructions — a dealer's spreadsheet of what they believe they earned, meeting the OEM's spreadsheet of what it believes it owes. Here the claim is generated from the records that earned it: the scheme claim from the consumption ledger's accruals against qualifying order lines, the rebate from the quarter's actual despatches, the return credit from the return document itself. The engine sweeps on schedule — nightly, monthly, quarter-end — and produces claims whose arithmetic is inspectable line by line. There is nothing to reconstruct, because nothing was ever off the record.
Concretely: a quarter-end trade scheme closes on the 30th. That night the claims run picks up the scheme's accruals — every qualifying order line, already priced by the same engine that promised the dealer the benefit — groups them by dealer, and writes one claim per dealer with the lines attached. Each claim carries a generation key, so if the run is repeated nothing duplicates; each line carries its source, so any number on the claim can be walked back to the order that produced it. By morning the claims sit in the approval queue with the scheme's budget consumption alongside — and the regional manager approving them is reading computed arithmetic, not adjudicating between two spreadsheets. The dealer sees the claim appear on their portal the same day, before they thought to ask.
Damage and freight: the claims that need eyes
Not every claim is arithmetic. A damage claim starts at the dealer's goods receipt — shortage and damage captured on the receipt itself, with photos, while the truck is still in the yard — and a freight claim starts from the despatch it reimburses. These route as evidence-first claims, built from the receiving and despatch documents the operation already wrote rather than from a phone camera and a rep's number. The approver sees the receipt and the photos on one screen; the dealer watches the status move on the dealer portal. The same posture warranty claims take — evidence attached, assembled from the operational record — applied to the commercial lanes by one configurable claims engine.
Decided line by line, settled into the books
Claims batch for review the way your finance team works — by type, region, period — and decisions apply per line: approved quantities, rejected quantities with reasons, lines held for more evidence. Approval triggers settlement automatically: the credit note posts against the dealer's account in the same ledger their invoices and outstanding live in, so a settled claim immediately changes the number the credit gate reads. Rejections stay visible as reclaimable work with the reason attached — not as a line the dealer discovers missing three statements later. Idempotent generation means a re-run cannot double-pay a claim; an audit trail means every decision has a name on it.
The dealer watches it settle
Half the cost of a manual claims process is the status conversation. On the portal each dealer sees their own claims — submitted, in approval, approved, settled, rejected-with-reason — scoped by row-level security to exactly their records, alongside the credit notes that settlement produced. The area manager stops being a claims call centre, and the monthly dealer meeting starts from a shared statement instead of two grievance lists — which changes the meeting's subject from history to business. Dealers who transact on the same platform get the full loop: the order that earned the scheme, the accrual it produced and the claim that settled it, one thread.
What the OEM sees
Turn the same records around: claim spend by type, region and dealer against scheme budgets; cycle time from generation to settlement; rejection rates and their reasons (the evidence problem you can fix beats the one you re-argue quarterly); damage claims by route and transporter, which is a logistics finding wearing a finance costume. Because settlements post to real books, channel-program cost is a ledger fact — auditable at year-end without a war room.
Common questions
What claim types does dealer claim management software need to cover?
The commercial set, not just warranty: trade-scheme settlements, quantity and slab rebates, cashback, contract price differences, sale-return credits, damage and shortage claims, freight reimbursements. On xMatix these run on shared claims machinery — one batching, approval and settlement path for every type, instead of a spreadsheet per type.
How are scheme and rebate claims generated?
From the transactions that earned them: the scheme's consumption ledger accrues against qualifying order lines as orders post, and the claim engine sweeps those accruals on schedule into claims whose computation is inspectable line by line. Generation is idempotent, so re-runs cannot create duplicate claims.
Can dealers track their claims themselves?
Yes — on the portal each dealer sees their own claims and where each one stands, from generation through approval to settlement, scoped by record security to exactly their records. Damage and shortage claims are built from the goods-receipt and return documents that captured the evidence, so a dealer is tracking computed claims, not chasing a submitted form. Approved claims post as credit notes against the dealer's account; rejections carry reasons.
How does claim settlement reach the dealer's account?
Approval triggers settlement automatically: the credit note posts into the same ledger that holds the dealer's invoices and outstanding, so their credit position updates the moment the claim settles — and the claim, the credit note and the ageing report can never disagree.