Managing Customs Information

A broker management computer system (“BMCS”) receives from a logistics computer system (“LCS”) information regarding an asset to be imported into a country. The BMCS creates an initial import record in a BMCS database. The initial import record includes information regarding the asset and a unique BMCS control number generated by the BMCS. The BMCS issuing an initial import packet including the BMCS control number and provides the initial import packet to an import broker in the country. The BMCS receives from the import broker a customs packet including documents that show that the asset has cleared customs in the country, a declaration number, and the BMCS control number. The BMCS searches the BMCS database using the BMCS control number as a key for the search, finds the initial import record, and updates the initial import record with the declaration number.

BACKGROUND

Enterprises that work in an international environment often find it useful to, for example, temporarily import equipment into a country for use for a period of time and then export the equipment for use in another country. For example, oil service companies may wish to temporarily import well logging equipment, such as a logging truck or a logging tool, into a country, leave it in that country for a few months or years, and then export it for use in another country.

Customs authorities collect customs duties when an asset is imported into a country. The amount of such duties varies in many countries depending on the value of the imported asset and the type of import. The duties charged for a Temporary import, i.e., an import in which an importer plans to remove the asset after a period of time, are often different from the duties charged for a Definitive import, i.e., a permanent import in which an importer plans to leave the asset in the country permanently. A customs authority may require an importer to prove that an asset imported as a Temporary import has been removed from a country or that it has been lost or destroyed in the country. Failure to produce the documents necessary to make such proof, even if the asset has actually been removed from the country, may result in the importer paying the higher duties usually required for a Definitive import as well as fines that may be assessed.

Government issued customs documents are issued for equipment and/or materials brought in to a country or moved around a country. Typically, one document is issued on import indicting the status of the import (i.e., Temporary or Definitive) and that the required duties or fees have been paid. Typically, at the time of export (for Temporary imports), another document is issued or the original import document is stamped showing that the equipment or materials have left the country. Additionally, special customs documentation may be required for a return-to-repair export, in which equipment is returned to a manufacturer or repair center for repair with the intent that it will be brought back to the country.

An importer may hire a broker in a country to manage the customs documentation associated with the importer's assets in that country. Relying on the record-keeping of the broker for a large number of assets to avoid paying unintended duties can be risky and limits the company's ability to change brokers.

DETAILED DESCRIPTION

A Broker Management Computer System (“BMCS”) provides a centralized document repository with customs declaration tracking ability to reduce liability with customs authorities globally and to ensure that document retention meets country customs retention laws and company retention policy.

In one embodiment, a logistics computer system (“LCS”) reduces the steps a user takes to create a customs transaction to bring equipment/material in country. In one embodiment, LCS integrates multiple modules of a commercially-available logistics computer system, such as those provided by SAP®, to and/or software code that has been internally developed by a company around or in the environment of the commercially-available logistics computer system to serve the needs of a company. For example, in one embodiment, BMCS provides the ability to access data about assets from an Asset Management Integration (“AMI”), which is internally developed code (i.e., code developed by the assignee of the instant patent application) in the SAP® environment that allows data about an asset to be accessed using a shipping invoice number for that asset, so that independent entry of that information is not necessary.

In one embodiment, BMCS provides a dashboard interface, discussed below in connection withFIG. 2, that allows a user to record Definitive, Temporary, Bonded, and Temporary Export customs declarations. In one embodiment, the dashboard interface allows a user to initiate an import or to change an existing declaration. In one embodiment, much of the data required for such imports is imported from LCS, minimizing user interaction and reducing the possibility of error. In one embodiment, once the information is entered, BMCS will allow the user to send clearance instructions to the broker and, once customs is cleared, full customs entry documents will be returned and uploaded into a document repository.

In one embodiment, BMCS provides comprehensive reporting for monitoring and auditing the customs status of an asset throughout the life of a customs declaration.

The workflow for creating an original import package is illustrated inFIG. 1.FIG. 1is divided horizontally into three sections to illustrate the activities of local country logistics (in the top section), a local broker (in the middle section), and customs (in the bottom section).

