CA2410424A1 - Real-time global tariff and import data system and method - Google Patents

Abstract

Published without an

Description

REAL-TIME GLOBAL TARIFF AND IMPORT DATA SYSTEM AND METHOD
Field of the Invention The present invention generally relates to systems and methods for providing tariff and import data. More specifically, the present invention relates to computer systems that determine and make such data available over a network.
Cross Reference to Related Auulications This application claims the benefit of priority from commonly owned U.S.
Provisional Patent Application Serial Number 60/207,788, filed May 30, 2000, entitled SYSTEM FOR
PROVIDING CONTINUOUSLY UPDATED REAL TIME GLOBAL CUSTOMS, TARIFF
AND M'ORT DATA VIA A COMPUTER NETWORK; U.S. Provisional Patent Application Serial Number 60/232,088, filed September 12, 2000, entitled GLOBAL PRODUCT
IDENTIFICATION SYSTEM FOR DETERMINATION OF TARIFFS; U.S. Provisional Patent Application Serial Number 60/250,407, filed November 30, 2000, entitled MASTER
UNWERSAL TARIFF SOFTWARE; and U.S. Provisional Patent Application Serial Number 60/279,641, filed March 29, 2001, entitled MASTER UNIVERSAL TARIFF SYSTEM AND
METHOD, incorporated herein by reference.
o Background of the Invention Over the past several years there has been a simultaneous growth in international trade and global interaction and expansion of the World Wide Web ("the Web").
Increasingly, nations and regions are entering into trade agreements to facilitate increased international trade. World markets are becoming more interrelated and the demands for the importation of goods and s services is growing accordingly. Part of the increased demand may also be attributed to the growth of the Web. The Web allows consumers, whether businesses, orgasuzations, or private individuals, to shop the world on-line, from the convenience of a home or office computer.
Unfortunately, despite increased activity and demand, issues surrounding international transactions remain. That is, for each purchase of a product from another country, certain tariffs (or duty) and import taxes are usually applied to the transaction. Tariff rates and tax rates are country specific and change from time to time. Additionally, for each country, duty rates and tax rates tend to vary among types or categories of products, thus multiplying the complexity and volume of duty and tax information.
Keeping track of such a large volume of information can be a daunting and expensive undertaking for a seller (e.g., retailer or distributor). As a result, fulfillment of international orders emanating from customers located around the globe is attempted by only a small percentage of companies, due to the complexities of shipping across international borders. Of that small percentage that does attempt fulfillinent of international orders, most usually only ship to a handful of countries.
To enable businesses, organizations, and individuals to more readily conduct international transactions, there is a need for a comprehensive system that provides updated tariff and tax information, as well as other transaction related costs and information. There is a further need for such a system to be a real-time system and for it to be accessible and functional over the Web, or other networks.
L o Summary of the Invention The present invention is a system and method for providing real-time tariff and import data over a computer network, preferably including the calculation of total landed cost. A duty calculation engine accesses relevant tariff rates and applies the rate that is applicable to arrive at a duty calculation. An import tax calculation engine accesses relevant databases of country is specific import tax rates, charges and fees and applies them to arrive at import tax costs. A total landed cost calculation engine calculates a total landed cost from the calculated duty (or tariff) and import tax, along with other transaction related costs, such as freight and insurance costs.
A real-time tariff and import data system in accordance with the present invention, may be implemented as a business-to-business ("B2B") system, a business-to-consumer ("B2C") o system, or as some combination thereof. The system may be accessed over one or more of any of a variety of networks, such as local area networks (LANs), wide area networks (WANs), virtual private networks (VPNs), intranets, extranets, the World Wide Web (the "Web"), the Internet, telephone networks or some combination thereof.
The real-time tariff and import data system includes databases having current duty and >. s tax rate information for a plurality of countries. These databases are coupled to a set of servers, for example, which host the duty calculation, tax calculation, and total landed cost calculation engines. The servers are accessible by any of a number of types of network enabled devices, such as personal computers (PCs), workstations, other (tlurd party) servers or systems, personal digital assistants (PDAs), telephones, or other such devices. The data in the databases may be o automatically updated by remote third party sources or they may be updated locally, or some combination thereof. Also, rather than representing each country in the system databases, the real-time tariff and import data system servers may link to third party sources of such tariff and tax information. The databases are kept substantially current, to provide accurate information to customers.

The content of the databases may embody trade restrictions imposed between countries. ~
That is, where a country prohibits trade with another country, the real-time tariff and import data system may include a transaction validity checker that alerts the customer that the input transaction is forbidden by one of the countries (e.g., destination country) involved. For example, the United States prohibits the importation of cigars from Cuba. If a customer entered information for such a transaction, the real-time tariff and import data system may be configured to alert the customer to the trade restriction or may refuse to perform the requested calculations.
Users enter transaction inputs via an electronic device (e.g., PC, workstation, PDA, and/or other network enabled devices configured for user input). The inputs may include one or more of a PIN (if access is controlled), access code, origin country, shipment (or export) country, destination (or import) country, input code type, product code, transaction value, number of units being bought, unit code, cost of transportation, insurance cost, other (ancillary) costs, transaction currency, conversion currency, and output format code.
The access code input specifies whether the duties and taxes are calculated within or over _5 a volume quota for a given product in a given country. The origin country is the country from where the product is considered to be manufactured. The shipment country is the country from where the products axe sent. And, the destination country is the country to where the products are to be sent, also referred to as the country of importation. The input code type represents the type of input given for the product code (e.g., HS code or user defined product code). The product o code identifies the category of the product: The unit code specifies the units (e.g., pounds, liters and so on) associated with the products, and the number of uiuts tells how many units are being imported (e.g., 10, 000). A desired output format from a predetermined set of output formats can be specified by the user through entry of an output format code. Output formats include duty rate, duty amount, detailed duty, tax rate, tax amounts, detailed taxes, duty and tax rates, duty and s tax amounts, detailed duty and tax output, or total landed cost.
The inputs are entered into an on-line request form, which may be an XML
(eXtensible Markup Language) document, for example. Preferably, the present invention includes a Web-based interface that allows users to interact with the system and get duty tariff and import data system servers to produce an output, in accordance with the chosen output format. As a Web o accessible system, the real-time tariff and import data system is configured to provide real-time import duty, tax, and total landed cost information for shipments among the various countries represented in the databases.
In the present invention, the real-time tariff and import data system may be accessed by any of a variety of client device configurations, such as Web user client, a Java client 102B, and an XML client. Regardless of the configurations of the client device, communication between the client device and the real-time tariff and import data system is preferably accomplished using standard communication and format protocols and languages, such as the Internet Protocol and XML. Additionally, communication using encryption and access control mechanisms may be used.
In various embodiments, the present invention may include fiulctionality or links to insurance providers for obtaining insurance cost figures and/ or to transportation providers for obtaining transportation figures. Additionally, the present invention may also facilitate or enable the purchasing of such insurance and transportation. In such embodiments, the user need not L o input insurance or transportation cost information, as the case may be, and the outputs may variously include the system calculated insurance and transportation costs.
The real-time tariff and import data system may provide for customer account and billing, based on use, transactions, or flat fee structures. The system may serve as a back-end system for a third party, or as a front end system that is directly accessible by customers.

Brief Descriution of the Drawings The foregoing and other objects of this invention, the various features thereof, as well as the invention itself, may be more fully understood from the following description, when read together with the accompanying drawings, described:
o FIG. 1 is a representative architecture of the real-time tariff and import data system, in accordance with the present invention;
FIG. 2 is an architecture of a distributed real-time tariff and import data system, in accordance with the present invention;
FIG. 3 is a software architecture for the real-time tariff and import data system of FIG.1 s or FIG. 2;
FIG. 4 is a block diagram showing the primary functional components of the software architecture of FIG. 3;
FIG. 5 is a diagram depicting a standard Web browser-based approach to client-server exchange with the real-time tariff and import data system of FIG. l and FIG.

2;
s o FIG. 6 is a diagram depicting a Java-based approach to client-server exchange with the real-time tariff and import data system of FIG. 1 and FIG. 2;
FIG.s 7A, 7B and 7C are diagrams depicting XML request string exchange and processing by the real-time tariff and import data system of FIG. 1 and FIG.
2;
FIG.s 8A, 8B and 8C are diagrams depicting Web-based request exchange and processing by the real-time tariff and import data system of FIG. 1 and FIG. 2; and FIG. 9A and 9B are diagrams depicting Java-based request exchange and processing by the real-time tariff and import data system of FIG. 1 and FIG. 2 For the most part, and as will be apparent when referring to the figures, when an item is used unchanged in more than one figure, it is identified by the same alphanumeric reference indicator in all figures.
Detailed Descriution of the Preferred Embodiment The present invention is a system and method for providing real-time tariff and import data over a computer network, including the calculation of total landed cost.
In the preferred L o form, a duty calculation engine accesses relevant tariff rates and applies the rate that is applicable to arrive at a duty calculation. An import tax calculation engine accesses relevant databases of country specific import tax rates, charges and fees and applies them to arrive at import tax costs.
A total landed cost calculation engine determines the total landed cost from the duty calculation and the import tax calculation, along with other transaction related costs, such as transaction Ls value, freight and insurance costs, type of good(s), import, shipment, and export countries.
A real-time tariff and import data system in accordance with the present invention, may be implemented as a business-to-business ("B2B") system, a business-to-consumer (B2C) system, or as some combination thereof. The system may be accessed over one or more of any of a variety of networks, such as local area networks (LANs), wide area networks (WANs), virtual o private networks (VPNs), intranets, extranets, the World Wide Web (the "Web"), the Internet, telephone network, or some combination thereof. The real-time tariff and import data system may serve as a front-end system, directly accessible by those seeking tariff, import tax and/or total landed cost data for a transaction. In other embodiments, the real-time tariff and import data system may serve as a back-end system, coupled to a front-end international transaction >.5 system, for example.
Part I - Hardware and Software Architecture FIG. 1 shows a representative architecture 100 implementing the present invention.
Architecture 100 includes a set of client devices 102 configured to access the real-time tariff and import data system 120 via the Internet 104. Access to the real-time tariff and import data o system may be provided via a standard router 106 and firewall 108.
In accordance with the preferred embodiment, the real-time tariff and import data system I20 malces information accessible regarding tariffs in approximately 225 countries for approximately 5,800 products listed in the Harmonized Coding System (HCS), which are represented as established country-based product Harmonized System (HS) codes.
Along with information on various customs duties, applicable tax rate information is provided for a plurality of products, and vital information necessary or useful for doing business in various countries.
Such information is stored and managed by a database management system 140.
Preferably, the real-time tariff and import data system 120 includes the following characteristics:
(1) High Level of Availability: To simultaneously accommodate the needs of clients around the globe, the system is preferably accessible for substantially 24 hours a day, 7 days a week, for a total availability rate of approximately 99%, or more. To accomplish such high availability, the system architecture accommodates a minimal mean-time-to-recovery (i.e., not ~ o more than a few seconds), which may be accomplished, at least in part, with customary redundancy, "hot spares", and fail-over mechanisms. As examples, for a 99%
availability rate, the system can not be down for more than 88 hours per year (i.e., up for 8,672), and for an availability rate of 100% the system is down for 0 hours per year (i.e., up for 8,760).
(2) High Level of Transparency of System Faults: Owing to the recovery mentioned above, client-users are substantially unable to detect that a system fault has occurred. In a worst-case scenario, response time of the system is only prolonged by a few seconds, rather than producing error messages or terminating jobs.

(3) Ability to Cope with a High Volume of Transactions: User traffic is an important factor to take into consideration with regard to bandwidth use. Indeed, the width of the a o bandwidth is an important element in the system response time. The following table, Table 1, presents the number of concurrent users that can be supported, depending on the kind of bandwidth used (calculated for a connection lasting in the order of 15 seconds):
Connection type Maximum bandwidth*Concurrent users*Hits per day*

Dedicated PPP/SLIPModem Speed 6 46, 258,560 56K (Frame Relay)56,000 bps 9 70,383,909 ISDN (using PPP) 56,000 - 64,000 19 157,988,571 bps T1 1,540,000 bps 210 1,851,428,571 Fractional T1 Varies as needed Varies Varies T3 45,000,000 bps 6,277 55,525,083,429 OC3 150,000,000,000 20,927 185,142,857,143 bps *These values are estimates and may vary, but they are useful as guidelines in choosing s connection types.
TABLE 1 - Concurrent Users (4) Tamper-Proof Data and Transaction Security: Use of a variety of security mechanisms, discussed in detail below, provide for control of access to data and protection of.
databases against attacks via the Internet, and ensures the confidentiality of clients' transactions.

