How do I know if a VIN is under a recall or Field Service Action?

Run the VIN through the OEM's portal at write-up. Open campaigns show against the VIN with a program or campaign number and the authorised operation code. Don't rely on the customer's recall letter alone — letters lag the OEM's records and a vehicle can have an open campaign the owner was never notified about, especially used vehicles bought in by the dealership.

Do I need owner consent to perform a recall repair?

You complete the recall repair on every affected VIN that comes through the workshop, even if the customer only booked for an unrelated job — but you still need the customer's authority to work on the vehicle. Document that you advised the owner of the open campaign and obtained authority. Some OEMs require you to action the campaign whenever an affected VIN is in for any service.

Can I claim a Field Service Action the same way as standard warranty?

No. FSA and recall claims use the program-specific operation code and must carry the VIN-specific campaign authorisation reference from the OEM portal. Submitting an FSA repair under a standard warranty op code is one of the most common rejection causes for these claims — the portal can't match it to the open campaign.

What's the difference between a TSB and a Field Service Action?

A Technical Service Bulletin (TSB) is diagnostic guidance — it tells the technician how to diagnose or repair a known issue, but it doesn't authorise a free repair on every affected VIN. A Field Service Action is a funded program: the OEM pays the dealer to repair every VIN in the affected range. A TSB may support a standard warranty claim; an FSA is its own claim type with its own authorisation.

Recall & Field Service Action Claims: A Dealer’s Guide

Field Service Actions (FSAs) and safety recalls are manufacturer-initiated repair programs with their own claim rules, separate from standard warranty. You complete the repair on every affected VIN regardless of mileage or whether the owner asked for it, then submit through the OEM’s recall workflow using the VIN-specific authorisation reference and the program-specific operation code — not a standard warranty op code.

By the Easy Claimz Warranty Team · 14 June 2026 · 10 min read

Recall vs Field Service Action vs Customer Satisfaction Program

These three terms get used interchangeably on the service drive, but they aren’t the same thing — and the OEM treats them differently at claim time. Getting the category right at write-up is the first step to getting paid.

A safety recall addresses a defect that affects safety or regulatory compliance. It’s usually reported to the regulator, and the OEM is obligated to repair every affected vehicle. The owner gets a formal notification letter. There’s no mileage limit and no warranty-expiry limit — a ten-year-old vehicle with an open safety recall still gets repaired free.

A Field Service Action (FSA) — some OEMs call it a service campaign or a service action — is a manufacturer-initiated program for a known defect that doesn’t meet the safety-recall threshold. The OEM funds the repair on every VIN in the affected range. Like a recall, it applies regardless of mileage or warranty status, but the regulatory reporting and owner-notification obligations are lighter.

A Customer Satisfaction Program (CSP) sits between FSA and goodwill. It’s an OEM-funded program for a quality issue the manufacturer wants to address proactively, often with a time or mileage cap. CSPs frequently require the customer to present with the concern rather than being actioned on every VIN that comes in.

Attribute	Safety recall	Field Service Action (FSA)	Customer Satisfaction Program (CSP)
Initiated by	OEM (often regulator-reported)	OEM	OEM
Trigger	Safety / compliance defect	Known defect, non-safety	Quality issue, proactive
Mileage / warranty limit	None	None	Often capped
Owner notified	Formal letter, mandated	Letter, lighter obligation	Sometimes
Action on every affected VIN	Yes, whenever in workshop	Yes, per OEM rules	Usually on presentation
Claim path	Recall workflow + campaign auth	FSA workflow + campaign auth	Program code, may need approval

The practical takeaway: recalls and FSAs are actioned on the VIN, not on the complaint. The CSP is closer to a standard warranty mindset — the customer usually has to raise the concern.

How dealers identify affected VINs

You cannot rely on the customer’s recall letter. Letters lag the OEM’s live records by weeks, and plenty of affected vehicles never reach their current owner — used cars bought in by the dealership, vehicles that changed hands privately, fleet vehicles with out-of-date address records. The owner in front of you may have no idea their VIN has an open campaign.

The only reliable source is the OEM portal, checked against the specific VIN at write-up. Every major OEM operating in Australia exposes open campaigns against the VIN: the campaign or program number, a short description, and the authorised operation code for the repair.

Build the VIN campaign check into your write-up routine the same way you check warranty eligibility:

Run the VIN at booking or write-up, before the vehicle goes into the bay.
Record the campaign number against the repair order — you’ll need it on the claim.
Advise the owner of any open campaign and get authority to action it, even if they booked for something unrelated.
Check again at delivery if the vehicle has been in for several days — campaigns can open mid-stay.

The recall / FSA claim workflow vs standard warranty

A standard warranty claim starts with a customer complaint, runs through diagnosis, and the dealer justifies that the fault was a warrantable defect. The 3Cs (Concern, Cause, Correction) carry that justification, and the operation code is chosen to match the diagnosed repair.

A recall or FSA claim is different because the OEM has already decided the repair is warranted. What the portal needs instead is proof you repaired the right VIN, under the right campaign, with the authorised code.

Step	Standard warranty	Recall / FSA
Trigger	Customer complaint	Open campaign on the VIN
Diagnosis	Technician diagnoses fault	Pre-defined by the campaign
3Cs	Full Concern / Cause / Correction	Often a fixed remedy description
Operation code	Chosen to match repair	Program-specific code, fixed by OEM
Authorisation	Warranty eligibility check	VIN-specific campaign reference
Labour hours	Dealer Standard Hours allowance	Campaign-set time, usually fixed
Eligibility limits	In-service date, mileage, warranty term	None — applies to every affected VIN

