<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE smbxml SYSTEM "http://www.netsuite.com/xml/dtd/smb_4_06.dtd">
<!--
smbXML Customer Record Import Example

Before attempting to import any example smbXML documents, NetSuite strongly suggests you read the smbXML Developer's Guide. This guide can be found on the NetSuite Web site at Partners > Developer Program > Technical Documentation. The Developer's Guide explains how to construct smbXML documents.

The Document Type Definition (DTD) defines the format used for smbXML documents imported into your NetSuite account. These documents can contain additions, updates and queries of NetSuite records and transactions. The DTD specifies required fields, field order and XML element and attribute structures. The DTD is your guideline for creating smbXML documents. The current DTD can be found on NetSuite's Web site at Partners > Developer Program > Technical Documentation.

This sample file provides a complete customer record import example, including mandatory and optional customer elements. A customer record import contains several references to objects that must already exist in your NetSuite account. Any objects referenced in this example that are available for import with smbXML are created prior to the example. This is necessary for the import to be successful.

Any referenced objects that cannot be created with smbXML must be created using the NetSuite user interface (UI) prior to importing the example. These situations are noted as they occur and instructions for creating the objects in the UI are included.-->

<!--
NetSuite IPR Software Notice
Copyright (c) 2000-2003 NetSuite, Inc. All Rights Reserved.-->

<smbxml missingFieldOverwrite="false">
	<!--The smbxml element may have multiple request elements.

Setting the missingFieldOverwrite attribute to false tells NetSuite to ignore missing elements on import and not to alter information in fields not included in the imported file. If this attribute is set to true, then any elements not included in your smbXML file will be erased upon import. Setting the missingFieldOverwrite attribute at the smbxml element level applies the setting to the entire import. This attribute can be overridden at the request element level. Detailed information on this attribute is provided in the smbXML Developer's Guide.-->
	<!--Multiple request elements are allowed in a single smbXML document. Each request may only have one add, addOrUpdate or query command. Each command may only have one record.-->
	<request>
		<!--Add an employee to be referenced on the customer record.-->
		<addOrUpdate>
			<!--An addOrUpdate request looks for the existence of an object (in this case, an employee) matching the handle or ID of the object being added. If it finds a match the information is updated for the existing object. If there is no match, a new object is created. We want to make certain the employee record exists in the system prior to referencing it on the customer record. If the employee record does not exist prior to the import of the customer record, the record will fail to import. 

The following example represents a very minimal import for an employee record, but it is enough to allow us to import the customer record below. Employee records may also be created through the UI at Lists > Employees > New. For a complete example of an employee record import, see the smbXML Employee Record Example.-->
			<employee handle="EMP0001">
				<entityId>Tom Barker</entityId>
				<isSalesRep>true</isSalesRep>
			</employee>
		</addOrUpdate>
	</request>
	<!--Add a contact record to be referenced on the customer record. For a complete example of a contact record import, see the smbXML Contact Record Example.-->
	<request>
		<addOrUpdate>
			<contact handle="CONT0001">
				<entityId>Jane Hamill</entityId>
			</contact>
		</addOrUpdate>
	</request>
	<!--Add a second contact record to be referenced on the customer record.-->
	<request>
		<addOrUpdate>
			<contact handle="CONT0002">
				<entityId>Campbell Smith</entityId>
			</contact>
		</addOrUpdate>
	</request>
	<!--Add a vendor record to be referenced on a sales tax item record that is referenced on the customer record. For a complete example of a vendor record import, see the smbXML Vendor Record Example.-->
	<request>
		<addOrUpdate>
			<vendor handle="VEND0001">
				<entityId>CA Department of Revenue</entityId>
			</vendor>
		</addOrUpdate>
	</request>
	<!--Add a sales tax item to be referenced on the customer record. -->
	<request>
		<addOrUpdate>
			<salesTaxItem handle="TAX0001">
				<name>Ocala County</name>
				<taxAgencyHandle handle="VEND0001"/>
			</salesTaxItem>
		</addOrUpdate>
	</request>
	<!--Add a customer category to be referenced on this customer record. 

You can use smbXML to add a customer category. However, an add request is used because customer categories are not currently supported for update. An add request attempts to add an object (in this case, a customer category) without checking first for a duplicate. 

If a customer category already exists in NetSuite with this name, the import will create another customer category with the same name. This causes an error when the category is referenced later in the import because the reference is not a unique name. To prevent this error, you can verify that a customer category does not already exist with this name, or you can create the category through the UI.