(5) Accuracy of the information contained in databases 146: Customs information varies from country to country. Additionally, countries often pass new laws that change tariffs from one year to the next, or even in the course of the same year. The real-time tariff and import data system 120 allows for the expedient integration of these changes, by accommodating automated information distribution and database updates. Database updates may be accomplished locally, remotely (possibly via third party systems), or some combinations thereof, as discussed in more ~o detail with respect to FIG. 5.
The hardware architecture shown in FIG. 1 embodies the characteristics outlined above.
The real-time tariff and import data system architecture 120 includes a clustei of front end application servers 130, as a first logic or application layer, coupled to a back end database management system 140, as a data layer. In the architecture of FIG. 1, the application servers L5 132 and 134 are accessible via the Internet through a local network 112, which includes muter 106 and firewall 108. Firewall 108 protects servers 132 and 134 from Internet attacks by filtering and controlling access to the servers, which is discussed in more detail below.
Generally, one of the major factors in the reliability of a Web site is the reliability of the servers used to host the Web site. Each of application servers 132 and 134 serve as intelligent >, o relief systems to the other; they "know" (i.e., monitor) each other's status, which aids in the processes of load balancing and fault recovery.
While FIG. 1 shows the application layer to include two application servers, a greater number of servers may be used and they may be located at geographically local or remote locations, or some combination thereof. The architecture of FIG. 1 offers scalability, in that >, s more servers may be easily added. In the preferred embodiment, an increased number of servers allows increased availability. Additionally, the processing load of the various application object components that are to be executed at a given time on the servers is dynamically balanced among the clustered application servers 130. In the preferred embodiment, the applications running on servers 132 and 134 are written in object oriented code.
s o Both application servers, 132 and 134, are configured to respond to client requests, so that they can easily share the load. A load-balancing module distributes requests between servers 132 and 134, such modules axe known in the art and not discussed in detail herein. If one server (e.g., server 132) is no longer responding, all requests must then be directed towards the other server (e.g., server 134), or other servers if there are more than two application servers. The load-balancing module is replicated on both (or all) application servers, which allows the application servers to ensure continuous request distribution, regardless of which servers) go down. To ensure system fault tolerance, status information is also replicated on each application server. Thus, even minor faults can be hidden from users, leaving application processing s substantially unaffected.
In FIG. 1, the application layer clustered servers 130 are coupled to the data layer 140 via a local network 122 that includes a switch 124 and firewall 126. The database management system 140, or data layer, includes the data servers 142 and 144 and the databases 146 that include all of the tariff and other import data. In the preferred form, database 146 includes a set ~o of shared RAID (Redundant Array of Inexpensive Disks) external disks . RAID
systems are known in the art and not discussed in detail herein. In the preferred form, the data layer servers 142 and 144 of FIG. 1 axe Microsoft SQL servers, clustered using standard clustering technology (e.g., such as that provided by Microsoft Corporation of Redmond WA).
The architecture of the data layer 140 is designed to provide maximum data availability.
L5 That is, if one server (e.g. server 142) breaks down, the other server (e.g., server 144) takes over in a manner that maintains transparency to users. Therefore, transactions that are taking place during a database management system 140 fault will not be interrupted, since the requests sent to the faulty server will be automatically transferred to the active server.
Since both data layer servers 142 and 144 are connected to RAID external disks 146, disk faults can be dealt with one a o disk at a time, without halting tasks. Using background monitoring, a problem with one disk can be detected before a fault occurs so that the damaged disk can be replaced before service is interrupted.
Both servers 142 and 144 share a "heartbeat" connection, are part of a local network, are linked to the Internet, and require the use of dual Ethernet network interface cards, in the >. s preferred embodiment of FIG. 1. In this configuration, the database servers 142 and 144 have public IP addresses in order to facilitate data updating operations, but this can expose the servers 142 and 144 to attacks from the Internet. To protect against such attacks, firewall 126 is used to filter requests to the database servers 142 and 144. Thus, only the logical layer servers 132 and 134, i.e., the servers used for updating data (replication), will be able to access the database o servers 142 and 144, and server 132 and 134 are also protected by firewall 10~.
The databases 146 of database management system 140 includes the following information or databases:
(1) Customs tariff and taxes databases, (2) Customs information databases on various countries, and (3) System client databases (where the system maintains client-user accounts).
As previously mentioned, real-time tariff and import data system 120 may include multiple application servers in different locations to provide a more robust fail-over solution, in case of maj or disaster at one site, as is shown in FIG. 2. As previously mentioned, the real-time s tariff and import data system 120 is preferably a Web-accessible system.
Therefore, a request may be submitted to a Domain Name Server (DNS) 250 which then returns up to two specific IP
addresses. Since the real-time tariff and import data system 120 has multiple servers in different locations, in this embodiment, the DNS server 250 returns the optimal address 252 and the second best address 254. The optimal address 252 can be defined as the one with the lowest ~o latency and with an acceptable load.
To provide a fail-over solution and to provide high availability, the client application 260 must react when the response is not sent back after an acceptable timeout. It is preferred that after an acceptable timeout expires, the request is resent a certain number of times to the DNS
server 250. To use this feature, a toolkit or client application 260 is configured support the following:
(1) multiple IP addresses in response to it's address resolution request, and (2) the ability to try to connect using the second IP address, if the first IP
address attempt is unsuccessful.
Preferably, the DNS server 250 always returns up to two 1P addresses, so if the optimal o application server 130A (with DB management system 140A) is down, the client application 260 (or device) redirects the request to the second best application server 130B
(with DB
management system 140B), after an acceptable timeout as been expired. However, if the client application 260 or toolkit does not support this feature, only the optimal ll' address will be available to the client application 260. To have a full fail-over proof client application 260, the s timeout is preferably set to be about 10 seconds. Also, when the timeout expires, the client application 260 is configured to re-send the request, alternating from the optimal server 130A to the second best server 130B
The preferred embodiment of a software architecture 300 of the real-time tariff and import data system 120 is shown in FIG. 3, which serves as the system's logical structure. This o logical structure allows for optimal use of resources from different servers. The application servers 132 and 134 support transparent replication, load balancing and fail-over for both the dynamic generation of Web pages (i.e., at the presentation layer) and components (i.e., at the logical layer components).
The real-time tariff and import data system 120 main application obj ect components 400 are shown in FIG. 4 and described below.
(1) A TFeedClient object component 402 includes all relevant information for customers (e.g., corporate customers) known to the system and provides methods for accessing specific customer information, which may be stored in customer accounts.
(2) TFeedMsgPI~CS object component 404 is configured to customize security levels to client specifications. Data exchanges may be conducted in encrypted or plain-text format. For encrypted transactions, this obj ect component 404 can encrypt and decrypt messages, however, this function requires that public and private access keys be installed in both the customer's system (or client device) and on the application servers 130.
Lo (3) TFeedReqMsg object component 406 prepares received client requests for the other system components. Requests may use the HTTP protocol, may be made directly from the components Tava installed in the customer's system or may use an XML format, as described in greater detail below. The TFeedReqMsg obj ect component may be instantiated using any one of these sources.
L5 (4) TFeedRespMsg object component 408 prepares a response to a client request and transmits the response to the client (via TFeed-Servlet, if needed). Responses are directly delivered using HTTP protocol or using an XML format from the TFeedRespMsg obj ect component 406, as described in further detail below with respect to the data exchange process.
(5) TFeedXMLMgr object component 410 manages the exchange of information between >. o the real-time tariff and import data system 120 Web site and clients using an XML format.

(6) TFeedDFeeCalc object component 412 calculates duty fees (i.e., customs charges).
This component is also referred to as the duty calculation engine.

(7) TFeedHSCtryData object component 414 provides the tariff for a country and for a specific corresponding HS code. This object component is used by TFeedDFeeCalc 412 to s perform customs charges calculations.

(8) TFeedHSCtryTax object component 416 provides the tax rate for a country and for a specific HS code. This object component is used by TFeedTaxCalc 418 below.

(9) TFeedTaxCalc object component 418 applies the tax rate for a product, according to the HS code provided and the country of import, to determine the tax charges This component is s o also referred to as the import tax calculation engine.

(10) TFeedBilling object component 420 manages the customer account billing process.

(11) TFeedLog object component 422 keeps a running log of all client requests fed into the database. This information may be used as a reference for operating difficulties reported by clients or for cases in which a customer wishes to contest a bill.

(12) TFeedServlet object component 424 manages incoming requests sent via a Web browser and outgoing responses, using HTTP protocol.

(13) TFeedTTLCalc object component 426 calculates the total landed cost for a transaction, using the calculated duty from the duty calculation engine 412 and the import tax s calculation engine 418, along with other transaction date (e.g., insurance and transportation costs).
The content of the databases may embody trade restrictions imposed between countries.
That is, where a country prohibits trade with another country, the real-time tariff and import data system may include a transaction validity checker (e.g., a TFeedValidTrans component, not o shown) that alerts the customer that the input transaction is forbidden by one of the countries (e.g., destination country) involved. For example, the United States prohibits the importation of cigars from Cuba. If a customer entered information for such a transaction, the real-time tariff and import data system may be configured to alert the customer to the trade restriction or may refuse to perform the requested calculations.
In various embodiments, the present invention may include functionality or links to insurance providers for obtaining insurance cost figures and/ or to transportation providers for providing transportation figures. Additionally, the present invention may also facilitate or enable the purchasing of such insurance and transportation. In such embodiments, the user need not input insurance or transportation cost information, as the case may be, and the outputs may o variously include the system calculated insurance and transportation costs.
Returning to the database management system 140 of FIG. 1, a variety of operations are involved in maintaining data integrity, as discussed below. Database security requires that customer (or user) security measures be established. Therefore, security audits may be conducted on a regular basis to verify access to the database and authentication may be required for access s to database 146. SQL Server offers two authentication modes:
(1) Windows NT Authentication Mode: SQL Server can use Windows NT to authenticate users. User accounts are managed and defined in Windows NT and the access rights (and roles) are defined on the SQL Server.
(2) Mixed Mode: Previous modes can be used along with the authentication mode above, o which requires that an account be created, with username and password, on the SQL Server.
This account is saved in the system tables of the SQL Server.
In the preferred embodiment, the mixed mode is used, since it requires no control over the network and its clients (e.g., NT accounts and client network management).
However, users who have different roles may also be defined on the SQL Server. By "role" it is meant that a group of users is treated as a single unit, to which access permissions can be applied. The access permission attributed and/or deleted for one role is applied to all of the users who share that role.
The following table, Table 2, shows a list of predefined roles on the SQL
Server. New roles may be defined to control access to the tables and/or procedures of any database.
Fixed database role Description db owner Carries out all of the maintenance and configuration operations in the database.

db_accessadmin Adds or deletes access rights for Windows NT

users and groups and SQL server accounts.

db datareader Reads all of the data from all of the tables.

db_datawriter Adds, deletes or modifies the data in all of the user tables.

db ddladmin Executes all data definition commands in the database (i.e., in the Data Definition Library (DDL)).

db securityadmin Changes role attribution and manages access permission.

db backupoperator Database backup.

db_denydatareader Denies access to functions for reading data in any of the user tables.

db denydatawriter Denies access to functions for adding, changing or deleting data in any one of the user views or tables.

TABLE 2 - Predefined Roles SQL Server also has a powerful "Profiler" that records and analyzes all of the operations executed by the SQL Server (i.e., database management servers 142 and 144).
The resulting reports can be saved in a text file or in an SQL Server table. Audits regarding access to the servers 142 and 144 may therefore be conducted by recording the following information: access granted; access denied; procedures used; sessions established; and user accounts used. All of this information provides an excellent support tool in establishing who has done what and when.
To protect the databases 146, backup operations are preferably conducted.
Generally, there are three methods for performing data backups:

(1) Offline (Cold) Backup: Database services are halted; backup operations are then carried out and the database is put back on line. During this time, the database is not available.
(2) Online (Hot) Backup: Database services are active, the database remains on line, but no access is granted during this operation.
s (3) Active Online Backup: The database is active and is accessible by the applications.
In the preferred embodiment, option 3 above is used, since it allows backup during normal operations without interruption. This option also allows around-the-clock access. Although this operation minimally increases the server load, it is still advisable to carry out these operations during the hours when the load is at its most stable.
L o Since there is such a heavy reliance on the database content for producing accurate cost figures, a significant challenge is to guarantee that the information contained in the databases is accurate. One way to ensure the accuracy of data is to perform database updates using the functions of the SQL Server. For example, data replication provides a fast and effective way of distributing information and reducing dependency on a central database server.
SQL Server ~s allows users to replicate data from one SQL Server to another SQL Server, or to several other types of databases by different makers (e.g., Oracle, Sybase or IBM DB2). The SQL Server replication function is based on the "publish and subscribe" model in which one database information server plays the role of a "publisher" while the others play the role of "subscribers", as is shown in FIG. 5. A publisher is the database system or server that makes data available for >. o replication, and may be the "owner" or source of the data. In FIG. 5, database changes may be sent from a client device 102, for example, to a publisher database system 502. Publisher 502 maintains a list of publications (i.e., data for distribution) and subscribers for the publications. A
subscriber may be a database server (e.g., servers 142 and 144) that receives and updates (or replicates) its own database data with the updated publication. Subscriber 1 504 and Subscriber S 2 506 may be systems, clients, or servers which are not directly a paxt of the real-time tariff and import data system 120.
Generally, there are two types of subscriptions:
(1) The "pull" subscription, in which the subscriber (e.g., 142, 504, or 506) requests regular updates from publisher 502.
o (2) The "push" subscription, in which publisher 502 distributes the changes to various subscribers (e.g., 142, 504 and 506) when changes occur or according to a predefined plan.
Database management system 140 supports at least three types of replication between a publisher and subscribers:
(1) Snapshot Replication: As its name indicates, this type of replication takes a photo or a snapshot of the data to be published at a given moment in time. These snapshots can be taken according to a plan or upon request. Snapshot replication uses very few system resources.
However, all of the subscriber data is refreshed. All information is transferred to the subscribers, which requires a high-performance bandwidth for high volumes of data.
s (2) Transactional Replication: In this type of replication the changes made at the publisher level are distributed on a continuous basis or at established intervals to one or several subscribers. This type of replication is most appropriate for cases in which only one publisher is available and updates are done on this publisher. Thus, subscribers could upload changes and update their data at a predetermined time.
~o (3) Merge Replication: This type of replications allows publisher 502 and subscriber 142, 504 and 506 to operate independently of each other and to periodically reconnect to update or consolidate their respective data.
In the case of the real-time tariff and import data system 120 Web site, transactional replication is preferred. Updates on customs data are carned out on a server that plays the role of a publisher and all changes are distributed to subscribers.
The following steps allow implementation of replication functionality on a server that will play the role of a publisher:
(1) Installation of one version of the database;
(2) Definition of publications and articles (including table sets, information to be a o replicated);
(3) Configuration of publication mode (for transactional replication);
(4) Definition of a publication frequency (for data transfer to subscribers);
(5) Definition of subscribers (e.g., database servers and in client database servers); and (6) Configuration of different firewalls or proxies for replication via the Internet.
>, s The flow diagram of FIG. 6 illustrates a process 600 used to manage users that access services provided by the real-time tariff and import .data system 120. First, a user operating client device 120A that wishes to use the services completes request form 802 (see FIG. 8A), which is made available on the real-time tariff and import data system 120 Web site.
The form 802 is sent to the Web server, 132 or 134, and processed by a dynamically generated page using the s o TFeedClient obj ect 402 (see FIG. 4). Next, a customer manager using device 602 accesses the reformed request 604 and validates the request by verifying the user properly entered required information contained in request form 802 (e.g., username and PIN 606). The application server 130 sends a user authorization 608 to client 102A. Customer manager 602 may open a customer (or user) account using device 602 via, for example, a Web interface. Customer manager 602, l4 preferably, e-mails confirmation to the customer that an account has been opened. Thereafter, the customer can carry out transactions using the real-time tariff and import data system I20 by logging in, without interaction with the customer manager 602. In some cases, installation of client components may be required on the customer's client device, as described with respect to FIG.s 8A-9B.
In some embodiments, the.real-time tariff and import data system 120 may be configured to bill its customers for usage, based on, for example, number of Web site hits, transactions processed, or requested outputs. Customer account related information (or billing data) may be stored in databases 146 (or other databases) and a mechanism may be established for customer ~ o access of the billing data. There are at least two possibilities in this area:
(1) a Web interface that gives access to a secure environment for billing data, or (2) a replication of billing data within the real-time tariff and import data system 120, allowing for a connection between a billing database and an accounting system.
The billing data may be use or fee information contained in customer account-related tables.
L5 Preferably, the real-time tariff and import data system 120 Web site includes a management section where access to billing data is password restricted, but with proper access allows account access for billing, payment or status.
An activity log is preferably generated to monitor server operations, which may be used for billing, as well as other purposes. Activities logged with respect to server operations may a o include client related transaction or system performance information (e.g., errors, processor utilization, and so on). That is, a log file may contain information concerning the sources of requests (e.g., IP Addresses, PIN numbers), requested product data, the date of the request and the date and type of information responses sent to clients. This file could be used by networlc operations or information technology personnel to resolve operations problems.
The activity log >. 5 functionality may also include importing and maintenance information.
A significant part of the real-time tariff and import data system 120 Web site, outside of the database content and user functionality, is its security system. Access is denied to hackers and content is be protected to ensure that it remains precise and consistent.
Thus, access to content is controlled, restore mechanisms are implemented, and content integrity is maintained.
o The application servers 132 and 134 used in the preferred embodiment provide the best security technology of its kind, with secure, flexible, and easy-to-configure architecture. The application server secures network applications through known, optional encryption, authentication and authorization functions, based on secured SSL RSA sockets, X.509 digital certificates and access control lists (ACLs). Together, all of these security fiulctions allow the system to determine the user of the provided services. Access to some application server 132 or 134 services is controlled through user and user group definition. The term "user" xefers to a human (e.g., a customer), a computer application, client device or a remote server. This security technology may be extended to all types of devices and users that access server resources.
ACLs are data structures that control access to resources. Each control list entry contains a set of access permission parameters associated with a user or a user group.
Access permission allows the system to carry out certain kinds of operations on server resources. Access permission may be positive (i.e., authorization for certain kinds of operations on specific objects) or negative (i.e., prohibition of some operations on specific objects).
~ o The application servers may be configured for a variety of levels of authentication. In the preferred form, application servers 132 and 134 are configured to use at Ieast one of two processes to authenticate the users: passwords and encryption certificates.
For minimal authentication, the process based on the password allows users to provide a password and their user name to access server resources. This process is based on the authentication process defined ~s in the HTTP protocol. A drawback to this process lies in the fact that passwords and usernames are traveling over the Internet in plain text format. For a more comprehensive and powerful authentication system, in the preferred embodiment, encryption is used in the form of encryption certificates. These certificates are issued by a Certificate Authority (CA), such those certificates issued by Verisign, Inc. of Mountain View, California.
>. o It is important to ensure that the information that passes through the Internet network circulates in am encrypted channel, and thus cannot be seen or altered.
Therefore, application servers 132 and 134 include an SSL implementation used in distributed applications, such as 128-bit SSL Global Server IDs by Verisign. SSL Version 3 allows for connection encryption and is the standard default protocol used to establish private and encrypted communications between >.5 two applications within a non-secured network. A digital certificate (or digital ID) is required on the server (e.g., server 132 or 134) for this protocol. A digital certificate allows the server to prove its identity with clients or other servers before a private connection is established.
Moreover, for greater security, application servers 132 and 134 can be configured to provide wo-way authentication for clients and browsers. In those cases, two-way authentication requires that s o the client system to have a digital certificate. Digital certificates are then cross-authenticated.
Part II - Preparing and Processing Requests In order to properly prepare the duty, import tax, or total landed cost of an item, a preferred set of transaction related inputs are required. Preferably, as discussed above, a request is sent from a client (e.g., client device 102) to the real-time tariff and import data system 120 via a Web site interface. In such an embodiment, the real-time tariff and import data system 120 guides the user to enter all needed inputs of the client by providing a well-structured request template or form with syntactic and semantic validation. Table 3 provides the preferred input requirements and their definitions for the request. (See also Appendix H for more information s about input validation). The client's request is processed by application servers 132 and 134 of the real-time tariff and import data system 120. After processing, the real-time tariff and import data system 120 returns a response to the client.
Parameter Definition ~o PINNumbe~ Personal identification number of the client provided by real-time customs tariffs and import data system I20.
Access Code A code that specifies whether the duties and taxes are calculated within or over a volume quota for a specific product in a specific country. If the specific quota is not known by the client, the client choose "Without" from the Web page request form. (See Appendix F).
Origin Country The country where the product is considered to be manufactured.
If the products) are classified by the real-time tariff and import data system 120, this input is optional since it already resides in database 146 for each HS code. Otherwise, an origin country code is entered in o the request and the country code in database 146 is not used. See Appendix AB for a sample of countries and corresponding country codes.
Shipment Country The country from where products) are sent (i.e., the country of exportation). See Appendix A/B.
s Destination Country The country to where products are sent (i.e., country of importation).
See Appendix AB.
Input Code Type A code that represents the type of input specified for the Product Code parameter in the request. See Appendix G.
Product Code Either user defined product code or the established HS code in the o system database. If a user-defined product code is entered, that user defined product code is used for the entire transaction. If the user uses an HS code, a valid HS code of the destination country is required.
Transaction Value Value of goods in the currency specified as the transaction currency parameter.

Number of Units Number of units specified for the Unit Code parameter.
Unit Code If a user-defined product code is entered, a unit~code (see Appendix C) and corresponding unit type (see Appendix D) specified by real-time tariff and import data system 120 must be entered. If an HS code was entered, the appropriate unit code and corresponding unit type are required. The user may be requested to send up to 10 different Unit Codes and Numbers of Units, in the preferred form.
Cost of Ti~ahsport The cost of transportation, in the currency specified for the transaction currency parameter. In some embodiments, this parameter may be ~ o generated upon request by the real-time tariff and import data system 120 or a third party system coupled thereto.
Ihsu~ahce Cost The cost of insurance, in the currency specified for the transaction currency parameter. In some embodiments, this parameter may be generated upon request by the real-time tariff and import data system L5 120 or a third party system coupled thereto.
Other Costs The amount of other costs, in the currency specified fox the transaction currency parameter.
T~ahsactioh Currency The currency code used for the amount specified for the transaction (e.g., U.S. Dollars). See Appendix A/B.
>. o Conversion Cu~rehcy The currency code used for the results to be provided by real-time tariff and import data system 120, for any output format under which dollar amounts are presented. See Appendix A/B.
Output Format Selected by entry of one of the predefined output format codes provided by real-time tariff and import data system 120. See >.5 Appendix E.
TABLE 3 - User Inputs In the preferred embodiment, a user can obtain the duty, tax and total landed cost associated with an international sale and shipment of one or more products by entering the above o inputs. Preferably, the real-time tariff and import data system 120 guides the user to properly enter inputs. When entering the required inputs (previously discussed), the user determines whether to use its own product codes or standard HS codes in the request. If the user uses its own product codes in requests, those product codes can be entered into the system during a classification phase, as part of a user/customer account setup, so that they will be recognized when forming requests. Thereafter, the user can send requests using its own set of codes or the HS codes, either will be valid for the specified unit type. If real-time tariff and import data system 120 also requires a weight unit for the entered product, the request can contain any valid unit code representing a weight: grams, kilograms, pounds, and so on.
The real-time tariff and import data system 120 requires all measurement units to precisely calculate duties and taxes. Even when using HS codes in the request, the user must include all required units. If a unit is omitted, real-time tariff and import data system 120 returns an error message indicating that a unit is missing. For example, certain countries require more than one measurement unit to calculate duties and taxes, or have "multiple units". For example, ~ o assume that a user plans to import wine from the United States to Canada.
Canadian authorities calculate duties and taxes depending on the number of wine bottles being imported and the volume of pure alcohol. Therefore, the user needs to send two unit types in the request: a number of wine bottles and pure alcohol volume.
The real-time taxiff and import data system 120 provides a default unit code for each unit type lmown to the system, see Appendix D. When referring to Appendix D, the "Unit Base"
column represents the default unit code. All other unit codes from the same unit type have a conversion factor based on the default unit code. Specifying the default unit code in the request typically reduces the response time, since the real-time tariff and import data system 120 will not need to perform a units conversion.
o In the preferred embodiment, there are at least three methods for exchanging data between users' (e.g., customers with accounts) client devices and the real-time tariff and import data system 120 Web site. These methods provide users with a laxge range of request structure possibilities. According to these methods, a client may be a Web user client 102A, a Java client 102B, and/or a client using XML string102C, as examples. Because of its open-ended, flexible s and self descriptive characteristics, the preferred embodiment uses XML
technology to exchange information with each type of client device. Thus, an XML format for the information exchanged between the clients and the real-time tariff and import data system 120 Web site is defined. That is, XML is used as a universal data exchange format, regardless of the type of client, as defined below.
o I . AIL Clients - To accommodate access by XML clients 102C, the real-time tariff and import data system 120 provides an HTTP service that accepts user inputs as part of a text/XML request from a client, as can be appreciated with respect to FIG.s 7A-C. XML
technology is used because it is supported by a variety of programming languages and by Web scripts, such as VBscript or Javascript. XML technology is derived from SGML, a relative of HTML, and defines a syntax for understanding and a format for data processing information.
XML syntax includes a series of tags used to insert markers into a document, and is generally known in the art. For example <Product> marks the bea nnin_g of the definition of a product and </product> marks the end. A product definition in XML can be written as follows:
<product hscode=" 12124560" country="ca" quantity="5000" l>
Once analyzed, this XML block will be interpreted as an entity containing three attributes:
"hscode," "country," and "quantity." An application can directly retrieve the value of a particular attribute without taking into account the order of the attributes within the document.
Generally, XML technology is open-ended and flexible. For example, an attribute .o "Price" may be added to a Document Type'Definition (DTD) document in order to support the specific needs of a new client application, but the existing client applications would not be affected, since they would continue to search for valid, previously defined attributes. The DTD
document is used to validate its corresponding XML documents, thus ensuring that the XML
format respects the format specified in the DTD document, so is much less prone to having or .5 causing errors. An XML document can be defined without using a DTD
document, but use of a DTD document is preferred. Generally, applications access an XML document using a series of functions defined in a DOM (Document Object Model). A DOM is an XML
application that provides a standard programming interface that allows an application to use the information defined within an XML document. FIG. 7A illustrates, at a top level, the interaction between the o real-time tariff and import data system 120 and XML client 102C. An XML
request message including an XML request string 702 is sent to. and processed by server cluster 130 (including servers 132 and 134). Server cluster 130 returns an XML response message including an XML
response string 704, as discussed in further detail below.
The communication between client device 1020 and real-time tariff and import data system 120 is shown in flowchart 710 of FIG. 7B. FIG. 7C shows a detailed view of the components involved in carrying out the steps of flowchart 710. In step 712, a client application 780 of client 102C gathers user input data to generate one or more client application request messages 742. In step 714 of FIG. 7C, using the data, the client application 780 generates a plurality of requests, i.e., Request 1 716A, Request 2 716B, and Request fa 716C. When possible, o generating multiple requests allows for more efficient, parallel processing.
An XML generator 756 uses a request message DTD 740 and the client application request message 742 to generate an XML request message 754. To create the XML request message, for each request, an XML, request string 702 is created, in step 718. Preferably, the XML request string 702 is encrypted in step 720 and, in step 722, xiVIL request message 754 is formed. In step 724, a sender 768 transmits XML request message 768 to server cluster 130.
Several components included on the real-time tariff and import data system servers, i.e., server cluster 130, facilitate communication with client 102C. Server cluster 130 receives the XML request message 754 from sender 768. The received XML request message 754 is parsed s by an XML server parser 744. A parser is a tool used for grammatical analysis, which includes a syntax analyzer, that can interpret tags and retrieve information from them.
Generally, the parser performs on a document in accordance with a corresponding DTD, which contains a tag description used in the XML document being parsed. Thus, a DTD document (e.g., DTD request message document 740) specifies the particular XML format for XML request message 754, ~ o identifying the tags that may or may not appear in XML document 754.
XML server parser 744 decrypts the XML request string 702 contained within XML
request message 754 and then parses XML request string 702. Parser 744 extracts input values and security attributes from the request XML request string 702, assuming security mechanisms are used. After the security attributes have been approved, the real-time tariff and import data ~s system 120 matches the user input product code with the appropriate HS code in database 146, assuming a user-defined product code was not entered. If using an HS code, system 120 validates that the HS code is correct fox the specified destination country.
If an error occurs, an XML response string containing the error message is sent back to the client 102C. Errors may be caused by invalid XML request values, invalid XML request node names, invalid inputs or o invalid security attributes, as examples.
Parsing XML request string 702 allows a request message object 764 to be created and passed to the real-time tariff and import data system application 138. The user's values, and any other needed values, are extracted and the duty calculation engine 412, tax calculation engine 418, and total landed cost engine 426 process the request, as required, in step 726, to produce a 'S response message object 762. XML generator 758 generates an XML response message 752 from the response message object 762 and a DTD response message document 746.
A sender 770 transmits the XML response message 770 to client device I02C.
Returning to flowchart 7I0 of FIG. 7B, client device 102C receives the XML
response message 752, in step 728. XML client parser 766 on client 102C paxses the XML
response o message 752, in step 730, to obtain the XML response string 704 and then decrypts the XML
response string, in step 732. XML client parser 766 creates a response message 744 from XML
response string 704 and DTD response message document 746 (which is also available to client 102C). Response message 744 includes the requested duty, tax, and/or total landed cost data and is passed to client application 780.

