CSV import: Order Entry transactions

You can import Order Entry transactions by uploading a CSV file, rather than entering them individually in the Order Entry application.

You cannot import Construction project contract invoices.

Download a template

We recommend downloading a new blank template from either the transaction list page or the Company setup checklist, whenever you import information into Sage Intacct. This is important because:

  • Templates are automatically customized based on your company configuration, including dimensions and custom fields you created.
  • Templates can be updated by Intacct at any time, especially when a new version of Intacct is released. This means that an older template might not work.

If you download from a transaction list page, you don't need any Company permissions.

To download a template from a transactions list page:

Subscription

Order Entry

User type Business, CRM, Warehouse, Employee
Permissions

Order Entry transactions: List, View, Edit, Delete, Add
Restrictions Employee users can only list and view the following types of transactions depending on their permissions:
  • List and View: Transactions with a type of Quote, such as sales quotes
  1. Go to Order Entry > All > Transactions.
  2. Select a transaction type to open a Transaction list page.
  3. Select Import. An Import dialog box opens.
  4. Select the Download template link.

To download a template from the Company setup checklist:

Subscription

Company

User type

Business user with admin privileges
Permissions

Company setup checklist: Run

  1. Go to Company > Setup > Configuration > Import data.

    A list of information that you can import appears.

  2. Decide on a type of information to upload, and select the Template link associated with that information.

Prepare a CSV file for import

When you download a template, the correct headers are in the template already. All you have to do is fill in the columns with your data, save it as a CSV file, and upload the file.

The header titles in the template you download correlate to fields in Intacct. Incorrect header titles will cause an upload error.

For more information about the CSV upload process, including best practices, common errors, and how to upload your CSV file, see Prepare your file for CSV import.

Best practices

The following best practices will help you prepare your CSV file for upload.

Download a template from the Company setup checklist or an object list page.

  • Use the latest template, especially following a product release.
  • Use the correct template for the area in which you want to upload information. Different templates organize different types of information. Use a template specifically for the information that you need to upload.
  • Don’t change the titles in the header row. The header titles correlate to fields in Intacct. Incorrect header titles will cause an upload error. When you download a template from the Company setup checklist, the correct headers are in the template.
  • Read the header descriptions in the template. The header description is the cell under the header row that explains what type of information is accepted for each column. If you enter information in the wrong format, or with an incorrect accepted value, it will cause an error in your upload. The header descriptions in the template show you how the information should look. For example, the header in the GL Journal Entries template for JOURNAL shows that allows up to four characters, is required, and has no default values. The header in the Reporting Periods template shows that the STATUS only allows the values 1 or 2, which correlates to True and False, and is not a required field.
  • Enter required information. Some data is required, while other data is not. Read the description field to determine which information is required. Required information is necessary for your upload to succeed.

Save the file as a comma-separated value, or CSV, file. If saving from Excel, you could choose the comma-delimited file type.

The file will have the file extension .csv after you save it. Leave the file open until your import is successful. Excel can sometimes reformat the file if you close it before the import is successful.

Avoid common import errors

Intacct recommends following these guidelines to avoid import errors.

In Microsoft Excel:

  1. Select all cells.
  2. Right-click the cells and select Format Cells.
  3. On the Number tab, select Text and then select OK.
  4. Save the file.

The short date format is formatted like this: 3/15/2021

In Microsoft Excel:

  1. Select a column of dates.
  2. Right-click the column and select Format Cells.
  3. On the Number tab, select Date and select the short date format.
  4. Save the file.

While spaces within memo fields are allowed, make sure there are no leading or trailing spaces in any field (not just memos). Leading and trainling spaces may cause import errors. For all other fields, remove unnecessary spaces at the start or end of the data.

In Microsoft Excel:

  1. Select a range of cells.
  2. On the Home tab, in the Editing group, select Find & Select and select Replace.
  3. In the Find what box, press the space bar once. Leave the Replace with box blank.
  4. Select Replace All. A prompt opens telling you how many spaces have been removed.
  5. Save the file.

