User's Manual - Drake Software

Data Entry
Drake Software User’s Manual
NOTES
Detail worksheets are produced as overflow statements but are not e-
filed with the return.
To print a description on a statement without a corresponding dollar
amount, enter a slash ( / ) in front of the description.
If you press CTRL+W (or double-click) in a Depreciation field, the program
opens the associated 4562 (Depreciation) screen with the For
and Multi-Form Code boxes completed. (See “Associating One
Screen with Another” on page 73.)
Field Flags
Use field flags to set certain fields apart for review. Flagged fields are shaded (default
is green) and must be manually verified (cleared) prior to e-filing.
To flag a field, click the field to activate it, and then press F2. You can also do this by
right-clicking in the field and selecting Flag For Review. The field is displayed with a
shaded background (Figure 3-15).
Figure 3-15: Flagged fields are shaded. (Default is green.)
When a return with flagged fields is calculated, an EF message is generated. It must be
removed (in other words, all flagged fields must be cleared) before the return can be e-
filed.
To clear a flagged field, place the cursor in the field and press F4. To clear all flagged
fields on an open screen, press CTRL+SHIFT+SPACE. To clear all flagged fields in the
open return, go to the Data Entry Menu and press CTRL+SHIFT+SPACE.
Global Flags
A user with administrative rights can designate certain fields to be flagged in all
returns. When flags are set globally, they apply to all returns. Global flags can be for
screens, or for new returns.
• Screens — The presence of an unverified flag produces an EF message only if the
screen exists for the return. For example, if the Employer ID # field on screen C
is flagged, an EF message for the unverified field is produced only if a Schedule C
is present on the return and the Employer ID # field has not been verified. If there
is no Schedule C, no verification is required.
• New Returns — When a field is flagged for all new returns, an unverified flag
produces an EF message whether or not the screen has been opened for the return.
In the above example, an EF message would be created even if no Schedule C was
present in the new return. In effect, this type of global flagging would force the
data entry operator to open screen C, even if only to clear the flag.
70 Tax Year 2012