The diagnostic runs entirely in your browser. Open DevTools (F12 → Network tab) before clicking upload — you'll see zero outbound traffic carrying file content. Only a SHA-256 hash is computed locally for workpaper provenance.
🗑️ Retention
Results stay in your browser session — auto-delete in 48 hours.
Scan results persist locally in your browser session and auto-delete within 48 hours. Nothing is stored on our servers — there's nothing to delete server-side. A Data Processing Log documenting the deletion schedule is included in your artifact set for workpaper compliance.
🔍 Structural Only
Structure, not substance.
The diagnostic evaluates structural integrity only. Entity labels are harmonized for comparison; numeric values are never inferred or altered. No tax advice, nexus determinations, or filing recommendations. Professional judgment remains with your firm.
Run the diagnostic on your own exports
Upload a recent export. 90 seconds. Six artifacts. Workpaper-ready.
Apportionment schedule, provision export, multi-entity rollup — any export from CCH Axcess, GoSystem RS, ONESOURCE, or Corptax. The diagnostic runs a 17-point structural check (CF-01 through CF-17) on your real data, entirely in your browser.
Most firms don't know the answer to this until they run it on their own files.
↑
Drop your export here, or click to browse
.xlsx, .xls, .csv — up to 50 MB. Multiple files supported.
~90 seconds per file. Runs entirely in your browser. Larger files (10K+ rows) may take up to 2 minutes.
What you receive
Six workpaper-ready artifacts per scan — the same artifact set you saw in the demo, with your data instead of synthetic.
Where the file goes
Nowhere. Processed in-memory. No upload to our servers. SHA-256 hash computed locally for workpaper provenance only.
This is what your team will actually review before sign-off:
What each scan produces
The same results experience you saw in the demo — with your real export data.
Data Consistency Score — 0–100 across four dimensions: Structural, Calculation, Jurisdiction, Compliance. Findings categorized by CF-01 through CF-15 with detection confidence, fix time estimate, affected rows, and resolution status.
Three role views — Sr. Associate (full detail), Manager (detection basis and resolution status), Partner (consequence summary). Switch between them based on who is reviewing.
Six artifact downloads — Export Exception Summary (PDF), Data Consistency Scorecard (PDF), Pre-Sign-Off Structural Validation Control (PDF), Corrected Workpaper Reference (Excel), Validation Workpaper Note (TXT), Data Processing Log (PDF).
Workpaper note + preparer attestation — Copy-paste-ready language for your engagement file, plus signature lines for your review layer.
This doesn't add review time — it replaces unstructured review time with a documented check.
Peer-share mechanic — Generate an anonymized version of the Export Exception Summary, safe to forward firm-wide with zero client-identifying data.
◆
If your files are clean, you still get the audit trail.
A clean Export Exception Summary attached to an engagement workpaper is documented evidence that structural validation was performed before sign-off. Whether findings exist or not, that documentation didn't exist before. In a state exam, that's the difference between 'we reviewed it' and 'we can prove what was checked.' If this isn't something your team would attach to an engagement workpaper before sign-off, you don't pay.
Need IT review before uploading?
Architecture memo available for InfoSec teams.
In-browser processing architecture, SHA-256 provenance methodology, $3M E&O / $1M Cyber insurance documentation. Forward to your IT security team — no upload required to download.
CF-06, CF-08, CF-09 — Whitespace, IC elimination, NOL
CF-10 through CF-14 — Schema, duplicates, completeness
Computing Data Consistency Score · generating artifacts
📄your_export.xlsxDiagnostic ID: DIAG-—
◆ Key question — CF-15 Factor Re-derivation
Can this build be re-derived from the exported components?
This diagnostic does not determine whether the factor is correct. It determines whether the factor can be proven from the export.
📋
—
—
CF-15 · Summary
Score—
Critical—
Flagged—
Convention—
Remediation—
—
⚠
Exceptions
Structural conditions identified — review required before sign-off.
Findings documented below. Numeric values were not modified — repairs are structural only. Attach Export Exception Summary to the engagement workpaper file.
Measures structural consistency of the export — not tax position accuracy.
⚠ EXCEPTIONS IDENTIFIED — PARTNER REVIEW REQUIRED
— critical · — flagged · — convention
Structural—
Calculation—
Jurisdiction—
Compliance—
Rows scanned—
Total findings—
Critical—
Flagged—
Convention—
Classification—
Remediation tier—
Checks runCF-01 through CF-17
View as:All findings · full detail · resolution status per item
Partner View — Consequence Summary
Structural diagnostic complete—
What this means for this file
On this file — right now
The gap this diagnostic documents
Whether findings exist or not, you now have a documented Export Exception Summary showing that structural validation was performed before sign-off. A clean result isn't nothing. It's workpaper evidence that the check ran — the audit trail that didn't exist before.
Repair Ledger
ValuesNo numeric values modified. All original values traceable to source.
✓ Untouched — provenance preserved
All artifacts generated locally from your scan results. Auto-deleted within 48 hours. The 6-file set is identical to what you saw in the demo — with your real export data.
Validation Workpaper Note — Copy / Paste Ready
Structural diagnostic performed. Diagnostic ID: —. SHA-256: —. No PII retained. In-browser processing — zero server transmission.
Paste into CaseWare, SharePoint, or CCH binder. Attach Export Exception Summary PDF for full documentation.
Preparer Attestation — Workpaper Sign-Off
Reviewed By
Date
Title / Role
Engagement
Structural screening only — not a tax opinion. This report identifies data format and consistency conditions; it does not evaluate the correctness of reported amounts or tax positions. CF-15 cause codes are diagnostic classifications requiring human verification at source — not determinations of preparer error or tax position. Professional judgment remains with your firm on all findings.
Forward this internally
Want to show a colleague? Forward an anonymized version.
Generate an anonymized version of your Export Exception Summary — entity names blanked, dollar values scaled — and forward it from your own email. Zero client-identifying data. Safe to share firm-wide. The diagnostic runs in-browser so the same check is available to any colleague immediately.
↓ Anonymized Export Exception Summary
Generate a peer-shareable PDF.
Same structure as your full Export Exception Summary. All entity-identifying data redacted. Numeric values scaled. CF findings, score, and grade preserved.
Redacted: entity names → "Entity 1, Entity 2…" · dollar values → scaled to nearest $10K · client identifiers removed · CF codes and score preserved.
📧 Email — peer review framing
Subject: Ran this on a QSSS return — caught something I wouldn't have seen in review
[Colleague],
I ran one of our recent QSSS multi-entity exports through a structural diagnostic — the kind of pre-sign-off check that goes a layer deeper than standard review. It runs a 17-point structural diagnostic (CF-01 through CF-17) — factor arithmetic, sign consistency, entity integrity, jurisdiction codes, consolidation conventions, and more.
What it caught: sign-inverted factors on QSSS subsidiary rows that looked like errors but were actually expected platform export behavior. Classified as CONVENTION_DOCUMENTED with workpaper notes pre-populated.
Attaching an anonymized version of the output. No client data. The check itself runs in-browser — no IT approval, no upload: financeocr.com/verify
[Your name]
Best for: SALT seniors, fellow partners, the tax director who would approve adoption firm-wide.
💬 Slack / Teams — quick share
Ran a QSSS multi-entity export through a structural diagnostic — 17-point structural check (CF-01 through CF-17). It caught sign-inverted QSSS subsidiary rows that standard review wouldn't flag. Classified as CONVENTION_DOCUMENTED with workpaper notes pre-populated. Anonymized output attached — no client data. Browser-only, no upload: financeocr.com/verify
Best for: Internal Slack/Teams channels, quick FYI to a colleague.
After your scan
Run 3–5 exports to build a full picture before engaging a Pod License.
One scan shows whether the diagnostic surfaces conditions on your real files. Three to five scans across different engagements gives you a representative sample to bring to your SALT director. If no critical findings and no material exceptions surface across the files you test — you have documented evidence that structural validation was performed. That's the deliverable either way.