To add a customer category with smbXML, enter the following elements:
	<request>
		<add>
			<otherList>
				<type>customer category</type>
				<name>Corporate</name>
			</otherList>
		</add>
	</request> -->
	<!--Add a partner record to be referenced on the customer record. 

Partner records are not available in the NetSuite Advanced Accounting product. If you use this product, do not add this partner record. For all other NetSuite products, partner records are available when the CRM feature is enabled. If you do not use the CRM feature, do not add this partner record. CRM can be enabled at Setup > Enable Features > CRM. For a complete example of a partner record import, see the smbXML Partner Record Example. To add a partner record for reference on your customer record, enter the following elements:
	<request>
		<addOrUpdate>
			<partner handle="PART0001">
				<entityId>Sam's Bait</entityId>
				<partnerCode>SABAIT</partnerCode>
			</partner>
		</addOrUpdate>
	</request> -->
	<!--Add a customer record.-->
	<!--Below is a list of the mandatory and optional references used in a customer record import. This list also includes information about where the objects being referenced may be created.

	Mandatory References:
		-	parenRef			created in the UI or via smbXML  (Parent references are only 												mandatory if the record is a child of another record.)
		-	currencyRef		created in the UI only  (Currency references are only mandatory if you 											use Multi-currencies.)
		
	Optional References:
		-	salesRepRef			created in the UI or via smbXML
		-	contactRef				created in the UI or via smbXML
		-	altContactRef			created in the UI or via smbXML
		-	taxItemRef				created in the UI or via smbXML
		-	categoryRef			created in the UI or via smbXML
		-	termsRef				created in the UI only
		-	priceLevelRef			created in the UI only
		-	territoryRef				created in the UI only
		-	leadSourceRef		created in the UI only
		-	partnerRef				created in the UI or via smbXML
		
Note that for each of these references, where allowed, we have chosen to use handle references. Handle references are more precise and easier to use.-->
	<request>
		<addOrUpdate>
			<!--We use an addOrUpdate command here to indicate that if a customer record already exists for this customer, the information should be updated. If a record does not exist, a new record will be created.-->
			<customer handle="CUST0001">
				<!--The customer element is used to indicate the object you are adding or updating with this request. You can use the handle attribute to create a handle for this record with the customer element. Creating this handle allows you to reference this item in other smbXML documents using handle references.-->
				<entityId>John Doe</entityId>
				<!--The entityId element is your customer's name or ID number. This element is required unless you use auto-generated numbers. This element populates the Customer field on customer records and has a maximum length of 80 characters.-->
				<!--If this customer record is a child of existing customers, you must include a parentRef or parentHandle for each parent record. If any of the parent records were created in the UI, a name reference must be used unless the parent handles can be determined with a query.

To use name references for parent records, enter the following elements:
				<parentRef>
					<parentName>Tammy Doe</parentName>
					<parentName>Janet Doe</parentName>
					<name>Candace Doe</name>
				</parentRef>

The top-level parent record is listed first and each level is listed in descending order. These parent records must exist in NetSuite prior to importing your file and the name references must match the record names identically.

To use handle references, enter the following elements:
<parentHandle handle="CUST0007"/>

This would be the handle for the lowest level parent record. With handle references, you do not have to include each level of the parent hierarchy, only the immediate parent handle.-->
				<companyName>John's Handy Mart</companyName>
				<!--The companyName element is your customer's legal name. This element is not required unless you use Online Bill Pay with this customer. This element populates the Company Name field on customer records and has a maximum length of 83 characters.-->
				<categoryRef>
					<name>Corporate</name>
				</categoryRef>
				<!--The categoryRef element is a reference to a category that already exists in NetSuite. This element is not required and the information populates the Category field on customer records. The category must exist prior to importing your file. This particular category was listed in a comment at the beginning of this example. The category must be added by inserting the smbXML from the comment or creating the category through the UI. To create a new category in the UI, go to Lists > Other Lists > New > Customer Category.-->
				<salesRepHandle handle="EMP0001"/>
				<!--The salesRepHandle element is a handle reference to an employee record that already exists in NetSuite. This particular employee record was created at the beginning of this example file. If you do not know the handle for the employee record being referenced, you can use a name reference.

