CSV import: Suppliers

You can now import information into this area of Sage Intacct with the new import service.

Learn more about the available imports.

Import a supplier list by uploading a CSV file.

If you want to add new suppliers to your existing supplier list, you can do so by uploading a CSV file that contains lines for the new suppliers only.

If you plan to pay your suppliers with bank files, your supplier import procedure is different. Learn more.

You must have the following to import Supplier information.

Subscription Accounts Payable
User type Business
Permissions

Suppliers: List, View, Add, Edit

Bank Details permissions required to access the supplier's bank account information for standard ACH.

Download a template

Download a new blank template from the Import pop-up window whenever you import supplier information into Sage Intacct to ensure the following:

  • Templates are automatically customized based on your company configuration, including the 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.
  1. Go to Accounts Payable > All > Suppliers.
  2. Select Import.
  3. Select the Download template link.
  1. Go to Accounts Payable > All > Suppliers.
  2. Select Import.
  3. Select the Download template link.

Prepare a CSV file for import

When you download a template from the import pop-up window or an object list page, 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 that 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.

  1. Download a template from the Import pop-up window 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.
  2. Use the column descriptions as a guide to entering information.
    • 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 Import pop-up window, 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 it is required, has no default value, and allows up to 4 characters. 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 it is not a required field.
    • Enter required information. Some data is required, while other data isn't. Read the description field to determine which information is required. Required information is necessary for your upload to succeed.
  3. 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.

Format dates

When uploading your CSV file, you can select a Date Format for the dates in your file.

Date sequence Date format
Day, month, year
  • DD MM YY
  • DD.MM.YY
  • DD/MM/YY
  • DD-MM-YY
Month, day, year
  • MM DD YY
  • MM.DD.YY
  • MM/DD/YY
  • MM-DD-YY
Year, month, day
  • YY MM DD
  • YY.MM.DD
  • YY/MM/DD
  • YY-MM-DD
Day, month, year
  • DD MM YYYY
  • DD.MM.YYYY
  • DD/MM/YYYY
  • DD-MM-YYYY
Month, day, year
  • MM DD YYYY
  • MM.DD.YYYY
  • MM/DD/YYYY
  • MM-DD-YYYY
Year, month, day
  • YYYY MM DD
  • YYYY.MM.DD
  • YYYY/MM/DD
  • YYYY-MM-DD

When you select a date format here, 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.

Import a supplier 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.

  1. Go to Accounts Payable > All > Suppliers.
  2. Select Import.
  3. Select Choose File and locate the CSV file you want to import.
  4. If your CSV file contains dates, you can set the date format to match the format in the CSV file.
  5. You can allow the system to auto-detect the type of CSV file that you are uploading, or you can select a specific CSV file format, such as Mac OSx, Windows-1252, and more.
  6. If your import file is large, you can choose to 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.

    Intacct recommends selecting 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.
  7. If you want to be notified by email when an offline import is finished or if errors occur in the import process, enter your email address.
    8. Intacct highly recommends always entering your email address in this field.
  8. Select Import.

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.

If your organization uses supplier approval, Sage Intacct automatically submits suppliers you import for approval. While the supplier is pending approval, you can create transactions for the supplier as drafts. After approval, you can post transactions. If you are set up to receive supplier approval notifications, you will be notified when the supplier is approved or declined.

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 the Process offline option on the import utility page.

When the offline process is complete, Intacct sends an email to the address you entered in the Import pop-up window (where you imported your file).

Transactions and other records that are processed offline show a source of System in the audit trail, instead of CSV import.
Intacct recommends selecting 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.

Notes about supplier CSV file fields

When uploading this list, keep the following in mind. The specifics of how to construct the file are defined in more detail in the field definitions section of this help topic.

