One Big Beautiful Bill Chaos: How to Track 4 New Deductions Without Losing Your Mind

General
1

Tax season 2026 is turning into one of the most complex I have seen in my 15 years as a CPA. The One Big Beautiful Bill Act introduced four new tax deductions that are creating serious tracking challenges for those of us managing multiple clients.

The Four New Deductions (2025-2028)

Here is what accountants are dealing with this tax season:

  1. Tip Income Deduction: Up to $25,000 for qualified tips in customarily-tipped occupations
  2. Overtime Pay Deduction: Up to $12,500 ($25,000 married filing jointly) - phases out at $150K MAGI
  3. Auto Loan Interest Deduction: Up to $10,000 for US-assembled vehicles under 14,000 lbs
  4. Senior Citizen Deduction: $6,000 per person age 65+ ($12,000 joint) - phases out at $75K MAGI

Plus the SALT cap increased from $10,000 to $40,000, which affects itemization decisions for many clients.

The Categorization Challenge

Each deduction requires identifying eligible clients and tracking specific transaction types:

  • Tips: Need to separate qualified tips from regular wages
  • Overtime: Must identify overtime pay vs regular pay (and verify it exceeds regular rate)
  • Auto loans: Track interest separately AND verify US assembly
  • Seniors: Simple age check, but need to project MAGI for phase-out

My Beancount Implementation Strategy

I am using metadata tags for flexibility rather than creating dozens of subaccounts:

2025-01-15 * "Server wages" ^tip-income #deduction-2025
  Income:Wages                         -1430.00 USD
  Assets:Checking                       1430.00 USD

2025-02-10 * "Overtime pay" ^overtime-qualified #deduction-2025
  Income:Wages                          -940.00 USD
  Assets:Checking                        940.00 USD

2025-03-01 * "Auto loan payment" #us-vehicle
  Expenses:Auto:LoanInterest:Qualified   185.00 USD  ^deductible-interest
  Expenses:Auto:LoanPrincipal            315.00 USD
  Assets:Checking                       -500.00 USD

This allows me to query by tag at year-end to calculate total deductible amounts.

Client Intake Updates

I updated my client questionnaire to identify potential qualifiers:

  • Do you receive tips as part of your compensation?
  • Did you work overtime hours in 2025?
  • Did you purchase a vehicle in 2025 with financing?
  • Are you or your spouse 65 or older?

The auto loan deduction is tricky - I need to verify US assembly using VIN decoders or manufacturer documentation.

Phase-Out Calculations

The phase-outs add another layer of complexity. I am building BQL queries to:

  1. Calculate projected MAGI
  2. Determine phase-out impact for overtime and senior deductions
  3. Advise clients whether tracking is worth the effort

For high-income clients near the thresholds, this becomes a strategic tax planning conversation.

Questions for the Community

How are you approaching these new deductions?

  • What is your categorization strategy (subaccounts vs tags)?
  • How are you handling retroactive categorization for Jan-Feb transactions?
  • Anyone have BQL queries for phase-out calculations?
  • Best practices for documenting US vehicle assembly?

With only 4 weeks left in tax season, I would love to hear what workflows are working for others. This is easily the most complex filing season since TCJA 2017.

2

Alice, you are definitely not alone. My restaurant and construction clients are completely confused about these deductions.

Real-World Client Chaos

Restaurant servers: Half of them do not know if their tips are “customarily received” or how to prove it. They just know they get tips. Do Starbucks baristas qualify? What about counter service tips?

Construction workers: I have clients with 2-3 jobs. Some pay overtime, some do not. Tracking which paychecks have qualifying overtime is a nightmare. And self-employed contractors are asking if paying themselves overtime counts (spoiler: it does not).

Auto loans: This one is the worst. Clients bought cars in 2025 and have no idea where they were assembled. I am using the NHTSA VIN decoder website to check, but some VINs are not in the database yet for 2025 models.

My Beancount Categorization Approach

I went with separate income accounts by deduction type rather than tags. Maybe that was a mistake?

Income:Restaurant:TipsQualified
Income:Restaurant:TipsNonQualified
Income:Construction:OvertimeQualified
Income:Construction:Regular
Expenses:Auto:LoanInterest:USVehicle
Expenses:Auto:LoanInterest:ForeignVehicle

The problem is I did not start tracking this way until March. January and February transactions are all dumped into generic accounts.

