Import Project Expense Types

This feature allows for the importing of Project level Expense Type information into the Unanet system.

Within one expense type import file, an Administrator can import expense type data for one to many projects, across multiple organizations if desired.  The Project Manager version of the import restricts the importing of expense type data to the specific org/project the Project Manager is accessing the project expense type import on.


This screen is available to users having any of the following roles: Administrator, P&R Administrator (and Project Manager has access to a project level version).


This feature is available with any Unanet edition.

Performance Tip Note:  Depending on the number of users in your installation and other factors such as the overall performance of your platform, the activity of importing one or many files may take up to several minutes.  Should this be the case with your installation, you may want to consider running these processes at non-peak times to minimize database contention.


Topics covered on this help page include:

Import File Record Layout



Field Header Name





ALWAYS REQUIRED.  This entry uniquely identifies the expense type being imported.  This value must match an existing Expense Type value defined in your system.  If the Expense Type you are trying to import does not already exist in on the master list of expense types, the entire record will be rejected.

Do note that you are allowed to import expense types that are inactive on the master expense type list.




ALWAYS REQUIRED.  This code uniquely identifies the Organization to which the project belongs.  This value must match an existing Project Organization Code value defined in your system.  If the Organization you are trying to import does not already exist in the database, the entire record will be rejected.




ALWAYS REQUIRED.  This project code identifies the project to which this Project Expense Type belongs.  This value must match an existing Project Code value defined in your system.  If the Project you are trying to import does not already exist in the database,  the entire record will be rejected.




This field is optional and can be used to supply a project specific expense type markup percentage value.   

You can use the special tag !BLANK! to remove an existing entry in this field.

This field accepts a numeric value up to 3 positions to the left of the decimal and 2 positions to the right (-999.99  to  +999.99).  Do not include the % sign within the file.




This field can be used to trigger the system to delete a project expense type entry.

To delete a project expense type, you must include the text string    !DELETE!    in this field.


Note: Check out the Unanet Data model for specific field data types, lengths, and other attributes.

Import File Format

The file to import must be saved in a comma delimited format.   The fields can be enclosed in double quotes -- which would be particularly necessary should the data being imported contain commas.

Importing a Sub-Set of Columns using a Field Header Record

If you are not using the default column layout sequence as defined above, you must include a header record (prefixed with an asterisk *), containing the column Header Names for those columns you are including in the import file (to indicated what data is contained in each column).  The specific Header Names for each column are listed in the table above.



Excel Template

You can create the comma delimited import file with any number of tools.  For those interested in using an Excel spreadsheet to create the file, you can download an Excel Template with predefined headers and required fields noted.  

See the Excel Tips regarding the use of double quotes and more.

Import Screen

The Import Project Expense Types screen simply looks like:

Field Descriptions:



Type of Import

Select the appropriate import type from the list of available types of imports.

File to Import

Enter (or browse for) the file that you would like to import.

Output Options

Specify the level of detail included in the output.  


The import process is triggered by pressing the Import button.  All Warnings and Error messages are written to the screen and can then be saved if desired.  While some line items may be found invalid and rejected, the remaining line items will be successfully imported and saved in the database.  The rejected line items will be written out to a file on the Unanet server as well as displayed at the bottom of the user feedback screen.  The rejected record file name will be UnanetProjectExpenseTypeImportErrorxxx, where xxx is a randomly generated number.  The file will be placed in the Unanet temporary directory (which is defined by the Temp Directory (Fully Qualified Directory Name) (unanet.temp_directory) Unanet property).

Related Topics