Commas are used to separate fields in CSV files.

To prevent data from shifting into the wrong columns, avoid using commas in numeric and text fields.

If you must include a comma in a text field, always surround the field with double quotes, for example "Smith, John".

Headers in your CSV file must match the template exactly, including spelling, capitalization, and spacing. Even small changes (such as adding a space or changing a letter’s case) will cause the import to fail. Always use the official template provided by Sage Intacct.

ID fields must contain exact references to customers or suppliers.

ID fields must match exactly, including capitalization. For example, ven100 and VEN100 do not match.

Enter the ID exactly as it appears in Intacct or you run the risk of matching transactions to the wrong supplier or customer, or having the upload fail.

If you reference a supplier, customer, term, budget, etc., in a CSV file, whatever you’re referencing must already exist in Intacct.

For example, if you’re uploading transactions for a particular supplier, if the supplier does not already exist as a supplier in Intacct before your upload, your upload will fail.

This does not apply when creating new customers or suppliers using the import process.

For more information about to correctly number line items, see CSV import: Line number examples.

For fields with predefined valid entries (such as True/False), use initial capitalization. For example True, not TRUE or true. IDs require exact case matches, while predefined entries require initial capitalization.

If your import template contains a country field, for example for an address, make sure that this field has an entry.

If your company has enabled ISO country codes, you must specify the country code in the country field for each record. If you are unsure whether ISO codes are enabled, check with your administrator or test a sample import to confirm the required format.

Import a CSV file

Now that you've entered your data and looked through it for any of the common issues imports can have, you’re ready to import your file to Intacct.

To import your CSV file:

  1. Go to Company > Setup > Configuration > Import data.

  2. Find the information type that you want to import, and select the corresponding Import link.

  3. In the Import Company Information dialog, set the following and select Import:

    Import file option descriptions
    Option Description

    Browse

    Use the Browse button to locate and select the CSV file you want to import.

    Date format

    When you select a date format here, Sage Intacct attempts to import your file using the selected date format. If Intacct can’t import your file with the selected date format, it attempts to discover the date format used in your file and import the data using that date format.

    File encoding

    Leave this option set to "auto-detect" unless you're unable to import your file. Depending on your operating system, you may need to select a different type of file encoding.

    Process offline

    Some imports can take considerable time, depending on their size and how much processing the system must do on the uploaded data. If you're not sure how much time your upload will take, select Process offline. When the system completes the process, it sends an email to the address you provide in the Email results to this address field. The system also sends you any errors that may have occurred in the process. If you prefer to wait until the upload process is complete, don’t select the Process offline checkbox.

    Transactions and other records that are processed offline show a source of System in the audit trail, instead of CSV import.

    Email results to this address

    Email address to which import results and errors should be sent. You can enter multiple email addresses, separated by a semicolon (;) or comma (,).

    Sage Intacct highly recommends entering an email address.

After an import, Sage Intacct informs you if the import was successful and how many records were imported.

In a completely successful import, the confirmation page lets you verify all the records in your original file were, in fact, successfully imported without having to verify them manually.

Import offline

Some imports can take considerable time, depending on their size and how much processing Intacct must do to the data. When in doubt, select Process offline on the import utility page.

When the offline process is complete, Intacct sends an email to the address you entered in the Import Company Information dialog (where you imported your file).

Intacct recommends that you select Process offline when importing CSV files, and provide your email address. If your import fails, you’ll always be notified, and the failed records are sent to your email.

Handle errors

If you experience import errors, review the importing tips and common errors.

Import errors occur when you try to import information that doesn’t match the requirements of the template. Each template has a set of required information you must enter to import the file successfully, and formats to follow for certain kinds of information. Read the descriptions in the template to determine the most accurate way to enter your data.