Implementation of the preferred approach to processing XML doccunents (i.e., requests and responses) takes place in several steps:
(1) Definition of DTD document 740 for requests from clients, (2) Definition of DTD document for responses 746 from the real-time tariff and import s data system 120, and (3) Implementation of XML parsers (e.g.~, parsers 744 and 766), which retrieve data from XNIL documents and convert the data into obj ects.
As mentioned, a DTD document 740 is used to create the structure of the XML
request string (see Appendix L). The DTD document 740 ensures that the request is properly formed for ~ o processing by the real-time tariff and import data system 120. The following is an example of a valid XML request message 754 prepared and sent by XML client 102C:
<!DOCTYPE TARIFFMESSAGE SYSTEM
"HTTP ://W W W . WEBSITE. COM:7001 /MES SAGE.DTD">
<TARIFFMESSAGE ENCRYPTIONMETHOD= "1"
L5 DTDVERSION= "I">
<! [CDATA[ ENCODED XML REQUEST ]]>
</TARIFFMESSAGE>
The Text attribute ([CDATA[...]]) in the TarifflYlessage request contains a valid XML
request string encrypted with a secret key that is provided to clients. An example of a valid XML
o request string (before it is encoded) is as follows:
<!DOCTYPE TFEEDREQUEST SYSTEM
"HTTP ://W W W . WEBSITE. COM:7001 /TARREQUEST.DTD">
<TFEEDREQUEST>
PIN="XXXX"
>. 5 ORIGINCOUNTRY="CA"
SHIPMENTCOUNTRY="CA"
DESTINATIONCOUNTRY="CG"
OUTPUTFORMAT=" 1 ">
<CURRENCY TRANSACTIONCUR="CAD"
o CONVERSIONCUR="CAD"/>
<DTREQUEST ACCESSCODE="2" INPUTCODETYPE="1"
PRODUCTCODE="010111" VALUE="500000" COSTOFTRANSPORT="SO"
INSURANCECOST="50" OTHERCOST="50">
<UNITS>

<UNIT NBOFUNIT=" 1" UNITCODE="4"/>
</UNITS>
</DTREQUEST>
</TFEEDREQUEST>
An example of XML response string is as follows:
<!DOCTYPE TFEEDREPLYSYSTEM
"HTTP://WWW. WEBSITE.COM/TARREPLY.DTD">
<TFEEDREPLY>
<TFEEDREPLY STATUS="0" HSCODE="1212121212" MESSAGE="OIL" NOTES="">
Lo <DUTY DUTY="500"/>
</TFEEDREPLY>
2. Web (i.e., ActiveXlCOM) Clients - The real-time tariff and import data system 120 accommodates Web clients 102A using ActiveX/COM components, as shown in FIG.s 8A-C.
With this type of client, a standard Web browser 806 is used by the client 102A, as is shown in L5 FIG. 8A. Using a browser, a client 102A generates a request 802, e.g., an HTML form, and transmits the request 802 to the real-time tariff and import data system 120.
Request 802 is serviced by the application servers 130. Request 802 contains all of the required information for conducting duty, import tax, and/or total landed cost calculations, depending on the user's selected output. Request 802 is well formed, since the client is prompted to enter all inputs o needed to process the request and the inputs are preferably validated. As discussed with respect to FIG. 4, a servlet 424 on server cluster 130 picks up request 802, retrieves the data (i.e., inputs) and processes the request by calculating the requested duty, import tax and/or total landed cost.
A more detailed view of the configuration of client 102A is shown in FIG. 8B.
An ActiveX/COM component 810 is loaded onto client device 102A to make the functionality of the a s real-time tariff and import data system 120 available to the client application 820, via Web browser 806. Functionally, component 810 acts as a translator between the client's Web-based application 820 and the real-time tariff and import data system 120 functionality. Component 810 simplifies processing by translating client application requests into XML
requests 802. All of the XML formatting and encryption is done by component 810. Loading component 810 on s o client 102A may require registration with the real-time tariff and import data system 120, depending on the embodiment. To use component 810, an encryption method is set internally, when encryption is used. The encryption method defznes the encryption key to be used for communication with the real-time tariff and import data system 120. Setting the encryption method is accomplished using the appropriate "set" methods of component 810.

