| # | Header | Description | Req. | Size | Notes |
| 1 | PrettyName | Recognizable Name of the Expense Code | Y | 28 | Must be unique. Must be first field. Only required field in modification imports. |
| 2 | Description | Full Description of the Expense Code | Y | 60 | Sometimes overloaded with abbreviations or codes for payroll or billing exports. |
| 3 | AutoAdd | Is this Expense Code automatically added to new Groups ? | N | 1 | Must be a capital "Y" for AutoAdd. Capital "N", blank, or any other value is not AutoAdd. |
| 4 | Visibility | Loggable, reportable only, or hidden | N | 4 | The acceptable values are "LR" for Loggable and Reportable, "RO" for Reportable Only, and "hide" for Hidden. |
| 5 | Groups | What Group s should the Expense Code be added to? | N | none | Name of each Group that the Expense Code should be added to. Comma-delimit multiple Groups names in the field. |
Just as in the application itself, hiding a Expense Code will remove it from all Groups. If the Expense Code was previously hidden (defined as not being a member of any Group) and gets set to either "LR" or "RO", then it is added to the All Group only (no other Groups).
The Visibility column is handled before the Groups column. This means that if you set a Expense Code to "hide" and then go ahead and specify some Groups, first it will be hidden, and then it will be added to the specified Groups, which effectively unhides it. (Though it will still show up as "RO" on the Expense Codes screen.) The Import Results screen will say "Expense Code Foo is hidden" and then it will say "Expense Code Foo added to Group Bar".