If individual transactions are in error, the rows in the transaction that are in error are saved in a CSV file for you along with an error code for each row. Check your email for information about specific errors. See Find and fix CSV import errors for more information.

For more information about the CSV upload process, read Prepare your file for CSV import.

About importing Order Entry transactions

Number of transactions

If you have more than 500 transactions and the import, either online or offline fails, check the batch frequency for the transaction definitions that are associated with the imported transactions. It's recommended that the Summary frequency on the Documents configuration tab of the Order Entry configuration page be set to Each document when importing a large number of transactions.

Serial numbers

The Order Entry transaction import template contains the options to add serial numbers for items.

If you are importing an item that is serialized, then the serial number columns must be populated, taking the following into consideration:

  • There can only be one unit per Serial Number.
  • To add a serial number, you must use the SERIALNO field.

  • Use COMPONENTID to specify the Item ID of a child of a kit that has a serial number assigned to it.

  • Aisle, row, and bin information is optional in the AISLEID, ROWID, and BINID columns.
  • The expiration date (EXPIRATION) is optional.
  • There can be multiple units per Lot Number (LOTNO).
  • Lot tracking can have multiple units in a given lot. Use the TRACK_QUANTITY column to define the quantity.
    • For example: The total quantity of the line is 10 units, but 6 units are in LOTNO Apple and 4 units are in LOTNO Banana. The 6 and 4 are defined in the TRACK_QUANTITY field.

For more information about importing serial numbers, see CSV import: Serial numbers.

When importing data, names in the FIELD column may differ from terminology used in your location. For information on terms that may differ in your location, see Terminology across locales.

Required fields for importing Order Entry transactions

Some columns of an import template are required fields. If these fields are left blank, your import will fail. Be sure to enter information for all required fields.

  • TRANSACTIONTYPE

  • DATE

  • GLPOSTINGDATE

  • DOCUMENTNO

  • CUSTOMER_ID

  • DATEDUE

  • EXCHRATEDATE - Required unless you provide the EXCHANGE_RATE.

  • STATE

  • LINE

  • WAREHOUSEID - Required if the item type is Inventory or Stockable Kit.

  • QUANTITY

  • UNIT

  • DISCOUNT_MEMO - Required if Track line-item discount or surcharge and Require notes for discounts and surcharges are enabled.

  • REVREC_TEMPLATE

  • SUB_LINE_NO - Required if you have subtotals for your transaction.

  • COMPONENTID - Required when a Kit has a child component that has either serial numbers or lots.

  • TRACK_QUANTITY - Required if Items have lots.

  • SERIALNO - Required if you are importing an Item that is serialized.

  • TAXSOLUTIONID - This field only applies to companies subscribed to the Taxes application.

Field descriptions

The field definitions in your template explain what type of information is required for each field, and how to enter valid information. It's always a good idea to read the field definitions before making entries.

You can reorder the columns of your CSV file for ease of use. However, the column header must contain the field name exactly as it appears in the original template.

If you downloaded a template from the Company Setup Checklist or an object list page, your template contains the headers and dimensions that are specific to your company. The headers in a standard template might not contain field definitions specific to your company.

To import dimension values, enter information in the appropriate dimension column of the import spreadsheet. Otherwise, no information appears for that dimension.

If you relabeled any dimensions (see Terminology for more information), your dimension name does not appear in the CSV template, but the original Intacct dimension name does.

When the preference Enable line-level distribution is enabled, dimension subtotals are not respected. The dimension subtotal is copied to respected distributed subtotals.

When importing data, names in the FIELD column may differ from terminology used in your location. For information on terms that may differ in your location, see Terminology across locales.

Field name: DONOTIMPORT

#

Any row that starts with # is ignored during import.
Field Name: TRANSACTIONTYPE

Field Name:

TYPE

UI Field Name:

Type

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid template name

Required:

Yes

Editable:

No

Note:

The transaction type field refers to the name of the transaction definition template. In this instance, transaction type is the same as transaction definition template name.

