Individual Account Number

[INDACCOUNTNUMBER] [Integer] [11]

The account number of the Individual in the Andar database if it already exists. If the account does not exist in Andar, leave it blank. Andar will create a new account if the Suspend Account Creation option in the Data Import Validate/Process Options section on the Data Import Validate/Process window is not selected.

The information that appears in this field will be written to the ACCOUNTNUMBER field in the Individuals file and the INDACCOUNTNUMBER field in the Transactions file.

Prefix

[PREFIX] [Character] [15]

This optional field is for a prefix such as Mr., Ms., Mrs., Dr., etc. for an individual.

If the Gender field is blank but a Prefix is present, Andar will determine the Gender from the Prefix based on Andar's Prefixes Table (#670). Default gender is U for Unknown.

If the Prefix field is blank but Gender is M or F, Andar will add Mr. or Ms. as a prefix respectively.

First Name

[FIRSTNAME] [Character] [15]

This required field is for an individual's first name.

Middle Name

[MIDDLENAME] [Character] [15]

This optional field is for an individual's middle name or middle initial.

Last Name

[LASTNAME] [Character] [25]

This required field is for an individual's last name.

Suffix

[SUFFIX] [Character] [20]

This optional field is for a suffix such as Jr., Sr., III, M.D., Ph.D., etc. for an individual.

External Account Number

[INDEXTACCOUNTNUMBER] [Character] [20]

This optional field is for a number assigned to an individual other than the Andar account number. It usually represents the account number from the fundraiser's previous database.

Birth Date

[BIRTHDATE] [Character] [8]

The Birth date of the Individual.

To avoid errors during the Andar Connector Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes). It only accepts full dates in YYYYMMDD.

The information contained in this field will be written to the Account Dates file with the dateType field automatically set to Birthdate and the imported YYYYMMDD string broken up into the dateYear, dateMonth, and dateDay fields.

Gender

[GENDER] [Character] [1]

The gender of the Individual.

To avoid errors during the Andar Connector Import process, make sure that the format of all gender codes on the .CSV file being imported matches the exact format of the Table Entry for each Gender Code (as shown in Table 2). Any field in the Andar Connector Import that requires a Table Entry from an Andar Table is case sensitive.

If the Gender field is blank but a Prefix is present, Andar will determine the Gender from the Prefix based on Andar's Prefixes Table (#670). Default gender is U for Unknown.

If the Prefix field is blank but Gender is M or F, Andar will add Mr. or Ms. as a prefix respectively.

Social Security Number

[SSN] [Integer] [11]

The Social Security Number (the Social Insurance Number in Canada) of the individual.

Account Status

[INDACCOUNTSTATUS] [Character] [15]

The status of the account in Andar, for example, active.

To avoid errors during the Andar Connector Import process, make sure that the format of all Individual Account Status Types on the .CSV file being imported matches the exact format of the Table Entry for each Individual Account Status type (as shown in Table 312). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

Web Site

[INDWEBSITE] [Character] [50]

The Individual account's web address.

Full Name

[FULLNAME] [Character] [100]

Full Name does not have a corresponding field in a profile. It is a "convenience" field that will be parsed into the Prefix, First Name, Middle Name, Last Name, and Suffix fields. A space is used as the separator.

If the name proves to be problematic then the Andar Data Import record will be flagged with an error which can be corrected interactively.

Do Not Merge

[DONOTMERGE] [Character] [1]

To avoid errors during the Andar Data Import process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

This information that appears in this field will be written to the DONOTMERGE field in the Individuals file for that individual.

Organization Account Number

[ORGACCOUNTNUMBER] [Integer] [11]

The account number of the Organization, or "Employer," profile. If the account does not exist in Andar, leave it blank. Andar will create a new account if the Suspend Account Creation option in the Data Import Validate/Process Options section on the Data Import Validate/Process window is not selected.

The information that appears in this field will be written to the ACCOUNTNUMBERA field of the EmployeeRelationships file, and, the ORGACCOUNTNUMBER field in the EnvelopeMaster file if Transaction/Envelope information has been entered.

If a value has been entered into either the Internal Organization Employee Number, or the Internal Organization Department Number field, an account number must be specified in this field in order for an Employment Relationship to be created.

Profile Attribute

[ORGPROFILEATTRIBUTE] [Character] [15]

When an Organization account is created in Andar, it must be assigned a Profile Attribute. The Profile Attribute assigned to an account indicates the type of Organization Account (Action Council, Agency, Campaign, Community Care, Company, Deposit Bank, Federation, Federation for Service Category, Funded Programs, Group Contract, Master, Program, Service Categories, Undesignated, and Vision Council) that serves to differentiate it from other types of Organization accounts. For example, a company named ABC Manufacturing would be an Organization account with the profile attribute of Company while Big Sisters/Big Brothers would have an Organization account with the profile attribute of Agency.

To avoid errors during the Andar Data Import process, make sure that the format of all Profile Attributes on the .CSV file being imported matches the exact format of the Table Entry for each Profile Attribute (as shown in Table 3). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the PROFILEATTRIBUTE field in the Organizations file for that organization.

Name: Line 1

[ORGNAME1] [Character] [40]

The name of the Organization.

The information that appears in this field will be written to the NAME1 field in the Organizations file for that organization.

Name: Line 2

[ORGNAME2] [Character] [40]

The second part of the name of the Organization if required.

Account Status

[ORGACCOUNTSTATUS] [Character] [15]

The status of the Organization account, for example, active.

To avoid errors during the Andar Data Import process, make sure that the format of all Organization Account Status Types on the .CSV file being imported matches the exact format of the Table Entry for each Organization Account Status Type (as shown in Table 311). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the ACCOUNTSTATUS field in the Organizations file for that organization.

SIC

[ORGSIC] [Character] [15]

The Standard Industry Classification code applicable to the selected organization. The Standard Industry Classification (S.I.C.) code identifies the company by industry.

The information that appears in this field will be written to the SIC field in the Organizations file for that organization.

Web Site

[ORGWEBSITE] [Character] [50]

The Organization's web address.

The information that appears in this field will be written to the WEBSITE field in the Organizations file for that organization.

NAICS

[ORGNAICS] [Character] [10]

The Organization's NAICS (North American Industry Classification System.) number. North American Industry Classification System is a federal classification of industry types which gives an average annual salary for the industry. Many Fundraisers use this to calculate potential. The NAICS is similar to the SIC Code, but is more specific.

The information that appears in this field will be written to the NAICS field in the Organizations file for that organization.

NCC

[ORGNCC] [Character] [15]

The NCC number of the Organization.

The information that appears in this field will be written to the NCC field in the Organizations file for that organization.

EIN

[ORGEIN] [Character] [20]

The Employer Identification Number of the Organization.

The information that appears in this field will be written to the EIN field in the Organizations file for that organization.

External Account Number

[ORGEXTACCOUNTNUMBER] [Character] [20]

This optional field is for a number assigned to an organization other than the Andar account number. It usually represents the account number from the fundraiser's previous database.

The information that appears in this field will be written to the EXTACCOUNTNUMBER field in the Organizations file for that organization.

Registration Number

[ORGREGISTRATIONNUMBER] [Character] [15]

The Organization's charitable registration number. The information that appears in this field will be written to the REGISTRATIONNUMBER field in the Organizations file for that organization.

Vendor Number

[ORGVENDORNUMBER] [Character] [15]

Vendor number is a unique identifier, defined in an Organization profile for accounting purposes. The information that appears in this field will be written to the VENDORNUMBER field in the Organizations file for that organization.

Scope

[ORGSCOPE] [Character] [15]

The scope of the charitable organization (Local, National or International). The information that appears in this field will be written to the SCOPE field in the Organizations file for that organization.

For the Scope, use the table entry of the Scope in Table 319 (200 for Local, 100 for National, and 50 for International) instead of the Full Description (Local, National, International).

Internal Employee Number

[INTERNALORGEMPLNUMBER] [Character] [20]

The Employee ID Number.

The information that appears in this field will be written to the EMPLOYEEID field in the EmployeeRelationships file. A value must be specified in the Organization Account Number field when this field is used; an Employment Relationship will be created.