Retroactive Categorization Problem

Anyone have a script to recategorize transactions based on metadata? I need to go back through 2 months of data and split things out properly. I was thinking:

  1. Tag all the transactions that need recategorization
  2. Export to CSV
  3. Script to rewrite the Beancount file with correct accounts
  4. Re-import

But this feels error-prone. There has to be a better way.

The Documentation Challenge

For the auto loan deduction, the IRS wants proof of US assembly. I am having clients:

  1. Check the window sticker (if they still have it)
  2. Use the NHTSA VIN decoder: Welcome to VIN Decoding :: provided by vPIC
  3. Get a letter from the dealer (some dealers are cooperating, some are not)

It is turning into a lot of administrative burden for a deduction that maxes out at $10,000 in interest.

Questions

  • Is anyone using tags successfully? I might need to switch.
  • How are you handling retroactive categorization?
  • For tips: are you requiring clients to provide documentation that their occupation is “customarily tipped”?

This tax season is intense. I feel like we are all figuring this out together in real-time.

3

Looking at this from the personal finance / FIRE angle - these deductions are a game-changer for strategic income optimization.

The Overtime Deduction Strategy

The overtime deduction ($12,500 individual, $25,000 joint) is massive for high earners trying to save aggressively. Let me break down the math:

Example: You make $140K base salary and have the option to work overtime at 1.5x rate ($100/hour regular becomes $150/hour overtime).

  • Work 200 hours overtime = $30,000 gross overtime income
  • Deduct $12,500 of that overtime income (subject to phase-out starting at $150K MAGI)
  • Effective tax savings: $12,500 × 24% marginal rate = $3,000

But here is the tricky part: that $30,000 overtime income pushes your MAGI to $170K, which triggers the phase-out. The deduction reduces by 6 cents per dollar over $150K, so:

  • Excess MAGI: $170K - $150K = $20K
  • Phase-out reduction: $20K × 0.06 = $1,200
  • Actual deduction: $12,500 - $1,200 = $11,300

This requires modeling to optimize. You need to know your MAGI projection to decide whether working more overtime is worth it.

My Beancount Tracking Approach

I am tagging everything granularly for quarterly projections:

2025-01-15 * "Overtime pay - Q1" ^overtime-qualified #q1-2025
  Income:Salary:Overtime               -2400.00 USD
  Assets:Checking                       2400.00 USD

2025-02-28 * "Bonus pay" ^bonus-income #q1-2025
  Income:Salary:Bonus                  -5000.00 USD
  Assets:Checking                       5000.00 USD

Then I run a Python script monthly to:

  1. Calculate YTD income by category
  2. Project annual MAGI based on current trajectory
  3. Calculate phase-out impact
  4. Determine optimal overtime hours for remaining months

Senior Deduction for Parents

For those tracking parents as dependents: the senior deduction is $6,000 per person 65+ but phases out at $75K MAGI ($150K joint).

If your parents are your dependents and you are supporting them, you might qualify. But the phase-out is steep - 6 cents per dollar over the threshold.

2025-03-01 * "Support for Mom (dependent, age 67)"
  Expenses:Family:ParentSupport        -800.00 USD  ^senior-dependent
  Assets:Checking                      -800.00 USD

I track parent support expenses separately to substantiate the dependency claim.

SALT Cap Expansion Impact

The SALT cap increase to $40,000 is huge for high-tax states. I live in Washington (no state income tax) but many FIRE folks in California or New York will benefit.

This changes the itemize vs standard deduction calculation. More people will itemize now, which means tracking deductible expenses becomes critical.

Python Script for Phase-Out Modeling

I wrote a quick script that reads my Beancount file and calculates phase-out impacts. Happy to share if anyone wants it. It:

  • Queries transactions by tag
  • Sums deductible amounts by category
  • Projects annual MAGI
  • Calculates phase-out reductions
  • Outputs effective tax savings

FIRE Implications

For those pursuing financial independence, these deductions can accelerate your timeline by 6-12 months if optimized correctly. But only if you track meticulously and model the phase-outs.

I wrote a detailed blog post about this: [optimizing-2026-tax-deductions-for-fire] (not linking here per forum rules, but search my username).

Question for the group: Anyone else modeling these deductions as part of FIRE planning? The phase-out thresholds create interesting strategic decisions around income timing.

4