You can view a list of transaction definition template names by going to Order Entry > Setup > Transaction definitions.
Field Name: DATE

Field Name:

DATE

UI Field Name:

Date

Type:

Date

Length:

  

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes

Editable:

No
Field Name: GLPOSTINGDATE

Field Name:

GLPOSTINGDATE

UI Field Name:

GL Posting Date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes, if you have enabled override of GL posting date during entry in the Configure Accounts Payable page.

Editable:

Yes
Field Name: DOCUMENTNO

Field Name:

DOCUMENTNO

UI Field Name:

Document Number

Type:

Alphanumeric

Length:

45

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

Yes, if you don't have auto-numbering enabled in your transaction definition

Editable

No
Field Name: CUSTOMER_ID

Field Name:

CUSTOMER_ID

UI Field Name:

Customer

Type:

Alphanumeric

Length:

21

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Should already exist

Required:

Yes

Editable

No
Field Name: TERMNAME

Field Name:

TERMNAME

UI Field Name:

Payment Terms

Type:

Alphanumeric

Length:

40

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Should already exist

Required:

No

Editable:

No
Field Name: DATEDUE

Field Name:

DATEDUE

UI Field Name:

Due Date/Ship Date

Type:

Date

Length:

  

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes

Editable:

No
Field Name: REFERENCENO

Field Name:

REFERENCENO

UI Field Name:

Reference Number

Type:

Alphanumeric

Length:

100

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: CUSTOMERPONUMBER

Field Name:

CUSTOMERPONUMBER

UI Field Name:

Customer PO number

Type:

Alphanumeric

Length:

120

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: MESSAGE

Field Name:

MESSAGE

UI Field Name:

Message

Type:

Alphanumeric

Length:

1000

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

No
Field Name: SHIPPINGMETHOD

Field Name:

SHIPPINGMETHOD

UI Field Name:

Shipping method

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid shipping method

Required:

No

Editable:

Yes
Field Name: BILLTO

UI Field Name:

 AP supplier invoice to

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid AP supplier invoice to.

Required:

No

Editable:

Yes
Field Name: SHIPTO

UI Field Name:

 Ship to

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid Ship to.

Required:

No

Editable:

Yes
Field Name: CURRENCY

Field Name:

CURRENCY

UI Field Name:

Currency

Type:

Character

Length:

3

Default Value:

Base Currency

Valid Values:

Any defined currency, such as USD or EUR. Blank denotes base currency.

Dependencies:

Must reference a previously-defined currency

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. This field defines the transaction currency. If no field is defined here, the base currency is used.
Field Name: BASECURR

Field Name:

BASECURR

UI Field Name:

Base Currency

Type:

Character

Length:

3

Default Value:

None

Valid Values:

Any defined, three-letter ISO-4127 currency code, such as USD or EUR

Dependencies:

Must reference a previously-defined currency. Locations in line items must use the same base currency.

Required:

No, except for shared multi-entity companies with multiple base currencies.

Editable:

No

Notes:

Applies only to shared multi-entity companies with multiple base currencies. This field defines the transaction base currency. Verify that locations in line items use the same base currency.
Field Name: EXCHRATEDATE

Field Name:

EXCHRATEDATE

UI Field Name:

Exchange Rate Date

Type:

Date

Length:

10

Default Value:

Today

Valid Values:

Any valid date format

Dependencies:

None

Required:

Yes, unless you provide the EXCHANGE_RATE

Editable:

Yes

Notes:

Use only in multi-currency companies. This field determines the exchange rate as of this date.
Field Name: EXCHRATETYPE

Field Name:

EXCHRATETYPE

UI Field Name:

Exchange Rate Type

Type:

Character

Length:

40

Default Value:

Intacct Daily Rate is used, unless a custom exchange rate is defined here.

Valid Values:

Alphanumeric and underscore

Dependencies:

Must reference a previously-defined exchange rate type

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. Defines an optional custom exchange rate type. The Intacct Daily Rate is used if one is not defined here.
Field Name: EXCHRATE

