Re: Ohio client letter trigger codes in TY2025 not working correctly - Intuit Accountants Community

Welcome back! Ask questions, get answers, and join our large community of tax professionals.

Ohio client letter trigger codes in TY2025 not working correctly

In 2025 ProSeries Professional, two “XXX” trigger codes are not operating correctly (and in the same manner as prior years) when pulling from the Ohio individual return. These two trigger codes, however, appear to be operating correctly with respect to various other states.

The two trigger codes that are operating unexpectedly and incorrectly when pulling from the 2025 Ohio return are:

[@XXXDueWPen]

[@XXXEFDwP]

My understanding of the above two codes is that when a balance is due in the Ohio return and the client is paying by check, only one of the above two codes should trigger a “yes” based on whether the return is setup for e-filing or paper filing. However, currently both of the above codes trigger a “yes” regardless of whether the return is set up for e-filing or paper filing.

This is causing duplicate amounts to show up in the standard client letter and causing other issues with the standard letter, as our firm has customized it.

To ProSeries support - I submitted a calculation challenge regarding this and did not hear back. Would you please look into and correct these trigger codes as mapped to the 2025 Ohio individual return.

12 Comments 12

Hi @markhurst Thanks for posting in the Community about the two trigger codes for Ohio IND. We’ve shared this with Development for review.

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

Hi Kathi - thanks for the follow up. As of now (1/23/26) those trigger codes have not been corrected. Any idea on when we can anticipate an update that addresses the issue? Thank You! Mark

Hi @markhurst Thanks for asking about the correction to the trigger codes. The information that we have at the moment is that development is aware and are reviewing. We do not have any estimated time when this will be fixed and we will update this post when there is one.

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

Hi @markhurst We did not forget about you. Development is still reviewing. Thanks for the patience and we'll keep you posted!

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

Hi @markhurst This will be fixed in a future release of ProSeries.

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

We are also having unexpected and incorrect behavior with trigger codes in Ohio letters. I'm not sure which trigger codes are causing the issue, but attached is a snip of the Ohio page of a client letter. It is showing instructions for both mailed and e-filed returns. Should only be showing one or the other.

Hi @gabletax Thanks for bringing this to our attention. The trigger words will be fixed in a future update. We would wait for this and then see if it is still happening.

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

Most of my returns are Ohio. Yes, when is this going to be fixed.

Hi @Debst99 Thanks for asking about when the trigger words will be fixed. We do not have an exact date for this to be fixed however we do know it will be in an update coming soon.

**Say "Thanks" by clicking the thumb icon in a post
**Click "Mark as Best Answer " to mark the post that answers your question.

As of today, the trigger codes mentioned in this thread appear to be working as expected. I appreciate ProSeries development looking into this and fixing it.

Connected to this, I also noticed today that there is another trigger code that is not working correctly in only the Ohio individual return, and that trigger code is [@XXXDDepNo]

This trigger code should only report true when there is an Ohio refund, and the refund method is mailed check, and the return is being paper-filed. However, this trigger code is also reporting true when the return is being or e-filed, and this is incorrect.

ProSeries Support - would you please submit this for correction as well? Thanks! Mark

ProSeries Support - one more item connected to this.

This trigger code is also not working correctly in the Ohio individual return: [@XXXRefund]

This trigger code should be true when there is a refund and the return is being paper filed. However, it is also incorrectly reporting true when the return is being e-filed.

These erroneous trigger codings are causing the standard letter, and our customized letter, to look repetitive and unusual - definitely not the refined and professional look that our clients deserve and expect. A quick fix to this would be appreciated.

Hi @markhurst thanks for letting us know. I've passed this along.