In one embodiment, the workflow begins (block102) when a pre-alert is received from a freight forwarder (block104). In one embodiment, such a pre-alert indicates that an asset or a set of assets is about to be taken into a country. Henceforth, this application will describe the BMCS operations concerning one asset. It will be understood that the same operations can be performed with a plurality of assets.

In one embodiment, a user will access a BMCS dash board on a computer display screen, illustrated inFIG. 2(note thatFIG. 2is labeled “BMS Dash Board”; “BMS” refers to Broker Management System and, for the purposes of this patent application, is equivalent to “BMCS”), and select “Create Declaration.” That selection will initiate the creation of the initial import packet, which includes the creation of the BMCS Control Number and the creation of the Broker Summary, (block108), causing the “Create Declaration Packet: Initial Screen,” illustrated inFIG. 3, to be displayed.

In one embodiment, the pre-alert includes a reference that can be used to retrieve information about the asset. In one embodiment, the reference is a LCS (e.g., SAP®) billing or shipping number that can be an AMI document number, an invoice number, or a shipment number. In one embodiment, the reference is a SAP® purchase order number. In one embodiment, the reference is an external reference, such as a vendor invoice for a sample purchased on a procurement card, not on a SAP® purchase order.

In one embodiment, the user uses the reference to make one of the selections shown inFIG. 3, and that selection causes additional information about the asset to be retrieved from LCS (e.g., SAP®) or another external reference source. In one embodiment, the additional information includes such information as a material number, a material description, an equipment description, a vehicle identification number (“VIN”), a vehicle manufacture date, a quantity, a unit of measure (“UOM”), an invoice value, a currency type, a contract number, a customer name, a business unit identifier, a cost center, and various other similar information.

In one embodiment, the “category” pull-down menu shown on the screen inFIG. 3allows the user to specify the import category as a Definitive import, a Temporary import, or a Lease/rental (or bonded) import (block106). In one embodiment, if the user specifies a Temporary import, the user further specifies one of the following “regimes” for the Temporary import: Temporary Import Standard, Temporary Import Product Sharing Agreement, Temporary Import No Product Sharing Agreement, Temporary Import Repetro, Temporary Import Commodato.

In one embodiment, once the selections onFIG. 3are made, the BMCS allows the user to create an initial import packet (block108), using the “Create Declaration Packet” screen shown inFIG. 4. In one embodiment, the screen shown inFIG. 4has several tabs: a “Control Data” tab, a “Reference Data” tab, a “Header Data” tab (which is currently displayed onFIG. 4), an “Equipment” tab, a “Material” tab, an “Attachments” tab, a “Broker Summary” tab, and a “Customs Declaration” tab.

In one embodiment, the “Control Data” tab includes a “BMCS Control Number” field which is populated automatically with a unique “BMCS Control Number.” In one embodiment, the “BMCS Control Number” is permanently assigned to the asset in BMCS and is used to identify and track the asset while it is in the country and thereafter.

In one embodiment, the “Control Data” tab includes a “Created On” field that contains the date the BMCS control number was created, a “Created By” field that contains an identifier for the person that created the declaration packet, a “Recvg Ctry” field that contains a letter code for the receiving country, a “CoCd” field that contains a numeric code for the receiving country, a “PSL Contact Name” field that contains the name of the business unit contact person for the asset, and an “Airway/BOL” field that contains a code for the air way bill or bill of lading for the asset. In one embodiment, some or all of these fields are automatically filled from LCS (e.g., SAP®).

In one embodiment, the Control Data tab includes status information (“Status Info”) about the Declaration Packet being processed. In one embodiment, the status information includes an “Import Status” field which can have the following values: “Pending” (if the Broker Summary is being prepared), “Open” (if the Broker Summary has been sent to the broker), or “Closed” (if the “Declaration Status” field, discussed below, is set to “Complete”).

In one embodiment, the status information includes a “Declaration Status” field, which includes a “traffic light” (illustrated inFIG. 4as three adjacent circles). In one embodiment, the “Declaration Status” field can have the following values (with the traffic light status in parentheses after the value): “Under Clearance” (no light, if the Broker Summary has been sent but the Declaration information has not been updated or attached), “Active” (green, only applicable for Temporary Imports, if the Declaration information has been updated and attached), “Expired” (only applicable for Temporary Imports, yellow if the current date is 30 days prior to expiration, red if expiration has passed), or “Complete” (blue or no light). In one embodiment, the Declaration Status field indicates “Complete” only when the following information is updated/attached:Custom Declaration NumberDeclaration From DateDeclaration ValueTotal Duty Amount

