Identifies the Customer assigned to the record, displayed as [CustomerID] - [Customer Name]. This is a single-select lookup that identifies the Customer, displayed as [Customer ID] - [Customer Name]. This default to blank on New. If changed, the details below will be updated to reflect the new Customer. This is editable by editing either the 'Customer ID' or 'Customer Name' from the 'Properties' tab on the Customer Record View.

Database Field: ERPx_ARCustomer.CustomerID + ERPx_ARCustomer.CustomerDescription

Customer IDs are used as a short description and the unique identifier for Customers. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Customer IDs the 3-3-2 method would be recommended. This is a text box that defaults to blank for new records, is required and must be <= 50 characters. If not assigned, the message "Customer Processing Failed: ([CustomerID]): Customer ID is required." will be displayed on Save. This value must be unique across all Customer accounts. If not unique, the message "Customer Processing Failed: ([CustomerID]): Duplicate Customer ID is not allowed." will be displayed on Save. This is always editable, but only in systems that are not integrating Customers with a third-party system. To be editable, the "Customer" 'Transaction Type on both the 'Inbound to NorthScope' and 'Outbound from NorthScope' Integration Modes must be set to "None" on the Integration Configuration page.

Database Field: ERPx_ARCustomer.CustomerID

Customer Names are used as a long description for Customer records.  This is a text box that defaults to blank, is required and must be <=100 characters. If not assigned, the message "Customer Processing Failed: ([CustomerName]): Customer Name is required." will be displayed on Save. This is always editable.

Database Field: ERPx_ARCustomer.CustomerName

The name used on Statements that can be sent out to Customers, Fishers, and/or Vendors. This is a text box that defaults to the Customer Name but is not required. If entered, it must be <=100 characters. This is always editable.

Database Field: ERPx_ARCustomer.StatementName

Customer Class IDs are used as a short description and unique identifier for Customer Class records.  This is a single-select lookup that defaults to blank but is required. If missing, the message "Customer Processing Failed: ([CustomerID]): Customer Class is required." will be displayed on Save. This field is always editable but changing it will not update any of the default customer properties or accounts that are assigned on the new Customer Class. 

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' records in the Customer Class master file.

Database Fields: ERPx_ARCustomerClass.ClassDescription, ERPx_ARCustomer.CustomerClassSK

Attribute Classes are assigned to master files to control which Attributes are visible, and/or required, to records within the master file. This is a single-select lookup that defaults to blank, is not required, and is always editable. Once assigned, the Attributes belonging to the Attribute Class will be visible and editable on the Attributes Tab. This is always editable.

The lookup contains a blank value, the current assigned value, and a list of all the 'Attribute Classes' with an 'Attribute Type' of "Customer Attribute Class". 

Database Field: ERPx_ARCustomer.AttributeClassSK

Checkbooks represent individual bank accounts (checking, savings, petty cash) that have funds deposited into, or payments made out of, that are reconciled to a bank statement. They are used in the Financial, Fisherman Accounting, Grower Accounting, Purchasing, and Sales Functional Areas to support receiving payments from customers, making payments, deposits, and other bank transactions.

This is a single-select lookup to assign the default 'Checkbook' that will be used for Payment Receipts received from the customer.  This default from the Checkbook assigned to the Customer Class but can be edited. This is required and if missing the message "Customer Processing Failed: ([CustomerID]): Checkbook is required." will be displayed on Save.

Database Fields: ERPx_MFCheckbook.CheckbookID, ERPx_ARCustomer.CheckbookSK

The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars. This is a single-select lookup that defaults from the Currency assigned to the 'Customer Class'. This is required and editable until the Customer is assigned to a transaction. If missing, the message "Customer Processing Failed: ([CustomerID]): Currency is required." will be displayed on Save.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Company Currencies.

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_MFDataEntityCompanyCurrency.CurrencySK, ERPx_ARCustomer.CurrencyID

Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts. This is a single-select lookup that defaults from the Payment Terms assigned to the 'Customer Class'. This is required and is always editable. If missing, the message ""Customer Processing Failed: ([CustomerID]): Payment Terms are required." will be displayed on Save.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms.

Database Fields: ERPx_MFPaymentTerms.PaymentTermName, ERPx_ARCustomer.PaymentTermSK

This field is not used.

Database Field: ERPx_ARCustomer.DiscountGracePeriod 

A single select lookup to specify where 'Favorite' items are stored. This defaults from the "Default Item Favorites Level" Sales Preference but can be change to any one of the following values:

• Address: Favorites are auto assigned and managed at the Address level. If set to "Address" the Favorites Tab on the Customer Record View will be disabled and will be enabled on the Address Record View. 
• Customer: Favorites are auto assigned and managed at the Customer level and shared across all the Customer Addresses for the Customer. If set to "Customer" the Favorites Tab on the Address Record View will be disabled and will be enabled on the Customer Record View. 
• None: Favorites will not be auto assigned, nor can they be manually assigned. The Favorites Tab on both the Customer and Customer Address Record Views will be disabled. 

Customer Favorites refer to the items saved on the Customer or Customer Address 'Favorites' tab. These the items that have been assigned because they are frequently purchased. The Customer Favorite Items appear first during Order entry.

Database Field: ERPx_ARCustomer.DueDateGracePeriod

A single select lookup to identify if, and how, Credit Limits are established for the Customer. This defaults from the Customer Class, is required and is always editable. If missing, the message "([CustomerID]): Credit Limit Option is required." will be displayed on Save.

This property works in conjunction with 'Credit Amount' property on this page and with the "When credit limits are exceeded" Sales Preference.  Click /wiki/spaces/HELP/pages/2684911629 for additional information on managing Credit Limits.

The options include:

• No Credit: The Customer does not have any credit and the 'Credit Amount' property is set to 0.00 and will be disabled. 
• Specific Amount: The Customer has a set Credit Limit that will be specified in the 'Credit Amount' property.
• Unlimited Credit: The Customer has unlimited credit (i.e., Credit Limits are not managed for the Customer), and the 'Credit Amount' property is set to 0.00 and will be disabled.   

This lookup contains the values in the ARCreditLimitOption Enumeration Class.

Database Field: ERPx_ARCustomer.CreditLimitOptionEN

A textbox to identify the Credit Amount for the Customer. This defaults from the Customer Class and must be >=0. If missing, it will be set to 0.00 on Save. If a negative amount is entered the message "([CustomerID]): Credit Amount must be greater than or equal to zero." will be displayed on Save.

Database Field: ERPx_ARCustomer.CreditLimitAmount

Identifies the Average Days it takes a customer to pay their invoices. It is calculated by summarizing the total number of days to pay for each applicable invoice and dividing that amount by the number of applicable invoices. This is calculated and never editable.  The value will be recalculated if the Sales "Number of Days for Average Days to Pay" preference value is updated.  

Database Field: ERPx_ARCustomer.AvgDaysToPay

A single select lookup to assign the Tax Class to the customer. This defaults to blank for new records, is not required and is always editable.

Tax Classes are used to calculate sales tax on Quick Sales transactions.

Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions.

Database Fields: ERPx_MFTaxClass.TaxClassSK, ERPx_ARCustomer.TaxClassSK 

This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Tax Class records.

Identifies if the Vendor is "on Hold". If a Vendor is on hold (set to "Yes") then new transactions can be entered for them but payments cannot be issued to them. If set to "No" or blank, the Vendor is not on hold and all transactions can be processed. This is a Yes/No lookup to identify if the Customer account should be placed on hold or not. This defaults to "No" and is always editable.

• If set to 'Yes' then new Quick Sale and Sales Orders cannot be entered for the Customer but Payments Receipts can still be taken.
• If set to 'No' then the record is not on hold and can be freely used.

Database Field: ERPx_ARCustomer.IsOnHold 

A single select lookup to identify the Address where payments from this customer should be sent. This is not required, and always editable.  

Identifies the Address ID that contains the address details that physical payments should be sent for the customer. Remit To Addresses are configured under Company-->Setup-->Addresses.

 Database Field: ERPx_ARCustomer.RemitToAddressSK

Identifies if the record is "Inactive". If inactive (set to "Yes"), it will not be included in look-ups for transactions or other master files. If set to "No" or blank, the record is active and can be freely used.This is a Yes/No lookup to identify if the Customer account is active or not. This defaults to "No" and is always editable.

• If set to 'Yes' then the record is "Inactive" and will not be included in lookups for transactions or other master files.
• If set to 'No' then the record is "Active" and can be freely used. This field is always editable. 

Only Customers with no open transactions/ balances can be set to Inactive, otherwise the message "[Customer Name] ([CustomerID]) has a balance, has unapplied transactions, or is on an open transaction and cannot be saved as Inactive." will be displayed on Save.  

Database Field: ERPx_ARCustomer.IsInactive

Address Line 1 typically contains the primary address information such as the street address. This is a text box to assign/edit the 'Address 1' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=75 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.AddressLine1

Address Line 2 typically contains secondary address information (e.g. floor, suite or mail stop number) related to Address Line 1. This is a text box to assign/edit the 'Address 2' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=75 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.AddressLine2