Employee Type

[EMPLOYEETYPE] [Character] [15]

The format of all Employee Types on the .CSV file being imported must match the exact format of the Table Entry of the Employee Type Table (#16) on the CSV file. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

Indicates the kind of employee. For example, Paid Employee, Retiree, etc. This will be used in the Employee Relationship. The information that appears in this field will be written to EMPLOYEETYPE field in the EmployeeRelationships file.

When importing Employee Relationship data without explicitly defining the Relationship Type of that data, Andar Data Import will check for existing active Employee Relationships and do the following:

• If there are no active Employee Relationships of any type with the organization, Andar Data Import will create a PE (Paid Employee) relationship with the data.
• If there is just one active Employee Relationship type with the organization, Andar Data Import will use that relationship type with the data.
• In the case of multiple active Employee Relationship types with the organization, Andar Data Import will issue an error message indicating that an explicit Relationship Type is needed.
  
  Andar Data Import will check if the system preference for Auto. expire employee record at envelope closing if new one will be added on the General tab has been set. When set, and Andar Data Import is processing pledge data that will cause the creation of a new Employee Relationship with a different employer, Andar Data Import will automatically expire ALL active Employee Relationships of that employee before creating the new relationship with a different employer.

Employee Local Checkoff Zip

[EMPDISTZIP] [Character] [10]

The zip code for the Local Check-Off Account on Employee Relationship.

If the donor organization uses the EZS- Both LUW/FUW from Emp Rel Zip Processing Option or the EZSWZF - LUW from Emp Rel Zip/FUW from Org Zip Process Option, be sure to import the zip code at the same time when you import the Employee Relationships via Andar Data Import. Otherwise, you will have to enter the zip code into the Add an Employment Relationship window of each account.

• The EZS- Both LUW/FUW from Emp Rel Zip Process Option will use this zip code to populate the Local Check Off Zip field and the Local Check-Off Account field on a transaction.
• The EZSWZF - LUW from Emp Rel Zip/FUW from Org Zip Process Option will use this zip code to determine the Local Check-Off Account and the company’s Main address zip code to determine the Fundraising Account on a transaction.

Effective Date

[EMPEFFECTIVEDATE] [Character] [8]

The date on which the employee relationship becomes effective.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EMPEFFECTIVEDATE field in the EmployeeRelationships file.

Expiry Date

[EMPEXPIRYDATE] [Character] [8]

The date on which the employee relationship expires.

To avoid errors during the Andar Data process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EMPEXPIRYDATE field in the EmployeeRelationships file.

Job Title 1

[JOBTITLE1] [Character] [40]

Job Title for the Individual. 

The information that appears in this field will be written to the JOBTITLE1 field in the EmployeeRelationships file.

Job Title 2

[JOBTITLE2] [Character] [40]

The second part of the Job Title for the Individual. It is not a second job title.

The information that appears in this field will be written to the JOBTITLE2 field in the EmployeeRelationships file.

Mail Drop

[MAILDROP] [Character] [20]

Indicates a Mail Drop or Routing Code usually associated with a very large organization's internal mail system. This field is for the internal (workplace) mailing address of the Employee. This information is used in Data Mining Extracts to supplement the employer's address when the employer's address is selected by an Address Pecking Order for mailing lists.

The information that appears in this field will be written to the MAILDROP field in the EmployeeRelationships file.

Internal Department Number

[INTERNALORGDEPTNUMBER] [Character] [100]

The name of the Department in which the Employee works.

The information contained in this field will be written to the DEPARTMENT field of the EmployeeRelationships file. A value must be entered into the Organization Account Number field when this field is used; an Employment Relationship will be created.

Sort Field 1-5

[SORTFIELD1] [SORTFIELD2] [SORTFIELD3] [SORTFIELD4] [SORTFIELD5][Character] [45]

The field name is defined on the Add Employee Information Header window under e-Pledge > Administration > Employee Information. For example, one site might want to define Sort Field 1 as Company, Sort Field 2 as Division, and Sort Field 3 as Department.

However, when you import data through Andar Data, you must use the original field name (SORTFIELD1) as import field name in order to be written to the Sort Field 1-5 field in the EmployeeRelationships file.

The information that appears in this field will be written to the SORTFIELD1, SORTFIELD2, SORTFIELD3, SORTFIELD4, SORTFIELD5  fields in the EmployeeRelationships file.

Class A1, A2,

• When an Andar Data Export job is run, the user-defined field name will become a field name in the header row of the resulting CSV file and your selection from the sorting field drop-down list will be listed in this column.
• However, when you import the data in the user-defined fields, you must use the original field name EMPCLASSA1 or EMPCLASSA2.

The information that appears in this field will be written to the EMPCLASSA1 or EMPCLASSA2 field in the EmployeeRelationships file.

Class B1

[EMPCLASSB1] [Character] [45]

A user defined field specific to the fundraiser.

Class B2

[EMPCLASSB2] [Character] [45]

Class B2 may be used in e-Pledge to divide employees of an Organization into smaller groups for web page customization. Class B2 consists of divisions or groups for an Organization account. It is not a separate Andar account.

You might want to define Class B2 as Employee Level, and then add Management, Admin. Staff, and Line Workers as possible values to Class B2. When you go to an Organization profile (and its employees' account profile) > Relationships tab - Employment sub-tab > User Defined tab, the Class B2 field (original field label) will become Employee Level allowing you to select a defined value (Management, Admin. Staff, and Line Workers) to assign to the employee.

However, when you import data into the user-defined fields, you must use the original field name EMPCLASSB2.

Last Year Gift

[EMPLYGIFT] [Decimal] [22]

The previous year's gift from the account.

The information that appears in this field will be written to the EMPLYGIFT field in the EmployeeRelationships file.

Suggested Gift

[EMPSUGGIFT] [Decimal] [22]

The suggested gift amount for the account. The suggested gift amount that a potential donor will see on their e-Pledge screen. For example, if the company plans to raise $10, 000 for the campaign, the company might suggest $500 gift for the Management, $200, for the permanent employees, and $100 for contractors.

The suggested gift amounts can be defined as EMPSUGGIFT, EMPSUGGIFT2, etc.

The information that appears in this field will be written to the EMPSUGGIFT field in the EmployeeRelationships file.

Salary

[EMPSALARY] [Decimal] [22]

Indicates the salary of an individual who is paid a set amount versus hourly wages.

The information that appears in this field will be written to the EMPSALARY field in the EmployeeRelationships file.

Percent Of Salary

[PERCENTOFSALARY] [Decimal] [22]

The percentage of the individual's salary being pledged.

The information that appears in this field will be written to the PERCENTOFSALARY field in the Transactions file.

Per Hour

[EMPPERHOUR] [Decimal] [22]

The amount an individual earns per hour.

The information that appears in this field will be written to the EMPPERHOUR field in the EmployeeRelationships file.

Income Level

[INCOMELEVEL] [Character] [15]

The income level of the employee. Income Levels are user-defined.

Other Income

[EMPOTHERINCOME] [Decimal] [22]

Other income paid to the employee.

The information that appears in this field will be written to the EMPOTHERINCOME field in the EmployeeRelationships file.

Number of Pay Periods

[NBRPAYPERIODS] [Integer] [11]

The number of pay periods per year for the employee. For example, an employee might have 26 pay periods per year.

The information that appears in this field will be written to the NBRPAYPERIODS field in the EmployeeRelationships file.

Minimum Billing Start Date

[MINBILLSTARTDATE] [Character] [8]

If an employee wishes to be billed directly by the fundraiser this will be the date that billing will begin. For example, if they wish to be billed quarterly and this field indicates 01/01/03 they will receive the first bill in January 03 and another each quarter until the pledge has been fully paid.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the MINBILLSTARTDATE field in the EmployeeRelationships file.

Minimum Payroll Start Date

[MINPAYROLLSTARTDATE] [Character] [8]

If an employee wishes to contribute using the payroll deduction option this will be the date those deductions will begin.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the MINPAYROLLSTARTDATE field in the EmployeeRelationships file.

User Defined 1-10

[USERDEFINED1] [USERDEFINED2] [USERDEFINED3] [USERDEFINED4] [USERDEFINED5] [USERDEFINED6] [USERDEFINED7] [USERDEFINED8] [USERDEFINED9] [USERDEFINED10] [Character] [45]

This field is defined by users to record any information about the employees as appropriate.

• When an Andar Data Export job is run, the user-defined field name will become a field name n the header row of the resulting CSV file and your selection from the sorting field drop-down list will be listed in this column.
• However, when you import the data in the user-defined fields, you must use the original field name (USERDEFINED1,USERDEFINED2, and so on).

User Defined Amount 1-10

[USERDEFINEDAMOUNT1] [USERDEFINEDAMOUNT2] [USERDEFINEDAMOUNT3] [USERDEFINEDAMOUNT4] [USERDEFINEDAMOUNT5] [USERDEFINEDAMOUNT6] [USERDEFINEDAMOUNT7] [USERDEFINEDAMOUNT8] [USERDEFINEDAMOUNT9][USERDEFINEDAMOUNT10][Decimal] [22]

This is a user-defined field for storing numerical data.

• When an Andar Data Export job is run, the user-defined field name will become a field name n the header row of the resulting CSV file and your selection from the sorting field drop-down list will be listed in this column.
• However, when you import the data in the user-defined fields, you must use the original field name (USERDEFINEDAMOUNT1, USERDEFINEDAMOUNT2, and so on).

Employee Fundraising Zip

[EMPFUNDRAISINGZIP] [Character] [10]

The zip code for the Fundraising Account on Employee Relationship.

If the Standard M license is NOT enabled, the EMPFUNDRAISINGZIP will be the same as the EMPDISTZIP. In the Andar Data Import csv file, you can leave this field blank or enter the same value as the EMPDISTZIP. If only the EMPDISTZIP is imported, Andar Data Import will automatically populate the EMPDISTZIP with the identical value. If both fields are imported, Andar Data Import will validate the fields and issue an error if the EMPFUNDRAISINGZIP and EMPDISTZIP are not identical.

If the Standard M license is enabled, the EMPFUNDRAISINGZIP can be different from the EMPDISTZIP. In the Andar Data Import csv file, enter both EMPDISTZIP and EMPFUNDRAISINGZIP. If only the EMPDISTZIP is imported, Andar Data Import will automatically populate the EMPDISTZIP with the identical value.

If the donor organization uses the EZS- Both LUW/FUW from Emp Rel Zip Processing Option, be sure to import the Zip Codes at the same time when you import the Employee Relationships via Andar Data Import. Otherwise, you will have to enter these zip codes into the Add an Employment Relationship window of each account. The EZS- Both LUW/FUW from Emp Rel Zip Processing Option will use this zip code to populate the Fundraising Zip field and the Fundraising Account field on a transaction.

The information that appears in this field will be written to the EMPFUNDRAISINGZIP field in the EmployeeRelationships file.

[DATETYPE] [Character] [15]

The Account Dates fields (dateType,dateYear,dateMonth,dateDay)can be used for both partial and full import of the birth date or any other Account Date Types. The information will be written to the dateType,dateYear,dateMonth,dateDay fields in the AccountDates file.

Enter the Date Type for the Date record. To avoid errors during the Andar Data Import  process, make sure that the format of all Date Types on the .CSV file being imported matches the exact format of the Table Entry for each Date Type in Date Types for Individuals Table (# 109) or Date Types for Organizations Table (# 104). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the DATETYPE field in the AccountDates file.

[DATEYEAR] [Integer]

This field is for the Year of the Date record. The value for this field should be formatted as follows: YYYY.

The information that appears in this field will be written to the DATEYEAR field in the AccountDates file.

[DATEMONTH] [Integer]

This field is for the Month of the Date record. The value for this field should be formatted as follows: MM.

The information that appears in this field will be written to the DATEMONTH field in the AccountDates file.

[DATEDAY] [Integer]

This field is for the Day of the Date record. The value for this field should be formatted as follows: DD.

The information that appears in this field will be written to the DATEDAY field in the AccountDates file.

[DATEWEEKNUMBER] [Integer]

This field is for the number of a week in a month. Make sure that the format of the Week Number on the .CSV file being imported matches the exact format of the Table Entry for each Week Number in Table # 112. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the DATEWEEKNUMBER field in the AccountDates file.

[DATESUN] [Character] [1]

If it is Sunday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATESUN field in the AccountDates file.

[DATEMON] [Character] [1]

If it is Monday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATEMON field in the AccountDates file.

[DATETUE] [Character] [1]

If it is Tuesday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATETUE field in the AccountDates file.

[DATEWED] [Character] [1]

If it is Wednesday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATEWED field in the AccountDates file.

[DATETHR] [Character] [1]

If it is Thursday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATETHR field in the AccountDates file.

[DATEFRI] [Character] [1]

If it is Friday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATEFRI field in the AccountDates file.

[DATESAT] [Character] [1]

If it is Saturday, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the DATESAT field in the AccountDates file.

[DATECATEGORY] [Character] [15]

The Date Category field records the frequency of the Date record.

To avoid errors during the Andar Data Import  process, make sure that the format of all Date Categories on the .CSV file being imported matches the exact format of the Table Entry for each Date Category in Table # 111. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the DATECATEGORY field in the AccountDates file.

[DATESPECIFICTIME] [Character] [6]

This field is for the Time of the Date record. Use the 24 hour military time format: hoursminutesseconds (no colons).

For example: 133142

The information that appears in this field will be written to the SPECIFICTIME field in the AccountDates file.

[DATEEFFECTIVEDATE] [Character] [8]

This field is for the Date that the record was created. To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EEFFECTIVEDATE field in the AccountDates file.

[EXPIRYDATE] [Character] [8]

This field is for the Date that the record expires. To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EXPIRYDATE field in the AccountDates file.

[DATEINFOSOURCE] [Character] [15]

Indicate the Information Source.

To avoid errors during the Andar Data Import  process, make sure that the format of all Information Sources on the .CSV file being imported matches the exact format of the Table Entry for each Information Source in Table # 77. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the INFOSOURCE field in the AccountDates file.

[DATECOMMENTTEXT] [Character] [50]

This field is for a short comment regarding the Date record.

The information that appears in this field will be written to the COMMENTTEXT field in the AccountDates file.

Demographic Type

[DEMOGRAPHICTYPE] [Character] [15]

Enter the Demographic Type in this field.

To avoid errors during the Andar Data Import  process, make sure that the format of all Demographic Types on the .CSV file being imported matches the exact format of the Table Entry for each Demographic Type (as shown in Table 6). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

The information that appears in this field will be written to the DEMOGRAPHICTYPE field in the Demographics file.

Effective Date

[DEMOGRAPHICEFFECTIVEDATE] [Character] [8]

This field records the date on which the selected Demographic became applicable to the selected profile.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EFFECTIVEDATE field in the Demographics file.

Expiry Date

[DEMOGRAPHICEXPIRYDATE] [Character] [8]

This field records the end of the validity or duration of the selected Demographic.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the EXPIRYDATE field in the Demographics file.

Numerical Data Type

[NUMERICALDATATYPE] [Character] [15]

Enter the Numerical Data Type in this field.

To avoid errors during the Andar Data Import process, make sure that the format of all Numerical Data Types on the .CSV file being imported matches the exact format of the Table Entry for each Numerical Data Type in Individual Numerical Data Types Table # 4 or Organization Numerical Data Types Table # 20. Any field in the Andar Data Import that requires a Table Entry from an Andar table is case sensitive.

The information that appears in this field will be written to the NUMERICALDATATYPE field in the NumericalInformation file.

Numerical Data

[NUMERICALDATA] [Decimal] [13]

Comment

[numericalDataComment] [Character] [50]

Include any additional information regarding the Numerical Information.

Information Source

[numericalDataInfoSource] [Character] [15]

Indicate the source of the Information.

To avoid errors during the Andar Data Import process, make sure that the format of all Information Sources on the .CSV file being imported matches the exact format of the Table Entry for each Information Source (as shown in Table 77). Any field in the Andar Data Import that requires a Table Entry from an Andar table is case sensitive.

The information that appears in this field will be written to the INFOSOURCE field in the NumericalInformation file.

Override Level

[OVERRIDELEVEL] [Character] [15]

If for any reason your fundraising organization has decided that an Individual is to be considered a Leader of a certain level even if their gift is too low), or is not to be considered a Leader (eve if their gift is high enough), the Individual can be assigned an Override Level.

To avoid errors during the Andar Data Import process, make sure that the format of all Override Levels on the .CSV file being imported matches the exact format of the Table Entry for each Override Level as shown in the Leadership Levels Group Table that has been assigned to the campaign (Leadership Levels Group Tables can be user-defined). Any field in the Andar Data Import that requires a Table Entry from an Andar table is case sensitive.

The information that appears in this field will be written to the OVERRIDELEVEL field in the LSIndiv file.

Campaign Account

[OverrideLevelCampaign] [Integer]

The campaign account that the override leadership level is assigned to.

The information that appears in this field will be written to the CAMPAIGNACCOUNT field in the LSIndiv file.

Campaign Year

[OverrideLevelYear] [Integer]

The campaign year for the override leadership level.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYY.

Other Name Type

[OTHERNAMETYPE] [Character] [15]

In addition to the Account Profile Name that appears on the Bio tab > Main sub-tab of an account profile, Andar can contain additional names for an individual or an organization. For example, Maiden Name, Nickname, Former Name, etc.

To avoid errors during the Andar Data Import process, make sure that the format of all Name Types on the .CSV file being imported matches the exact format of the Table Entry for each Name Type (as shown in Table 5). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

Other Name 1

[OTHERNAME1] [Character] [40]

The first part of the Other Name.

The information that appears in this field will be written to the NAME1 field in the Names file.

Other Name 2

[OTHERNAME2] [Character] [40]

The second part of the Other Name. This is not another Other Name.

The information that appears in this field will be written to the NAME2 field in the Names file.

When updating an Other Name with the Connector, if the current name is contained in both Other Name 1 and Other Name 2 fields, but the import data contains values in the Other Name 1 field and the Other Name 2 field is blank, only Other Name 1 will be updated. A blank field in the import csv file will not blank out the field in Andar.

Other Name Effective Date

[OTHERNAMEEFFECTIVEDATE] [Character] [8]

The date that the Other Name becomes effective in Andar.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

Other Name Expiry Date

[OTHERNAMEEXPIRYDATE] [Character] [8]

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

Address Type

[ADDRESSTYPE] [Character] [15]

Indicates the kind of address. For example, Main Address, Preferred Address, Home Address, Billing Address, etc.

To avoid errors during the Andar Data Import process, make sure that the format of all Address Types on the .CSV file being imported matches the exact format of the Table Entry for each Address Type (as shown in Table 7). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The value entered in this field will determine the Address Type for the address information entered in the Address Line 1, Address Line 2, Address Line 3, and Address Line 4 fields. It will be written to the ADDRESSTYPE field in the Addresses file. If no value is specified in the Address Type field, then any address information entered will be assigned the Main Address Type.

Address Line 1

[ADDRESSLINE1] [Character] [40]

The first line of an address. This should not include a company name or a person's name. At least one of the two address lines (Address line 1 and Address line 2) must be filled when Andar Connector imports an address.

If an Address Type is selected, data must be entered in this field. The information that appears in this field will be written to the ADDRESSLINE1 field in the Addresses file.

If an Address Type is not specified, the default type for the information entered in this and any other Address Line fields will be Main.

Address Line 2

[ADDRESSLINE2] [Character] [40]

Additional address information when there is not enough space in the Address 1 field. At least one of the two address lines (Address line 1 and Address line 2) must be filled when Andar Connector imports an address.

The information that appears in this field will be written to the ADDRESSLINE2 field in the Addresses file.

Address Line 3

[ADDRESSLINE3] [Character] [40]

Additional address information when there is not enough space in the Address 1 and Address  2 fields.

The information that appears in this field will be written to the ADDRESSLINE3 field in the Addresses file.

Address Line 4

[ADDRESSLINE4] [Character] [40]

Additional address information when there is not enough space in the Address 1, Address 2, and Address 3 fields.

The information that appears in this field will be written to the ADDRESSLINE4 field in the Addresses file.

City

[CITY] [Character] [25]

State or Province

[STATEORPROV] [Character] [15]

The name of the State or Province. When Andar Connector imports an address, State or Province is required if the country is USA or Canada.

To avoid errors during Andar Data Import process, make sure that the format of all State or Province Codes on the .CSV file being imported matches the exact format of the Table Entry for each State or Province Code (as shown in Table 8). Any field in the Lockbox Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the STATEORPROV field in the Addresses file.

Zip/Postal Code

[ZIPPOSTALCODE] [Character] [10]

The Zip Code (Postal Code in Canada) for the address.

The combination of city, state, county, and zip code in the ZipCodeCtySt database table and the ZipCodePlusFour database table as well as the settings in the system preferences for Zip Code Management will also have an impact on importing Zip Codes through Andar Connector.

When Andar Connector imports an address, Zip Code cannot be blank if the country is USA or Canada. If the system preference for Validate Zip Codes is turned on, the Zip Code must exist in the ZipCodeCtySt database table or the ZipCodePlusFour database table, with a matching city, state, and county (if County is not blank).

When importing Canadian addresses, spaces and lower case will be allowed for a postal code. It will be converted to the  LNL NLN format (for example, L4D 1E4) when the address record is created.

The information that appears in this field will be written to the ZIPPOSTALCODE field in the Addresses database table.

If you prepare the source file in Excel, in order to retain the leading zeroes (for example, 05043) in this column you should change the formatting for this column from General to Text. To do so, highlight the column and right-click. Then select Format Cells. Click on the Number tab. Select Text from the drop-down list and click OK.

This format change will be retained when the file is saved as a .csv file. You can check the file with Notepad to confirm.

NOTE:

1. If the format of the column is kept as General then the leading zeros will be dropped and Andar will create address records with a four digit zip code (for example, 5043).
2. If the .csv file is re-opened in Excel the formatting will be lost. Once the formatting has been changed to  Text, save the file, close it then import, validate, and process.

In order for the system to validate the zip codes being imported, the zip codes must already exist in the ZipCodeCtySt database table or the ZipCodePlusFour database table. You can import zip codes from a USPS database (either 5- or 9-digit). Then you will have everything you need in Andar for address validation.

If you do not want to import zip codes from USPS database, and the Andar Data Import contains new zip codes, you can use the following workaround to avoid error messages and process the imported data:

With the system preference for Learn Your Zip Codes set ON and Validate Zip Codes set Off, zip codes that are NOT in Andar can be processed through Andar Connector. However, they are not actually "learned" by Andar (they are not put in Zip Code Maintenance) so each time they are used in Andar Connector, they must be "learned" as they will always be considered "new".

With the Learn Your Zip Codes flag on, you must be careful because bad data can be entered and accepted into Andar. You can turn the flag off when you are finished, and turn the Validate Zip Codes flag back on. However, another issue arises when you use this work-around. Because you have addresses in Andar that were not actually "learned", if you try to update that address with the Learn Your Zip Codes flag off, you will not be able to proceed. You will get a message:

The entered Zip Code was not found in the zip code maintenance table matching the entered city or state.

So, if you then turn the Learn Your Zip Codes flag on, you will get this message:

Do you wish to add a new zip, state, county, and city to the database?

If you click Yes, the zip code will be added to Zip Code Maintenance. Leaving both flags off, you will be able to update the address but it will not be validated nor learned.

After processing your Andar Data Import, the new zip codes in Andar are in the Addresses database table only. They have not been learned yet but you can run Rebuild Zip Codes that will add all zip codes from addresses to the ZipCodeCtySt database table and the ZipCodePlusFour database table. That way they can be imported through Andar Connector with the Validate Zip Codes flag on. To do so, go to System Administration  > Rebuilds > Zip Codes > Rebuild Zip Codes, select the radio button for Add Zip Codes from the existing addresses table and click Submit.

If you want to check to see if there are new zip codes each time you import through Andar Connector, you could keep the Validate Zip Codes  flag on when you process the Andar Data Import the first time to generate the zip code error. That way you know how many records have new zip codes. Then you would proceed to turn the Validate Zip Codes flag off to successfully process the Andar Data.

Country

[COUNTRYCODE] [Character] [3]

The Country Code for the address.

To avoid errors during the Andar Data Import process, make sure that the format of all Country Codes on the .CSV file being imported matches the exact format of the Table Entry for each Country Code (as shown in Table 9). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the COUNTRYCODE field in the Addresses file.

Neighborhood

[NEIGHBORHOOD] [Character] [15]

The neighborhood in which an individual lives or an organization is located. For example, Buckhead, Creekside, Downtown, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Neighborhoods on the .CSV file being imported matches the exact format of the Table Entry for each Country Code (as shown in Table 212). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the NEIGHBORHOOD field in the Addresses file.

County

[COUNTY] [Character] [50]

The county in which an individual lives or an organization is located. Validation of Counties only applies to importing through Andar Data Import. When entering via the address panel, if the system preference for Validate Zip Codes is on, then one can only select an associated County with that zip code. In Andar Data Import, it checks to see if the County is associated with this zip code independent of what the city is. If there is no County or it is *Unknown, then it is perfectly valid to have that address without the County name.

To avoid errors during the Andar Data Import  process, make sure that the format of all County Codes on the .CSV file being imported matches the exact format of the Table Entry for each County Code (as shown in Table 211). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the COUNTY field in the Addresses file.

At Subway Line

[ATSUBWAYLINE] [Character] [1]

Indicates the Individual lives near the subway.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the ATSUBWAYLINE field in the Addresses file.

At Bus Line

[ATBUSLINE] [Character] [1]

Indicates the individual lives near the bus route.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the ATBUSLINE field in the Addresses file.

Seasonal From Date

[SEASONALFROMDATE] [Character] [4]

The date that this particular Address Type starts to be the mailing address for the Profile. For example, a Summer Address may only be applicable from May 15 to Oct 1.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: MMDD (no spaces, no slashes).

The information that appears in this field will be written to the FROMDATE field in the Addresses file.

Seasonal To Date

[SEASONALTODATE] [Character] [4]

The date that this particular Address Type ceases to be the mailing address for the Profile. For example, a Summer Address may only be applicable from May 15 to Oct 1.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: MMDD (no spaces, no slashes).

The information that appears in this field will be written to the TODATE field in the Addresses file.

Phone Number Type

[PHONENUMBERTYPE] [Character] [15]

Indicates the kind of phone number. For example, Main Phone, Work Phone, Fax Number, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Phone Number Types on the .CSV file being imported matches the exact format of the Table Entry for each Phone Number Type (as shown in Table 10). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The value entered in this field will determine the Phone Number Type for the phone number information entered in the Area Code, Phone Number, and Extension fields. It will be written to the PHONENUMBERTYPE field in the PhoneNumbers file for the first Phone Number.

Area Code

[AREACODE] [Integer] [11]

The area code of the selected Phone Number Type.

The information that appears in this field will be written to the AREACODE field in the PhoneNumbers file.

Phone Number

[PHONENUMBER] [Integer] [11]

The seven digit telephone number of the selected Phone Number Type.

The information that appears in this field will be written to the PHONENUMBER field in the PhoneNumbers file. Do not include a hyphen after the first three digits in the PHONENUMBER column of the .CSV import file (i.e. format the data as 5551234 instead of 555-1234; Andar will insert the hyphen).

Extension

[EXTENSION] [Integer] [11]

The telephone extension number of the selected Phone Number Type.

The information that appears in this field will be written to the EXTENSION field in the PhoneNumbers file.

2nd Phone Number Type

[PHONENUMBERTYPE2] [Character] [15]

The second Phone Number Type for the Individual. For example, Main Phone, Work Phone, Fax Number, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Phone Number Types on the .CSV file being imported matches the exact format of the Table Entry for each Phone Number Type (as shown in Table 10). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The value entered in this field will determine the Phone Number Type for the phone number information entered in the Area Code, Phone Number, and Extension fields. It will be written to the PHONENUMBERTYPE field in the PhoneNumbers file for the second Phone Number.

2nd Area Code

[AREACODE2] [Integer] [11]

The area code of the second selected Phone Number Type.

The information that appears in this field will be written to the AREACODE field in the PhoneNumbers file.

2nd Phone Number

[PHONENUMBER2] [Integer] [11]

The phone number of the second selected Phone Number Type.

The information that appears in this field will be written to the PHONENUMBER field for the second Phone Type in the PhoneNumbers file.

Do not include a hyphen after the first three digits in the PHONENUMBER column of the .CSV import file (i.e. format the data as 5551234 instead of 555-1234; Andar will insert the hyphen).

2nd Extension

[EXTENSION2] [Integer] [11]

The extension number of the second selected Phone Number Type.

The information that appears in this field will be written to the EXTENSION field for the second Phone Type in the PhoneNumbers file.

e-Mail Type

[EMAILTYPE] [Character] [15]

Indicates the kind of email address. For example, Main Email, Work Email, Home Email, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Electronic Mail Types on the .CSV file being imported matches the exact format of the Table Entry for each Electronic Mail Type (as shown in Table 68). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the EMAILTYPE field in the EMails file for the first e-Mail Address.

e-Mail Address

[EMAILADDRESS] [Character] [70]

The Individual's e-Mail address of the selected e-Mail Type.

The information that appears in this field will be written to the EMAILADDRESS field in the EMails file next to the first e-Mail Address Type.

2nd e-Mail Type

[EMAILTYPE2] [Character] [15]

The second e-Mail address type selected for the individual. For example, Main Email, Work Email, Home Email, etc.

To avoid errors during the Andar Data process, make sure that the format of all Electronic Mail Types on the .CSV file being imported matches the exact format of the Table Entry for each Electronic Mail Type (as shown in Table 68). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

2nd e-Mail Address

[EMAILADDRESS2] [Character] [70]

The Individual's e-Mail address of the second selected e-Mail type.

Make sure that the format of all Billing Schedules matches the exact format of the Table Entry for each Billing Schedule (as shown in Table 62). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the BILLINGSCHEDULECODE field in the BillingSched file.

To avoid errors during the Andar Data Import process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the BILLINGSTARTDATE field in the BillingSched file.

Indicates Andar will not issue statements for the account with this schedule. This rule also applies to pre-authorized payments. Selecting the Pre-Authorized Payment Type will not automatically suppress issuing statements.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the SUPPRESSSTATEMENT field in the BillingSched file.

Specifies the type of pre-authorized payment. The format of all Credit Card Types on the .CSV file being imported must match the exact format of the Table Entry of the Credit Card Type in Table 46 (Payment Type Table). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

NOTE: The Pre-Authorized information must be accompanied by the transaction type and billing schedule code.

Specifies the credit card number when a credit card is selected for a pre-authorized payment type.

The information that appears in this field will be written to the CARDNUMBER field in the BillingSched file.

Specifies the credit card expiry date when a credit card is selected for a pre-authorized payment type. Data in this column must be in MM/YY format.

NOTE: The "/" between the MM and YY is required.

The information that appears in this field will be written to the CARDEXPIRYDATE field in the BillingSched file.

Specifies the card holder's name when a credit card is selected for a pre-authorized payment type.

The information that appears in this field will be written to the NAMEONCARD field in the BillingSched file.

ACH Bank Account Number.

Enter the Bank Transit ABA number in this field.

The information that appears in this field will be written to the ABA field in the BillingSched file.

Enter the ACH Account Type in this field. The format of all ACH Account Types on the .CSV file being imported must match the exact format of the Table Entry of the ACH Account Types in ACH Account Type Table #4901. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the ACHACCOUNTTYPE field in the BillingSched file.

The information that appears in this field will be written to the ACHACCOUNTNAME field in the BillingSched file.

Envelope Number

[ENVELOPENUMBER] [Integer] [11]

Most people do NOT create the envelope in Andar before importing data through Andar Connector. Andar Connector will automatically create Envelopes for the organizations found on the import file.

If the Envelope Type is Workplace, a new envelope will be created for each different organization account on the import file. The general rule is if the table definition in Table # 22 stipulates the Organization account to be Mandatory on the envelope face (meaning there can be only one in the envelope transactions), then a new envelope will always be created for each different organization account in the import file. Currently the only envelope type with this setting is Workplace.

If the Envelope Type is NOT Workplace (for example, A/R Payments), you can decide whether to create a different Envelope for each organization or to keep all transactions from different organizations in the same Envelope.

• There is a system preference on the General tab labeled Break Envelope By Organization On Connector and an option on the Connector submission window labeled Break On Organization that allow you to define when new envelopes are created during an Import Process based on the organization account numbers in the import file.
• The System Preference for Break Envelope By Organization On Connector on the General tab will control the default Connector behavior. It is set to selected. The Break On Organization checkbox on the Connector submission window controls the actual Connector behavior. The Break On Organization checkbox will default to the System Preference for Break Envelope By Organization On Connector.

When Break On Organization is selected, the Connector will create a new envelope for each different organization account found on the import file.

When Break On Organization is not selected, Andar Connector will place all organizations found on the import file in the same envelope.

All other rules relating to envelopes still apply:

• If a maximum number of transactions is set for the envelope a new envelope will still be created when the maximum number of transactions is reached.
• If an organization is entered on the submission screen (the envelope face) all records on the import file must be for the same organization.
• If envelope numbers are used on the import records, the transactions will be added to those envelopes (when valid).

The information that appears in this field will be written to the ENVELOPENUMBER field in the EnvelopeMaster file.

Campaign Account

[CAMPAIGNACCOUNT] [Integer] [11]

The account number of the Campaign to which the gift is to be directed (i.e., Local Campaign, CFC, State, etc.).

The information that appears in this field will be written to the CAMPAIGNACCOUNT field in the EnvelopeMaster file and in the Transactions file.

Envelope Type

[ENVELOPETYPE] [Character] [15]

The type of Envelopes (for example, Workplace Envelope, Accounts Receivable Payment Envelope,) used to process different types of fundraising dollars.

The information that appears in this field will be written to the ENVELOPETYPE field in the EnvelopeMaster file.

Accounting Date

[ACCOUNTINGDATE] [Character] [8]

The date that affects General Ledger. In most cases, this is the date that money is deposited to a bank.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the ACCOUNTINGDATE field in the EnvelopeMaster file and in the Transactions file.

File Number

[FILENUMBER] [Character] [15]

This field is used to attach a user-defined alphanumeric File Number, of up to 15 characters in length, to the Envelope. This File Number provides an alternative to the system-generated Envelope Number; you can use either to search for an Envelope. The File Number in combination with the Campaign Year is a unique identifier; this means that the File Number will be checked, and an error message will be issued, if the same number already exists in the current Campaign Year only. Note that this field supports mixed-case entries; therefore, a file number abc001 will not be considered a duplicate of a file number ABC001.

The information that appears in this field will be written to the FILENUMBER field in the EnvelopeMaster file.

Reference Number

[REFERENCENUMBER] [Character] [15]

This field is used to indicate the account number assigned by an organization to the fundraising organization to which it contributes; it is included for reference purposes only.

The information that appears in this field will be written to the REFERENCENUMBER field in the EnvelopeMaster file.

Campaign Year

[CAMPAIGNYEAR] [Integer] [11]

A Campaign Year is a time period established by a Fundraising Organization. The Campaign Year may not correspond to the current calendar year. A Campaign Year is required to import any pledge information into Andar.

The information that appears in this field will be written to the CAMPAIGNYEAR field in the EnvelopeMaster file and in the Transactions file.

Local Check-Off Account

[MASTERACCOUNT] [Integer] [11]

The Andar account number of the Local Check-Off Account on imported transaction or designation.

Transaction Type

[TRANSACTIONTYPE] [Character] [15]

Indicates the type of gift. (i.e., Employee Payroll, Employee To Be Billed, Individual, etc.).

To avoid errors during the Andar Data Import  process, make sure that the format of all Transaction Types on the .CSV file being imported matches the exact format of the Table Entry for each Transaction Type (as shown in Table 30). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the TRANSACTIONTYPE field in the Transactions file.

#Payroll Deductions

[NUMBEROFDEDUCTIONS] [Integer] [11]

The number of deductions that the donor wishes to make in order to fulfill his pledge. For example, a donor might wish to pay his/her pledge over 3 payroll periods beginning in May. #Payroll Deductions must be less than the for the employee.

The information that appears in this field will be written to the NUMBEROFDEDUCTIONS field in the Transactions file.

Deduction Start Date

[DEDUCTIONSPAYROLLSTARTDATE] [Character] [8]

The start date that the donor wishes to pay his pledge by payroll deduction. For example, a donor might wish to pay his pledge over 3 payroll periods beginning in May.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the DEDUCTIONSPAYROLLSTARTDATE field in the Transactions file.

Batch Transaction

[BATCHTRANSACTIONFLAG] [Character] [1]

Indicates that this transaction is a sum of multiple gifts. For example, a $1,000 pledge from 10 donors for whom you do not have names. This would be a batch transaction.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all Batch Transactions is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the BATCHTRANSACTIONFLAG field in the Transactions file.

Batch Breakdown

[BATCHBREAKDOWNFLAG] [Character] [1]

Indicates this is a Batch Breakdown transaction. Sometimes, to save time, a number of similar Transactions will be totaled and added as a single Batch Transaction. This allows the Envelope to be closed - thus updating all campaign summary records and allowing campaigners to see the progress of the campaign quickly after the receiving an Envelope. Later on, the Transactions that made up the Batch will be added individually; this is called a "Batch Breakdown."

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all Batch Breakdown transactions is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

This is a process flag. The information that appears in this field will not be written to any field in other files.

Number of Donors

[NUMBEROFDONORS] [Integer] [11]

Indicates the number of donors for this transaction. For one gift this number would be 1. For a batch transaction it would typically be more.

The information that appears in this field will be written to the NUMBEROFDONORS field in the Transactions file.

Pledge Amount

[PLEDGEAMOUNT] [Decimal] [22]

The dollar amount of the Pledge.

The information that appears in this field will be written to the TOTALPLEDGEAMOUNT field in the Transactions file.

Payment Amount

[PAYMENTAMOUNT] [Decimal] [22]

The dollar amount of the Payment.

The information that appears in this field will be written to the TOTALPAYMENTAMOUNT field in the Transactions file.

Payment Type

[PAYMENTTYPE] [Character] [15]

Indicates the method of payment. For example, Cash, Check, Visa, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Payment Types on the .CSV file being imported matches the exact format of the Table Entry for each Payment Type (as shown in Table 46). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the PAYMENTTYPE field in the Transactions file.

Check Number

[CHECKNUMBER] [Character] [15]

The number that appears on the actual physical check received from the donor.

The information that appears in this field will be written to the CHECKNUMBER field in the Transactions file.

Check Date

[CHECKDATE] [Character] [8]

The date that appears on the actual physical check received from the donor.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the CHECKDATE field in the Transactions file.

Card Number

[CARDNUMBER] [Character] [50]

The number which appears on the donor's credit card.

The information that appears in this field will be written to the CARDNUMBER field in the Transactions file.

Card Expiry Date

[CARDEXPIRYDATE] [Character] [8]

The date that the donor's credit card expires. Data in this column must be in MM/YY format. NOTE: The "/" between the MM and YY is required.

The information that appears in this field will be written to the CARDEXPIRYDATE field in the Transactions file.

Name On Card

[NAMEONCARD] [Character] [40]

The name which appears on the donor's credit card.

The information that appears in this field will be written to the NAMEONCARD field in the Transactions file.

Authorization Number

[AUTHORIZATIONNUMBER] [Character] [20]

The number supplied by the credit card company approving the payment.

The information that appears in this field will be written to the AUTHORIZATIONNUMBER field in the Transactions file.

ACH Bank Account Number

[ACH] [Character] [50]

ACH Bank account number.

The information that appears in this field will be written to the ACH field in the Transactions file.

Bank Transit ABA

[ABA] [Character] [50]

Bank Transit ABA Number.

The information that appears in this field will be written to the ABA field in the Transactions file.

The ACH Bank Account Type. The format of all ACH Account Types on the .CSV file being imported must match the exact format of the Table Entry of the ACH Account Type in ACH Account Types Table 4901. Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

ACH Settlement Status.

To avoid errors during the Andar Data Import  process, make sure that the format of all ACH Settle Statuses on the .CSV file being imported matches the exact format of the Table Entry for each ACH Settlement Status (as shown in Table 4902). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive.

To indicate that the donor authorized ACH payment over the Internet, enter Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

ACH authorization reference number.

The information that appears in this field will be written to the pnref field in the Transactions file.

Credit Card Status

[CREDITCARDSTATUS] [Character] [15]

The status of the credit card.

The information that appears in this field will be written to the CREDITCARDSTATUS field in the Transactions file.

Credit Card Reference Number

[CREDITCARDREF] [Character] [12]

Reference number of the process to validate the credit card. The information that appears in this field will be written to the CREDITCARDREF field in the Transactions file.

Authorization Result

[CCAUTHRESULT] [Character] [20]

Adjustment Amount

[ADJUSTMENTAMOUNT] [Decimal] [22]

The changes made to the balance of an account (for example, write-offs and/or credit balance adjustments). This is not the amount used to correct pledges and/or payments entered incorrectly, or, to the wrong account.

The information that appears in this field will be written to the TOTALADJUSTMENTAMOUNT field in the Transactions file.

Adjustment Reason

[ADJUSTEMENTREASONTYPE] [Character] [15]

Indicates the reason for the adjustment.

To avoid errors during the Andar Data Import  process, make sure that the format of all Adjustment Reason Types on the .CSV file being imported matches the exact format of the Table Entry for each Adjustment Reason Type (as shown in Table 48). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

The information that appears in this field will be written to the ADJUSTEMENTREASONTYPE field in the Transactions file.

Billing Schedule

[BILLINGSCHEDULECODE] [Character] [15]

Indicates how an individual or an organization wishes to be billed for any balance due. For example, Quarterly, Monthly, Yearly, etc.

To avoid errors during the Andar Data Import  process, make sure that the format of all Billing Schedule Codes on the .CSV file being imported matches the exact format of the Table Entry for each Billing Schedule Code (as shown in Table 62). Any field in the Andar Data Import that requires a Table Entry from an Andar Table is case sensitive. 

NOTE:

The selected Billing Schedule Code for the entered Transaction Type will be checked first against the default Billing Schedule Code for the Transaction Type as defined on the Billing Schedule Tab of the Individual (employee) account. However, it could check the Organization (employer) account default Billing Schedule Code for the Transaction Type if the Billable To field of the Transaction Type in the Transaction Attributes table for the selected Envelope has been set to "Organization." Andar will use the Billing Schedule Code for the Transaction Type set for a specific profile as an override of the global setting, regardless of who is specified as the Billable account. If a Billing Schedule Code for the Transaction Type has not been set on the profile's Billing Schedule Tab, then Andar will check the System Preferences - Billing Schedule Tab for the global default for the Transaction Type. Andar will accept any Billing Schedule Code for a Transaction only if both the profile Billing Schedule Tab and the System Preferences Billing Schedule Tab have no defaults set.

The information that appears in this field will be written to the BILLINGSCHEDULECODE field in the Transactions file.

Billing Start Date

[BILLINGSTARTDATE] [Character] [8]

The date for the first bill. For example, if an individual wants to be billed quarterly and the start date is 01/01/03 a bill will be sent in January and another each quarter until the pledge has been fully paid.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the BILLINGSTARTDATE field in the Transactions file.

Comments

[COMMENTS] [Character] [40]

Free form texts attached to the transaction not to be confused with notes. This Comment will be found only on the transaction screen.

Any information entered into this field will be written to the COMMENTS field of the Transactions file.

Local Check Off Zip

[ORGDISTRIBUTIONZIP] [Character] [10]

Source Code

[SOURCECODE] [Character] [20]

A code used to track pledges resulting from a specific mailing.

Any information entered into this field will be written to the SOURCECODE field of the Transactions file.

Release Name

[RELEASEFLAG] [Character] [1]

Indicates the donor's wish to have their name given to an agency if they designated part or all of their gift to that agency.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records that have given consent for Release is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

If Release Name is Yes and Acknowledgement is Yes, then you need to check at least one of Release Address or Release Email. Release Amount is optional.

The information that appears in this field will be written to the RELEASEFLAG field in the Transactions file.

Publish

[PUBLISHFLAG] [Character] [1]

Indicates the donor's wish to have their name published in any listing or advertisement by the fundraiser.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records that have given consent is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the PUBLISHFLAG field in the Transactions file.

Acknowledgement

[ACKNOWLEDGEMENTFLAG] [Character] [1]

Indicates the donor's wish for an agency to acknowledge their gift if they designated to that agency.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records that have requested an Acknowledgement is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

An Andar Data Import Error will occur if this flag is true and the Release flag is not.

If Release is Yes and Acknowledgement is Yes, then you need to check at least one of Release Address or Release Email. Release Amount is optional.

The information that appears in this field will be written to the ACKNOWLEDGEMENTFLAG field in the Transactions file.

Information Request

[INFORMATIONREQUESTFLAG] [Character] [1]

Indicates the donor's wish for additional information about the fundraiser.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records that have requested information is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the INFORMATIONREQUESTFLAG field in the Transactions file.

Volunteer

[VOLUNTEERFLAG] [Character] [1]

Indicates the donor's wish to be contacted regarding future volunteer opportunities.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records which indicate the presence of interest in Volunteer activities is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the VOLUNTEERFLAG field in the Transactions file.

Perpetual Pledge

[PERPETUALPLEDGEFLAG] [Character] [1]

Indicates the donor's wish to have their gift repeated each year until they change it.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records which indicate a Perpetual Pledge is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the PERPETUALPLEDGEFLAG field in the Transactions file.

Designated

[DESIGNATEDFLAG] [Character] [1]

This flag is used to indicate the presence of Donor Choice designations.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records that contain designations is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The box for this field will contain either a checkmark, or, it will be blank. This value will be written to the DESIGNATEDFLAG field in the Transactions file.

Generate Receipt

[GENRECEIPTFLAG] [Character] [1]

Indicates whether the donor qualifies and/or wishes to receive a receipt (IRS Tax Letter) for their gift.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field for all records for which a Receipt is to be Generated is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the GENRECEIPTFLAG field in the Transactions file.

A check mark in this box will enable Andar to send an e-Mail automatically to the donor to confirm the transaction.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the SENDEMAIL field in the Transactions file.

If this flag is on, the Organization will use Donor Choice Catalogue instead of Donor Choice structure for designations. If it is off, Andar will use the Donor Choice Structure to locate the designated accounts.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the OUTOFAREA field in the Transactions file.

e-Pledge Flag 1-9

[EPLEDGEFLAG1] to [EPLEDGEFLAG9][Character] [1]

e-Pledge flags 1-9 are defined by users using e-Pledge Web Notes. The flags are used to collect Yes/No information from the donors.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False. Use the original flag name in the CSV file, for example, EPLEDGEFLAG1.

New Donor

[NewDonor] [Character] [1]

 Indicating the account is a new donor.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the NewDonor field in the Transactions file.

Receipt Selection Date

[RECEIPTSELECTIONDATE] [Character] [8]

Receipt Selection Date is used when the desired date to be included in the Receipt Submission is something other than the Accounting Date on the Envelope that contains the transaction. If the date is left blank, the Envelope closing process will populate it with the Accounting Date.

For example:

A donor sent in a check dated December 27, 2004. He wanted a tax receipt for 2004. But the check did not reach the fundraiser until January 2005. The payment is entered with an accounting date of January 2005.

To be able to issue a tax receipt for this donor for 2004, you can specify the Receipt Selection Date of this payment to be December 2004.

On the Create Pending Receipts submission panel, you can specify the Date Range to be 01/01/2004 to 12/31/2004 and choose the Date Type of Receipt Selection Date. This payment will be shown on the donor's 2004 tax receipt.

To avoid errors during the Andar Data Import  process, make sure that the value entered in the import file for this field is formatted as follows: YYYYMMDD (no spaces, no slashes).

The information that appears in this field will be written to the RECEIPTSELECTIONDATE field in the Transactions file.

Receipt Amount

[RECEIPTAMOUNT] [Decimal] [22]

The Tax Receipt process will produce Receipts based on the Receiptable Amount. Andar automatically populates the Receiptable Amount on each transaction with the payment amount. If the Receiptable Amount is less than the payment amount, you can enter the amount that will be receipted into this field. The Receiptable Amount can be updated, even after the Envelope is closed.

The information that appears in this field will be written to the RECEIPTAMOUNT field in the Transactions file.

Release Amount

[RELEASEAMOUNT] [Character] [1]

This indicates that the donor consents to have his or her designated amount released by your fundraising organization to the recipient agency when the payment is made.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

If Release Name is Yes and Acknowledgement is Yes, then at least one of Release Address or Release Email should be Yes. Release Amount is optional.

The information that appears in this field will be written to the RELEASEAMOUNT field in the Transactions file.

Release e-Mail

[RELEASEEMAIL] [Character] [1]

This indicates that the donor consents to have his or her e-mail address released by your fundraising organization to the recipient agency when the payment is made.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

If Release Name is Yes and Acknowledgement is Yes, then at least one of Release Address or Release Email should be Yes. Release Amount is optional.

The information that appears in this field will be written to the RELEASEEMAIL field in the Transactions file.

Release Address

[RELEASEADDRESS] [Character] [1]

This indicates that the donor consents to have his or her address released by your fundraising organization to the recipient agency when the payment is made.

To avoid errors during the Andar Data Import  process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

If Release Name is Yes and Acknowledgement is Yes, then at least one of Release Address or Release Email should be Yes. Release Amount is optional.

The information that appears in this field will be written to the RELEASEADDRESS field in the Transactions file.

Event Account

[EVENTACCOUNT] [Integer] [11]

The Andar account number of the Event.

The information that appears in this field will be written to the EVENTACCOUNT field in the Transactions file.

Occurrence

[EVENTOCCURRENCE] [Integer] [11]

Use the Occurrence number found on the Event Account > Occurrence tab > Occurrence column or on the Occurrence tab > Add/Update/Display panels > Occurrence field.

The information that appears in this field will be written to the EVENTOCCURRENCE field in the Transactions file.

Processing Account

[PROCESSINGACCOUNT] [Integer] [11]

The Andar account number of the Processing Account on the imported transaction or designation.

The information that appears in this field will be written to the PROCESSINGACCOUNT field in the Transactions file and the PROCESSINGACCOUNT field in the DCDetails file.

Fundraising Account

[FUNDRAISINGACCOUNT] [Integer] [11]

The Andar account number of the Fundraising Account on the imported transaction or designation.

The information that appears in this field will be written to the FUNDRAISINGACCOUNT field in the Transactions file and the FUNDRAISINGACCOUNT field in the DCDetails file.

Fundraising Zip

[FUNDRAISINGZIP] [Character] [10]

The zip code for the Fundraising Account on the imported transaction. It is used to retrieve the Fundraising Account.

If your site does not have the Standard M license, you should leave this field blank.

The information that appears in this field will be written to the FUNDRAISINGZIP field in the Transactions file.

Solicitor Account

[SOLICITORACCOUNT] [Integer] [11]

The Andar account number of the person who solicits the donors.

The information that appears in this field will be written to the SOLICITORACCOUNT field in the Transactions file.

Book Number 1-12

[BOOKNUMBER1-12] [Character] [20]

The Book Number of the Agency, Program, or Service Category that receives the Designation. If a Book Number is used to identify the recipient of the first designation, then the Designated Account column must be left blank

The information that appears in this field will be written to the BOOKNUMBER field in the DCDetails file.

Designated Account 1-12

[DSGNACCOUNT1-12] [Integer] [11]

The account number of the recipient agency of Designation 1-12. If an Account Number is used to identify the recipient of the first designation, then the Book Number column must be left blank

The information that appears in this field will be written to the DSGNACCOUNT field in the DCDetails file.

Designated Amount 1

[DSGNAMOUNT1-12] [Decimal] [22]

The dollar amount of Designation 1-12. If the Amount field is used to identify the amount of the first designation, then the Designated Percentage 1 field must be left blank.

The information that appears in this field will be written to the DSGNAMOUNT field in the DCDetails file.

Designated Percentage 1-12

[DSGNPERCENTAGE1-12] [Decimal] [22]

Percentage of the total pledge to be designated to Designation agency. 25% is entered as 25. If the Percentage field is used to identify amount of the first designation, then the Designated Amount 1 field must be left blank.

The information that appears in this field will be written to the DSGNPERCENTAGE field in the DCDetails file.

Flags for Designations 1-12

[DCFLAG1_1] to [DCFLAG4_12][Character] [1]

The designation flags are used to collect designation information from the donors. The flags can be used for any purposes. For example, you want a checkmark in Flag 1 of Designation 1 to mean "This designation is for 1 year only."  The flags work like e-Pledge flags but cannot be customized like e-Pledge flags. The flags (Flag 1, 2, 3, 4) can be imported into Andar and changed from the Update Donor Choice window. These flags cannot be data mined and they do not appear on the e-Pledge website or in reports.

Each designation can have up to 4 user-defined flags. The Column Headers will be:

• DCFLAG1_1, DCFLAG2_1, DCFLAG3_1, DCFLAG4_1 for designation 1.
• DCFLAG1_2, DCFLAG2_2, DCFLAG3_2, DCFLAG4_2 for designation 2.
• and so on.

To avoid errors during the Andar Data Import process, make sure that the format of the value in this field is either Yes, Y, True, T, 1, or X. All other values will be treated as No or False.

The information that appears in this field will be written to the same field in the DCDetails file. 

Designation Federation Account 1-12

[DSGNFEDACCT1]to [DSGNFEDACCT12] [Integer] [11]

The Federation Account Number for the Designation.

In the case of book numbers and/or account numbers existing on multiple federations, you should specify the Federation account number in the CSV file using the Short Form Column Names  DSGNFEDACCT1 (or 2, 3, ...) or Long Form Column Names: IndOrg.Transactions.DCDetails[1].federationAccount.

The Connector will validate book numbers, designated account numbers, and federation account numbers, using whatever is provided in the CSV to find a matching Donor Choice structure record.

Where a conflict arises or a unique match can not be determined, the Connector will issue an error. In the Designations section of the Connector Update screen, the federation account number will be displayed and can be edited as well as the book number and designated account number.

In the case of book numbers and/or account numbers existing on multiple federations, pressing the Validate button on the record Update screen will bring up a dialog that will allow the user to choose from amongst the potential matching structure records.

Donor Choice Write-In Amount

[DCWRITEINAMOUNT] [Decimal] [22]

This field is used to indicate the dollar amount of the designation to the Write-In agency.

Donor Choice Write-In Percentage

[DCWRITEINPERCENTAGE] [Decimal] [22]

This field is used to indicate the designation to the Write-In agency and is expressed as a percentage of the Total Pledge.

The information that appears in this field will be written to the DCWRITEINPERCENTAGE field in the DCDetails file.

Donor Choice Write-In Name 1

[DCWRITEINNAME1] [Character] [40]

The name of the Write-In agency.

The information that appears in this field will be written to the NAME1 field in the DCWriteIn file.

Donor Choice Write-In Name 2

[DCWRITEINNAME2] [Character] [40]

Donor Choice Write-In Notes

[DCWRITEINNOTES] [Character] [50]

ExtDocumentFilename1, ExtDocumentRefOnly

ExtDocumentFilename2, ExtDocumentRefOnly