Attachments:AWB/BOLCommercial InvoiceCustoms DeclarationCustoms Release
Further, in one embodiment, for a Temporary Import, the Declaration Status field indicates “Complete” only when the above conditions are met that all parent/child transactions (described below) are in a final status (i.e., Lost-in-Hole, Damaged/Scrap, or Export).

In one embodiment, the status information includes a “Document Status” field, which includes a “traffic light” (illustrated inFIG. 4as three adjacent circles). In one embodiment, the “Document Status” field can have the following values (with the traffic light status in parentheses after the value): “Upload Complete” (green, if all required documents for the transaction have been uploaded/attached), or “Not Upload” (red, if all required documents for the transaction have not been uploaded/attached).

Thus, in one embodiment, the status of the Declaration Packet being processed can be ascertained by glancing at the Control Data tab. That is, in one embodiment, the Declaration Packet is complete or on track if all lights are green or if no lights are illuminated. In one embodiment, there is a problem or potential problem with the Declaration Packet being processed if any of the lights are yellow or red. In one embodiment, the problems can be investigated by clicking on one of the other tabs, as discussed below.

In one embodiment, the “Reference Data” tab displays the information submitted on the initial screen illustrated inFIG. 3.

In one embodiment, the “Partner Details” area includes a “Broker Name” field that includes the name of a broker chosen from a drop down list of brokers in the receiving country, a “Broker E-mail” field that contains the e-mail address of the selected broker, and an “Alt. Broker E-mail” field that contains an alternative e-mail address for the selected broker. In one embodiment, the “Partner Details” area includes a “Contract Number” field that contains an identifier for the contract under which the asset covered by the Declaration Packet is being imported as selected using a drop down list of contract numbers, a “Contract Valid from Date” field that contains the date that the selected contract became valid, a “Contract Valid to Date” field that contains the date that the selected contract expires, a “Customer Name” filed that contains the name of the customer to whom the service is being sold, and a “Reference Number” field that contains user-selected free form text.

In one embodiment, the “General Details” contains a “Superior BMS Number” field that contains a next level number under the parent in the hierarchy (child) indicating the previous change. and a “Top BMS Number” field that contains the ultimate top level number in the hierarchy (parent) when creating imports.

In one embodiment, the “Comments” field contains user comments with a user identification and a date-or-time stamp.

In one embodiment, the “Equipment” tab, illustrated inFIG. 5, allows the user to select the equipment that will be included under this Declaration Packet. In one embodiment, the “Equipment” tab lists equipment associated with the reference entered or selected through the initial screen illustrated inFIG. 3with information (e.g. “AMI Number,” “SAP Invoice Number,” “SAP Shipment Number,” etc.) pulled from LCS (e.g., SAP®). In one embodiment, the “Equipment” tab includes a “Select” box next to each listed item of equipment. In one embodiment, if the “Import Status” in the “Control Data” area is “Pending,” the user can select the Equipment to be included in the Declaration Packet using the “Select” boxes. In one embodiment, if the “Import Status” in the “Control Data” area is “Open” or “Closed,” no further selection is possible.

In one embodiment, the “Material” tab (which is available for the “Definitive” and “Bonded” import categories but not for the “Temporary Import” category), illustrated inFIG. 6, allows the user to select the material that should be imported under this Declaration Packet. In one embodiment, the “Material” tab lists equipment associated with the reference entered or selected through the initial screen illustrated inFIG. 3with information (e.g. “AMI Number,” “SAP Invoice Number,” “SAP Shipment Number,” etc.) pulled from LCS (e.g., SAP®). In one embodiment, the “Material” tab includes a “Select” box next to each listed item of material. In one embodiment, if the “Import Status” in the “Control Data” area is “Pending,” the user can select the Material to be included in the Declaration Packet using the “Select” boxes. In one embodiment, if the “Import Status” in the “Control Data” area is “Open” or “Closed,” no further selection is possible.

In one embodiment, each Equipment and Material item can have one of the statuses listed in Table 1:

In one embodiment, if an entry is made in the “External Reference” field on the “Initial Screen” (seeFIG. 3), an “External Reference” tab will appear on the “Create Declaration Packet” screen (FIG. 4) and provide a form for the user to enter or add information such as that listed above for the “Equipment” and “Material” tabs for external equipment and materials.

In one embodiment, the “Attachments” tab, illustrated inFIG. 7, provides a list of documents associated with the Declaration Packet. In one embodiment, each of the listed documents has an “Upload Check” box, a “Required” box and a “Document Status” traffic light (indicated by the three circles adjacent the document name under the “Document Status” heading).

In one embodiment, the user will click on the “Required” box for a document if upload of the document is required to turn the “Document Status” traffic light green on the “Control Data” tab. The user checks the “Upload Check” box for a document upon uploading the document. A document is uploaded by clicking on the document in the “Document Name” column and clicking on the Upload button (the button has the appearance of a conversation bubble) on the tool bar. The upload status of a document does not affect the status of the “Document Status” traffic light on the “Control Data” tab if the “Required” box for a document is not checked. The “Document Status” traffic light on the “Control Data” tab will turn green if the “Upload Check” box is checked for each document having a checked “Required” box. In the example shown inFIG. 7, the “Document Status” traffic light on the “Control Data” tab is red because the “Customs Release” document, which has a checked “Required” box, does not have a checked “Upload Check” box. The “Document Status” traffic light on the “Control Data” tab will turn green when the “Customs Release” document is uploaded and the “Upload Check” box is checked.

In one embodiment, the “Broker Summary” tab, illustrated inFIG. 8, includes a “BMS Summary” area that provides a different set of entry fields depending on the “Category” selection made on the “Initial Screen” shown inFIG. 3according to Table 2:

In one embodiment, the “Broker Summary” includes a “Broker instructions” area where the user can record comments with a user identification and date and time stamp.

FIG. 8shows one embodiment of the data entry fields for a Temporary Import (as indicated by the “Category” field in the “Control Data” tab). In one embodiment, after filling in the fields in the “BMS Summary” area, the user will click on the “Mail to Broker” button on the tool bar, which will cause the document shown inFIG. 9to be displayed. In one embodiment, after review, the user can click the “Send to Broker” button, causing displayed document to be sent to the broker by email to the address filled in on the “Header” tab, “Cancel” button, which causes the display to return to that shown inFIG. 8, or the “Save” button causing the information shown onFIG. 8to be saved for later editing.

In one embodiment, the form shown inFIG. 9has fields to be filled in by the broker, with the set of broker-fillable fields included on the form being different depending on the “Category” selection made on the “Initial Screen” shown inFIG. 3according to Table 3:

Returning toFIG. 1, the local broker receives the initial import packet and creates and submits a customs packet for the asset to customs (FIG. 1, block110).

Customs receives and processes the customs packet (block112) and creates a declaration number, clears the asset for import (block114) and provides the import documents to the broker.

The broker provides BMCS with a custom packet, with the broker-fillable fields in the form shown inFIG. 9completed, and the BMCS “Control Number,” which is one of the previously-filled fields in the form shown inFIG. 9, remitting the customs documents electronically and in hard copy (block116).

In one embodiment, the “Customs Declaration” tab, shown inFIG. 10, includes fields that are automatically filled from the returned form. In one embodiment, the fields are manually filled using information from the returned form.

In one embodiment, the “Customs Declaration” tab will include only the fields applicable for the “Category” selected for on the “Initial Screen” (FIG. 3) as listed in Table 3.

Returning toFIG. 1, in one embodiment, BMCS verifies that the Initial Import Packet is complete, updates BMCS with the new Declaration Number, and uploads the Declaration Packet (block118).

In one embodiment, having ascertained that the Initial Import Packet is complete, and only if it is complete, BMCS remits payment to the broker (block122). In general, in one embodiment, a broker is not paid until the information necessary to completely document the current and correct customs status of the asset has been provided by the broker and is input into BMCS. In one embodiment, this is true of all broker interactions. In one embodiment, the process of creating the Initial Import Package is then complete (block124).