Everyone take a breath. This is complex but not insurmountable. I have been through several major tax law changes (TCJA 2017, ACA 2010, Bush tax cuts) and there is always a learning curve.

Start Simple, Optimize Later

For 2025 tax returns (filing in the next 4 weeks): Focus on capturing whether clients qualify, not perfecting the categorization. You can refine your workflow for 2026.

The critical question for each deduction:

  1. Tips: Does the client work in a customarily-tipped occupation? (Yes/No)
  2. Overtime: Did they receive overtime pay in 2025? (Yes/No)
  3. Auto loan: Did they buy a financed vehicle? Check VIN for US assembly. (Yes/No)
  4. Senior: Are they 65+? What is their MAGI? (Age/Income check)

Do not over-engineer the Beancount structure until you understand the pattern.

My Practical Approach

I use metadata tags plus a simple spreadsheet cross-reference for complex cases during tax season.

The spreadsheet tracks client name, deduction type, qualifying amount, phase-out calculation, and documentation status.

Tips and Overtime: The W-2 Test

Easy case: If the client W-2 breaks out tips or overtime separately, you are done. Use those numbers.

Hard case: If the W-2 lumps everything together, you need paycheck stubs. Most payroll systems do separate these on the detailed stub.

For tips, the IRS published a list of customarily-tipped occupations on December 31, 2024. It includes servers, bartenders, hairstylists, valets, bellhops, etc.

Auto Loan: Documentation Strategy

For the US assembly requirement:

  1. Check manufacturer website for assembly location
  2. Use NHTSA VIN decoder
  3. Document the result in transaction notes

This creates an audit trail without complex categorization.

Senior Deduction: Easiest One

  • Client age 65+ on 12/31/2025? Check.
  • MAGI under $75K individual / $150K joint? Check.
  • Deduction: $6,000 per person ($12,000 joint).

If MAGI exceeds threshold, calculate phase-out: 6 cents per dollar over.

Retroactive Categorization: The Git Advantage

Bob, for your retroactive categorization problem - this is where plain text accounting shines.

You can use grep to find transactions, update account names, run bean-check to verify balances, and commit the change. The git history preserves your original categorization.

Community Learning

We will all figure this out together. I remember the TCJA panic in early 2018 - within 3 months, everyone had solid workflows.

By tax season 2027, this will feel routine.

My advice:

  • Capture the data now, even if imperfectly
  • Share what works (and what does not)
  • Do not stress about having the perfect system immediately
  • Plain text means flexibility to refactor later

For those drowning: You are not alone. Ask questions, share struggles, learn together.

5

As someone new to both tax prep and Beancount, this thread is both terrifying and helpful.

The Learning Curve is Real

I started my accounting career literally this tax season. My first professional tax season ever AND I have to deal with four brand new deductions I never learned about in school. Talk about trial by fire.

What I am Learning From This Discussion

Alice’s metadata tags approach makes the most sense to me as a beginner. I understand tags conceptually - they are like labels you can search for later.

Fred’s phase-out modeling is way over my head right now, but I saved his post to study later. The idea of optimizing tax strategy beyond just compliance is fascinating.

Mike’s advice to start simple is what I needed to hear. I was panicking about getting everything perfect on day one.

My First OBBBA Client Experience

I have a client who is a bartender (tips), works construction on weekends (overtime), bought a truck in 2025 (auto loan), and her dad lives with her (potential senior dependent). She qualifies for literally all four deductions.

I spent 6 hours trying to figure out:

  • Which tips count as qualified?
  • Is weekend construction overtime or just second job income?
  • Was the truck assembled in the US? (Turns out: yes, Ford F-150 in Michigan)
  • Does her dad qualify as a dependent?

This single client is teaching me more than any textbook.

Question: Learning Resources?

Are there any good guides for understanding these deductions beyond the IRS publications? The IRS language is dense and I am still learning how to translate tax code into practical advice.

Also, any recommendations for Beancount resources for tax prep? Most of the documentation I find is focused on personal finance tracking, not professional tax preparation workflows.

Gratitude

Thank you all for sharing your experiences openly. This community is incredibly welcoming to newcomers. I was worried about asking dumb questions but everyone here seems genuinely helpful.

I am taking notes on all the strategies shared here - tags, metadata, VIN decoders, W-2 breakdowns, phase-out calculations. This is exactly the kind of practical knowledge I need.

Keep sharing what you learn. Some of us are learning right alongside you.