Address Line 3 is used for additional address information that could not be contained in Address Line 1 or 2. This is a text box to assign/edit the 'Address 3' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=75 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.AddressLine3

Customer Address IDs are used as a short description and unique identifier for Customer Address records. They can be changed at any time to any alphanumeric value. For Customers with only one Address, the default value of PRIMARY can be used. Address IDs of BILLING and SHIPPING are often used for Customers with separate addresses for each. For customers with many Ship-to addresses a City or Street name can be used. This is a text box to assign/edit the value of the Address ID. This defaults to "Primary" and is required to be unique by Customer (For example, every Customer can have an Address ID of 'PRIMARY' but that ID can only be used once for each Customer account) and must be <=25 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.AddressID

The Address Name is used to name an Address ID. This is a text box to assign/edit the value for the Address Name that applies to the Address ID. This defaults from the Customer Name entered on the Properties tab but can be overwritten and must be <=150 characters. This is required and if missing the message "Customer Processing Failed: ([CustomerID]): Address Name is required." will be displayed on Save. This is always editable.

Database Field: ERPx_ARCustomerAddress.AddressName

Customer Address Types are used to classify Customer Address IDs by purpose. The Address Types include:

• Billing - Identifies the single address used for sending invoices. A Customer can only have one Address ID assigned with an Address Type of 'Billing' or 'Both'.
• Shipping - Identifies the address(es) used to ship product. Customers can have many Address ID assigned with an Address Type of Shipping.
• Both - Identifies an address that is used for both Billing and Shipping.  A Customer can only have one Address ID assigned with an Address Type of 'Both'.
• Inactive - Identifies Address IDs that are no longer active.

This lookup contains the values in the AddressType Enumeration Class.

Database Field: ERPx_ARCustomerAddress.AddressTypeEN 

The City identifies the value of 'City' in an address record. This is a text box to assign/edit the 'City' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=35 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.City

The Country identifies the 'Country' of an address record. This is a text box to assign/edit the 'Country' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=50 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.Country

Email is used to record the email address(es) associated with an address. This is a text box to assign/edit the 'email' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=1,000 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.Email

Used to record the fax number associated with an address. This is informational only. This is a text box to assign/edit the 'email' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=25 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.Fax

A single select lookup to identify the default 'Freight Terms' for the Customer Address. This defaults to blank, is not required, and is always editable. If assigned, this will default on new Sales Order transactions (but can be overwritten).

Freight Terms are used to describe the contract terms between the shipper and receiver or product. They can be assigned to Inventory Transfer and Sales Order Shipments. These can print on transaction documents but do not drive an other functionality.

The lookup contains a blank value, the current assigned value, and the list of all 'Active' Freight Terms.

Database Field: ERPx_SOFreightTerms.Name

Used to record the primary phone number associated with an address. This is informational only. This is a text box to assign/edit the 'Phone' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=25 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.Phone1

A single select lookup to identify a default 'Inside Salesperson' for the Customer Address. This defaults to blank, is not required, and is always editable. If assigned, this will default on new Sales Order transactions (but can be overwritten). The lookup contains a blank value, the current assigned value, and the list of all 'Active' Inside Salespersons. 

Inside Salespeople typically work in the office and are involved with sales over the telephone, email, or other cyber communication methods.

Database Field: ERPx_ARCustomerAddress.InsideSalespersonSK

A single select lookup to identify a default 'Outside Salesperson' for the Customer Address. This defaults to blank, is not required, and is always editable. If assigned, this will default on new Sales Order transactions (but can be overwritten). The lookup contains a blank value, the current assigned value, and the list of all 'Active' Outside Salespersons. 

Outside Salespeople typically work outside the office and are involved with face to face meetings with active and prospective customers.

Database Field: ERPx_ARCustomerAddress.SalespersonSK

A single select lookup to identify the default 'Site' for the Customer Address. This defaults to blank, is not required, and is always editable. If assigned, this will default on new Sales Order transactions (but can be overwritten). The lookup contains a blank value, the current assigned value, and the list of all 'Active' Sites.

Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances.

Database Field: ERPx_ARCustomerAddress.SiteSK

The State identifies the value of 'State' in an address record. This is a text box to assign/edit the 'State' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=30 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.State

This field is not currently used, it is managed at the Customer level.

A single select lookup to assign the Tax Class to the Customer Address. This defaults to blank for new records, is not required and is always editable.

Tax Classes are used to calculate sales tax on Quick Sales transactions.

Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions.

Database Field: ERPx_ARCustomerAddress.TaxClassSK 

