Discretionary Edits

A discretionary edit (DE) is a system-generated message triggered when the information entered on a transaction window does not conform to business rules. The event is called "discretionary" because you (or a supervisor) might choose not to correct the data entry issue before proceeding with the transaction.

Examples of discretionary edits include:

• The system cannot contact a federally-maintained database to validate the data, such as EVVER for DOB or SSOLV for SSN.
• The odometer reading is unknown for a vehicle included in a transaction. (This might also be a form error in certain transactions.)

You must perform some sort of action before the system saves and/or processes the data. Three possible courses of action can be taken when a discretionary edit window appears:

• Correct the error and proceed with the transaction.
• Click the Auto Approve button to proceed with the transaction without fixing the data, if your authority level is high enough for the specific DE (each type of DE has its own user-defined approval level).
• Click the Process Selected button to submit the error to Work Management, where someone with an appropriate approval level will do one of the following:
  • Return it to you to fix.
  • Approve the error, which allows you to proceed with the transaction without fixing the data.

Your user profile determines whether you can approve a DE. If you have the appropriate level of permission, you can approve the DE directly from the Error Worksheet window. If you do not have the appropriate level of permission, you can send a tag request, which is a notification requesting that an authorized user review the DE.

When a discretionary edit is processed, a tag is created as a record for how the edit request was handled. For more information, see Internal Messages.