The maximum number of supplier records you can import in one CSV file is 25,000 records.

  • PARENT_ID refers to a valid Supplier. Child records must be imported after the parent record. Child records that incorrectly reference a parent ID fail to import. For example, if the parent does not exist, or if the parent already references the child as a parent, the import fails.
  • If you include an ACCT_LABEL, an account label is created on the fly when you upload. Because of that, you cannot re-use the ACCT_LABEL already in use by another customer. Furthermore, if you include an ACCT_LABEL, then you must also include a GL_ACCTNO that matches the primary or subaccount in Company > Setup > Configuration, and must also point to valid account.
  • FORM1099TYPE/BOX In the user interface, you find these fields on the Form 1099 Information page by selecting the Form 1099 link for an existing supplier. These fields set the default form type/box for transactions going forward. You may later update this field to other box types for individual existing transactions using the Update Supplier 1099 Transactions upload.
  • NAME1099 supplies the information for the Recipient's Name box on the 1099 form. In the normal user interface, this field is title 1099 Name and is found on the Supplier Information page, Additional Information tab (Accounts Payable > Setup > Suppliers).
    On the 1099 form, the 1099 name is first placed in the "Recipients name" box if the 1099 name exists, and the "print as" name (which is usually a copy of the supplier name) second. The "print as" name is found on the Supplier tab. If the 1099 name does not exist, the "print as" name is used as the only name. You can update the NAME1099 field for multiple suppliers simultaneously with the Update supplier 1099 Transactions upload.
The maximum supplier records you can import in one file is 25000 records.

Required and optional contact fields

Contact Fields Supplier lists have optional sets of Contact Fields for the returnto and/or payto contact. The fields are identical to the required set of primary contact fields, except returnto contact fields have an "R_" prefix and the payto contact fields have a "P_" prefix. If either the returnto and/or payto contact fields are not included, the primary contact information is used instead.

For example, the COMPANY_NAME field when used for the returnto contact would be "R_COMPANY_NAME", and the payto contact would be "P_COMPANY_NAME".

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 Import pop-up window or an object list page, your template contains the headers and dimensions that are specific to your company. The following headers are for a standard template and may not contain some 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 doesn’t appear in the CSV template, but the original Intacct dimension name does.

The following fields on the Supplier Information page are not included in the template : Don't Include On Company's Contact List, GL Group, Payment Priority and Default AP supplier invoice Payment Date. Do not enter this information into the template or your upload will fail.

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: VENDOR_ID

UI Field Name:

Supplier ID

Type:

Character

Length:

20

Default Value:

None, unless supplier sequence auto-numbering is enabled

Valid Values:

Alphanumeric and underscore

Dependencies:

None

Required:

Yes, if supplier sequence auto-numbering is not enabled.

Editable:

No

Notes:

The Supplier ID is provided if you don't provide one, and if supplier sequence auto-numbering is enabled (Company > All > More > Subscriptions > Subscriptions > Accounts Payable > Configure).
Field Name: NAME

UI Field Name:

Supplier Name

Type:

Character

Length:

100

Default Value:

None

Valid Values:

None

Dependencies:

None

Required:

Yes

Editable:

Yes
Field Name: PARENT_ID

UI Field Name:

Parent Supplier Name

Type:

Character

Length:

20

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid supplier

Required:

No

Editable:

Yes
Field Name: TERM_NAME

UI Field Name:

Term

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: VENDTYPE_NAME

UI Field Name:

Supplier Type ID

Type:

Character

Length:

80

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: TAX_ID

UI Field Name:

VAT Reg No

Type:

Character

Length:

20

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: TAXGROUP

UI Field Name:

Contact tax group

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: CREDIT_LIMIT

UI Field Name:

Credit Limit

Type:

Number

Length:

38,2

Default Value:

None

Valid Values:

Any valid amount

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: VENDOR_ACCTNO

UI Field Name:

Supplier account no.

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: ACCT_LABEL

UI Field Name:

Account Label

Type:

Character

Length:

80

Default Value:

None

Valid Values:

Any, however, the account label must be unique for each customer.

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: GL_ACCTNO

UI Field Name:

GL Account

Type:

Character

Length:

24

Default Value:

None

Valid Values:

Must conform to primary/sub account specification in More > Import company data.

Dependencies:

If ACCT_LABEL is specified, a GL_ACCTNO must be included, which also must refer to a valid account number.

Required:

No

Editable:

No
Field Name: BILLING_TYPE

UI Field Name:

Supplier Billing Type

Type:

Character

Length:

1

Default Value:

None

Valid Values:

B = balance forward; O = open item

Dependencies:

None

Required:

Yes

Editable:

Yes

Notes:

Set to Open item (O) to show all AP supplier invoices, adjustments, and payments as line items on a supplier statement.

Set to Balance forward (B) to consolidate previous months AP supplier invoices, adjustments, and payments to a single line item.
Field Name: DISC_ON_CKSTUB

UI Field Name:

Display Term Discount on Cheque Stub

Type:

Character

Length:

5

Default Value:

False

Valid Values:

True or False

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: ONHOLD

UI Field Name:

On Hold

Type:

Character

Length:

5