Field Name:

EXCHRATE

UI Field Name:

Exchange Rate

Type:

Number

Length:

17, not including decimal point

Default Value:

Defaults to the exchange rate of the CURRENCY on the EXCH_RATE_DATE for the EXCH_RATE_TYPE

Valid Values:

Positive integers

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. Overrides the default exchange rate, which is the product of the CURRENCY, EXCH_RATE_DATE, and EXCH_RATE_TYPE.
Field Name: STATE

Field Name:

STATE

UI Field Name:

Transaction Status

Type:

Character

Length:

  

Default Value:

Draft

Valid Values:

Draft, Post

Dependencies:

None

Required:

Yes

Editable:

Yes
Field Name: NEEDBYDATE

Field Name:

NEEDBYDATE

UI Field Name:

Need by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SHIPBYDATE

Field Name:

SHIPBYDATE

UI Field Name:

Ship by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

Calculated field if NEEDBYDATE is specified and shipping method is available. User can also override value.

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: CANCELAFTERDATE

Field Name:

CANCELAFTERDATE

UI Field Name:

Cancel after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: DONOTSHIPBEFOREDATE

Field Name:

DONOTSHIPBEFOREDATE

UI Field Name:

Do not ship before date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: DONOTSHIPAFTERDATE

Field Name:

DONOTSHIPAFTERDATE

UI Field Name:

Do not ship after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SERVICEDELIVERYDATE

Field Name:

SERVICEDELIVERYDATE

UI Field Name:

Service delivery date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: TRACKINGNUMBER

Field Name:

TRACKINGNUMBER

UI Field Name:

Tracking number

Type:

Alphanumeric

Length:

4000

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Multiple tracking numbers can be entered if they are separated by a comma with no spaces.

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SHIPPED_DATE

Field Name:

SHIPPED_DATE

UI Field Name:

Shipped date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: LINE

Field Name:

LINE

UI Field Name:

  

Type:

Number

Length:

  

Default Value:

None

Valid Values:

Number

Dependencies:

None

Required:

Yes

Editable:

No
Field Name: ITEMID

Field Name:

ITEM_ID

UI Field Name:

Item ID

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid item ID

Required:

Yes

Editable:

Yes
Field Name: ITEMDESC

Field Name:

ITEMDESC

UI Field Name:

Item Description

Type:

Character

Length:

100

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: ITEMALIASID

Field Name:

ITEMALIASID

UI Field Name:

Cross-reference item ID

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid cross-reference item ID

Required:

No

Editable:

Yes
Field Name: WAREHOUSEID

Field Name:

WAREHOUSEID

UI Field Name:

Warehouse

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Must refer to a valid warehouse

Required:

Yes, if the item type is Inventory or Stockable Kit

Editable:

Yes
Field Name: QUANTITY

Field Name:

QUANTITY

UI Field Name:

Quantity

Type:

Numeric

Length:

8

Default Value:

None

Valid Values:

Integer

Dependencies:

None

Required:

Yes

Editable:

Yes
Notes

You can't have a negative quantity if the Item type is set to Inventory, Kit, or Stockable kit.

Kit, however, CAN be negative if Inventory s not subscribed.

Kit cannot be negative if Inventory is subscribed.
Field Name: UNIT

Field Name:

UNIT

UI Field Name:

Unit

Type:

Character

Length:

N/A

Default Value:

Count

Valid Values:

Count, Length, Time, Volume, Weight, etc.

Dependencies:

Valid unit

Required:

Yes

Editable:

Yes
Field Name: LINELEVELSIMPLETAXTYPE

Field Name:

LINELEVELSIMPLETAXTYPE

UI Field Name:

Tax type

Type:

Character

Length:

N/A

Default Value:

First taxable subtotal from the transaction definition

Valid Values:

Alphanumeric and underscore

Dependencies:

Valid tax from transaction definition

