Module 1 — Framework, Scope, and Methodology

Blueprint for solving the revenue gap exposed by statutory vs. operational treatment of Ohio sales tax (ORC 5739).

Purpose

Establish how every module classifies transactions, compares law to audit reality, and flags system failures.

This project produces a clear, verifiable, and practical breakdown of Ohio sales and use tax for:

• Business operators and retailers
• Tax practitioners and auditors
• Policy reviewers and voters
• Enforcement accountability

It is not a general tax guide. It is a structured analysis system: law → practice → gap → fix.

Core objectives

Core principles

The binary rule

Every transaction must resolve to either TAXABLE or NOT TAXABLE. No subjective middle layer at the classification stage.

Law vs. practice vs. problem

Separate three layers in every module:

1. Law — what ORC and OAC say
2. Practice — how POS systems, retailers, and auditors actually apply it
3. Problem — where ambiguity, inconsistency, or enforcement gaps create leakage or unfairness

System failure flag

If a rule is too complex for a standard POS system or a consumer to verify at transaction time, it is flagged as a System Failure (see Module 11).

Standard module structure

Modules 2–20 follow this pattern unless noted:

1. Governing law — ORC citations, definitions
2. Exact rule definitions — plain-language operational rules
3. Real-world application — receipts, scenarios, POS behavior
4. Points of confusion / misapplication — where operators disagree
5. Transparency & enforcement gaps — what receipts and audits cannot show
6. Policy problems — fairness and base-integrity impact
7. Proposed fixes — concrete reforms tied to Modules 12–14

Primary problem statement

Ohio sales tax (primarily ORC 5739) is:

• Exception-based, not default-rule-based — most goods are taxable; exemptions require proof
• Dependent on undefined or loose terms (e.g., “premises,” soft-drink tests, fixture vs. realty)
• Applied inconsistently across businesses, counties, and audit samples
• Hard to verify for consumers and small retailers at checkout

Result: identical transactions taxed differently, compliance risk for honest businesses, and revenue leakage where classification is gamed or skipped.

Data sources

Authoritative:

• ORC 5739.01 (definitions), 5739.02 (levy and exemptions)
• Ohio Administrative Code (OAC 5703 series)
• tax.ohio.gov guidance and forms

Operational (contrast with law):

• POS system defaults (Square, Toast, Clover, etc.)
• Real receipts and invoices
• Audit outcomes and industry patterns (where documented)

Scope alignment

Module 1 sets the repeatable framework used by Modules 2–20. Later modules inherit these definitions unless explicitly overridden.

Deliverables this framework supports

• Policy modules (Modules 2–20) — voter- and operator-readable articles
• Conflict mapping — statute vs. operational reality tables
• Reform mandates — real-time validation, receipt transparency (Modules 12, 17)
• Public advocacy materials — plain-language examples without overclaiming revenue (Module 14)

Module checklist (framework complete)

• [x] Documented definitions aligned with ORC 5739
• [x] Seven-section template for all policy modules
• [x] Law / practice / problem separation rule
• [x] Binary classification and system-failure criteria
• [x] Authoritative and operational data-source list