Additionally, inputs 812 entered via the client's Web-based application 820 are incorporated into XML request 802 using appropriate.set methods of component 810. Use of such set methods for assigning attribute values is known in the art, so not discussed in detail herein. The following is a preferred embodiment of an interface definition used by the ActiveX/COM component 810 with client application 820:
interface ISingleRequestSession : IDispatch HRESULT ProcessRequest();
HRESULT setEncryptionKey([in] BSTR EncryptionKey);
~ o HRESULT setEncryptionMethod([in] BSTR EncryptionMethod);
HRESULT setDtdVersion([in] BSTR DtdVersion);
HRESULT getHSCode([out,retval] BSTR'~ HSCode);
HRESULT getStatus([out,retval] BSTR* Status);
HRESULT getMessage([out,retval] BSTR* Message);
L5 HRESULT getCustomTarifRate([out,retval] BSTR*
CustomTarifRate);
HRESULT getPerUnitCusTarif([out,retval] BSTR* PerUiutCusTarif);
HRESULT getProductBaseUnit([out,retval] BSTR
ProductBaseUnit);
o HRESULT getDutyAmount([out,retval] BSTR * DutyAmount);
HRESULT getTaxCount([out,retval] int* TaxCount);
HRESULT getCategory([in]~int index,[out,retval] BSTR* Category);
HRESULT getTaxRate([in] int index,[out,retval] BSTR* TaxRate);
HRESULT getPerUnitTax([in] int index,[out,retval] BSTR*
>.5 PerUnitTax);
HRESULT getTaxBaseUnit([in] int index,[out,retval]
BSTR*TaxBaseUnit);
HRESULT getTaxAmount([in] int index,[out,retval] BSTR*
TaxAmount);
c o HRESULT getTaxName([in] int index,[out,retval] BSTR* TaxName);
HRESULT getSumTaxes([out,retval] BSTR* SumTaxes);
HRESULT getValue([out,retval] BSTR* Value);
HRESULT getCostOfrransport([out,retval] BSTR* CostOfTransport);
HRESULT getInsuranceCost([out,retval] BSTR* InsuranceCost);

HRESULT getOtherCosts([out,retval] BSTR* OtherCosts);
HRESULT getTotalLandedCost([out,retval] BSTR* TotalLandedCost);
HRESULT getServerAddress([out,retval] BSTR* ServerAddress);
HRESULT setPinNmnber(jin] BSTR PinNumber);
HRESULT setShipmentCountry([in] BSTR ShipmentCountry);
HRESULT setOriginCountry([in] BSTR OriginCountry);
HRESULT setDestinationCountry([in] BSTR DestinationCountry);
HRESULT setOutputFormat([in] BSTR OutputFormat);
HRESULT setProductCode([in] BSTR ProductCode);
~o HRESULT setValue([in] BSTR Value);
HRESULT setUnit([in] BSTR NbOfUnit, [in] BSTR UnitCode, [in] int UnitIndex);
HRESULT setCostOfTransport([in] BSTR CostOfTransport);
HRESULT setliisuranceCost([in] BSTR InsuranceCost);
~5 HRESULT setOtherCost([in] BSTR OtherCost);
HRESULT setCurrency([in] BSTR Currency);
HRESULT setConversionCurrency([in] BSTR ConversionCurrency);
HRESULT setInputCodeType([in] BSTR InputCodeType);
HRESULT setAccessCode([in] BSTR AccessCode);
o HRESULT getNotes([out,retval] BSTR* Notes);
HRESULT getTaxNote([in] int,index,[out,retval] BSTR~' TaxNote);
FIG. 8C illustrates a client-side view of a method 850 of interaction between client 120A
(with the ActiveX/COM component 810) and the real-time tariff and import data system 120.
Component 810 receives inputs 812 and creates one or more corresponding requests 856A-C, in :5 step 854, according to the appropriate DTD. Using the DTD minimizes the potential for XML
errors, because the XML request string 802 built is inherently valid and well formed. Encryption and decryption will also be.valid, minimizing the potential for encryption errors. As an example, the request 856A, in step 858, is formed into an XML request string 802, using a ProcessRequest() method of component 810. Component 810 sends XML request string 802 to o server 132 and/or 134.
In step 860, the real-time tariff and import data system 120 processes the requests and returns an YML response to component 810. The response will be in the form of an XML
response string 804 that provides duty, tax, and/or total landed cost values, in accordance with the user's selected output. Component 810 decrypts the XML response 804 with an appropriate encryption key (i.e., the public key of system 120). The XML response string.804 is then parsed by component 810. All values are extracted from the XML response string and set in the component. The client application retrieves desired values from the response by using the appropriate "get" method 814 for each value needed. Each response value has its appropriate s "get" method. The values are combined in step 864 and provided to the client application 820, in step 866.
3. .lava Clients - The real-time tariff and import data system 120 provides a set of Java classes, embodied in Tariffjar 910, loaded on the client 102B that prepares and sends an XML request 902 to the server 132 or 134, as is shown in FIG. 9A. An application (e.g., client ~o application 920) uses the Java classes 910 by calling one method to pass a request object 912 and by receiving a reply object 914. Using Java to prepare and send XML request string 902 is similar to the use of ActiveX/COM component 810 discussed above. Tariffjar 910 acts as a translator between client application 920 and the real-time tariff and import data system 120.
That is, Java classes 910 allow XML requests to be sent by client 102B and XML
responses to be received by client 102B.
To use the Java classes 910, the classes must first be added to the client's class path or project environment, which makes the Java classes available to the client application 920. An encryption method and encryption key must also be set in the Tariffj ar 910 classes to facilitate secure communications. Thereafter, processing a request merely requires calling one method, a o ProcessRequest(), and passing a request object containing the input parameters discussed previously (see also Appendix H).
The ProcessRequest() method of Tariffjar 910 builds a valid XML request string from the user's inputs. This approach minimizes XML errors, since the XML request string will necessarily be valid and well formed according to its DTD. Also, given that the a 5 ProcessRequest() method builds the request, encryption and decryption will also be valid, minimizing encryption errors. After building the XML request string 902, the Java classes 910 send the XML request to servers 132 and134, receives the XML response message, and decrypts the XML response string 904 therefrom. The Java classes 910 decrypt the XML
response string 904 with the appropriate encryption key (e.g., system 120's public key).
o The Java classes 910 parse the XML response string. All values are extracted from the XML response string 904 and set in the Java classes. A response object 914 is then returned to the client application 920. These values can be retrieved by the client application 920 by calling the appropriate "get" methods of the response object. Each response value has its appropriate "get" method. All values can be retrieved and output in client application 920.

FIG. 9B shows a client-side view of a method 950 of interaction between a client appli-cation 920 and server cluster 130. ~In step 952, the client application 920 gathers the inputs from the user and generates one or more request objects, 956A-C. In step 958, the Java classes 910 receive the request object 912 (or 956A) and gets the needed inputs from the request object and s then creates an XML request string 902. The request string 902 is then sent (in an AML request message) to the real-time tariff and import data system 120 servers 132 and 134, which processes the request, in step 960. An XML response string (in a response message) is then returned to the Java classes 910 from the servers 132 and 134. The Java classes 910 get data from the XML
response string and form response objects 914, in step 962. The response includes the duty, tax, ~ o and/or total landed cost, as requested by the user. The client application 920 retrieves values from the response objects 914 by calling the appropriate "get" methods and combines the values, in step 964. The values are then output to the client application 920, in step 966.
Part III - Calculations The following is the preferredgembodiment of the manner of calculating duties and taxes associated with an international transaction. The methods are implemented by the duty calculation engine 412, import tax calculation engine 418, and total landed cost calculation engine 426, previously discussed with respect to FIG. 4. The duty calculation engine 412 accesses relevant tariff rates for a specified product and destination country from the database 146 and applies the lowest of such applicable rates to arrive at a duty calculation. The import tax >. o calculation engine 418 accesses relevant databases of country specific import tax rates, charges and fees and applies them to arrive at import tax costs. The total landed cost calculation engine 426 determines the total landed cost from the duty calculation and the import tax calculation, and any other relevant costs (e.g., transportation and insurance costs).
The inputs for the various engines are gathered from the XML request process previously s described. The inputs for the various engines are described above in Part II
and Appendix H.
Validation of the inputs is performed as the data is input into appropriate fields of, for example, a Web-based request form. The validation occurs by testing inputs against field-based validation criteria, described in Appendix H. Appendix I identifies the returned values for each of the ten (10) possible output formats of the preferred embodiment.
;o 1. Duty (or Tarifj~ Calculation The following tables identify the steps taken by the duty calculation engine 412 to calculate the duty (or tariffs) for a given international transaction. At a macro level, the steps include selecting a duty rate, converting currencies, and calculating the duty fee. The tables include object oriented pseudo code describing calls and method steps used in the process and also describes error codes applicable to the various steps.
Table 4 below shows the steps for selecting a duty rate for a given set of inputs.
Step Processing 1. Verify HS code Tables:

_TariftDescription = (Country.CountryCode of destination country) + "TarrifDescription"

Information:

TariftDescription.HSCode TariffDescription.UnitCode TariffDescription.ApplicableTariff Selection criteria:

TariffDescription.HSCode = HS Code Error processing:

If no record is returned:

Error code: S 110 - The HS code is not in the HS code list for the destination country.

zs Step Processing 2. verify tariff Tables:

preference _TariffCode = (Country.CountryCode of destination country) + "TariffCode"

_TariflScheme = (Country.CountryCode of destination country) + "Tarif~cheme"

Information:

TariffCode.TariffCodeID

TariffCode.Acronym TariffCode. GeneralTariff TariffScheme.CountryCode (optional) Selection criteria:

Tarif~cheme.CountryCode = Country.CountryCode of country of origin of goods _TariffCode.Acronym in TariffDescription.ApplicableTariff Error processing:

If the Country code is not in the items returned by the request, the item containing the general tariff must be selected.

Error code: S 120 - No Tariff code available.

Error code S 120 should be brought to the attention of the system administrator.

Step Processing 3. Select Duty Required:
Rate The specified HS code must be a valid HS
code (see Step 1).

There is an applicable tariff code (-TariffCode.TariffCodeID o NULL) (see Step 2).

Table:

TariffData = (Country.CountryCode of destination country) +"TariffData"

Information:

TariffData.AddValoremRate TariffData.PerUnit TariffData.CalculationMethod Selection criteria:

TariffData.HSCode = TariffDescription.HSCode TariffData.TariffCodelD = TariffCode.TariffCodelD

Selecting a tariff:

If more than one rate is available, the application selects the highest.

Error processing:

If no tariff is returned:

Error code: 5130 - No tariff code available for HS code specified in request.

Error code 5130 should be brought to the attention~of the system administrator.

Step Processing 4. Convert per-unitRequired for output formats 1, 3, 7 and 9 rate (See Appendix I) If the conversion currency of the request (Request.ConversionCur) is the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedPerUnitRate = TariffData.PerUnit Else If the country's customs tariff currency is "USD" Then ConvertedPerUnitRate = Conversion of per-unit rate from "USD" to the conversion currency of the request (See Table 5) Else USDPerUnitRate = Conversion of per-unit rate to "USD" (See Table 5) ConvertedPerUnitRate = Conversion from USDPerUnitRate to the conversion currency of the request (See Table 5) TABLE 4 - Duty Rate Selection Table 5 shows the steps for converting between currencies among countries, which is useful in the calculations, since typically the origin country, shipment country, and destination country may have different currencies.

WO 01/93125 PCT/IBO1/01204 .
Step Processing 1. Find rate Tables:

Country Currency Information:

Currency.Rate Selection criteria:

Country.CountryCode = <Country ISO code>

Currency.Code = <Currency ISO code>

Note - the currency ISO code can come from:

The request (TransactionCur; ConversionCur) The Country table (Country.CurrencyCode;

Country.TariffsCurrency) Error processing:

If no item is returned:

5210 - No exchange rate available for the following currency code: <Currency ISO code>.

Error code 5210 should be brought to the attention of the system administrator.

2. Calculate convertedTo convert to USD (as an example) amount Amount / Currency.Rate To convert from USD

Amount * Currency.Rate TABLE 5 - Currency Conversion Table 6 shows the steps for calculating the duty (or tariff), which incorporates the steps in Table 4 for selecting a duty (or tariff) and the steps of Table 5 for converting currencies.

Step Processing 1. Select a tariffSee Table 4.

2. Identify applicableTable:

basis for duty Country calculation CalculationBase Information:

CalculationBase.CostOfGoods CalculationBase.Transport CalculationBase.InsuranceCost CalculationBase.OtherCost Selection criteria:

Country.CountryCode = Destination Country code CalculationBase.CaculationBasell~ _ Country.DutyFeeCalculationBase 3. Calculate applicableApplicable Fees = 0 duty If CalculationBase.CostOfGoods is TRUE Then Applicable Fees = Request.PriceOfGoods If CalculationBase.Transport is TRUE Then .

Applicable Fees = Applicable Fees +

Request. CostOf Transport If CalculationBase.InsuranceCost is TRUE
Then Applicable Fees = Applicable Fees +

Request.InsuranceCost If CalculationBase.OtherCost is TRUE Then Applicable Fees = Applicable Fees + Request.OtherCost Step Processing 4. Convert applicableIf the transaction currency (Request.TransactionCurrency) is 'fees the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedApplicableFees = ApplicableFees Else If the transaction currency is "USD"
Then ConvertedApplicableFees = Conversion of applicable fees from "USD" to the tariff currency (See Table 5) Else USDApplicableFees = Conversion of applicable fees to "USD"

(See Table 5) ConvertedApplicableFees = Conversion of USD
applicable fees to the tariff currency (See Table 5) Step Processing 5. Convert quantitiesTables:

UnitCode TariffDescription Information:

UnitCode.UnitType UnitCode.ConversionFactor TaxiffDescription.UiutCode Methods:

If Request.ProductBaseUnit =

TariffDescription.UnitCode, Then ConvertedQuantity = Request.NbOfLTnit Else If the unit type of Request.ProductBaseUnit is different from the type associated with the product unit measure; Then Error code: 5560 - The base unit of the products is incompatible with the base unit specified in the request.

Else ConvertedQuantity = Request.NbOfUnit UnitCode.ConversionFactor Remarks: To find out the base unit type, refer to the UnitCode.UnitType field.

Step Processing 6. Calculate duty AddValoremFee = (ConvertedApplicableFees TariffData.AddValoremRate) PerUnitFee = (ConvertedQuantity * TariffData.PerUnit) If the tariff calculation method is "Applied Both"

(,TariffData.CalculationMethod = I O Then DutyFee = AddValoremFee + PerUnitFee Else If the tariff calculation method is "Applied Greatest"

(-TariffData.CalculationMethod = 20) Then If AddValoremFee > PerUnitFee Then DutyFee = AddValoremFee Else DutyFee = PerUnit'Fee Else If the tariff calculation method is "Applied Smallest"

~TariffData.CalculationMethod = 30) Then If AddValoremFee > PerUnitFee Then DutyFee = PerUnitFee Else DutyFee = AddValoremFee Step Processing 7. Convert duty If the conversion currency of the request (Request.ConversionCur) is the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedDutyFee = DutyFee Else If the country's customs tariff currency is "USD" Then ConvertedDutyFee = Conversion of duty fee from "USD"

to the conversion currency of the request (See Table 5) Else USDDutyFee = Conversion of duty fee from "USD" (See Table 5) ConvertedDutyFee = Conversion of USD duty fee to the conversion currency of the request (See Table 5) TABLE 6 - Duty Fee Calculation 2. Tax Calculation The following tables identify the steps tal~en by the import tax calculation engine 418 to calculate the tax for a given international transaction. At a macro level, the steps include selecting a tax rate and calculating the applicable taxes. The tables include object oriented pseudo code describing calls and method steps, and also describes error codes for the various steps.
LO

Table 7 below, shows the steps for selecting a tax rate for a given set of inputs.
Step Processing 1. Verify HS Table:
code HSDescription Information:

HSDescription.HSCode Selection criteria:

HSDescription.HSCode = Input.HS Code[ 1:6]

Error processing:

If no record is returned:

Error code: 5410 - The HS code is not in the standard HS code list.

2. Identify Tables:

categories HS CategoryInterval Information:

HSCategorylnterval.CategorylD

Selection criteria:

HSCategoryInterval.HSFrom >= Input.HS Code[1:6]

HSCategorylnterval.HSTo <=Input.HSCode[1:6]

Error processing:

If no category is returned:

Error code: 5420 - The product does not belong to any product category.

Error code 5420 should be brought to the attention of the system administrator.

Step Processing 3. Select applicableTables:

taxes ApplicableTax Tax Information:

Tax.TaxeAcronym Tax. TaxeRate Tax.TaxePerUnit Tax.TaxeUnitBase Method:

For each category identified in the previous step:

Select all taxes applicable to the category.

Eliminate those taxes that were selected more than once (duplicates).

Step Processing 4. Convert par-unitApplicable to output formats 4, 6, 7 and 9 taxes For each tax selected, the applicable per-unit tax must be converted if it is greater than zero.

If the conversion currency of the request (Request.ConversionCurrency) is the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedPerUnitTax = Taxe.TaxPerUnit Else If the country's customs tariff currency is "USD" Then ConvertedPerUnitTax = Conversion of per-unit tax from "USD" to the conversion currency of the request (See Table 5) Else USDPerUnitTax = Conversion of per-unit tax to "USD (See Table 5) ConvertedPerUnitTax = Conversion of USDPerUnitTax to the conversion currency of the request (See Table 5) TABLE 7 - Tax Rate Selection Table 8 shows the steps for calculating the import tax, which incorporates the steps in Table 6 for selecting a tax rate and the steps of Table 5 for converting currencies.

Step Processing 1. Select applicableSee Table 7.

taxes 2. Identify applicableTables:

basis for tax Tax calculation CalculationBase Information:

CalculationBase.CostOfGoods CalculationBase.Transport CalculationBase.InsuranceCost CalculationBase.OtherCost CalculationBase.DutyFee Selection criteria:

CalculationBase.CalculationBaselD =

Tax.TaxCalculationBase Step ~ Processing 3. Calculate taxableTaxable Fees = 0 fees If CalculationBase.CostOfGoods is TRUE Then Taxable~Fees = Taxable Fees + Request.Value If CalculationBase.Transport is TRUE Then Taxable Fees = Taxable Fees + Request.CostOtTransport If CalculationBase.InsuranceCost is TRUE
Then Taxable Fees = Taxable Fees + Request.InsuranceCost If CalculationBase.OtherCost is TRUE Then Taxable Fees = Taxable Fees + Requete.OtherCost If CalculationBase.DutyFees is TRUE Then Taxable Fees = Taxable Fees + Calculated Duty Fee (See Table 6) 4. Calculate surtaxNote: It is important to verify that a given on tax is not applied as taxes a surtax on a second tax which is itself applied to the first tax. In the event of such a loop, an error code must be returned.

Error code: 5440 - System error. Unable to calculate taxes.

Error code 5440 should be brought to the attention of the system administrator along with the information pertaining to the request.

Calculate the tax with surtax.

Add the resulting amount to the Taxable Fees.

Repeat the operation for all taxes on which a surtax applies.

Step Processing 5. Convert taxableIf the transaction currency (Request.TransactionCur) fees is the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedTaxableFees = ApplicableFees Else If the transaction currency is "USD"
Then ConvertedTaxableFees = Conversion of taxable fees from "USD" to the tariff currency (See Table 5) Else USDTaxableFees = Conversion of to "USD" (See Table 5) ConvertedTaxabIeFees = Conversion of USD
taxable fees to the tariff currency (See Table 5) Step Processing 6. Convert quantitiesTable:

UnitCode Tax Information:

UnitCode.UnitType UnitCode. ConversionFactor Tax.UnitCode Methods:

If Request.ProductBaseUnit = Tax.UnitCode Then ConvertedQuantity = Request.NbOfUnit Else If the unit type of Request.ProductBaseUnit is different from the type associated with the product base unit Then Error code: 5560 - The base unit of the products is incompatible with the base unit specified in the request.

Else ConvertedQuantity = Request.NbOfUnit UnitCode.ConversionFactor Remarks:

To find out the base unit type, refer to the UnitCode.UnitType field.

Step Processing 7. Calculate taxesTransactionTax = (Converted Taxable Fees * Tax.TaxeRate) UnitTax = (ConvertedQuantity * Tax.TaxPerUnit) If the tax calculation method is "Apply Both"

(Tax.CalculationMethod) =10 Then Tax = TransactionTax + Unit Tax Else If the tax calculation method is "Applied Greatest"

(Tax.CalculationMethod = 20) Alors If Transaction Tax > Unit Tax Then Tax = Transaction Tax Else Tax = Unit Tax Else If the tax calculation method is "Applied Smallest"

' (Tax.CalculationMethod = 30) Then If Transaction Tax > Unit Tax Then Tax = Unit Tax Else Tax = Transaction Tax Step Processing 8. Convert taxes If the conversion currency of the request (Request.ConversionCurrency) is the same as the country's customs tariff currency (Country.TariffsCurrency) Then ConvertedTax = Tax Else If the country's customs tariff currency is "USD" Then ConvertedTax = Conversion of taxes from "USD"
to the conversion currency of the request (See Table 5) Else USDTax = Conversion of taxes to "USD" (See Table 5) ConvertedTax = Conversion of USDTax to the conversion currency of the request (See Table 5) TABLE 8 - Import Tax Calculation 3. Total Landed Cost (TLC) Calculation s The TLC engine uses the output from the duty calculation engine and the tax calculation engine, along with user inputs described in Part II, to arrive at a total landed cost, as follows:
TLC = Duty Fee + Impost Taxes + Price of Goods +
Cost of Trayaspo~t + Ihsu~ahce Costs + Other Costs ~o The invention may be embodied in other specific forms without departing from the spirit or central characteristics thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by appending claims rather than by the foregoing description, and all changes that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

APPENDIX A/B - Country and Currency Codes Following is a list of country and currency codes:
Country CountryCurrency Currency Code Code dorra ad dorran Peseta P

rated Arab Emirates ae td. Arab Emir. Dirham D

f hanistan of f anistan Af hani A

tigua and Barbuda ag astern Carribean Dollar CD

guilla ai astern Carribean Dollar CD

lbania al lbanian Lek L

etherlands Antilles an Antillian Guilder G

gola ao olan New Kwanza ON

tartica a S Dollar SD

gentina ar gentine Peso S

erican Samoa ~ as S Dollar SD

ustria at Euro UR

ustralia au ustralian Dollar UD

ba aw ban Florin WG

osnia and Herze ovina a ahraini Dinar HD

arbados b arbados Dollar BD

angladesh d an ladeshi Taka DT

e1 ium a uro UR

urkina Faso f CFA Franc BEAC

ulgaria al arian Lev GL

ahrain h ahraini Dinar HD

urundi i urundi Franc IF

enin j CFA Franc BEAC

ermuda m ermudian Dollar MD

runei Darussalam n runei Dollar ND

olivia o olivian Boliviano OB

razil r razilian Real RL

ahamas s ahamian Dollar SD

hutan t hutan Ngultrum TN

ouvet Island v orwe 'an Kroner OK

otswana w otswana Pula WP

elize z elize Dollar ZD

WO 01/93125 , .. PCT/IBO1/01204 Canada ca Canadian Dollar CAD

Cocos (Keeling Islands cc ustralian Dollar UD

Congo (Kinshasa) cd CFA Franc BEAC

Central African Re ublic cf CFA Franc BEAC

Con o (Brazzaville cg CFA Franc BEAC

Switzerland ch Swiss Franc CIiF

Cote d'Ivoire ci CFA Franc BEAC

Cook Islands ck ew Zealand Dollar ZD

Chile c1 Chilean Peso CLP

Cameroon cm CFA Franc BEAC

China cn Chinese Yuan Renminbi CNY
~

Colombia co Colombian Peso COP

Costa Rica . cr Costa Rican Colon CRC

Cuba cu Cuban Peso CUP

Cape Verde cv Ca a Verde Escudo CVE

Christmas Islands cx ustralian Dollar UD

C rus cy Cyprus Pound CYP , Czech Re ublic cz Czech Koruna CSK

Germany de uro UR

jibouti dj jibouti Franc JF

enmark dk uro UR

ominica dm astern Carribean DollarCD

omincan Re ublic do ominican Peso OP

a lgeria dz lgerian Dinar ZD

Ecuador ec cuador Sucre CS

stoma ee stonian Kroon EK

t a tian Pound GP

Western Sahara eh oroccan Dirham ritrea er ussian Rouble UB

S ain es uro UR

thio is et thio ian Birr TB

uro can Union eu uro UR

inland fi uro UR

iji iji Dollar JD

alkland Islands (Malvinas) fk alkland Islands Pound KP

icronesia, Federative Statesfin S Dollar SD
Of aroe Islands fo apish Krone KK

rance fr uro UR

Gabon ga CFA Franc BEAC

Uiuted Kingdom gb uro UR

Grenada gd astern Carnbean Dollar CD

Ghana Ghanaian Cedi GHC

Gibraltar gi United Kin dom Pound GBP

Greenland g1 apish Krone ~ KK

Gambia gm Gambian Dalasi GMD

Guinea gn Guinea Franc GNF

Guadelou a rench Franc RF

quatorial Guinea q CFA Franc BEAC

Greece uro UR

Geor is South gs nited Kin dom Pound GBP

Guatemala Guatemalan Quetzal GTQ

Guam gu S Dollar SD

Guinea-Bissau gw CFA Franc BEAC

Guyana gy Guyanan Dollar GYD

on Kong ilc ong Kong Dollar eard and MacDonald Islands ustralian Dollar UD

onduras onduran Lem ira Croatia Croatian Kuna aiti t aitian Gourde TG

up ary a ungarian Forint donesia 'd donesian Rupiah R

eland 'e uro UR

srael i1 sraeli New Shekel S

Tildia in dian Ru ee Iraq i a i Dinar QD

an it avian Rial celand is celand Krona SK

tal it . uro UR

Jamaica 'm Jamaican Dollar JMD

Jordan 'o Jordanian Dinar JOD

Japan Ja anese Yen Y

enya a enyan Shillin S

Cambodia (Kam uchea) am uchean Riel Cambodian Riel 'ribati ustralian Dollar UD

Comoros Comoros Franc St Kitts and Nevis astern Carribean DollarCD

WO 01/93125 _ PCT/IBO1/01204 orea, North orth Korean Won W

orea, South orean Won W

uwait uwaiti Dinar WD

Cayman Islands Cayman Islands Dollar YD

azakhstan azakhstan Tenge T

aos la ao Ki AK

ebanon 1b ebanese Pound BP

Saint Lucia lc astern Carnbean Dollar CD

iechtenstein 1i Swiss Franc CHF

Sri Lanka 1k Sri Lanka Ru ee KR

Liberia 1r Iberian Dollar RD

esotho is esotho Loti SL

Lithuaiua It ithuanian Litas TL

uxembour 1u uro UR

atvia 1v atvian Lats VL

ibya 1y ibyan Dinar YD

orocco a oroccan Dirham onaco c rench Franc RF

adagascar g alaysian Rin git arshall Islands S Dollar SD

ali 1 CFA Franc BEAC

anmar (Burma) yanmar Kyat on olia ongolian Tugrik T

acau o acau Pataca OP

orthern Mariana Islands p S Dollar SD

artinique q rench Franc RF

auritania auritanian Ouguiya O

ontserrat s astern Carnbean Dollar CD

alta t altese Lira TL

I
auritius a auritius Ru ee aldives my aldive Rufiyaa alawi w alawi Kwacha WK

Mexico exican Peso ',Malaysia y alaysian Rin it ozambique Zz ozambi ue Metical ZM
-I na amibia Dollar AD
~Namibia Niger a CFA Franc BEAC

Norfolk Island ustralian Dollar UD

igeria g igerian Naira GN

etherlands 1 uro UR

orway o orwegian Kroner ~ OK

a al p epalese Ru ee R

a~ ustralian Dollar UD

eutral Zone t uwaiti Dinar WD

iue a ew Zealand Dollar ZD

ew Zealand ew Zealand Dollar ZD

Oman om Omani Rial OMR

anama a anamanian Balboa AB

eru a eruvian Nuevo Sol EN

apua New Guinea g a ua New Guinea Kina GK

hili roes h hilippine Peso HP

akistan k akistan Ru ee KR

oland 1 olish Zloty LZ

St Pierre and Miquelon m rench Franc RF

itcairn Island n ew Zealand Dollar ZD

uerto Rico r S Dollar SD

ortugal t ortuguese Escudo TE

alau w S Dollar SD

aragua y ara ay Guarani YG

Qatar . a Qatari Rial QAR

Bunion a rench Franc RF

omania o omanian Leu OL

ussian Federation ussian Rouble UB

Saudi Arabia sa Saudi Riyal SAR

Solomon Islands sb ustralian Dollar UD

Seychelles and Dependensies sc Seychelles Rupee SCR

Sudan sd Sudanese Dinar SDD

Sweden se uro UR

Singapore s Singa ore Dollar SGD

St Helena sh United Kingdom Pound GBP

Slovenia si Slovenian Tolar SIT

Svalabard and Jan Mayen Islandss' orwegian Kroner OK

Slovakia ~ sk Slovak Koruna SKK

Sierra Leone s1 Sierra Leone Leone SLL

San Marino sm talian Lira TL

ISene al sn CFA Franc BEAC

Somalia so Somali Shillin SOS

Suriname sr Suriname Guilder SRG

Sao Tome and Principe st Sao Tome/Princi a DobraSTD

EI Salvador sv 1 Salvador Colon SVC

Syria sy Syrian Pound SYP

Swaziland sz Swaziland Lilangeni SZL

Turks and Caiscos Islands c S Dollar SD

Chad d CFA Franc BEAC

rench Southern Terntories f rench Franc RF

1'0 o g CFA Franc BEAC

Thailand h Thai Baht THB

Tokelau k ew Zealand Dollar ZD

Tunisia Tunisian Dinar TND

Ton a o Tongan Pa'anga TOP

Turkey Turkish Lira TRL

Trinidad and Tobago t Trinidad/Tobago Dollar TD

Tuvalu ustralian Dollar UD

Taiwan ~ Taiwan Dollar TWD

Tanzania z Tanzanian Shilling TZS

sine a sine Hryvnia AH

ands ands Shilling GS

sited States Minor Outl ~ng S Dollar SD
Islands sited States s S Dollar SD

ru ay y ruguayan Peso atican Ci a talian Lira TL

Saint Vincent-Grenadines c astern Carribean DollarCD

enezuela a enezuelan Bolivar EB

ritish Virgin Island vg US Dollar SD

jVir 'n Islands oftheUnited i US Dollar USD
States 'Viet Nam Vietnamese Dong Vanuatu anuatu Vatu VUV

'Walks and Futuna Islands f Central Pacific Franc CFP

Samoa ws Samoan Tala WST

~~Yugoslavia ugoslav Dinar South Africa a South African Rand AR

Zambia m ambian Kwacha MK

Zimbabwe w imbabwe Dollar WD

APPENDIX C - Unit Codes Following is a list of unit codes:
Base Unit (Code PLATO/HECTOLITER ~ 154 23 %VOL PER HECTOLITRE ' 102 40 %VOL PER IIVVIPERIAL GALLON 103 40 %VOL PER LITRE 98 40 %VOL PER US GALLON 107 40 1,000,000 STICKS OF TOBACCO 165 27 100 CONTAINERS 179 ~ 1 100 KILOGRAMS PER 1% BY WEIGHT OF SUCROSE 212 543 100 KILOGRAMS/BR (Gross) 106 15 100 KILOGRAMS/NET MAS (Net weight on dry matter) 75 12 ;ARREL (BEER AND FERMENTED ALCOHOL) 59 4 BARREL (PETROLEUM) 49 36 .DU OF 1089.6 KG 187 29 ~ECQUEREL 196 7 idon (ne pas utiliser) 888 0 .OX 197 34 ~TU (HEATING CAPACITY) 13 45 :ALORIE (HEATING CAPACITY) 133 45 ;ARAT 33 ~ 2 ;C (kilowatt-power * 26.667, used for electrical 131 44 engines) JARETTES,CIGARS,CIGARILLOS LENGHT (inches) 129 43 sARETTES,CIGARS,CIGARILLOS LENGHT (mm) 112 43 OF PURE ALCOHOL ~ 177 18 /L (Hull capacity) 148 35 BIC CENTIMETER (CC) OF ENGINE DISPLACEMENT 99 21 ICKER PAIRS (10 pairs) 186 3 iGAJOULE 13 (SEMI-GROSS WEIGHT) 69 25 OF CHROMIUM (Cr) 122520 OF FISSILE ISOTOPE(GFl) 108508 OF GOLD (Au) 115513 OF IRIDIUM (Ir) 119517 OF NICKEL (Ni) 123521 OF OSMIUM (Os) 121519 OF PALLADIUM (Pd) 117515 OF PLATINUM (Pt) 116514 OF RHODIUM (Rh) 1 516 OF RUTHENIZJM (Ru) 120518 OF SILICON (Si) 127525 OF SILVER (Ag) 114512 OF TUNGSTEN (W) 124535 OF VANADIUM (V) 125523 S CHOLINE CHLORHYDRATE (CSH14CLN0) 371529 S DIPHOSPHORUS PENTAOXIDE (P2O5) 32951C

8 DIPOTASSIUM OXIDE (K20) 332511 S DIPOTASSIUM PENTAOXIDE (K205) 399541 S METHYLAMINE (CHSN) 37453C

S NITROGEN (I~ 326509 S OF AWiYDIOUS MORPHINE CONTENT (C17H19NO3) 377531 S OF COPPER CONTENT (Cu) 39353S

S OF HYDROGEN PEROXIDE (H2O2) 314505 S OF LEAD CONTENT (Pb) 39053~

S OF MAGNESIUM (Mg) 38453E

S OF MOLYBDENUM (Mo) 38753 i S OF PHOSPHORUS PENTOXll~E (P2O5) 31750E

AMS OF POTASIUM HYDROXIDE (KOH) 30550 AMS OF POTASSIUM OXIDE (K20) 31150 AMS OF SODIUM HYDROXIDE (NaOH) 30850 AMS OF SUCROSE (C12H22O11) 20452 AMS OF LRANIUM (L~ 32050 AMS OF ZINC (Zn) 14650 AMS PER 1% BY WEIGHT OF SUCROSE 21054 AMS VOLATILE ORGANIC COMPOUND(VOC) 40254 OSS (i.e. 12 DOZENS) 37 CTOGRAM OF GOLD (Au) 40451 CTOGRAM OF PLATINUM (Pt) 40351 CTOGRAM OF SILVER (Ag) 40551 ~RSE POWER 1413 ~HE 17 (INSULIN UNIT) 128 52 ~OGRAM (SEMI-GROSS WEIGHT) 70 2 ~OGRAM OF 90% DRY SUBSTANCE 93 1 GRAMS CHOLINE CHLORHYDRATE (C5H14CLN0) 150529 GRAMS DIPHOSPHORUS PENTAOXIDE (P2O5) 110510 GRAMS DIPOTASSIUM OXll~E (K20) 111511 GRAMS DIPOTASS1UM PENTAOXIDE (I~2O5) 189541 GRAMS DRY AlR 40 13 GRAMS METHYLAM1NE (CHSN) 151530 GRAMS NITROGEN (I~ 109509 GRAMS OF ANHYDIOUS MORPHINE CONTENT (C17H19N03) 166531 GRAMS OF CHROMIUM (Cr) 357520 GRAMS OF COPPER CONTENT (Cu) 175539 GRAMS OF FISSILE ISOTOPE(KFl~ 321508 GRAMS OF GOLD (Au) ~ 336 51 GRAMS OF HYDROGEN PEROXIDE (H2O2) 89 50 GRAMS OF IRIDIUM (Ir) 348 51 GRAMS OF LEAD CONTENT (Pb) 174 53 GRAMS OF MAGNESIUM (Mg) 172 53 GRAMS OF MANGANESE (Mn) 170 53 GRAMS OF MOLYBDENUM (Mo) 173 53 GRAMS OF NICKEL (Ni) 360 52 GRAMS OF OSMICTM (Os) 354 51 GRAMS OF PALLADIUM (Pd) 342 51 GRAMS OF PHOSPHORUS PENTOXIDE (P2O5) 90 50 GRAMS OF PLAT1NLJM (Pt) 339 51 GRAMS OF POTASIUM HYDROXIDE (KOH) 86 50 GRAMS OF POTASSIUM OXIDE (K20) 88 50 GRAMS OF RHODIUM (Rh) 345 51 GRAMS OF RUTHENIUM (Ru) 351 51 GRAMS OF SILICON (Si) 366 52 GRAMS OF SILVER (Ag) 333 51 GRAMS OF SODIUM HYDROXIDE (NaOH) 87 50 GRAMS OF SUCROSE (C12H22O11) 206 52 GRAMS OF TUNGSTEN CONTENT (W) 171 53 GRAMS OF LI~~IUM (LT) 91 50 GRAMS OF VANADIUM (V) 363 52 GRAMS OF VOLATILE ORGANIC COMPOUND(VOC) 193 GRAMS OF ZINC (Zn) 143 50 GRAMS PER 1 % BY WEIGHT OF SUCROSE 211 54 GRAMSBR (Gross) 26 1 GR.AMS/TOTAL ALCOHOL 100 1 ATT

JR OF VINEGAR ~ 1911 26 JOULE ~ 1 CARAT (200G) 94 ~1BER OR UNIT 18 1 'ANE LEVEL 65 41 NCE (SEMI-GROSS WEIGHT) 77 25 NOES OF SUCROSE (C12H22O11) 207 522 NOES OF ZINC (Zn) 147 509 NOES PER 1% BY WEIGHT OF SUCROSE 213 543 UNCES CHOLINE CHLORHYDRATE (C5H14CLN0) 370 529 UNCES DIPHOSPHORUS PENTAOXIDE (P2O5) 328 51C

UNCES DIPOTASSIUM OXIDE (KZO) 331 511 UNCES DIPOTASSIUM PENTAOXIDE (I~2O5) ' 398 541 UNCES METHYLAMINE (CHSN) 373 530 UNCES NITROGEN (I~ 325 509 UNCES OF ANHYDIOUS MORPHINE CONTENT (C17H19N03) 376 531 UNCES OF CHROMIUM (Cr) 359 52C

UNCES OF COPPER CONTENT (Cu) 392 539 UNCES OF FISSILE ISOTOPE(OFI) 323 508 UNCES OF FISSIONABLE MATERIAL . 302 50C

UNCES OF GOLD (Au) 338 513 UNCES OF HYDROGEN PEROXll~E (H202) . 313 505 UNCES OF IRIDIUM (Ir) 350 517 UNCES OF LEAD CONTENT (Pb) 389 538 UNCES OF MAGNESICJM (Mg) 383 53E

UNCES OF MANGANESE (Mn) 379 534 UNCES OF MOLYBDENUM (Mo) 386 537 UNCES OF NICKEL (Ni) 362 521 DUNCES OF OSMIUM (Os) 356 519 DUNCES OF PALLADIUM (Pd) 344 515 UNCES OF PHOSPHORUS PENTOXIDE (P2O5) 316 506 iUNCES OF PLATINUM (Pt) 341 514 iUNCES OF POTASIUM HYDROXIDE (KOH) 304 502 iUNCES OF POTASSIUM OXIDE (K20) 310 504 iUNCES OF RHODIUM (Rh) 347 516 DUNCES OF RUTHENIUM (Ru) ' 353 518 DUNCES OF SILICON (Si) 368 525 DUNCES OF SILVER (Ag) 335 512 DUNCES OF SODIUM HYDROXIDE (NaOH) 307 503 >UNCES OF TUNGSTEN (~ 381 535 >UNCES OF URANIUM (U) 319 507 )UNCES OF VANADIUM (V) 365 523 >UNCES PER THOUSAND UNITS 81 39 >UNCES VOLATILE ORGANIC COMPOUND(VOC) 401 542 'ER LEAF OR TUBE 137 1 'ERCENTAGE OF ALCOHOL 188 20 'ERCENTAGE OF SULPHUR 96 42 OUND (SEMI-GROSS WEIGHT) 76 2.

OUNDS CHOLINE CHLORHYDRATE (CSH14CLN0) 369 52' OUNDS DIPHOSPHORUS PENTAOXIDE (P2O5) 327 51~

OUNDS DIPOTASSIUM OXIDE (K20) 330 51 OUNDS DIPOTASSIUM PENTAOXIDE (K2O5) 397 54 OUNDS METHYLAMINE (CHSN) 372 53 OUNDS NITROGEN (I~ 324 50 OUNDS OF ANHYDIOUS MORPHINE CONTENT (C17H19N03) 375 53 OUNDS OF CHROMIUM (Cr) 358 52 OUNDS OF COPPER CONTENT (Cu) 391 53 OUNDS OF FISSILE ISOTOPE(PFI) 322 . 50 OUNDS OF GOLD (Au) 337 51:

OUNDS OF HYDROGEN PEROXIDE (H202) 312 50'.

OUNDS OF IRIDIUM (Ir) 349 51' OUNDS OF LEAD CONTENT (Pb) 388 53!

OUNDS OF MAGNESIUM (Mg) 382 53i OUNDS OF MANGANESE (Mn) 378 53~

OUNDS OF MOLYBDENUM (Mo) 385 53' OUNDS OF NICKEL (Ni) 361 52' OUNDS OF OSMIUM (Os) 355 51!

OUNDS OF PALLADIUM (Pd) 343 51:

OUNDS OF PHOSPHORUS PENTOXIDE (P2O5) 315 50i OUNDS OF PLATINUM (Pt) ' 340 51~

OUNDS OF POTASIUM HYDROXIDE (KOH) 303 50;

OUNDS OF POTASSIUM OXIDE (K20) 309 50~

OUNDS OF RHODIUM (Rh) 346 51 ~

OUNDS OF RUTHENI<JM (Ru) 352 51.

OUNDS OF SILICON (Si) 367 52.

OUNDS OF SILVER (Ag) 334 51:

OUNDS OF SODIUM HYDROXIDE (NaOH) 306 50:

OUNDS OF SUCROSE (C12H22O11) 209 52:

OUNDS OF TOTAL SOLUBLE SOLIDS 394 54~

OUNDS OF TUNGSTEN (W) 380 53 'OUNDS OF LTIZANIUM (U) 318 50' 'OUNDS OF VANADIUM (V) 364 52:

'OUNDS OF ZINC (Zn) 153 50' 'OUNDS PER 1% BY WEIGHT OF SUCROSE 214 54 'OUNDS PER THOUSAND UNITS 82 3' 'OUNDS VOLATILE ORGANIC COMPOUND(VOC) 400 54 'OUNDSBR (Gross) 38 1 'ROOF GALLON (US) 57 1 'ROOF LITER 53 1 ;OLL 55 '.CORE (i.e. 20 units) 52 SQUARE YARD

.TICKS OF TOBACCO 63 2 'ETRAJOULE 61 BR (Gross) 14 OF 90% DRY SUBSTANCE (SDT) I 13 GALLON

APPENDIX D - Unit Type Following is a list of unit types:
nit Name IUnit Base TEIGHT/NET WEIGHT grams OLUME cubic mete APACITY itre ISTANCE eter TION
8 CONSUMPTION RATE/ENERGY /h 9 T/EDA, NET/MAS (NET WEIGHT DRAINED AND DRYED) grams SACCHARINE NET WEIGHT grams 11 TOTAL ALCOHOL IN WEIGHT grams 12 RY WEIGHT grams 13 RY AlR WEIGHT grams 14 90% DRY SUBSTANCE BY WEIGHT (SDT) grams GROSS WEIGHT grams ~

16 T TOBACCO CONTENT grams 17 RAINED WEIGHT grams 18 URE ALCOHOL VOLUME litre 19 ROOF VOLUME litre ERCENTAGE OF ALCOHOL each 21 NGINE DISPLACEMENT ' cubic mete 22 OLUME/DAY cubic mete 23 EGREE PLATO litre 4 ACK each 5 SEMI GROSS WEIGHT gran 6 INEGAR VOLUME litre 7 TOBACCO PRODUCTS AND PREPARATION eacr 8 CONTAINER each 9 DU(BONE DRY UNIT) WEIGHT gran 1 SET eacr SHIP HULL CAPACITY

0 %vol per volume 3 CIGARETTES,CIGARS,CIGARTLLOS LENGHT

O1 TROGEN (N) WEIGHT
02 OTAS1UM HYDROXIDE (I~OH) WEIGHT
03 SODIUM HYDROXIDE (NaOH) WEIGHT
04 OTASSIUM OXIDE (K20) WEIGHT
OS YDROGEN PEROXIDE (H202) WEIGHT
06 HOSPHORUS PENTOXIDE (P2O5) WEIGHT
07 (LT) WEIGHT
08 ISSILE ISOTOPE(GFI) WEIGHT
09 INC (Zn) WEIGHT
IPHOSPHORUS PENTAOXIDE (P2O5) WEIGHT
11 IPOTASSIUM OXIDE (K20) WEIGHT
12 SILVER (Ag) WEIGHT
13 GOLD (Au) WEIGHT
14 LATINUM (Pt) WEIGHT
ALLADIUM (PD) WEIGHT
16 ODIUM (Rh) WEIGHT
17 IUM (Ir) WEIGHT
18 UTHEN1UM (Ru) WEIGHT
19 OSMIfJM (Os) WEIGHT
~20 CHROMIUM (Cr) WEIGHT
~21 CKEL (Ni) WEIGHT
~22 SUCROSE (C12H22O11) WEIGHT
~23 ANADIUM (V) WEIGHT
~24 ACTIC MATTER DRY WEIGHT
~25 SILICON (Si) WEIGHT
~26 (INSULIN UNIT) 27 ~HOSPONIC ANHYDRIDE WEIGHT (P2O5) 29 CHOLINE CHLORYDRATE (C5H14CLN0) WEIGHT
30 THYLAMINE (CHSN) WEIGHT
31 RIOUS MORPHINE (C17H19N03) CONTENT WEIGHT
34 GANESE (Mn) WEIGHT
35 TUNGSTEN (W) CONTENT WEIGHT
36 GNESIUM (Mg) WEIGHT
37 OLYBDENLTM (Mo) WEIGHT
38 EAD CONTENT (Pb) WEIGHT
39 COPPER (Cu) CONTENT WEIGHT

1 IPOTASSIUM PENTAOXJDE (I~ZOS) WEIGHT
2 VOLATILE ORGANIC COMPOUND(VOC) WEIGHT
BY WEIGHT OF SUCROSE

APPENDIX E - Output Format Codes Following are output format codes:
Output Format Code Duty Rates 1 Duty Amounts 2 Detailed Duty 3 Tax Rates 4 Tax Amounts 5 Detailed Taxes 6 Duty and Tax Rates 7 Duty and Tax Amounts8 Detailed Duty and 9 Taxes Landed Cost 10 APPENDIX F - Access Codes Following are output format codes:
Access Codes Code Within access 1 Over access 2 APPENDIX G - Input Code Types Following are input format codes:
Access Codes Code Product Code 1 Tariffeed Internal 2 Use HS Code 3 APPENDIX H - Requested Values and Data Validation (Input) Input Type Valid Values Example Pin Number String 1 character followed"a-11111111"

by a dash and ~

numbers Access Code String Number from 0 "1"
to 2 see "Appendix F"

Origin Country String 2 characters "us"

see "Appendix A"

Shipment Country String 2 characters "us"

see "Appendix A"

Destination CountryString 2 characters "ca"

see "Appendix A"

Input Code Type String Number from 1 "1"
to 3 see "Appendix G"

Product Code String String value "4901990091"
of the product code (alphanumeric) Transaction ValueString Number from "500000"

0 to 1.7X103os Number of Unit String Number from "5"

0 t0 1.7X10308 Unit Code String Number from 0 "4"
to See "Appendix C"

Input Type Valid Values Example Cost of TransportString Number from "500"

0 t0 1.7X10308 Insurance Cost String Number from "250"

0 t0 1.7X10308 Other Costs String Number from "25"

0 to 1.7X103os Transaction CurrencyString 3 characters "cad"

see Appendix B

Conversion CurrencyString 3 characters "cad"

see "Appendix B"

Output Format String Number from 1 "10"
to 10 See "Appendix E"

APPENDIX I - Returned Values (Output) 1-Duty Rate 2-Duty Amount 3-Detailed Duty Customs Tariff Rates Duty Amount Customs Tariff Rates *

Per Unit Customs Tariff Per Unit Customs Tariff Product Base Unit Product Base Unit Duty Amount 4-Tax Rates 5-Tax Amounts 6-Detailed Taxes t Tax Name Sum Taxes Sum Taxes Category Tax Rate Category Tax Rate Per Unit Tax Tax Amount Per Unit Tax Tax Base Unit ' Tax Base Unit Category Tax Amount Tax Name Tax Amount Category Category Tax Rate ( ... ) Tax Rate Per Unit Tax Per Uiut Tax Tax Base Unit Tax Base Unit Tax Amount ( ... ) Category ( ... ) 7-Duty and Tax Rates 8-Duty and Tax Amounts9-Detailed Duty and Taxes Customs Tariff Rates Duty *

Per Unit Customs Sum Taxes Tariff Product Base Unit Duty Category Customs Tariff Rate Tax Amount Per Unit Customs Tariff Product Base Unit Tax Name Category S~ Taxes Category Tax Amount Tax Rate Tax Rate Per Unit Tax ( , , _ ) Per Unit Tax Tax Base Unit Tax Base Unit Tax Amount Tax Name Category Category Tax Name Tax Rate Per Unit Tax Tax Rate Tax Base Unit Per Unit Tax Tax Base Unit Tax Amount ( . , , ) Category Tax Name ( ... ) 10-Landed Cost Value Cost of Transportation Insurance Cost Other Cost Duty Sum Taxes Total Landed Cost Category Tax Amount Category .

Tax ,Amount ( ... ) * If Customs Tariff Rate is equal to 999999, the product is prolubited in the specified country.

Claims (31)

1. A real-time global tariff and import data system comprising:
A. a data storage system, comprising a set of tariff and duty data including, for each of a plurality of countries, a set of product codes and corresponding duty rates and import tax rates;
B. an input mechanism, configured to accept a set of transaction information including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, and transaction currency;
C. a duty calculation engine, configured to calculate a subject product duty as a function of said duty rate and said set of transaction information; and D. a tax calculation engine, configured to calculate a subject product import tax as a function of said tax rate and said set of transaction information.

2. A system as in claim 1, wherein said data storage system is coupled to a remote data source configured to supply at least a subset of said set of tariff and duty data.

3. A system as in claim 1, wherein said data storage system is coupled to a remote data source configured to update said set of tariff and duty data.

4. A system as in claim 1, further comprising:
E. a Web server system, coupled to said duty calculation engine and said tax calculation engine, wherein said Web server system includes a Web page generator configured to generate said input mechanism as a set of Web pages.

5. A system as in claim 4, wherein said Web server system is accessible via one or more wired or wireless networks from a group of networks comprising:

1) the Internet;
2) the Web;
3) a virtual private network;
4) an extranet;
5) an intranet;
6) a telephone network; and 7) a satellite network.

6. A system as in claim 1, wherein said tariff and import data system includes or is configured to access international transaction restriction information, said system further comprising:
E. a transaction validater, configured to verify that said set of transaction inputs complies with relevant said international transaction restriction information.

7. A real-time global tariff and import data system comprising:
A. a data storage system, comprising a set of tariff and duty data including, for each of a plurality of countries, a set of product codes and corresponding duty rates and import tax rates;
B. an input mechanism, configured to accept a set of transaction information including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, and transaction currency;
C. a duty calculation engine, configured to calculate a subject product duty as a function of said duty rate and said set of transaction information; and D. a tax calculation engine, configured to calculate a subject product import tax as a function of said tax rate and said set of transaction information; and E. a total landed cost engine, configured to calculate a total landed cost from said subject product duty, said subject product import tax, and a set of ancillary cost information.

8. A system as in claim 7, wherein said ancillary cost information includes costs from a group comprising:
1) insurance costs; and 2) transportation costs.

9. A system as in claim 7, wherein said real-time global tariff and import data system is coupled to a transportation system configured to generate a transportation cost associated with said set of transaction inputs, wherein said transportation cost comprises at least a portion of said ancillary cost information.

10. A system as in claim 9 wherein said real-time global tariff and import data system is enabled to procure transportation services via said transportation system.

11. A system as in claim 7, wherein said real-time global tariff and import data system is coupled to an insurance system configured to generate an insurance cost associated with said set of transaction inputs, wherein said insurance cost comprises at least a portion of said ancillary cost information.

12. A system as in claim 11 wherein said real-time global tariff and import data system is enabled to procure insurance coverage via said insurance system.

13. A real-time global tariff and import data system comprising:
A. a data storage system, comprising a set of tariff and duty data including, for each of a plurality of countries, a set of product codes arid corresponding duty rates and import tax rates;
B. an input mechanism, configured to accept a set of transaction information including output format code, origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, and transaction currency;
C. a duty calculation engine, configured to calculate a subject product duty as a function of said duty rate and said set of transaction information; and D. a tax calculation engine, configured to calculate a subject product import tax as a function of said tax rate and said set of transaction information; and E. an output mechanism, configured to selectively invoke said duty calculation engine and said import tax calculation engine as a fraction of said output format code, wherein said system includes a set of predetermined output formats with each output format having a unique output format code, and wherein each of said output formats includes at least one of subject product duty information or subject product tax information.

14. A system as in claim 13, wherein said at least one of subject product duty information or subject product tax information include information chosen from a group comprising:
1) duty rate;
2) duty amount;
3) tax rate;
4) duty amount;