Required:

No

Editable:

Yes
Field Name: PRICE

Field Name:

PRICE

UI Field Name:

Price

Type:

Numeric

Length:

10,2

Default Value:

0

Valid Values:

Decimal

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: TAXABLE

Field Name:

TAXABLE

UI Field Name:

Taxable

Type:

Character

Length:

N/A

Default Value:

Derived from ITEM

Valid Values:

T or F (for true or false respectively)

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: DISCOUNT_MEMO

Field Name:

DISCOUNT_MEMO

UI Field Name:

Discount or surcharge notes

Type:

Alphanumeric

Length:

4000

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

Yes, if Track line-item discount or surcharge and Require notes for discounts and surcharges are enabled.

Editable:

Yes
Field Name: REVREC_TEMPLATE

Field Name:

REVREC_TEMPLATE

UI Field Name:

Rev Rec Template

Type:

Alphanumeric

Length:

40

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to an existing template

Required:

Yes, if the line is to be deferred

Editable:

No
Field Name: REVREC_STARTDATE

Field Name:

REVREC_STARTDATE

UI Field Name:

Start Date

Type:

Date

Length:

10

Default Value:

None

Valid Values:

Any valid date format

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: REVREC_ENDDATE

Field Name:

REVREC_ENDDATE

UI Field Name:

End Date

Type:

Date

Length:

10

Default Value:

None

Valid Values:

Any valid date format

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: BILLING_TEMPLATE

Field Name:

BILLING_TEMPLATE

UI Field Name:

Billing template

Type:

Alphanumeric

Length:

30

Default Value:

None

Valid Values:

Any valid date format

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: RENEWAL_MACRO

UI Field Name:

Renewal Macro

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Must refer to a valid renewal macro ID

Required:

No

Editable:

Yes
Field Name: DEPARTMENTID

Field Name:

DEPARTMENTID

UI Field Name:

Department

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

No
Field Name: LOCATIONID

Field Name:

LOCATIONID

UI Field Name:

Location

Type:

Character

Length:

20

Default Value:

None

Valid Values:

An existing valid location

Dependencies:

None, except in shared multi-entity companies with multiple base currencies; the LOCATION_ID must use the same currency as the BASECURR field.

Required:

No

Editable:

Yes, if the transaction is not partially or fully paid, or partially or fully converted.

Notes:

In shared multi-entity companies with multiple base currencies, LOCATION_ID must be in an entity that uses the same base currency as BASECURR.
Field name: SODOCUMENTENTRY_CLASSID

Field Name:

SODOCUMENTENTRY_CLASSID

UI Field Name:

Class

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid class

Required:

No

Editable:

No
Note: Used on the line item.
Field name: SODOCUMENTENTRY_PROJECTID

Field Name:

SODOCUMENTENTRY_PROJECTID

UI Field Name:

Project

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid project

Required:

No

Editable:

No
Note: Used on the line item.
Field Name: SODOCUMENTENTRY_CUSTOMERID

Field Name:

SODOCUMENTENTRY_CUSTOMERID

UI Field Name:

Customer

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid customer

Required:

No

Editable:

No
Note: Used on the line item.
Field Name: SODOCUMENTENTRY_EMPLOYEEID

Field Name:

SODOCUMENTENTRY_EMPLOYEEID

UI Field Name:

Employee

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid employee

Required:

No

Editable:

No
Note: Used on the line item.
Field Name: SODOCUMENTENTRY_VENDORID

Field Name:

SODOCUMENTENTRY_VENDORID

UI Field Name:

Supplier

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid supplier

Required:

No

Editable:

No
Note: Used on the line item.
Field Name: SUB_LINE_NO

Field Name:

SUB_LINE_NO

UI Field Name:

  

Type:

Number

Length:

  

Default Value:

None

Valid Values:

Number

Dependencies:

None

Required:

Yes, if you have subtotals for your transaction

Editable:

Yes
Note:  Usually subtotals are auto-calculated.

Field Name:

 SUBDESC

Field Name:

SUBDESC

UI Field Name:

Description

Type:

Alphanumeric and underscore

Note:

Must match the description available in your subtotals
Field Name: ABSVAL

Field Name:

ABSVAL

UI Field Name:

Transaction Value

Type:

Numeric

Length:

10,2

Default Value:

0

Valid Values:

Decimal

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: PERCENTVAL

Field Name:

PERCENTVAL

UI Field Name:

Percent

Type:

Character
Length:

3.2

Default Value

None

Valid Values:

Numbers

Dependencies:

None

Required:

No

Editable

Yes
Field Name: SUBLOCATIONID

Field Name:

SUBLOCATIONID

UI Field Name:

Location
Type:

Character

Length:

20

Default Value:

None

Valid Values:

An existing valid location

Dependencies:

None, except in shared multi-entity companies with multiple base currencies, the LOCATION_ID must use the same currency as the BASECURR field

Required:

No

Editable:

Yes, if the AP supplier invoice is not partially or fully paid

Notes:

In shared multi-entity companies with multiple base currencies, LOCATION_ID must be in an entity that uses the same base currency as BASECURR
Field name: SUBDEPARTMENTID

Field Name:

SUBDEPARTMENTID

UI Field Name:

Department

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

No
Field name: SODOCUMENTSUBTOTALS_CLASSID

Field Name:

SODOCUMENTSUBTOTALS_CLASSID

UI Field Name:

Class

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid class

Required:

No

Editable:

No
Notes:

Used to designate the Class ID on a sales order.
Field name: SODOCUMENTSUBTOTALS_PROJECTID

Field Name:

SODOCUMENTSUBTOTALS_PROJECTID

UI Field Name:

Project

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid project

Required:

No

Editable:

No
Notes:

Used to designate the Project ID on a sales order.
Field Name: SODOCUMENTSUBTOTALS_CUSTOMERID

Field Name:

SODOCUMENTSUBTOTALS_CUSTOMERID

UI Field Name:

Customer

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid customer

Required:

No

Editable:

No
Notes:

Used to designate the Customer ID on a sales order.
Field Name: SODOCUMENTSUBTOTALS_EMPLOYEEID

Field Name:

SODOCUMENTSUBTOTALS_EMPLOYEEID

UI Field Name:

Employee

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid employee

Required:

No

Editable:

No
Notes:

Used to designate the Employee ID on a sales order.
Field Name: SODOCUMENTSUBTOTALS_VENDORID

Field Name:

SODOCUMENTSUBTOTALS_VENDORID

UI Field Name:

Supplier

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric
Dependencies:

Refers to a valid supplier

Required:

No

Editable:

No
Notes:

Used to designate the Supplier ID on a sales order.
Field Name: MEMO

UI Field Name:

 Memo
Field Name: SODOCUMENTENTRY_TASKKEY

Field Name:

 SODOCUMENTENTRY_TASKKEY
Field Name: PROJECTID

UI Field Name:

 Project

Type:

 Character

Length:

 20
Dependencies: A valid project

Required:

 No
Field Name: ORIGDOCDATE

UI Field Name:

 Original AR sales invoice date

Type:

 Date

Length:

 12

Required:

 No
Field Name: COMPONENTID

Field Name:

 COMPONENTID

Required:

 Yes, when a Kit has a child component that has either serial numbers or lots.
Notes:

Specifies the Item ID of a child of a kit that has a serial number or Lot assigned to it.
Field Name: TRACK_QUANTITY

Field Name:

 TRACK_QUANTITY
Required: Yes, if Items have lots.
Notes:

Lot tracking can have multiple units in a given lot. Use the TRACK_QUANTITY column to define the quantity.

For example: The total quantity of the line is 10 units, but 6 units are in LOTNO Apple and 4 units are in LOTNO Banana. The 6 and 4 are defined in the TRACK_QUANTITY field.
Field Name: SERIALNO