To use a name reference for the employee above, enter the following elements:
				<salesRepRef>
					<name>Tom Barker</name>
				</salesRepRef> -->
				<contactHandle handle="CONT0001"/>
				<!--The contactHandle element is a handle reference to a contact record that already exists in NetSuite. This particular contact record was created at the beginning of this example file. If you do not know the handle for the contact record being referenced, you can use a name reference.

To use a name reference for the contact above, enter the following elements:
				<contactRef>
					<name>Jane Hamill	</name>
				</contactRef> -->
				<email>jdoe@handymart.com</email>
				<!--The email element is the e-mail address of this customer. This element is not required. The information populates the E-mail field on customer records and this field has a maximum length of 64 characters. The information entered in this field must conform to standard e-mail address format. I.e. name@domain.com -->
				<isEmailPDF>false</isEmailPDF>
				<isEmailHTML>true</isEmailHTML>
				<!--The isEmailPDF and isEmailHTML elements set the value of the E-mail Type field on customer records. This field determines the default e-mail type for this customer. When you send this customer e-mail through NetSuite, this is the e-mail format that is used. When setting the values of these elements, you may only use true or false. If one element is set as true, the other must be set as false or excluded. Setting both elements as true produces an error and your import will fail. If you do not include these elements or set them both to false, the Type field is set to Default and e-mail to this customer is sent in your default format. -->
				<phone>555-555-1111</phone>
				<!--The phone element is the primary telephone number for this customer. This element is not required and the information populates the Phone field on customer records. The Phone field has a maximum length of 21 characters and the information entered in this field must be in one of the following formats:
	- 999-999-9999
	- (999) 999-9999
	- 1-999-999-9999
	- 1 (999) 999-9999
	- 999-999-9999 ext 999 -->
				<fax>555-555-1212</fax>
				<!--The fax element is the fax number for this customer. If you use NetSuite's faxing capabilities, this number is used when faxing transaction through NetSuite. You can set up NetSuite's faxing capabilities at Setup > Set Up Printing, Fax & E-mail. This element is not required and the information populates the Fax field on customer records. The Fax field has a maximum length of 21 characters and the information entered in this field must be in one of the following formats:
	- 999-999-9999
	- (999) 999-9999
	- 1-999-999-9999
	- 1 (999) 999-9999
	- 999-999-9999 ext 999 -->
				<altPhone>555-555-1313</altPhone>
				<!--The altPhone field is a place to enter an additional telephone number for this customer. This element follows the same guidelines as the phone element. -->
				<altContactHandle handle="CONT0002"/>
				<!--The altContactHandle is a place to reference an additional contact record. In this case, this particular contact record was created at the beginning of this example. The altContactHandle element follows the same guidelines as the contactHandle element. -->
				<comments>This is an example of a comment.&#xD;This sentence will be on a new line.</comments>
				<!--The comments element is not required. The information entered populates the Comments field on customer records. The Comments field is a multi-line string with a 999 characters maximum length. You may use the new line string &#xD; to separate lines. -->
				<accountNumber>12345798</accountNumber>
				<!--The accountNumber element is used to enter this customer's account number with your company. This element is not required and the information populates the Account field on customer records. The Account field has a maximum length of 99 characters. -->
				<termsRef>
					<name>Net 15</name>
				</termsRef>
				<!--The termsRef element is a reference to terms that already exists in NetSuite. This element is not required and the information populates the Terms field on customer records. The terms must exist prior to importing your file. Terms are only created through the UI. To create new terms, go to Lists > Other Lists > New > Term. -->
				<creditLimit>15000</creditLimit>
				<!--The creditLimit element is used to record this customers credit limit with your company. This element is not required and the information populates the Credit Limit field on customer records. The information entered in this field must be a currency amount up to 9,999,999,999.99. -->
				<resaleNumber>FG1245</resaleNumber>
				<!--The resaleNumber element is used to record this customer's resale number, if applicable. This element is not required and the information populates the Resale Number field on customer records. The Resale Number field has a maximum length of 15 characters.-->
				<!--If you use Multiple Prices, you can include the priceLevelRef element to reference a price level that already exists in NetSuite. You can enable this feature at Setup > Enable Features > Sales Transactions. This element is not required and the information populates the Price Level field on customer records. The price level must exist prior to importing your file. Price level are only created through the UI. To create new price levels, go to Lists > Other Lists > New > Price Level.

To reference a price level, enter the following elements:
				<priceLevelRef>
					<name>Corporate</name>
				</priceLevelRef> -->
				<!--If you use Multiple Currencies, you can include the currencyRef element to reference a currency that already exists in NetSuite. You can enable this feature at Setup > Enable Features > General. This element is not required and the information populates the Currency field on customer records. The currency record must exist prior to importing your file. 