5) detailed duty; and 6) detailed tax.

15. A real-time global tariff and import data system comprising:
A. a data storage system, comprising a set of tariff and duty data including, for each of a plurality of countries, a set of product codes and corresponding duty rates and import tax rates;
B. an input mechanism, configured to accept a set of transaction information including output format code, origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, transaction currency, and ancillary cost information;
C. a duty calculation engine, configured to calculate a subject product duty as a function of said duty rate and said set of transaction information; and D. a tax calculation engine, configured to calculate a subject product import tax as a function of said tax rate and said set of transaction information; and E. a total landed cost engine, configured to calculate a total landed cost from said duty, said import tax, and ancillary cost information; and F. an output mechanism, configured to selectively invoke said duty calculation engine and said import tax calculation engine as a function of said output format code, wherein said system includes a set of predetermined output formats with each output format having a unique output format code, and wherein each of said output formats includes at least one of duty or tax rate or amount information.

16. A system as in claim 15, wherein said input mechanism is configured to accept XML
requests comprising said set of transaction information.

17. A real-time global tariff system, accessible via a network, comprising:
A. a data storage system comprising duty data including, for each of a plurality of countries, a set of product codes and corresponding duty rates;
B. an input mechanism, configured to accept a set of transaction information including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, transaction currency, and ancillary cost information;

