Bankruptcy Exemption Checker Guide for Kentucky
7 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
DocketMath’s Bankruptcy Exemption Checker (Kentucky) helps you translate Kentucky’s key time-based and exemption-related rules into a workflow you can follow when preparing a bankruptcy filing. The tool focuses on timing windows that show up in exemption planning—so you can see whether particular assets or actions fall inside or outside certain lookback periods.
In Kentucky, several statutes tie eligibility questions to 5-year (and sometimes 1-year) periods. Your results will use those time windows and the applicable exceptions listed in the Kentucky Revised Statutes data set in DocketMath.
Core timing anchors the tool uses (KY)
| Rule / statute | Default lookback window | Built-in exception notes (from the tool’s KY rule set) |
|---|---|---|
| KRS 500.020 | 5 years | Exception P3 |
| KRS 500.050 | 5 years | Exception P2 |
| KRS 500.050 | 1 year | Exception P4 |
| KRS 500.050(2) | 1 year | Exception V3 |
| Ky. Rev. Stat. § 355.2-725 | 5 years | Exception D3 |
Note: This guide is about using DocketMath’s exemption checker workflow. It’s not legal advice, and it doesn’t replace a full review of your bankruptcy eligibility, asset-specific exemptions, or any federal bankruptcy rules that may also apply.
Use the Bankruptcy Exemption Checker (Kentucky)
When to use it
Use DocketMath’s Kentucky exemption checker when you need clarity around whether a date-based fact pattern might place an asset, transaction, or claim within a specific window—particularly if you’re working backward from a filing date or trying to understand how long ago something occurred.
Good times to run the tool
- You have a specific filing target date in mind and want to test timing scenarios.
- You’re dealing with events that happened within the last 5 years, including major transactions or ownership changes.
- You’re concerned about shorter 1-year periods that can trigger different outcomes under KRS 500.050 and KRS 500.050(2).
- You have issues involving contract or sale-of-goods claims and need to track a 5-year limitations window tied to Ky. Rev. Stat. § 355.2-725.
When you may want a “second pass”
Run it again if any input date changes—because a shift of even a few months can move a fact from one lookback window to another (for example, from a 5-year window into a “still inside” or “already outside” category).
Step-by-step example
Below is a practical example showing how you can use DocketMath and how the output typically changes when you adjust dates.
Example fact pattern (Kentucky)
Assume you plan to file bankruptcy on June 15, 2026. You’re reviewing the timing of several events:
- Event A (asset transfer): March 1, 2021
- Event B (another transfer/transaction): September 10, 2025
- Event C (related claim timing issue): April 20, 2021
- Event D (contract/sale-of-goods claim): November 30, 2020
Now apply the lookback logic embedded in the KY rule set.
Step 1: Set your “reference date” (filing date)
- Enter June 15, 2026 as the date you’re planning to file (or the date you want the tool to count backward from).
Step 2: Enter event dates as your tool inputs
For each event, enter the date the event occurred (e.g., transfer date, claim date trigger date, or relevant transaction date).
Step 3: Watch the lookback windows trigger
The tool uses the KY timing anchors:
- **5-year window (KRS 500.020; KRS 500.050; Ky. Rev. Stat. § 355.2-725)
- **1-year window (KRS 500.050 and KRS 500.050(2))
- Exceptions (P2, P3, P4, V3, D3) are accounted for in the tool’s rules engine.
Now test each event:
Event A: March 1, 2021
- From June 15, 2026 back to June 15, 2021 is 5 years.
- March 1, 2021 is inside the 5-year window.
- Output will generally flag that this event falls within KY’s 5-year lookback timing logic tied to rules like KRS 500.020 and KRS 500.050 (depending on which scenario category your entries map to) and may also interact with the exception labels the tool provides (such as P2 or P3).
Event B: September 10, 2025
- This is well within 1 year of June 15, 2026.
- The tool will likely categorize it under the 1-year logic tied to KRS 500.050 and KRS 500.050(2) exceptions (including P4 and V3, depending on the mapping).
Event C: April 20, 2021
- Also inside the 5-year window.
- Expect the tool to treat it similarly to Event A for the 5-year-based logic.
Event D: November 30, 2020
- More than 5 years before June 15, 2026.
- The tool should show this event as outside the KY 5-year window used for limitations-style timing (including Ky. Rev. Stat. § 355.2-725, which the tool tracks as 5 years under the provided rule set).
Step 4: Adjust one input date to see how results change
If you move Event B from September 10, 2025 to July 1, 2024, it becomes:
- Still inside 5 years, but
- Outside the 1-year window for June 15, 2026
That single change typically shifts the tool’s classification away from “1-year period logic” and toward “5-year period logic,” which can materially change how you interpret timing risk.
Common scenarios
Kentucky filings often involve timing questions that resemble the following patterns. Use these checklists to decide what to enter into DocketMath.
Scenario checklist (tick what applies)
Quick mapping: what the time windows usually mean in practice
| Timeline from your reference date | What the tool tends to flag |
|---|---|
| Within 1 year | Heightened relevance to KRS 500.050 and KRS 500.050(2) time-based exceptions (like P4 and V3) |
| Between 1 and 5 years | Primarily interacts with 5-year timing logic under KRS 500.020, KRS 500.050, and potentially Ky. Rev. Stat. § 355.2-725 (subject to your scenario mapping) |
| More than 5 years | Often treated as outside the core lookback windows in the tool’s KY rule set, including the 5-year limitations-style tracking (e.g., § 355.2-725) |
Pitfall: People often enter the date they heard about something rather than the actual transaction/claim-trigger date. If your input date is wrong, the calculator can legitimately classify the event under the wrong window (1-year vs 5-year), even when all your other facts are correct.
Tips for accuracy
You’ll get the most useful output when your date inputs are precise and consistent with the meaning of the event you’re entering.
Use consistent dates across your dataset
- If you enter the filing date as June 15, 2026, use that same reference date for every event comparison.
- Don’t mix calendar conventions (for example, using a “month-only” date for one event and a full day for another).
Enter the “event date,” not secondary dates
Examples of higher-quality inputs:
- Transfer date for asset transfers
- Date of the triggering act for claims tied to a limitations period
- Date the relevant contract/goods event occurred when applying timing under Ky. Rev. Stat. § 355.2-725 (5 years in the tool’s KY rule set)
Sanity-check boundaries at exactly 1 year and 5 years
Because Kentucky’s embedded time windows include 5-year and 1-year periods (including the specific rule groupings in the tool:
- KRS 500.020 — 5 years (exception P3)
- KRS 500.050 — 5 years (exception P2)
- KRS 500.050 — 1 years (exception P4)
- KRS 500.050(2) — 1 years (exception V3)
- Ky. Rev. Stat. § 355.2-725 — 5 years (exception D3)),
you should pay close attention to dates that fall close to the boundary.
- If an event is exactly one year earlier, confirm the day/month/year—not just the year.
- If an event is exactly five years earlier,
Sources and references
Start with the primary authority for Kentucky and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