Default Value:

False

Valid Values:

True or False

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: COMMENTS

UI Field Name:

Comments

Type:

Character

Length:

200

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: FORM1099TYPE

UI Field Name:

Form Name (Found on the Form 1099 Information page by selecting the Form 1099 link for an existing supplier.)

Type:

Character

Length:

N/A

Default Value:

None

Valid Values:

DIV, INT, MISC, R, S

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: FORM1099BOX

UI Field Name:

Default 1099 Box (Found on the Form 1099 Information page by selecting the Form 1099 link for an existing supplier.)

Type:

Character

Length:

1

Default Value:

None

Valid Values:

Positive integers

Dependencies:

Box types vary according to the form type

Required:

No, unless FORM1099TYPE is defined

Editable:

Yes
Field Name: NAME1099

UI Field Name:

1099 Name

Type:

Character

Length:

100

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: CURRENCY

UI Field Name:

Default Currency

Type:

Character

Length:

3

Default Value:

None

Valid Values:

Any ISO three-letter ISO-4127 currency code

Dependencies:

You must previously define the transaction currency via Company > Records: Transaction Currencies.

Required:

No

Editable:

Yes

Notes:

This field applies only to companies that use multiple transaction currencies.

Field Name: VENDOR_ACCTNO

UI Field Name:

Supplier account no.

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Any

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: PAYMENTPRIORITY

UI Field Name:

Payment Priority

Type:

Character

Length:

N/A

Default Value:

Normal

Valid Values:

Urgent, Normal, High, Low

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: HIDEDISPLAYCONTACT

UI Field Name:

Don't include in Company contact list

Type:

Character

Length:

1

Default Value:

F

Valid Values:

T (true) or F (false)

Dependencies:

None

Required:

No

Editable:

Yes
Field Name: ACTIVE

UI Field Name:

Status

Type:

Character

Length:

1

Default Value:

F

Valid Values:

T (true) or F (false)

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

 T = visible in lists; F = not visible in lists, but remains in Intacct for later use.
Field Name: CONTACT_NAME

UI Field Name:

Varies, depending on the type of import. For example, in Employees it is Primary Contact Name. For Customers, there are several (Contact, AP supplier invoice to Contact and Shipto Contact).

This field is required, and its value is typically the same as the value for the NAME field.

Type:

 Character

Length:

 200

Default Value:

 None

Valid Values:

 Must be unique

Dependencies:

 None

Required:

 Yes, if contact is specified.

Editable:

 No

Notes:

If the contact name already exists, you must create the supplier manually in Intacct or enter a new contact name in this file.
Field Name: COMPANY_NAME

UI Field Name:

 Company Name

Type:

 Character

Length:

 100

Default Value:

 Supplier Name

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: MRMS

UI Field Name:

 Prefix

Type:

 Character

Length:

 15

Default Value:

 None

Valid Values:

 Mr., Ms., or Mrs.

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: FIRST_NAME

UI Field Name:

 First Name

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: MI

UI Field Name:

 Middle Name

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: LAST_NAME

UI Field Name:

 Last Name

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: PRINT_AS

UI Field Name:

 Print As

Type:

 Character

Length:

 200

Default Value:

 Supplier Name

Valid Values:

 Any

Dependencies:

 None

Required:

 Yes

Editable:

 Yes
Field Name: TAXABLE

UI Field Name:

 Taxable

Type:

 Checkbox

Default Value:

 True

Valid Values:

 T or F

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: PHONE1

UI Field Name:

 Primary Phone Number

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: PHONE2

UI Field Name:

 Secondary Phone Number

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: CELLPHONE

UI Field Name:

 Mobile phone

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: PAGER

UI Field Name:

 Pager Number

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: FAX

UI Field Name:

 Fax Number

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: EMAIL1

UI Field Name:

 Primary Email Address

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Valid e-mail format

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: EMAIL2

UI Field Name:

 SecondaryEmail Address

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Valid e-mail format

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: URL1

UI Field Name:

 Primary URL

Type:

 Character

Length:

 256

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: URL2

UI Field Name:

 Secondary URL

Type:

 Character

Length:

 256

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: ADDRESS1

UI Field Name:

 Address line 1

Type:

 Character

Length:

 80

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: ADDRESS2

UI Field Name:

 Address line 2

Type:

 Character

Length:

 80

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: CITY

UI Field Name:

 City

Type:

 Character

Length:

 80

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: STATE

UI Field Name:

 State or territory

