Uniformity Issues for Federal

Fed/State Uniformity
State Acknowledgments
Jamie Stiles, Drake Software
Squire Dahl, Orrtax Software Solutions
Season In Review
 IRS
system highly successful
 Standardization of ack format
 Centralized Acknowledgment Source
 Fed and State
 No transaction cost solution
1
State Issues
To accurately process acks, industry
needs the following:
 All piggyback states use IRS centralized
system
 All states follow the standard 120-byte
format
 More fields need to be required
Suggested Required Fields










Return Sequence Number (RSN)
Refund/Balance Due
Acceptance Code
Duplicate Code
Date Accepted
Declaration Control Number
Number of error records
State DD Indicator
State-Only Code
State Packet Code (2-digit state code)
2
Acknowledgment Codes




A = Accepted … No re-transmission is
required
R = Rejected … Return will NOT be
processed
D = Duplicate (rejected) … Return will NOT
be processed
N (Notification) and C (Conditional) are not
consistent between states and the software
developer community prefers they not be
used at all
Reject Codes
 Follow
4-digit standard
 Only use for rejected (R or D) returns
 Consistency between states and IRS
(For example, 0902 = Duplicate DCN)
 Reject for all conditions where your
system cannot process the return:
 Duplicate
DCN
 Missing State-Only Indicator
3