Managing Transaction Definitions and Mapping 835's

It would be ideal if a user group with permission to edit transaction codes could also specify one or more CARC Adjustment Reasons that are listed and imported with an 835 map to a transaction definition created in the system, and if one is not mapped, it maps to the generic denial that is standard in EchoVantage.

Also need to have start and end dates for transaction codes so that termed transaction definitions do not appear to billing users.