Why transcripts come first
Everything a client tells you on a call is recall — useful for tone and urgency, unreliable for balances and enforcement. The IRS account transcript is the ledger. RESO treats parsed transcript facts as the highest authority tier on the case: balances, enforcement signals, and statute inputs in your reports come from the transcript, and narrative elsewhere must reconcile with it rather than contradict it.
Uploading transcripts
Transcript upload lives in the Reports tab, inside the Discovery Report flow. Upload the transcript PDFs you have — account transcripts for open years are the workhorses; wage and income documents add cross-reference value. You do not need a Power of Attorney to start: client-downloaded transcripts from the IRS Online Account are enough for qualification and Discovery work before representation begins. Uploaded files are stored on the case in Documents, and the Profile tab shows transcript coverage per party so you can see which years are still missing.
What gets parsed
The transcript parser converts each document into structured rows — transaction codes, dates, amounts, and periods — and a refresh pass derives intelligence on top of the parse:
- Balances and posting posture per tax year, from the IRS ledger rather than client memory.
- Enforcement signals — liens, levy indicators, and related collection flags that the parser captures.
- CSED inputs — assessment dates and tolling-relevant events that feed collection-statute analysis.
- Filing posture, including substitute-for-return (SFR) signals on unfiled years.
- Cross-reference findings from deterministic reconciliation — for example, withholding reported on wage documents with no matching credit posted, refund-statute windows, and amendment opportunities.
Refreshing transcript intelligence
Derived intelligence is stamped onto the case when transcripts are uploaded or explicitly refreshed. When you add newer transcripts — say the client pulls a fresh account transcript after a payment posts — the refresh re-derives the intelligence and the case carries the updated facts forward. Reports read the stamped facts rather than re-deriving them on every view, so what you reviewed is what gets exported.
How transcript facts ground reports
The Discovery Report reads the parsed evidence directly: per-year balances, enforcement posture, urgency signals, and program-fit framing all trace to transcript lines. The Strategy Report combines the same ledger facts with the 433 financial intake to evaluate program viability. When the client story disagrees with the ledger — “I already filed that year” against a missing return posting — RESO frames it as a timing or staleness question to verify, never as alternate truth.
Practical tips
- Pull account transcripts for every open year before quoting implementation — partial coverage produces partial pictures.
- Add wage and income transcripts where unfiled years or withholding questions exist; that is where reconciliation findings tend to surface.
- Re-upload fresh transcripts after significant events (payments, filings, IRS notices) and refresh before regenerating a report.
- Use a desktop browser for upload and parsing — the mobile workspace is for review.
What RESO does not do
RESO does not invent ledger facts. If a signal is not on the transcript, it is not asserted as IRS truth — it may appear as client-reported context with verification language, but balances, enforcement posture, and statute inputs always trace back to parsed evidence your firm can show its work on.