Is there an example/template of Job Cost's Import Estimate?

Note: If your import file includes Job,Extra, Cost Code and/or Category custom fields and you are running version 17.1 or above the layout of the import file may need to be modified to include two additional fields that were added to the software in version 17.1 for the Row ID and Row Version.

The field will be populated automatically by the system, but the placeholders for these fields do need to be included in the text file. See article Custom fields are not populating from import file for further information.

The attached template includes the Job record, Cost Code records, and Category records. The first field in each row defines the record type:

* = Job Record (Required)

P = Cost Code record (Optional) The P records are only required if adding new cost codes to the job or when tracking Production Units.

C = Category Record (Required)

For more information about the import estimate record layouts, see the Job Cost Help topic "Import estimates file."

Notes:

If your import file has estimate values for an extra and the extra has not been set up yet, make sure to put the extra record in before the cost code or category record. Otherwise, any information in the extra record (like address or city) is ignored and Job Cost creates the extra without a description.
In order to import category records for multiple extras, make sure that you have the extra record listed before the category record. If the values are for different jobs, then you need to include the job record, then the extra record, then the category record. See the attached topic for an example of an import file with multiple extras.
Each import record has fields which are required for the import file. For example, the Job header record needs an asterisk followed by the job ID (*,07-123,). Refer to the "Import estimates file" Help topic for the required fields for each import record.
Some columns in the import file are a check box type. Use a 1 for a value of checked and use 0 or a blank value for not checked.
When you import files into Job Cost, you may get rejection messages. Multiple rejections may be misleading because one rejection may cause other rejections. Look in either Job Cost Help or the Technical Support Knowledgebase for more information on these errors.
The date format in the import file must match the date format your system uses. For example, in the United States, 05/10/12 represents May 10, 2012, but in Canada 05/10/12 represents October 5, 2012.
Include quotes around any text fields in the import file, if you have a character that might cause a field break such as a comma.

For more information about the import estimate file layout, see the Job Cost Help topic "Import estimates file."