The Zip identifies the value of 'Zip' (Zip Code) in an address record. This is a text box to assign/edit the 'Zip' value for the Address ID. This defaults to blank and is not required. If entered, it must be <=15 characters. This is always editable.

Database Field: ERPx_ARCustomerAddress.Zip

Used to record the email address(es) associated with a Contact. This is informational only. This is a text box to assign/edit the value for the Contact. This defaults to blank and is not required. If entered, it must be <=1,000 characters. This is always editable.

Database Field: ERPx_ARCustomerContact.Email

Used to record the fax number associated with a Contact. This is informational only. This is a text box to assign/edit the value for the Contact. This defaults to blank and is not required. If entered, it must be <=25 characters. This is always editable.

Database Field: ERPx_ARCustomerContact.Fax

Used to record the name associated with a Contact. This is informational only. This is a text box to assign/edit the value for the Contact. This defaults to blank and is not required. If entered, it must be <=100 characters. This is always editable.

Database Field: ERPx_ARCustomerContact.Name

Used to record the primary phone number associated with a Contact. This is informational only. This is a text box to assign/edit the value for the Contact. This defaults to blank and is not required. If entered, it must be <=25 characters. This is always editable.

Database Field: ERPx_ARCustomerContact.Phone

A text box to identify the Customer Address ID assigned to the Sales Program.

Database Fields: ERPx_ARCustomerAddress.AddressID, ERPx_SPProgramCustomerAddress.CustomerAddressSK, ERPx_SPProgram.ProgramHeaderSK

A textbox to identify the Program Type. Program Types can be as follows:

• Accrual: Accrual programs use Sales Transactions to automate rule-based journal entries that are included with the Sales transaction's Journal Entry and are not visible to the customer. They can be used for rule-based delivered freight, royalties, and other taxes that are paid for by the company.
• Brokerage: Brokerage programs use sales transactions to account for and store the details of an expense that will be paid to a vendor in the future. The expense and accrual entries are included with the Sales transaction's Journal Entry and the details are added to the Broker Balance sub-ledger. When Brokerage programs are 'Settled', AP Invoices are created to debit the accrual account and credit the Vendor's Accounts Payable account. This moves the sub-ledger balance from the Broker to the Vendor.
• Off Book: Off Book programs use Sales Transactions to automate rule-based entries to an Off Book sub-ledger. These balances can be paid (to a customer or vendor) in the future or written off. These programs do not impact the General Ledger when the Sales transaction is posted, and they are not visible to the customer. They only impact the General Ledger when they are Settled. When they are 'Settled', AP Invoices or AR Credit Memos are created to debit the programs assigned 'Expense Account' and credit the Vendor's Accounts Payable or Customer's Accounts Receivable account. This moves the sub-ledger balance from the Broker to the Vendor. These are often used to keep a tally of money that can be used for food shows and other marketing activities. Balances that are written off have no impact on the General Ledger. 
• On Invoice: On Invoice programs automate adding additional line items to Sales Transactions (i.e., Promotional Discounts, Sales Tax, or rule-based Freight charged to a customer). These line items are included with the Sales transaction's Journal Entry and are visible to the customer.
• Rebate: Rebate programs use sales transactions to account for and store the details of an expense that will be paid to a vendor or credited to a customer in the future. The expense and accrual entries are included with the Sales transaction's Journal Entry and the details are added to the Rebate Balance sub-ledger. When Rebate programs are 'Settled', AP Invoices or AR Credit Memos are created to debit the accrual account and credit the Vendor's Accounts Payable or Customer's Accounts Receivable account. This moves the sub-ledger balance from the Rebate to the Vendor/Customer. Open Rebates balances can also be applied to open sales transactions when applying payment receipts.

Database Fields: ERPx_SPProgramClass.ClassName, ERPx_SPProgramCustomerAddress.ProgramHeaderSK

A textbox to identify if the 'Start Date' assigned to the Sales Program.

Database Fields: ERPx_SPProgram.StartDate

This field contains the following account types: 

Accounts Receivable: The GL Account that is assigned for the "Accounts Receivable" Account Type, on the Accounts tab of the Customer Record View and Customer Class Record View. This is the account where accounts receivable amounts are posted for the selected customer.  This Account is not editable on transactions.

Database Field: ERPx_ARCustomer.GLARAccountSK 

Writeoffs:  The GL Account that is assigned for the "Write Off" Account Type, on the Accounts tab of the Customer, Vendor, Fisherman, and Loan Record Views and the Customer Class, Vendor Class, and Fisherman Class Record Views. This is the account where write off amounts entered during Payment Receipt applications are posted to.   This Account is editable when applying payments.

Database Field: ERPx_ARCustomer.WriteOffActSK