If you do not set a currency for this customer upon import, the customer's currency defaults to your company's default currency. Once the customer's currency is set, it cannot be changed. Currency records are only created through the UI. To create new currency records, go to Lists > Currencies > New.

To reference a currency record, enter the following elements:
				<currencyRef>
					<name>U.S. dollar</name>
				</currencyRef> -->
				<isTaxable>true</isTaxable>
				<!--The isTaxable element is used to indicate if a customer is charged sales tax. This element is not required and the information populates the Taxable field on customer records. Because this field is a check box and records a true or false value, you must enter either true or false for this element. -->
				<taxItemHandle handle="TAX0001"/>
				<!--The taxItemHandle is a handle reference to a sales tax item that already exists in NetSuite. This element is not required and the information populated the Tax Item field on customer records. This particular sales tax item was created at the beginning of this example. You can also use a name reference for sales tax items.

To use a name reference for this sales tax item, enter the following elements:
				<taxItemRef>
					<name>Ocala County</name>
				</taxItemRef> -->
				<isInactive>false</isInactive>
				<!--The isInactive element is used to indicate if a customer is inactive. This element is not required and the information populates the Customer is Inactive field on customer records. Because this field is a check box and records a true or false value, you must enter either true or false for this element. If you choose to enter true for this element, the customer record is inactive. The record will not appear in lists or be available on transactions. -->
				<!--If you use Sales Force Automation, you can set up and assign statues to your customer records. To enable Sales Force Automation, go to Setup > Enable Features > CRM. Check the Sales Force Automation box and click Save. To include a status for your customers, enter the following element:
				<status>Closed Won</status>
				
The status element is not required and the information populates the Status field on customer records. The information entered for the status element must be a customer status that already exists in NetSuite. Customer statuses can only be created in the UI. To create a new customer status, go to Setup > Customer Statuses > New. -->
				<!-- If you use Sales Force Automation, you can set up sales territories for your customers. Each customer is then assigned to a particular sales territory. To include a sales territory for your customers, enter the following elements:
				<territoryRef>
					<name>Default Round-Robin</name>
				</territoryRef>
				
The territoryRef element is a reference to a sales territory that already exists in NetSuite. This element is not required and the information populates the Territory field on customer records. Sales territories can only be created in the UI and they are based on sales rules. To create new sales rules, go to Setup > Set Up Sales Rules.-->
				<!--If you use Marketing Automation, you can create marketing campaigns and record leads from these campaigns. To enable Marketing Automation, go to Setup > Enable Features > CRM. Check the Marketing Automation box, agree to NetSuite's Terms and click Save. When a lead is generated from a marketing campaign, you can indicate which campaign by choosing a lead source on the customer record. To include a lead source for your customer records, enter the following elements:					<leadSourceRef>
					<name>Ad</name>
				</leadSourceRef>
				
The leadSourceRef element references a lead source, or campaign, that already exists in NetSuite. This element is not required and the information populates the Lead Source field on customer records. Marketing campaigns can only be created in the UI. To create a new marketing campaign, go to Lists > Campaigns > New. -->
				<!--If you use Partner records in NetSuite, you can reference the partner who referred this customer to your business. To use partners, you must have the CRM feature enabled. To enable CRM, go to Setup > Enable Features > CRM. Check the Customer Relationship Management box and click Save. To reference a partner on your customer records, enter the following elements:
				<partnerRef>
					<name>Sam's Bait</name>
				</partnerRef> 
				
The partnerRef element references a partner record that already exists in NetSuite. This particular partner record was created at the beginning of this example. This element is not required and the information populates the Partner field on customer records. When you include a partner on a customer record, that customer can only use promotion codes associated with the partner selected on their record. Partner records can be created with smbXML and in the UI. For a complete smbXML example, see the smbXML Partner Record Example. To create new partner records in the UI, go to Lists > Partners > New. -->
				<startDate>06/03/97</startDate>
				<!--The startDate element is used to record the date this customer first purchased from your company. If you have a contract with this customer, you can also use this element to record the start date of your contract. This element is not required and the information populates the Start Date field on customer records. The date entered for this element must be entered in one of the following formats:
		- MM/DD/YY
		- MM/DD/YYYY