C. a duty calculation engine, configured to calculate a subject product duty as a function of said duty rate and said set of transaction information;
D. a Web server system, coupled to said duty calculation engine, wherein said Web server system includes a Web page generator configured to generate said input mechanism as a set of Web pages; and E. an output mechanism, configured to selectively invoke said duty calculation engine and wherein said Web server system is configured to generate a Web page presenting said duty.

18. A real-time global import tax system, accessible via a network, comprising:
A. a data storage system comprising import tax data including, for each of a plurality of countries, a set of product codes and corresponding import tax rates;
B. an input mechanism, configured to accept a set of transaction information including origin country, shipment country, destination country, product code, transaction value, quantity of product units, transaction currency, and ancillary cost information;
C. a tax calculation engine, configured to calculate a subject product import tax as a function of said tax rate and said set of transaction information;
D. a Web server system, coupled to said tax calculation engine, wherein said Web server system includes a Web page generator configured to generate said input mechanism as a set of Web pages; and E. an output mechanism, configured to selectively invoke said tax calculation engine and wherein said Web server system is configured to generate a Web page presenting said tax.

19. A method of providing real-time global tariff and import data over a networked computer system, said method comprising:
A. establishing in a data storage system a set of tariff data and duty data, including for each of a plurality of countries, a set of product codes and corresponding duty rates and import tax rates;
B. entering at a client device a set of transaction inputs including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, and transaction currency;
C. transmitting said set of transaction information to a tariff and import data system;