In one embodiment of another view of the initial import process that focuses on the interactions between LCS (e.g., SAP®)1102, BMCS1104, and an import broker1106, illustrated inFIG. 11, BMCS1104receives information regarding an asset to be imported into a country1108from LCS (e.g., SAP®)1102. In one embodiment, the “information regarding an asset to be imported into a country”1108includes the information shown on the “Equipment” tab (seeFIG. 5), the “Material” tab (seeFIG. 6), and/or on the “External Material” tab, if such a tab exists.

In one embodiment, BMCS1104creates an initial import record1110in a BMCS database1112. In one embodiment, the initial import record1110includes information regarding the asset1114, which in one embodiment is some or all of the “information regarding an asset to be imported into a country”1108. In one embodiment, the initial import record1110includes the unique BMCS control number1116generated by the BMCS, as shown inFIG. 8.

In one embodiment, BMCS issues an initial import packet1118. In one embodiment, the initial import packet1118includes a broker summary1120, such as the “Broker Summary” illustrated inFIG. 9, including a portion of the information regarding the asset1114from which a customs packet for import of the asset into the country can be generated. In one embodiment, the initial import packet1118includes the BMCS control number1116.

In one embodiment, the BMCS provides the initial import packet1118to an import broker1106in the country. In one embodiment, this is done by e-mail as described above.

In one embodiment, the interactions between the import broker1106and customs proceed as described above in connection withFIG. 1resulting in the issuance of customs documents to the broker1106. In one embodiment, BMCS1104receives the following items from the import broker: an electronic version of a customs packet1122for the asset, which includes the documents listed on the attachments tab that show that the asset has cleared customs in the country (seeFIG. 7) and the “Broker Summary” form illustrated inFIG. 9with the broker-fillable fields filled in, a declaration number1124assigned to the asset by customs in the country, which would be included in one of the broker-fillable fields in the “Broker Summary” form illustrated inFIG. 9, and the BMCS control number.

In response, BMCS1104searches the BMCS database1112using the BMCS control number1116as a key for the search and finds the initial import record1110. BMCS1104then updates the initial import record1110with the declaration number1124and associates the electronic version of the customs packet for the asset1122with the initial import record1110.

In one embodiment, BMCS determines that the declaration packet is complete, such as by determining that the “Declaration Status” in the “Control Data” tab (FIGS. 4-8, 10) is completed and, in response, the BMCS initiates payment to the import broker1106.

One embodiment of the process for changing (i.e., renewing, transferring, re-exporting, or scrapping) a declaration packet, illustrated inFIG. 12, begins (block1202) by receiving a notification that the declaration for an asset will expire within 90 days (block1204).

In one embodiment, the user will access the dashboard illustrated inFIG. 2and select “Change Declaration Packet,” which will cause a search screen to appear. In one embodiment, the user will enter the original BMCS control number, which will cause information about the original declaration package to appear, and click a button (not shown) to create a new broker summary. In one embodiment, the user will click a button (not shown) to send the broker summary to the broker (block1206). The BMCS will create a child BMCS control number for the change (block1208).

The broker will receive the new broker summary and create and submit a new customs packet to customs (block1210).

Customs will receive and process the customs packet (block1212) and create a new declaration or notate the original declaration reflecting the selected change type (block1214) and send it to the broker.

In one embodiment, the broker will return to BMCS the letter or declaration packet with the notation reflecting the change along with the BMCS control number and will remit the customs documents electronically and in hard copy (block1214).

In one embodiment, BMCS will associate the change (e.g., enter a new declaration number if one is provided) to the child system control number and attach the required documents (block1216). BMCS will then verify that the import packet is complete and, if only if it is complete, remit payment in response to the broker invoice (block1218), completing the process (block1220).

One embodiment of the process for renewing a customs declaration, illustrated inFIG. 13, begins with BMCS receiving a notification that the declaration number for the asset is about to expire (block1302). In one embodiment, the notification includes the declaration number that is about to expire. In one embodiment, BMCS accesses the initial import record1110for the asset using the declaration number for the asset. In one embodiment, BMCS receives a command to renew the import of the asset to the country, for example through the dashboard shown inFIG. 2and the additional screens discussed above in connection withFIG. 12.

