Six months of documented
structural validation.

FinanceOCR provides structural integrity verification of tax export files during the engagement term. The diagnostic answers one core question: can the build be proven from the exported components?

• 17-point structural diagnostic (CF-01 through CF-17) applied to SALT apportionment schedules, multi-entity rollups, and provision exports from CCH Axcess, GoSystem RS, ONESOURCE, and Corptax
• CF-15 Factor Re-derivation Gap check on every applicable file — whether the factor can be re-derived from exported numerator, denominator, and factor columns without additional source-level explanation
• Per-scan Export Exception Summary (PDF) with Structural Reliability Score, finding-level detail, cause classification, and SHA-256 provenance hash
• Validation Workpaper Note formatted for direct attachment to engagement files in CaseWare, SharePoint, CCH binder, or equivalent systems
• Corrected Workpaper Reference (Excel) with CF-15 re-derivation tab and exception log — structural repairs applied, numeric values never modified
• Master Export Integrity Summary at engagement close, aggregating findings across all files diagnosed during the term, formatted for risk committee review
• Standard business hours support throughout the engagement term, with priority response during active filing deadline windows

Engagement term: Six (6) months from date of signature. Coverage activates immediately upon execution and payment receipt. No auto-renewal — engagement terminates automatically at the end of the six-month term unless renewed in writing.

Engagement fee: $15,000 USD. Partner-level license covering one (1) tax partner and direct team members. No usage caps on diagnostic scans during the engagement term. Contact onboarding if your team is larger.

Practice-level and firm-wide licenses available separately for firms deploying across multiple practice groups. Contact emmanuel@financeocr.com to discuss.

Payment due upon execution. Engagement activates upon payment receipt.

• Stripe checkout (credit card or ACH): immediate activation — account provisioned within minutes
• Net 30 invoice: activation upon invoice receipt; for firms with AP or procurement requirements
• Wire transfer or check: contact onboarding to arrange; activation upon funds receipt

The diagnostic operates as a client-side application. File processing occurs entirely within the reviewer's browser via WebAssembly. No file content is transmitted to FinanceOCR infrastructure at any point during diagnostic execution. Every claim below is verifiable by your IT team without taking our word for it.

• In-browser processing: no disk writes, no server storage of input files, no transmission to FinanceOCR servers
• PII pattern detection at ingestion: The scanner is configured to detect SSN, EIN, credit card, and bank account number patterns and reject before processing. Testable: create a CSV with a synthetic SSN pattern (e.g., 123-45-6789) and attempt a scan — the file is rejected at ingestion. This is a configuration control verifiable by behavior, not an architectural guarantee
• Cryptographic provenance: SHA-256 hash computed locally for every file diagnosed, embedded in all workpaper artifacts. Verifiable independently: after any scan, run PowerShell Get-FileHash [filename] -Algorithm SHA256 and compare to the hash in the Export Exception Summary — they will match, confirming the hash was derived from your file
• Diagnostic outputs: Export Exception Summary, Scorecard, and Workpaper Note generated client-side and downloaded directly to your machine
• Four independent verification methods — no trust required:
  ① No transmission: DevTools (F12) → Network tab → run a scan → zero outbound POST requests carrying file content.
  ② No browser storage: DevTools → Application tab → Storage → inspect localStorage, sessionStorage, IndexedDB before and after scan — nothing written.
  ③ In-browser processing: DevTools → Sources → confirm .wasm file loaded locally; Performance tab shows all CPU work client-side with no network calls during processing.
  ④ Client-side outputs: DevTools → Network tab → download Export Exception Summary → the download is triggered by a blob: URL, not a server response. No GET request to financeocr.com servers.

Professional Liability (E&O): $2,000,000 aggregate. Certificate of Insurance provided at engagement start, with engaging firm named as certificate holder upon request.

Cyber Liability: $1,000,000 aggregate. Engaging firm may be named as additional insured upon request.

Pre-signed Non-Disclosure Agreement covering the engagement period is included in the engagement packet. Mutual confidentiality obligations apply throughout the engagement term and survive termination.

This is a partner-level license structured as professional services — designed for a tax partner with their own P&L who can authorize engagement under existing professional services authority, the same channel used for outside counsel, forensic accountants, and valuation firms. No IT procurement approval, no vendor onboarding queue, no software contract. One (1) tax partner and direct team members.

Additional partners at the same firm may independently license access for their own practice groups under the same terms. Each partner license is a separate engagement — no firm-wide approval required.

Practice-level (6–25 users) and firm-wide licenses available separately at reduced per-partner cost. Contact onboarding to discuss multi-license arrangements.

Within the first 30 days of the engagement term, your team runs the diagnostic on 3–5 of your own export files. Two outcomes:

• Findings surfaced: you have documented Export Exception Summaries showing what the diagnostic found and what was done about it before sign-off. That documentation is the deliverable.
• Files are clean: you have documented Export Exception Summaries showing that structural validation was performed — the audit trail that didn't exist before. That documentation is still the deliverable.

This assurance allows your team to begin diagnostic work immediately while internal stakeholders complete any procurement reviews on their own timeline.

Either party may terminate with written notice. Upon termination:

• Your team retains all diagnostic outputs already generated — Export Exception Summaries, Scorecards, Workpaper Notes, and all workpaper artifacts
• Any retained provenance hashes (SHA-256 only — no file content) are deleted within 30 days; deletion confirmation provided in writing
• If terminated under the 30-day workpaper assurance, full refund issued within 10 business days
• If terminated mid-engagement after the 30-day assurance window, no refund of remaining term unless otherwise agreed in writing

FinanceOCR maintains the insurance coverage described in Section 05. Total liability under this engagement is limited to the engagement fee paid ($15,000), except for claims covered by applicable insurance policies. FinanceOCR is not liable for indirect, incidental, consequential, or punitive damages.

The diagnostic identifies structural data consistency conditions only. Cause codes are diagnostic classifications requiring human verification at source — not determinations of preparer responsibility or tax position. Professional judgment on all findings remains with the engaging firm.