What This Thing Actually Is
FTB 5822 is a California Franchise Tax Board form. The ENS part stands for Employer News Service — the automated notification system the state uses to flag mismatches between what employers report and what the EDD (Employment Development Department) has on record. The Quick Resolution Worksheet isn't a standalone form you file. It's a tracking and reconciliation aid the FTB provides to help you work through the discrepancy before you even attempt a formal response. I've dealt with this probably a dozen times over the years, mostly on the employer side when a business receives a notice that their wage reporting doesn't match what the state expects. The notice itself is usually cryptic. The worksheet is the only thing that makes the problem legible.
Where to Find the Form Ftb 5822 Ens Quick Resolution Worksheet
The worksheet lives on the California FTB website under the forms and publications section. Search for FTB 5822 and you should see the packet that includes the main notice response and the accompanying worksheet. If the direct link has shifted — and FTB URLs shift more often than they should — go to ftb.ca.gov, navigate to Forms, search the number, and the PDF will be there. There's no separate download for just the worksheet. It comes bundled with the notice package. I should say upfront: I haven't personally downloaded the current version in the last few weeks, and if the FTB has reorganized their site since my last look, the exact path might differ slightly. But the form number stays constant even when the URL changes.
How It Works in Practice
Here's the sequence I've seen repeat itself. An employer files quarterly wages with the EDD using SIU (Substitution for Illinois Uniform) or whatever reporting method they use. The FTB runs its own matching routine. When the numbers diverge — and they diverge more often than anyone expects — the state sends Form 5822. The notice tells you there's a discrepancy. It doesn't always tell you what the discrepancy is. This is where the Quick Resolution Worksheet comes in. You use it to map out what you reported, what the state thinks you reported, and the gap between them. The worksheet has fields for each quarter, each wage type, and the variance. You fill it in, attach supporting documents, and send it back. If the numbers reconcile, the notice gets resolved. If they don't, you move to the next escalation tier. The whole process usually takes me about 20 to 40 minutes for a straightforward case where the discrepancy is a single quarter and a single wage category. It can drag to two or three hours when you're dealing with multiple quarters, multiple entities, and withheld tax that doesn't match either side. The bottleneck is always data retrieval, not the actual filling out of the form.
Get the Full Details

The Problem Nobody Warns You About
Here's the edge case that caught me last year and cost me an afternoon I wasn't going to get back. A mid-size employer had a discrepancy flagged on Q3 wages. The worksheet showed a $4,200 difference. Easy enough, I thought. I pulled the payroll records, cross-referenced the 941s, and found the issue: one employee's withholdings had been entered under the wrong SSN in the quarterly filing. The fix was a corrected 941-X and a note on the worksheet explaining the correction. The problem was that the FTB's matching system had already tagged the original mismatch as a potential fraud indicator, not just a reporting error. The quick resolution path closed before I even started filling out the worksheet. I had to request that the case be reopened under the standard discrepancy resolution process instead. This took another three weeks and a phone call to the FTB taxpayer assistance line that went nowhere until I specifically asked for a supervisor who handled ENS mismatches. The workaround I ended up using was to submit the completed worksheet anyway, with a cover letter referencing the notice number and explicitly requesting manual review due to the fraud flag. The FTB eventually accepted it, but the automatic quick resolution lane was permanently blocked for that notice. I learned to check whether the notice had a fraud or compliance code before assuming the worksheet would take the fast track.
Counter-Intuitive Things I've Learned
First, the worksheet is not evidence. It's a narrative tool. The FTB reviewer reads it to understand your side before looking at the actual documents you attach. If the worksheet is sloppy or contradictory, the reviewer assumes the underlying data is too. I've seen clean discrepancies get rejected because the worksheet was confusing, and messy discrepancies get accepted because the worksheet told a clear story. Second, and this will surprise people, sometimes the state is right and you're wrong — but the wrong number is on the state's side, not yours. The FTB's matching system pulls from multiple data sources: your filed returns, third-party information returns, and sometimes data shared from other states. A multi-state employer I worked with had a discrepancy that looked like underreporting. It turned out another state had reported wages to California that California had never received, and the matching algorithm attributed those phantom wages to the employer. The worksheet helped surface this because it forced us to itemize each data source instead of treating the discrepancy as a single number.
What the Worksheet Actually Looks Like
The document has a header section with your FTB account number, the notice date, and the tax period in question. Below that are rows for each quarter, with columns for reported wages, state-verified wages, and the difference. There's a section for withholding amounts and a section for tip income if applicable. The bottom part is for your explanation and signature. Don't skip the explanation section. I've seen people fill in every numeric field and leave the explanation blank, assuming the numbers speak for themselves. They don't. The reviewer needs context. A single sentence explaining the root cause — even if it's "corrected return filed 03/15/2024" — makes the difference between a five-minute resolution and a three-week backlog.

When This Approach Completely Fails
The quick resolution worksheet only works when the discrepancy is purely numerical and documented. If the issue involves intent, fraud, or a compliance investigation, the worksheet is irrelevant. The FTB will route your case to a different unit regardless of how clean your worksheet is. I've had two clients where the notice included language about potential civil penalties, and the quick resolution path was immediately unavailable. Also, if you've already filed a formal protest or appeal on the same notice, you can't use the worksheet as a parallel track. The FTB treats these as mutually exclusive pathways. Pick one and stick with it. There's no real alternative to the worksheet for simple ENS mismatches. You could try calling the FTB directly and working it out over the phone, but that rarely produces a paper trail, and if the case escalates later you'll have nothing to show for the conversation. The worksheet at least creates a record of your good-faith effort to resolve the discrepancy.
A Few Practical Details
File the worksheet within the response deadline on the notice. The clock starts on the date printed on the notice, not the date you receive it. If you need more time, request an extension before the deadline expires. The FTB is generally reasonable about extension requests for ENS discrepancies, but they won't grant one retroactively. Keep a copy of everything. Not because you think you'll need it, but because you will. I once spent forty-five minutes on the phone with the FTB trying to reconstruct a submission from six months ago because my client hadn't kept a copy. The worksheet had been accepted, the case was closed, and we still couldn't prove it without documentation. If you're working with a payroll provider or CPA, send them the notice immediately. Don't wait to see if you can handle it yourself. ENS discrepancies often involve quarterly filings that your internal team doesn't have ready access to, and the payroll company usually has the data in their system within minutes.