In one embodiment, BMCS1104creates a renewal child record1304in the BMCS database1112. In one embodiment, the renewal child record includes a unique child BMCS control number1306generated by the BMCS1104and a link1308to the initial import record for the asset1110. In one embodiment, the link1308is part of the initial import record1110rather than the renewal child record1304.

In one embodiment, BMCS issues a renewal packet1309including a renew broker summary1310comprising information from which a renewal customs packet for the asset can be generated, and the child BMCS control number1306. In one embodiment, BMCS provides the renewal packet1309to a renewal broker1312in the country.

In one embodiment, after the renewal broker1312acquires the renewal declaration as described above in connection withFIG. 12, BMCS receives from the renewal broker1312an electronic version of a renewed declaration packet for the asset1314, the renewed customs packet including documents that show that customs declaration for the asset has been renewed, a new declaration number for the asset1316, and the child BMCS control number1306.

In one embodiment, BMCS determines that the renewed declaration packet1314is complete and, in response updating the renewal child record1304with the new declaration number1316for the asset, and associating the electronic version of the renewal declaration packet1316for the asset with the renewal child record1304, and initiating payment to the broker.

In one embodiment of the procedure for transferring the asset from one contract/bond to another contract/bond, the information regarding the asset1114includes a contract/bond to which the asset is assigned1401. In one embodiment, BMCS receives a notification that the asset is to be transferred to another contract/bond1402, the notification1402including the BMCS control number for the asset1116. In one embodiment, BMCS accesses the initial import record1110for the asset using the BMCS control number for the asset1116. In one embodiment, BMCS creates a transfer child record1404in the BMCS database1112. In one embodiment, the transfer child record1404includes a unique child BMCS control number1406generated by the BMCS1104and a link1408to the initial import record for the asset. In one embodiment, the link1408is part of the initial import record1110.

In one embodiment, the BMCS1104issues a transfer packet1409including a transfer broker summary1410including information from which a transfer customs packet for the asset can be generated, and the child BMCS control number1406. In one embodiment, BMCS provides the transfer packet to a transfer broker1412in the country.

In one embodiment, after the transfer broker1412acquires the renewal declaration as described above in connection withFIG. 12, BMCS1104receives from the transfer broker1412an electronic version of a transfer customs packet1414for the asset, the transfer customs packet including documents that show that customs declaration for the asset has been transferred to the new contract/bond, a new declaration number for the asset1416, and the child BMCS control number1406.

In one embodiment, BMCS determines that the transfer customs packet1414is complete and, in response, updates the transfer child record1404with the new contract/bond1418and the declaration number1416, associates the electronic version of the transfer customs packet1414for the asset with the transfer child record1404, and initiating payment to the transfer broker1412.

In one embodiment of informing customs that an asset has become lost-in-hole, illustrated inFIG. 15, BMCS1104receives a notification1502that the asset has been lost-in-hole, the notification1502including BMCS control number1114for the asset. In one embodiment, BMCS1104accesses the initial import record1110for the asset using the BMCS control number1116for the asset. In one embodiment, BMCS creates a lost-in-hole child record1504in the BMCS database1112. In one embodiment, the lost-in-hole child record1504includes a unique child BMCS control number1506generated by BMCS1104and a link1508to the initial import record1110for the asset. In one embodiment, the link1508is part of the initial import record1110.

In one embodiment, the BMCS1104issues a lost-in-hole packet1509including a lost-in-hole broker summary1510comprising information from which a lost-in-hole customs packet for the asset can be generated and the child BMCS control number1506. In one embodiment, BMCS1104provides the lost-in-hole packet1509to a lost-in-hole broker1512in the country.

In one embodiment, after the lost-in-hole broker1512acquires the transfer declaration from customs as described above in connection withFIG. 12, BMCS receiving from the lost-in-hole broker1512an electronic version of a lost-in-hole customs packet1514for the asset, the lost-in-hole customs packet1514including documents that show that customs for the country recognizes that the asset has been lost-in-hole, a new declaration number1516for the asset, and the child BMCS control number1506.

In one embodiment, BMCS1104determines that the lost-in-hole customs packet1514is complete and, in response, associates the electronic version of the lost-in-hole customs packet1514for the asset with the lost-in-hole child record1504, and initiates payment to the lost-in-hole broker1512.

