Appendix A

Import Reference

This appendix provides sample CSV files and a complete reference of all XML import types supported by Quasar’s Import Screen.

Sample Item CSV

A 13-column CSV file. No header row. The importer auto-creates departments, subdepartments, and vendors as needed.

1001,049000012345,,Grocery,Canned Goods,Tomato Soup,Campbell's,EA,1,1.25,2.49,GST,GST
1002,049000067890,,Grocery,Canned Goods,Chicken Noodle Soup,Campbell's,EA,1,1.35,2.69,GST,GST
1003,,,Grocery,Baking,All Purpose Flour,Robin Hood,KG,2.5,3.50,7.49,,GST
2001,088888000111,,Dairy,Milk,2% Milk 2L,Beatrice,EA,1,2.80,4.49,,
2002,088888000222,,Dairy,Cheese,Cheddar Mild 400g,Cracker Barrel,EA,1,4.25,6.99,,
3001,,,Cleaning,General,Multi-Surface Cleaner,Mr. Clean,EA,1,2.10,4.99,GST,GST
4001,077777000333,,Hardware,Fasteners,Wood Screws #8 100pk,Hillman,EA,1,3.40,7.99,GST,GST

What Happens On Import

Departments Grocery, Dairy, Cleaning, Hardware are created if they don’t exist
Subdepartments Canned Goods, Baking, Milk, Cheese, General, Fasteners are created under their respective departments
Vendors Campbell’s, Robin Hood, Beatrice, Cracker Barrel, Mr. Clean, Hillman are created
Empty UPC/tax fields are allowed — the importer uses the screen defaults

Sample Customer CSV

A 20-column CSV file. No header row.

,100,Acme Construction Ltd,,,,John Smith,123 Main Street,,Edmonton,AB,Canada,T5J 1N3,780-555-0100,,780-555-0101,john@acme.ca,www.acme.ca,5000.00,Y
,,,,Jane,Doe,Charge,,456 Oak Avenue,Suite 2,Calgary,AB,Canada,T2P 3N4,403-555-0200,403-555-0201,,jane.doe@email.com,,1000.00,N
,102,Northern Supplies Inc,,,,Mary Wilson,789 Railway Ave,,Whitehorse,YT,Canada,Y1A 2B3,867-555-0300,,867-555-0301,orders@northern.ca,,10000.00,Y

Key Points

Row 1: column 1 is blank (not “Blank”), so it processes normally. Company name is populated → treated as company customer.
Row 2: no customer number → auto-assigned from Next Customer #. No company name but First/Last populated → individual customer (“Doe, Jane”).
Row 3: Customer Type “Charge” looked up — if not found, the default type from the screen is used.
Column 1 set to “Blank” skips the row entirely.

XML Import Types Reference

The following table lists every XML tag supported by the import engine. Each type supports Insert and Update operations unless noted. The XML file must have a doctype of IMPORT.

Setup & Configuration

XML Tag	Update Tag	Description
account	accountUpdate	GL accounts (also supports accountDelete)
accountType	accountTypeUpdate	Account type categories
adjustReason	adjustReasonUpdate	Inventory adjustment reasons
brand	brandUpdate	Item brands
cancelReason	cancelReasonUpdate	E-invoice cancellation reasons
charge	—	Extra charges (freight, handling)
color	colorUpdate	Matrix item colors
depreciation	depreciationUpdate	Depreciation methods
discount	discountUpdate	Discount definitions
expense	expenseUpdate	Recurring expense templates
extra	—	Extra data field definitions
group	—	Groups (for any data type)
linkType	linkTypeUpdate	Item link type definitions
location	—	Inventory locations
mediaType	mediaTypeUpdate	Media/document type definitions
priceZone	priceZoneUpdate	Price zones
satProduct	satProductUpdate	Government product catalog codes
securityType	securityTypeUpdate	Security type profiles
station	stationUpdate	POS station definitions
store	storeUpdate	Store definitions
taskType	taskTypeUpdate	Task/CRM type definitions
tax	taxUpdate	Tax codes and rates
tender	tenderUpdate	Tender types (cash, cheque, etc.)
term	—	Payment terms
user	userUpdate	User login accounts

Cards

XML Tag	Update Tag	Description
customer	customerUpdate	Customer master records
customerType	customerTypeUpdate	Customer type definitions
customerUnit	customerUnitUpdate	Customer unit / ship-to records
employee	employeeUpdate	Employee records
vendor	vendorUpdate	Vendor/supplier records
patgroup	patgroupUpdate	Patronage groups (also supports patgroupDelete)
crm	crmUpdate	CRM contact records

Inventory

XML Tag	Update Tag	Description
dept	deptUpdate	Departments
subdept	subdeptUpdate	Subdepartments (also supports subdeptDelete)
item	itemUpdate	Items (also supports itemDelete)
media	mediaUpdate	Media/document attachments
labelBatch	—	Label print batches
priceBatch	—	Price change batches
priceCalc	—	Price calculation rules
promoBatch	—	Promotional price batches
orderTemplate	orderTemplateUpdate	Purchase order templates

Transactions

XML Tag	Update Tag	Description
journalEntry	—	General ledger journal entries
cheque	chequeUpdate	Cheques (vendor or customer)
customerInvoice	customerInvoiceUpdate	Customer invoices (sales)
customerReturn	customerReturnUpdate	Customer returns
vendorInvoice	vendorInvoiceUpdate	Vendor invoices (purchases)
vendorClaim	vendorClaimUpdate	Vendor claims
salesOrder	salesOrderUpdate	Sales orders
quote	quoteUpdate	Customer quotes
order	orderUpdate	Purchase orders
slip	slipUpdate	Packing slips (also supports slipDelete)
consignIn	consignInUpdate	Consignment receipts
consignOut	consignOutUpdate	Consignment shipments
cardAdjustment	—	Card balance adjustments
itemAdjustment	itemAdjustmentUpdate	Inventory adjustments
itemTransfer	—	Inventory transfers between stores
asset	assetUpdate	Fixed asset records
assetType	assetTypeUpdate	Fixed asset type definitions

XML File Structure

All XML import files follow this structure:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE IMPORT>
<Import>
  <account>
    <name>Cash in Bank</name>
    <number>1020</number>
    <type>Bank</type>
  </account>

  <accountUpdate>
    <oldNumber>1020</oldNumber>
    <name>Cash in Bank - Chequing</name>
  </accountUpdate>

  <item>
    <number>1001</number>
    <description>Widget A</description>
    <dept>Hardware</dept>
    <subdept>Fasteners</subdept>
    <purchased>Yes</purchased>
    <sold>Yes</sold>
    <inventoried>Yes</inventoried>
  </item>
</Import>

Mixing Types in One File A single XML file can contain multiple object types. The importer processes them in the order they appear. Put setup objects (accounts, taxes, departments) before transaction objects (invoices, adjustments) to ensure references resolve correctly.

Update Operations Update tags (e.g., accountUpdate, itemUpdate) require an old field (e.g., oldNumber, oldName) to identify the existing record. Only fields included in the update tag are changed — other fields remain untouched.