The two things that catch dealers out: the operation code is fixed by the campaign, not chosen by the clerk, and the claim must carry the VIN-specific campaign authorisation reference. Use a standard warranty op code for a recall repair and the portal can’t match it to the open campaign — the claim bounces. Forget the campaign reference and the OEM has no record that links your repair to the funded program.

Documentation differences

The evidence for a recall or FSA claim is leaner than a standard warranty claim in some respects and stricter in others. You’re not justifying that a defect existed — the OEM already accepts that. You are proving you did the authorised work on the authorised VIN.

What stays the same:

VIN plate photo — proof you worked on the claimed vehicle. Still mandatory, still needs to be fully legible.
Odometer photo — required by most programs even though mileage doesn’t affect eligibility.
Customer authority — you still need documented authority to work on the vehicle.

What changes:

3Cs are often a fixed remedy description. Many campaigns supply the wording. You’re confirming the prescribed remedy was performed, not diagnosing a unique fault. Don’t pad it with invented diagnosis — follow the campaign’s remedy text.
Campaign / program number is mandatory on the claim. This is the field that ties your claim to the open campaign in the OEM’s records.
Authorised operation code only. The campaign defines it. Don’t substitute.
Before/after or completion photos where the campaign specifies them — some software or recall actions require a screenshot of the completed procedure (for example, a module reflash confirmation) rather than a failed-part photo.

A recall to reflash a control module won’t have a failed part to photograph at all — the proof is the campaign reference plus the software-completion evidence the program asks for. Read the campaign instructions: the evidence list is program-specific and differs from your standard six-photo warranty habit.

Owner-notification requirements and dealer obligations

Recalls carry obligations that ordinary warranty work doesn’t, and they sit partly outside the claim itself.

For safety recalls, the OEM is generally required to notify owners and report progress to the regulator. As the dealer, your obligations typically include:

Action the open recall whenever an affected VIN is in the workshop, within the OEM’s stated rules — even if the customer booked for something else.
Advise the owner of the open campaign and document that you did so.
Not return a vehicle with a known open safety recall unactioned without recording the customer’s informed decision, where the OEM requires it.
Report completion promptly so the OEM’s records — and the regulator’s — reflect the repair.

For FSAs and CSPs, the obligations are lighter but the principle holds: if the VIN has an open program and the vehicle is in front of you, action it. An unactioned campaign on a vehicle you serviced is a missed funded repair and a possible comeback.

Document the notification step. “Advised owner of open campaign [number], authority obtained, [date]” on the repair order is the kind of note that protects the dealership if the repair is ever questioned.

Common rejection reasons specific to recall / FSA claims

Standard warranty rejection patterns — weak 3Cs, photo gaps, op code errors — still apply. But recall and FSA claims add their own failure modes that won’t show up on a normal warranty claim.

Standard warranty op code used instead of the campaign code. The most common one. The portal can’t match the repair to the open campaign.
Missing or wrong campaign authorisation reference. No link between your claim and the funded program.
Claiming a campaign that’s already closed against the VIN. Another dealer actioned it, or it was closed in error. Always confirm the campaign is open at write-up.
Labour hours that don’t match the campaign allowance. Recall and FSA times are usually fixed by the program — booking actual time over the set allowance gets the excess stripped.
VIN outside the affected range. A similar model or adjacent VIN that isn’t actually on the campaign list. The portal check prevents this.
Required completion evidence missing. Software-reflash confirmation or a campaign-specific photo the program asked for and didn’t get.
Stacking a recall and a related warranty repair on one line. When the same visit includes both campaign work and a separate warrantable fault, they’re separate claims with separate codes — don’t merge them.

The fix for nearly all of these is the same as the standard-warranty fix: a structured check before submission. Confirm the campaign is open, copy the authorisation reference, use the campaign’s operation code and allowance, and attach the evidence the program specifies.

Key takeaways

Recalls and FSAs are OEM-initiated repair programs, separate from standard warranty, actioned on the VIN regardless of mileage or warranty status.
A safety recall is mandated and regulator-reported; an FSA is a funded non-safety program; a CSP is proactive and often capped and presentation-based.
Identify affected VINs from the OEM portal at write-up — never rely on the customer’s recall letter alone.
Recall and FSA claims use the program-specific operation code and must carry the VIN-specific campaign authorisation reference — standard warranty op codes get rejected.
Documentation shifts from justifying a defect to proving the authorised work on the authorised VIN; some campaigns need software-completion evidence, not a failed-part photo.
Action open campaigns whenever an affected VIN is in the workshop, advise the owner, and document the notification step.

Handle recall and FSA claims alongside standard warranty

Easy Claimz prepares recall and Field Service Action claims with the program-specific operation codes and VIN-level campaign authorisation built in — so the right code and reference are on every claim, alongside your standard warranty work, without the clerk hunting through portals.

Request access

Easy Claimz is independent and not affiliated with Hyundai Motor Company, Ford Motor Company, or Toyota Motor Corporation. OEM warranty policies are subject to change — consult your OEM dealer support materials for current requirements.

Recall & Field Service Action Claims: A Dealer's Guide