Type:

 Character

Length:

 40

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: ZIP

UI Field Name:

 Postal code

Type:

 Character

Length:

 30

Default Value:

 None

Valid Values:

 Any

Dependencies:

 None

Required:

 No

Editable:

 Yes
Field Name: COUNTRY

UI Field Name:

 Country

Type:

 Character

Length:

 60

Default Value:

 None

Valid Values:

 Any, see Notes.

Dependencies:

 None

Required:

 No

Editable:

 Yes

Notes:

If you enabled ISO country codes in your Company, it is recommended you use the ISO country code as the value for this column. For more information about enabling ISO country codes, see the General information tab section of Company information
Field Name: LATITUDE

UI Field Name:

 Latitude

Type:

 Character

Length:

 12

Default Value:

 None

Valid Values:

 Decimal number between -90 and 90, with up to 8 decimal places. A positive (+) or negative (-) symbol can proceed the number.

Dependencies:

 None

Required:

 No

Editable:

 Yes

Notes:

 Latitude and longitude coordinates are useful when mailing addresses do not exist. The coordinates are sent as the addresses for AvaTax calculations if your AvaTax integration is configured to use latitude and longitude, you enter values for both latitude and longitude, and the coordinates specify a location within the United States.
Field Name: LONGITUDE

UI Field Name:

 Longitude

Type:

 Character

Length:

 13

Default Value:

 None

Valid Values:

 Decimal number between -180 and 180, with up to 8 decimal places. A positive (+) or negative (-) symbol can proceed the number.

Dependencies:

 None

Required:

 No

Editable:

 Yes

Notes:

 Latitude and longitude coordinates are useful when mailing addresses do not exist. The coordinates are sent as the addresses for AvaTax calculations if your AvaTax integration is configured to use latitude and longitude, you enter values for both latitude and longitude, and the coordinates specify a location within the United States.
Field Name: R_CONTACT_NAME
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_COMPANY_NAME
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_MRMS
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_FIRST_NAME
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_MI
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_LAST_NAME
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_PRINT_AS
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_TAXABLE
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_PHONE1
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_PHONE2
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_CELLPHONE
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_PAGER
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_FAX
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_EMAIL1
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_EMAIL2
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_URL1
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_URL2
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_ADDRESS1
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_ADDRESS2
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_CITY
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_STATE
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_ZIP
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: R_COUNTRY
Notes:

This snippet is used several times in the same topic.The returnto (R- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_CONTACT_NAME
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_COMPANY_NAME
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_MRMS
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_FIRST_NAME
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_MI
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_LAST_NAME
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_PRINT_AS
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_TAXABLE
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_PHONE1
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_PHONE2
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_CELLPHONE
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_PAGER
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_FAX
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_EMAIL1
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_EMAIL2
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_URL1
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_URL2
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_ADDRESS1
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_ADDRESS2
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_CITY
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_STATE
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_ZIP
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: P_COUNTRY
Notes:

This snippet is used several times in the same topic.The payto (P- prefix) contact fields are optional. If they are not included in the upload, the primary contact information is used instead.

For field definition specifics, refer to the corresponding contact field definition.
Field Name: APACCOUNT

UI Field Name:

 AP account

Type:

 Character

Length:

 24

Default Value:

 None

Valid Values:

 Must conform to primary/sub account.

Dependencies:

 Refers to a valid account number and balancing account as payable account.

Required:

 No

Editable:

 Yes
Field Name: MERGE_PAYMENT_REQUESTS

UI Field Name:

 Merge payment requests

Type:

 Character

Default Value:

 true

Valid Values:

 true, false

Required:

 No
Field Name: DEFAULT_LEAD_TIME

UI Field Name:

 Lead time default (days)

Type:

 Number

Default Value:

 None

Valid Values:

 0 or any positive whole number

Dependencies:

 None

Required:

 No

Editable:

 Yes

Notes:

 The value is used as the default value for the lead time in the Supplier entries table in an item record, both at the item level in the Supplier tab and the item/warehouse level in the General tab.
Field Name: BILLAPPROVERID

UI Field Name:

AP supplier invoice approver

Type:

Character

Length:

200

Default Value:

None

Valid values:

A user or user group.

Dependencies:

The Supplier-based approval rule must be present in your AP supplier invoice approval policy.

The user or user group you specify must have Approve AP supplier invoices: List permission and be unrestricted. For a user group, this means that all members of the group must be unrestricted.

Required:

No

Editable:

Yes