Who Needs to Be Involved in a Claims-System Implementation?

Claims-software implementations don't fail on technology — they fail on an unassigned decision. This article names the five roles that make the project work, and what each one actually decides, sized for an Indian SMB where three people usually wear the five hats.

The five: a commercial/sales owner for scheme rules, an accounts owner for credit notes and ledgers, a data owner for the DMS/ERP exports, one pilot distributor, and a decision-maker for disputed claims and the cutover call.

The five roles, and what each decides

1. Commercial / sales owner — the scheme authority. Owns what every scheme means: which slab applies at the boundary, whether the window is invoice-date or dispatch-date, what the circular intended when the wording is loose. During scheme mapping this person converts circulars and Excel formulas into agreement terms — and every ambiguity they resolve now is a distributor dispute that never happens later.

2. Accounts owner — credit notes and ledgers. Owns the settlement side: the commercial-versus-GST credit-note decision per claim type (the distinction is in financial vs tax credit notes), how settlements post to the ledger, and whether the platform's numbers reconcile with the books. This is the person the parallel run answers to.

3. Data owner — the export runner. Whoever already produces the sales register from Tally, Busy, Marg or the DMS. They know which report, which columns, which quirks (the September file with the changed column order). Their job: the platform gets the same data Excel got, on a schedule, with changes announced.

4. Pilot distributor — the outside tester. One cooperative distributor who submits real claims through the new flow during the pilot. They find what internal testing can't: the claim format that doesn't match how distributors actually keep records, the document requirement nobody can fulfil, the status label that reads as an insult. Choose one who is digitally comfortable and speaks up.

5. Decision-maker — the tie-breaker. Owns the calls software can't make: the disputed opening balance, the legacy claim with missing documents, the go/no-go at cutover. Usually the founder, CFO or commercial head. The role is small in hours and decisive in effect — implementations stall precisely where this hat is missing.

The RACI, sized for ₹100–500 crore

Decision / activity	Commercial	Accounts	Data	Pilot distributor	Decision-maker
Scheme terms mapped to agreements	R/A	C	—	—	I
Historical data extraction & loads	C	C	R/A	—	I
Opening balances & distributor sign-off	C	R	C	C	A
Claim format & document requirements	R	C	—	C	I
Credit-note basis per claim type	C	R/A	—	—	I
Weekly parallel-run comparison	C	R	C	—	I
Disputed claims & exceptions	C	C	—	C	R/A
Cutover / parallel-run exit	C	R	C	I	A

R = does the work · A = owns the outcome · C = consulted · I = informed. Three-people version: commercial head takes column one, the accountant takes two and shares three with whoever runs the ERP, and the founder takes the last column. That works — as long as the hats are named out loud, because the failure mode is never "too few people"; it's a decision that belonged to nobody.

What this team does NOT need

A steering committee, a project-management office, or a full-time project manager. At mid-market scale the coordination overhead of a heavy structure costs more than the project. A weekly 30-minute review — variance log, exceptions list, blockers — run by the accounts owner, is the entire governance the project needs. Save the ceremony; spend the attention on the parallel-run comparisons and the opening-balance sign-offs, which is where implementations are actually won.