In one embodiment of the process for informing customs that the asset has become damaged or scrap, illustrated inFIG. 16, BMCS1104receives a notification1602that the asset has become damaged/scrap, the notification including the BMCS control number1116for the asset. In one embodiment, BMCS accesses the initial import record1110for the asset using the BMCS control number1116for the asset. In one embodiment, the BMCS creates a damaged/scrap child record1604in the BMCS database1112. In one embodiment, the damaged/scrap child record1604includes a unique child BMCS control number1606generated by the BMCS1104, and a link1608to the initial import record1110for the asset.

In one embodiment, BMCS1104issues a damaged/scrap broker packet1609including a damaged/scrap broker summary1610including information from which a damaged/scrap customs packet for the asset can be generated, and the child BMCS control number1606. In one embodiment, BMCS1104provides the damaged/scrap packet1609to a damaged/scrap broker1612in the country.

In one embodiment, after the damaged/scrap broker1612acquires the transfer declaration from customs as described above in connection withFIG. 12, BMCS1104receives from the damaged/scrap broker1612an electronic version of a damaged/scrap customs packet1614for the asset, the damaged/scrap customs packet including documents that show that customs for the country recognizes that the asset has become damaged/scrap, a new declaration number1616for the asset, and the child BMCS control number1606.

In one embodiment, BMCS1104determines that the damaged/scrap customs packet1609is complete and, in response, updates the damaged/scrap child record1604to show that the asset is lost-in-hole1618and to include the new declaration number1616. In one embodiment, BMCS1104associates the electronic version of the damaged/scrap customs packet1614for the asset with the damaged/scrap child record1604, and initiates payment to the damaged/scrap broker1612.

In one embodiment of the process for exporting the asset, illustrated inFIG. 17, BMCS1104receives a notification1702that the asset is to be exported from the country, the notification including the BMCS control number1116for the asset. In one embodiment, BMCS1104accesses the initial import record1110for the asset using the BMCS control number1116for the asset. In one embodiment, BMCS1104creates an export child record1704in the BMCS database1112. In one embodiment, the export child record1704includes a unique child BMCS control number1706generated by the BMCS and a link1708to the initial import record for the asset.

In one embodiment, BMCS1104issues an export packet1709including an export broker summary1710comprising information from which an export customs packet for the asset can be generated and the child BMCS control number1706. In one embodiment, BMCS1104provides the export packet to an export broker1712in the country.

In one embodiment, after the export broker1712acquires the transfer declaration from customs as described above in connection withFIG. 12, BMCS1104receives from the export broker an electronic version of an export customs packet1714for the asset, the export customs packet including documents that show that customs for the country recognizes that the asset has been exported, a new declaration number1716for the asset, and the child BMCS control number1706.

In one embodiment, BMCS1104determines that the export customs packet1714is complete and, in response updates the export child record1704with the new declaration number1716, associates the electronic version of the export customs packet for the asset with the export child record, and initiates payment to the export broker1712.

In one embodiment, illustrated inFIG. 18, the initial import record1110is linked to a plurality of child records18021 . . . Nby a linked list, with each child record18021 . . . Nbeing linked by a successive link18041 . . . Nand each child record18021 . . . Nrecording a change in the customs status of the asset. In one embodiment, each child record18021 . . . Nis linked directly to the initial import record rather than through a linked list.

In one embodiment, illustrated inFIG. 19, various reports regarding the import status of assets can be accessed through the “Reports” buttons on the dash board illustrated inFIG. 2. In one embodiment, preparation of a report begins (block1902) with a request for information about an asset (block1904). In one embodiment, the initial import record for the asset is accessed (block1906) using the BMCS control number for the asset, the declaration number, or another key provided by the BMCS database1112. In one embodiment, pertinent children records of the initial import record are accessed (block1908). In one embodiment, customs packets associated with the initial import record and the pertinent children are accessed (block1910). In one embodiment, the information requested about the asset is provided in the form of a report (block1912) and the process ends (block1914).

The text above describes one or more specific embodiments of a broader invention. The invention also is carried out in a variety of alternate embodiments and thus is not limited to those described here. The foregoing description of an embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.