smbXML will only accept one of these two formats. Dates entered in any other format will return an error. If you use another date format in your account, NetSuite will convert the date to be consistent with your chosen format. To choose a date format for your NetSuite account, go to Setup > General Preferences. -->
				<endDate>04/25/10</endDate>
				<!--The endDate element is used to record the end date of any contract you may have with the customer. You may also use endDate to record the last date a purchase was made by an inactive customer. This element is not required and the information populates the End Date field of customer records. The same formatting requirements list above for startDate also apply to the endDate element. -->
				<reminderDays>5</reminderDays>
				<!--The reminderDays element is used to set the number of days before a customer's end date that you want to be reminded of that end date. You can set up the reminder to appear in your Reminders portlet on your home page. To set up reminders, go to Home > Customize Page > Reminders. This element is not required and the information populates the Reminder Days field on customer records. The information entered for this element must be a positive integer no more than ten digits long.-->
				<openingBalance>2500</openingBalance>
				<!--The opendingBalance element is used to record any initial balance this customer has with your company. This element is not required and the information populates the Opening Balance field on customer records. If you choose to enter an opening balance, an open invoice for that amount is created for this customer. The information entered in this field must be a currency amount up to 9,999,999,999.99. -->
				<!--If you use Accounting Periods, you must have an open period for the date entered in the Opening Balance Date field. If you do not have a valid open period, you will receive and error when importing your smbXML file. To include an opening balance date for this customer, enter the following element:		
				<openingBalanceDate>07/25/97</openingBalanceDate>
				
The openingBalanceDate element is used to record the effective date of the balance listed in the Opening Balance field. This element is not required and the information populates the Opening Balance Date field on customer records. The date entered for this element must be entered in one of the following formats:
		- MM/DD/YY
		- MM/DD/YYYY

smbXML will only accept one of these two formats. Dates entered in any other format will return an error. If you use another date format in your account, NetSuite will convert the date to be consistent with your chosen format. To choose a date format for your NetSuite account, go to Setup > General Preferences. -->
				<loginAccess>true</loginAccess>
				<!--The loginAccess element is used to indicate if this customer has access to the Customer Center for your account. This element is not required and the information populates the Give Access field on customer records. Because this field is a check box to record a true or false value, you must enter either true or false for this element. -->
				<sendEmail>false</sendEmail>
				<!--If you choose to give login access to this customer, the sendEmail element is used to notify the customer of their access. This element is not required and the information populates the Send Notification E-mail field on customer records. Because this field is a check box to record a true or false value, you must enter either true or false for this element. If you choose to send notification e-mail, the customer's password is not included in that e-mail. You must notify the customer with their password separately from this e-mail.-->
				<password>jdoe01</password>
				<!--The password element is used to set a login password for this customer. This element is not required and the information populates the Password field of customer records. This element should only be used for customers in which the loginAccess element is true. -->
				<!--If you use the Marketing Automation feature, you can unsubscribe customers from marketing campaigns with smbXML. However, you cannot subscribe customers to marketing campaigns using smbXML. To enable Marketing Automation, go to Setup > Enable Features > CRM. Check the Marketing Automation box, agree to NetSuite's term and click Save. To unsubscribe a customer from marketing campaigns, enter the following elements:
				<unsubscribe>false</unsubscribe>
				
The unsubscribe element should always contain a false entry, otherwise you will receive an error when importing your smbXML file. -->
				<addressList>
					<!--The addressList element is used to indicate to NetSuite that you are beginning a list of addresses for this customer record. In NetSuite, it is possible to enter multiple addresses for a single customer record. This element is only required if you are including addresses in your import. -->
					<addressLine>
						<!--The addressLine element is used to indicate to NetSuite that you are beginning a line in your address list. This element should be placed before each individual address. This element is only required if you are including addresses in your import. -->
						<addressName>Work</addressName>
						<!--The addressName element is used to name this particular address. This is the name that appears in the address select field on transactions. This element is not required and the information populates the Label field on customer records. The maximum length for this field is 50 characters. -->
						<attention>J. Doe</attention>
						<!--The attention element is used to add a specific person's name to this address. This element is not required and the information populates the Attention column of the address list on customer records. The maximum length for this field is 50 characters. -->
						<addressee>John's Handy Mart</addressee>
						<!--The addressee element is used to add the name of this customer or business. This element is not required and the information populates the Addressee column of the address list on customer records. The maximum length for this field is 50 characters. -->
						<line1>123 Main Street</line1>
						<!--The line1 element is used to enter the first line of the street address. This element is not required and the information populates the Address 1 column of the address list on customer records. The maximum length for this field is 50 characters. -->
						<line2>Box 423</line2>
						<!--The line2 element is used to enter additional address information���such as a suite or box number. This element is not required and the information populates the Address 2 column of the address list on customer records. The maximum length for this field is 50 characters. -->
						<city>Palo Alto</city>
						<!--The city element is used to enter the city for this address. This element is not required and the information populates the City column of the address list on customer records. The maximum length for this field is 50 characters. -->
						<state>CA</state>
						<!--The state element is used to choose a state or province for this address. This element is not required and the information populates the Province/State column of the address list on customer records. 