D. calculating a subject duty, as a function of a product duty rate and said set of transaction information;
E. calculating a subject import tax, as a function of a product duty rate and said set of transaction information; and F. transmitting said subject duty and said subject import tax to said client device in substantially real-time.

20. A method as in claim 19, wherein said client device and tariff and import data system are remote to each other and parts C and F include transmitting over one or more wired or wireless networks from a group of networks comprising:

1) the Internet;
2) the Web;
3) a virtual private network;
4) an extranet;
5) an intranet;
6) a telephone network; and 7) a satellite network.

21. A method as in claim 19, wherein said tariff and import data system includes a Web server system, said method further comprising in part B:
B.1 generating a set of Web pages for accepting said set of transaction information; and B.2 validating said set of transaction information against predetermined syntax and semantic constraints.

22. A method as in claim 19, wherein a plurality of output formats are stored in said tariff and import data system and each output format has a corresponding output format code, wherein part P includes:
B.1 entering a subject output format code; and wherein said method further comprises:
G. outputting one or more of said subject duty, and said subject import tax at said client device in an output format corresponding to said subject output code.

23. A method of providing real-time global tariff and import data over a networked computer system, said method comprising:
A. establishing in a data storage system a set of tariff data and duty data, including for each of a plurality of countries, a set of product codes and corresponding duty rates and import tax rates;
B. entering at a client device a set of transaction inputs including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, and transaction currency;
C. transmitting said set of transaction information to a tariff and import data system;
D. calculating a subject duty, as a function of a product duty rate and said set of transaction information;
E. calculating a subject import tax, as a function of a product duty rate and said set of transaction information; and F. calculating a total landed cost as a function of said subject product duty, said subject product import tax, and a set of ancillary information; and G. transmitting one or more of said subject duty, said subject import tax, and said total landed cost to said client device in substantially real-time.

24. A method as in claim 23, wherein said ancillary cost information includes costs from a group comprising:
1) insurance costs; and 2) transportation costs.

25. A method as in claim 24, wherein said tariff and import data system is coupled to a transportation system and part F comprises:
F.1 generating a transportation cost associated with said set of transaction inputs, wherein said transportation cost comprises at least a portion of said ancillary cost information.

26. A method as in claim 25, wherein part F further comprises:
F.2 procuring transportation via said transportation system.

27. A method as in claim 24, wherein said tariff and import data system is coupled to an insurance system and part F comprises:

F.1 generating an insurance cost associated with said set of transaction inputs, wherein said insurance cost comprises at least a portion of said ancillary cost information.

28. A method as in claim 27, wherein part F further comprises:
F.2 procuring insurance via said insurance system.

29. A method as in claim 24, wherein a plurality of output formats are stored in said tariff and import data system and each output format has a corresponding output format code, wherein part P includes:
B.1 entering a subject output format code; and wherein said method further comprises:
H. outputting one or more of said subject duty, said subject import tax, and said total landed cost at said client device in an output format corresponding to said subject output code.

30. A method of providing real-time global tariff data over a networked computer system, said method comprising:
A. establishing in a data storage system a set of duty data, including for each of a plurality of countries, a set of product codes and corresponding duty rates and a plurality of output formats wherein each output format has a corresponding output format code;
B. entering at a client device a set of transaction inputs including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, transaction currency and subject product code;
C. transmitting said set of transaction information to a tariff and import data system;
D. calculating a subject duty, as a function of a product duty rate and said set of transaction information;
E. transmitting said subject duty to said client device in substantially real-time; and G. outputting said subject duty at said client device in an output format corresponding to said subject output code.

31. A method of providing real-time global import tax data over a networked computer system, said method comprising:

A. establishing in a data storage system a set of import tax data, including for each of a plurality of countries, a set of product codes and corresponding import tax rates and a plurality of output formats wherein each output format has a corresponding output format code;
B. entering at a client device a set of transaction inputs including origin country, shipment country, destination country, subject product code, transaction value, quantity of product units, transaction currency and subject product code;
C. transmitting said set of transaction information to a tariff and import data system;
D. calculating a subject import tax, as a function of a product import tax rate and said set of transaction information;
E. transmitting said subject import tax to said client device in substantially real-time;
and G. outputting said subject import tax at said client device in an output format corresponding to said subject output code.