Field Name:

 SERIALNO
Required: Yes, if you are importing an Item that is serialized.
Notes: If you are importing an Item that is serialized, then the serial number columns should be populated. There can only be one unit per Serial Number.
Field Name: AISLEID

Field Name:

 AISLEID
Required: No
Dependencies: Must be part of a valid Warehouse.
Notes: Used to designate an aisle.
Field Name: ROWID

Field Name:

 ROWID
Required: No
Dependencies: Must be part of a valid Warehouse.
Notes: Used to designate a row.
Field Name: BINID

Field Name:

 BINID
Required: No
Dependencies: Must be part of a valid Warehouse.
Notes: Used to designate a bin.
Field Name: LOTNO

Field Name:

 LOTNO
Required: No
Notes: Lot tracking can have multiple units in a given lot. The units are defined as the quantity in TRACK_QUANTITY.
Field Name: SODOCUMENTSUBTOTALS_ITEMID

Field Name:

 SODOCUMENTSUBTOTALS_ITEMID
Required: No
Notes:

Used to designate the Item ID on a sales order.
Field Name: SODOCUMENTENTRY_SHIPTO

Field Name:

 SODOCUMENTENTRY_SHIPTO
UI field name: Ship to contact
Type: Alphanumeric
Required:

No
Dependencies Must be a valid contact.
Field Name: DROPSHIP

Field Name:

 DROPSHIP
UI field name: Drop ship
Type: Character
Default value: F
Valid values: T (true), F (false)
Required: No
Editable: Yes
Dependencies Applicable only if drop ship has been enabled on the Configure Order Entry page and the transaction definition for the transaction has been mapped to a Purchasing transaction definition
Field Name: BUYTOORDER

Field Name:

 BUYTOORDER
UI field name: Buy to order
Type: Character
Default value: F
Valid values: T (true), F (false)
Required: No
Editable: Yes
Dependencies Applicable only if buy to order has been enabled on the Configure Order Entry page and the transaction definition for the transaction has been mapped to a Purchasing transaction definition
Field Name: SODOCUMENTENTRY_BUYTOORDERSHIPTO

Field Name:

 SODOCUMENTENTRY_BUYTOORDERSHIPTO
UI field name: Buy-to-order deliver to
Type: Character
Default value: None
Valid values: Alphanumeric and underscore
Required: No
Editable: No
Dependencies Applicable only if BUYTOORDER is true
Field Name: SODOCUMENTENTRY_NEEDBYDATE

Field Name:

SODOCUMENTENTRY_NEEDBYDATE

UI Field Name:

Need by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SODOCUMENTENTRY_SHIPBY

Field Name:

SODOCUMENTENTRY_SHIPBY

UI Field Name:

Ship by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SODOCUMENTENTRY_DONOTSHIPBEFOREDATE

Field Name:

SODOCUMENTENTRY_DONOTSHIPBEFOREDATE

UI Field Name:

Do not ship before date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SODOCUMENTENTRY_DONOTSHIPAFTERDATE

Field Name:

SODOCUMENTENTRY_DONOTSHIPAFTERDATE

UI Field Name:

Do not ship after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SODOCUMENTENTRY_DATEPICKTICKETPRINTED

Field Name:

SODOCUMENTENTRY_DATEPICKTICKETPRINTED

UI Field Name:

Pick ticket printed date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: SODOCUMENTENTRY_CANCELAFTERDATE

Field Name:

SODOCUMENTENTRY_CANCELAFTERDATE

UI Field Name:

Cancel after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.
Field Name: TAXSOLUTIONID - This field only applies to companies subscribed to the Taxes application.
UI Field Name: Tax solution
Type: Character
Length: 100
Default Value: None
Valid Values: Alphanumeric and underscore
Dependencies: None
Required: Yes, if your organization is configured for multiple tax jurisdictions and you are importing at the top level
Editable: No