When entering information for this element, the standard, two-letter state or province abbreviations must be used. If these abbreviations are not used, it will not result in an error. However, the Province/State field will remain blank upon import. For a complete list of state and province abbreviations, see the Appendix of the smbXML Developer's Guide. -->
						<zipCode>94404</zipCode>
						<!--The zipCode element is used to enter a postal zip code for this address. This element is not required and the information populates the Zip column of the address list on customer records. The maximum length for this field is 13 characters. -->
						<country>US</country>
						<!--The county element is used to choose a country for this address. This element is not required and the information populates the Country column of the address list on customer records. 

When entering information for this element, the standard, two-letter country codes must be used. If these abbreviations are not used, it will not result in an error. However, the Country field will remain blank upon import. For a complete list of country codes, see the Appendix of the smbXML Developer's Guide. -->
						<phone>555-555-1111</phone>
						<!--The phone element is used to enter a contact number for this address. This element in not required and the information populates the Phone field of the address list on customer records. The maximum length for this field is 21 characters. The previous formatting requirements introduced for phone number fields do not apply to this element. -->
						<defaultBilling>true</defaultBilling>
						<!--The defaultBilling element is used to indicate that this address is the default billing address for this customer. This element is not required and the information populates the Default Billing column of the address list on customer records. Because this field is a check box and records a true or false value, you must enter either true or false for this element. If this element is not included, the field defaults to true. -->
						<defaultShipping>false</defaultShipping>
						<!--The defaultShipping element is used to indicate that this address is the default Shipping address for this customer. This element is not required and the information populates the Default Shipping column of the address list on customer records. Because this field is a check box to record a true or false value, you must enter either true or false for this element.  If this element is not included, the field defaults to true. -->
						<addressText>John Doe&#xD;123 Main Street&#xD;Box 423&#xD;Palo Alto, CA 94403</addressText>
						<!--The addressText element is used to enter the exact information you want to appear in address fields on transactions when this address is chosen for this customer. This element is not required and the information populates the Address column of the address list on customer records. If you do not enter any information for this element, the information entered for attention, addressee, line1, line2, city, state, zipCode and country is entered in this field. -->
					</addressLine>
					<!--Add another address for this customer record. -->
					<addressLine>
						<addressName>Warehouse 1</addressName>
						<attention>J. Doe Jr.</attention>
						<addressee>John's Handy Mart</addressee>
						<line1>47 Foundry Street</line1>
						<line2>Warehouse 1</line2>
						<city>Palo Alto</city>
						<state>CA</state>
						<zipCode>94403</zipCode>
						<country>US</country>
						<phone>555-555-1313</phone>
						<defaultBilling>false</defaultBilling>
						<defaultShipping>true</defaultShipping>
						<addressText>John Doe Jr.&#xD;John's Handy Mart&#xD;Warehouse 1&#xD;47 Foundry Street&#xD;Palo Alto, CA  94403</addressText>
					</addressLine>
				</addressList>
			</customer>
		</addOrUpdate>
	</request>
</smbxml>
<!--
	To import an XML file:
	1. Click the Transactions tab.
	2. On the Transactions tab, under the Other heading, click Submit XML Document.
	3. Click Browse.
	4. Locate your smbXML field and select it.
	5. Click Submit. 
	
	You will see a status bar with the import progress. Once the import is complete, a message appears below the status bar indicating if there are any errors. You will also have the opportunity to download and view the XML response file from NetSuite. The response file lists any errors you may have received and acknowledgements for successful imports.

If you received any errors, you can edit your file to correct the errors and import the file again. Any requests that were successful do not need to be imported again. 

For more information about constructing and importing XML documents, see the Developer's Guide on the NetSuite Web site at Partners > Developer Program > Technical Documentation. -->
