481-2023 (COMIECO-EX) dated November 16, 2023, be published, which approves that, as of January 30, 2024, the electronic transmission of the data from the harmonized sanitary and phytosanitary export certificates among the States Parties shall be carried out through the Central American Digital Trade Platform (PDCC) administered by SIECA; and its Annex: "Technical guide for the electronic transmission of the data set of the information contained in the sanitary and phytosanitary certificates", which is transcribed below:
(Sinalevi Note: By article 2 of this decree, resolution No. 485-2023 (COMIECO-CV) dated December 5, 2023, was approved, which amended this resolution, as follows: "1. Amend Resolution No. 481-2023 (COMIECO-EX), of November 16, 2023, in the sense that the same shall apply to the Republic of Panama, no later than March 30, 2024. 2. While the period referred to in numeral 1 of this Resolution is being met, trade in shipments and goods, between the Republic of Panama and the rest of the States Parties, requiring sanitary or phytosanitary export certificates, shall continue to be carried out in accordance with Resolution No. 456-2021 (COMIECO-XCVIII), of December 17, 2021, and other applicable regulations. 3. For greater certainty, the transitory period contemplated in numeral 4 of Resolution No. 481-2023 (COMIECO-EX), of November 16, 2023, shall not apply to the Republic of Panama.)
(COMIECO-EX) THE COUNCIL OF MINISTERS OF ECONOMIC INTEGRATION
That in accordance with Articles 38, 39 and 55 of the Protocol to the General Treaty on Central American Economic Integration (Guatemala Protocol), amended by the Amendment of February 27, 2002, the Council of Ministers of Economic Integration (COMIECO), has under its competence the matters of Central American Economic Integration, therefore it is responsible for approving the administrative acts applicable in the States Parties of the Economic Subsystem; That in Agreement No. 01-2015 (COMIECO-LXXIII), of October 22, 2015, COMIECO approved in all its parts the "Central American Strategy for Trade Facilitation and Competitiveness with emphasis on Coordinated Border Management" (ECFCC), therefore the Trade Facilitation Group was instructed to coordinate its implementation, in accordance with the Strategy and the policies of the Central American governments; That through Resolution No. 376-2016 (COMIECO-LXXVII), of September 1, 2016, COMIECO reaffirmed the strategic importance of intraregional trade of the States Parties of the Central American Economic Integration Subsystem, therefore it was resolved to accelerate the execution of the five priority short-term measures contemplated in the ECFCC; That through Resolution No. 428-2020 (COMIECO-XCII), of October 27, 2020, COMIECO approved the amendment of Annexes III and IV of the Sanitary and Phytosanitary Directive for the Facilitation of Trade in Central American Shipments and Goods, which contain the formats of the harmonized sanitary and phytosanitary export certificates applicable for the Republics of Costa Rica, El Salvador, Guatemala, Honduras and Nicaragua, and by Resolution No. 456-2021 (COMIECO-XCVIII), of December 17, 2021, the format of said certificates was approved for the Republic of Panama, these being harmonized at the regional level; That for the implementation of short-term measure number three of the ECFCC, called "Electronic phytosanitary and zoosanitary certificates", it is necessary for the information contained in the sanitary and phytosanitary certificates to be transmitted electronically, using SIECA as a transmission node; That the instances of Economic Integration have reached an agreement for the electronic exchange process of the information contained in the sanitary and phytosanitary certificates, and submit it for consideration by this forum; That COMIECO may meet virtually, in which case, the signing of the adopted decisions shall be carried out a posteriori, without affecting their validity, and it is the responsibility of the Secretariat for Central American Economic Integration (SIECA), to follow up on the signing of the administrative acts by the members of the Council,
Based on Articles 6, 36, 37, 38, 46, 52 and 55 of the Guatemala Protocol, and 26, 28, 40 and 41 of the Regulations for the Organization and Operation of the Councils: of Ministers of Economic Integration, Intersectoral of Ministers of Integration and Sectoral of Ministers of Economic Integration,
1. To approve, as of January 30, 2024, that the electronic transmission of the data from the harmonized sanitary and phytosanitary export certificates among the States Parties shall be carried out through the Central American Digital Trade Platform (PDCC) administered by SIECA.
2. To approve the "Technical guide for the electronic transmission of the data set of the information contained in the sanitary and phytosanitary certificates", in the form that appears in the Annex of this Resolution and which forms an integral part thereof.
3. To implement the electronic transmission indicated in numeral 1 of this Resolution:
a. The economic agents of the States Parties must manage the issuance of the sanitary and phytosanitary export certificates, solely through the digital means enabled by the States Parties for this purpose.
b. The data of the sanitary and phytosanitary certificates authorized by the competent authority of the exporting State Party must be transmitted electronically, through the PDCC, to the competent authorities of the importing State Party.
c. In accordance with Annex 2 of Resolution No. 409-2018 (COMIECO-LXXXV), of December 7, 2018, which contains the instructions for completing the DUCA, field 54 "Supporting documents", economic agents must enter the number of the sanitary or phytosanitary export certificate that has been previously authorized by the competent institution in the DUCA-F.
d. The States Parties may require that the means of transport carrying goods and shipments must comply with the provisions of numeral 1 of this Resolution, prior to entering the primary zone of their Border Posts.
4. Notwithstanding the period indicated in numeral 1, the competent authorities of the States Parties may issue sanitary and phytosanitary export certificates in physical or electronic format during the period from January 30, 2024, to March 1, 2024. Once the transitory period contained in this numeral has elapsed, sanitary and phytosanitary export certificates may only be issued in electronic format, as provided in numeral 1 of this Resolution.
5. In the event of failures in the computer systems of the States Parties or of SIECA, which prevent the management or issuance of sanitary or phytosanitary certificates or the transmission of their data, as a contingency measure, such certificates may be managed, issued and presented in physical format or through another digital platform defined by agreement between the States Parties, while the corresponding services are reestablished.
6. SIECA and the sanitary and phytosanitary authorities of the States Parties may, by mutual agreement, modify the mentioned Guide. The foregoing shall not prevent SIECA from carrying out the actions or taking the necessary measures to ensure the proper functioning of the platform and the implementation of the measure.
7. The electronic transmission of the data referred to in numeral 1 of this Resolution substitutes the physical presentation of the corresponding certificates and shall have the same value and probative efficacy as if said certificates had been stamped and signed in handwritten form.
8. The competent authority of a State Party shall recognize as authentic and valid, the sanitary and phytosanitary certificates of the competent authority of the other State Party, whose data were transmitted electronically. The information and documentation resulting from the electronic transmission shall constitute, in itself, authentic documentation and for all purposes shall give full faith as to the existence of the transmitted original.
9. The sanitary and phytosanitary measures at the border posts of the States Parties shall be applied in accordance with the applicable regulations.
10. Shipments and goods that, at the time of entry into force of this Resolution, have a certification previously issued by the competent authorities of the States Parties, may complete the operation for which they were intended with said certification, in accordance with the regulations applicable to them.
11. This Resolution enters into force as of this date and shall be published by the States Parties.
Central America, November 16, 2023 The undersigned Secretary General of the Secretariat for Central American Economic Integration (SIECA) CERTIFIES: That this photocopy and the three (3) preceding ones, printed only on their front side, as well as those of one (1) attached annex, printed on the front and back, all initialed and stamped with the seal of SIECA, faithfully reproduce Resolution No. 481-20 (COMI O-EX), adopted by the Council of Ministers of Economic Integration, on November sixteenth, two thousand twenty-three, in a virtual meeting, from whose originals they were reproduced. And to send to the States Party for their corresponding publication, I issue this certified copy in Guatemala City, Guatemala, on January twenty-fifth, two thousand twenty-four.
TECHNICAL GUIDE FOR THE ELECTRONIC TRANSMISSION OF THE DATA SET OF THE INFORMATION CONTAINED IN THE SANITARY AND PHYTOSANITARY CERTIFICATES
Content Background ....................................................................................... ............................... 1 Objectives of the technical guide ................................................................................................ 3 Scope of the facilitation measure .................................................................................. 4 Definition of the Computer System ..................................................................................... 4 Computer functionality .............................................................................................. 4 P1. Process for transmitting the data set of the information contained in the certificates ....................................................................................... ............................... 3 P2. Process for transmitting the event associated with a Certificate ................................. 6 P3. Process for system consultation of the data set of the information contained in a certificate ..................................................................................... ............................. 7 P4. Process for system consultation of transmission list ............................... 11 Additional considerations ......................................................................................... 12 Data set of the information contained in the Certificates ......................................... 14 Data set of the information contained in the Phytosanitary Certificates .............. 14 Data set of the information contained in the Sanitary Certificates .................... 19 Use of the Regional Platform messaging service ............................................... 23 Schemes and structures of the data to be transmitted ............................................................ 25 E1. XML Message for transmitting the data set of the information contained in the Phytosanitary Certificates ............................................................................................ 25 E2. XML Message for transmitting the data set of the information contained in the Sanitary Certificates ... :. ............................................................................................. 29 E3. XML Message for transmitting the events associated with the Certificates (including Annulment) .................................................................................. , .................................. 31 E4. XML Response to the transmission of the data set of the information contained in the certificates or of the events ................................................................................... 35 E5. XML Message for consulting the data set of the information contained in a Certificate ........ .................................................................................................... ......... 36 E6. XML Response to the consultation of the data set of the information contained in a Certificate ...... .................................................................................................... ........... 36 E7. XML Message for consultation of transmission list ........................................... 37 E8. XML Response to the consultation of transmission list ..................................... 38
Error Catalog .......................................................................................... '. ........... 41 Country Catalog ................................................................................. ....................... 42 Catalog of Border, Maritime and Air Posts ................................................. 48
Background Within the framework of the Central American Strategy for Trade Facilitation and Competitiveness (ECFC) with emphasis on coordinated border management, five priority short-term measures were established, within which the third of them refers to the electronic transmission of sanitary and phytosanitary export certificates. This measure underpins the transmission process established in this document and is supported by efforts promoted through international cooperation.
Resolution No. 338-2014 approved by the Council of Ministers of Economic Integration (COMIECO) "Central American sanitary and phytosanitary directive to facilitate trade in shipments and goods" which entered into force on July 17, 2014, with which procedures are established to simplify the application of sanitary and phytosanitary measures with the purpose of facilitating trade in shipments and goods, taking into account considerations on the risk associated with them, as well as production systems, areas or production sites and processing establishments.
Based on the aforementioned and taking into account the mandate established in COMIECO Resolution No. 376-2016, which, in its annex instructs the preparation of a technical guide for the electronic transmission of the data set contained in the certificates cited in the previous paragraph and based on COMIECO Resolution No. 338-2014 and its recent modification through COMIECO Resolution No. 428-2020 and COMIECO Resolution No. 456-2021, the Secretariat for Central American Economic Integration (SIECA), responsible for administering the Central American Digital Trade Platform (PDCC) and preparing this Technical guide for review and validation by the countries with the counterparts related to the Ministries of Agriculture and Livestock and the Single Windows for Foreign Trade.
This document defines the technological inputs for carrying out the electronic exchange of the data set of the information contained in the sanitary and phytosanitary certificates; the first corresponds to the standards defined by the World Organisation for Animal Health (OIE); and the second, determined by the International Plant Protection Convention (IPPC).
The data structure to be transmitted was agreed upon by the countries taking as reference the fields contained in Annexes III and IV of the Sanitary and Phytosanitary Directive for the Facilitation of Trade in Central American Shipments and Goods, recently modified through COMIECO Resolution No. 428-2020 and COMIECO Resolution No. 456-2021.
The model of the technological architecture for data transmission is attached, which will be carried out correctly and securely through the interoperability BUS of the Central American Digital Trade Platform (PDCC).
Objectives of the technical guide General To present the technical details for the electronic transmission of the data set of the information contained in the sanitary and phytosanitary certificates among the States Parties of the Central American region, according to the international standards of the OIE and IPPC, with the purpose of guaranteeing the electronic exchange and its interoperability with the competent institutions in Sanitary and Phytosanitary matters.
Specific a. Establish the interconnection model to be implemented in the Central American region for the electronic exchange of the data set of the sanitary and phytosanitary certificates, through the PDCC.
b. Define and adopt the XML messaging for the exchange, including the structure, data types, description and mandatory nature of the fields.
c. Allow the institutions responsible for executing the controls to have, prior to the departure from the exporting country, the information required to manage and size the necessary resources for the analysis, management and dispatch of shipments or goods at the Quarantine Control Posts (PCC).
Scope of the facilitation measure The scope of the project is defined around the electronic transmission in the format and communication channels to be established with each of the competent authorities. Similarly, this guide focuses on the electronic transmission of the data set of the information contained in the sanitary and phytosanitary certificates generated by the competent authorities.
It excludes the services or processes that register, manage and issue certificates and the transformation of the data set of the information contained in import permits.
Definition of the Computer System Computer functionality The regional platform or Central American digital trade platform (PDCC) will be an intermediary between the country of origin of the information and the country of destination thereof, that is, it will function as a data transmission bus since the necessary resources for connectivity, information stability, temporary storage, notifications or any other mechanism for transmitting and receiving information are part of the platform infrastructure.
The authorities of the countries involved must take note that they must implement the following:
° As the issuing or originating country: the transmission of the XML message with the information of the data set contained in the certificates.
° As the destination country: the receipt of the XML message with the data set of the information contained in the certificates.
° The receipt or sending of any other XML message that is related to any data set of the information contained in the certificates issued or received by the country.
In this context, each of the countries will operate completely independently and will use their national systems to generate, administer, process and transmit the data set contained in the certificates.
In any of the described cases, the information flows from one country to another, the regional platform being only a bus for transmitting information, that is, a channel through which said information will circulate.
In cases where for connectivity reasons or another reason the normal transmission process is affected, the country issuing the message must guarantee the retransmission of the message; for which it will have the technical support of those responsible for administering the PDCC, if required; the regional institution being empowered to provide immediate support. Each entity is responsible for its transmission segments.
P1. Process for transmitting the data set of the information contained in the certificates The process flow is detailed below:
- a)The system of the institution in the country of origin authorizes and issues the certificate to the exporter applying the processes, procedures and standards dictated by national legislation. The use of queues is recommended to carry out the data transmission and save the transmission status.
- b)The system of the institution issuing the certificate in the country of origin transmits the data set of the information contained in the certificate through the regional platform. This will be done from national systems or applications, generating the XML message and transmitting the information, thus becoming national and independent nodes.
0 If the institution does not have national systems for transmission, it could develop a simple data capture utility that generates the XML and transmits it to the web service of the regional platform.
0 A utility application for Microsoft Windows can be obtained from the regional platform that allows manual transmission of the data set of the information contained in the certificate entered in XML format. This system can be used independently of the national systems to transmit the information and receive a response. See ANNEX 2 of this guide.
The institution of the country of origin will connect to the service bus of the regional platform through the private URL (via VPN) or public URL to consume the electronic transmission web service.
· See Use of the Regional Platform messaging service where the URL and form of calling the service is referred to. To make use of this, you must have a username and password that will be assigned by SIECA to each country and institution.
· The format of the XML containing the data can be consulted in Schemes and structures of data to be transmitted, E1 or E2.
- c)Upon receiving the message, the regional platform will perform minimum validations, including (1) the XML is complete, (2) the established scheme is met, (3) it carries the information of the country of origin and destination.
The XML message is persisted in the Regional Platform database.
In ANNEX 1, Error Catalog you can identify the error codes that the regional platform may generate as a result of the validations.
- d)After a successful validation, the regional platform, through the regional bus, will transmit the XML message to the destination country referred to in the data set.
- e)The system in the destination country receives the XML message with the data set, persists it in the most convenient way, and will return a response message also in XML format. The structure of the XML response can be consulted in Schemes and structures of data to be transmitted, E4.
- f)The regional platform receives the XML response from the destination country, validates the response format, and if there is conformity, returns it to the country system that initiated the transmission.
- g)The system in the destination country receives the XML response and updates the transmission status.
The use of the regional platform as a data bus guarantees that data is transmitted in a centralized manner and that the distribution of messages is effective, accurate and in the minimum necessary time covering the connectivity needs and resources between the involved parties, besides guaranteeing high availability of connectivity.
P2. Process for transmitting the event associated with a Certificate The flow of this process is analogous to Process P1 for transmitting the data set of the information contained in the certificates. The differences between this process and the aforementioned one consist of (1st) that the trigger of the process is an annulment of a certificate in the issuing country, and (2nd) the transmitted XML message corresponds to Schemes and structures of data to be transmitted, E3.
This process is used to notify an annulment, a modification or a replacement of data in a previously transmitted certificate; the processes can be identified by a parameter sent in the data set (see process E3) and will be used according to the following descriptions:
· Annulment: this event is sent when a country wishes to annul a previously sent certificate.
· Modification: this process must be used when the country wishes to modify the sent data of a certificate, therefore this modification event is sent and the changes must be documented and reasoned in the observation fields.
· Replacement: this process must be used when the country wishes to make a modification to a certificate, but wants to use a new certificate attached to the previous one, so it must send a replacement event followed by the new updated data set mentioned in the previous process P1.
P3. Process for system consultation of the data set of the information contained in a certificate For this process, implementation is optional, but recommended as an alternative to the eventual situations of not receiving a data set. The reasons why one or more transmissions were not received may be related to connectivity issues, instability, or unavailability of the country system (sender or destination) at the time the original transmission was made.
The process flow is detailed below:
- a)Given a certain eventuality, the authority in the destination country could require obtaining the data set of the information contained in a certificate, considering that it did not receive the data set in advance.
- b)The authority's system in the destination country generates and transmits a message to query the data set of the information contained in a certificate through the regional platform.
The institution will connect to the service bus of the regional platform through the private URL (via VPN) or public URL to consume the web service for electronic transmission.
o See Use of the Regional Platform messaging service where the URL and method of calling the service are referenced. To use it, you must have a username and password that will be assigned by SIECA to each country and institution.
o The XML message format for querying the data set in a certificate can be obtained in Schemas and data structures to transmit, E5.
- c)Upon receiving the message, the regional platform will perform minimum validations, including (1) that the XML is complete, (2) that it complies with the established schema, (3) that it carries the information of the country of origin and of the query.
In ANNEX 1, Error Catalog, you can identify the error codes that the regional platform may generate as a result of the validations.
- d)If the data set is found on the Regional Platform, a response message, also in XML format, will be returned. The structure of the XML response can be obtained from Schemas and data structures to transmit, E6. The flow continues at (h).
- e)If the data set is NOT found on the Regional Platform, the regional platform, through the regional bus, will transmit the XML message to the country of origin referenced in the XML message.
- f)The system of the country of origin receives the XML message, queries the information in its local database, and will return a response message, also in XML format. The structure of the XML response can be consulted in Schemas and data structures to transmit, E6.
- g)The regional platform receives the XML response from the country of origin, validates the format of the response, and if there is conformity, persists the XML response; the XML message is persisted in the Regional Platform database.
- h)The system of the receiving country that makes the query receives the XML response and processes the data set at its convenience.
P4. Query process by transmission list system Similar to the previous process, this one is optional for its implementation, but recommended as an alternative to the eventual situations of not receiving transmissions for prolonged periods of time. The reasons why one or more transmissions were not received may be related to connectivity issues, instability, or unavailability of the country system (sender or destination) at the time the original transmission was made; requiring individual actions, according to the section that corresponds with their providers responsible for data transmission; if support is required to make queries between different providers, actions may be taken at the country or regional level, if necessary, to overcome technical inconveniences in the transmission.
The process flow is detailed below:
- a)Given a certain eventuality, the authority in the destination country could require obtaining the list of transmissions related to the data set of the information contained in certificates or their events, considering that it did not receive them in advance.
- b)The authority's system in the destination country generates and transmits a message to query the list of transmissions through the regional platform. The institution will connect to the service bus of the regional platform through the private URL (via VPN) or public URL to consume the web service for electronic transmission.
o See Use of the Regional Platform messaging service where the URL and method of calling the service are referenced. To use it, you must have a username and password that will be assigned by SIECA to each country and institution.
o The XML message format for querying the list of transmissions can be obtained in Schemas and data structures to transmit, E7.
- c)Upon receiving the message, the regional platform will perform minimum validations, including (1) that the XML is complete, (2) that it complies with the established schema, (3) that it carries the information of the querying country.
- d)The query will be performed on the regional database, and a response message, also in XML format, will be returned. The structure of the XML response can be obtained from Schemas and data structures to transmit, E8.
- e)The system of the receiving country that makes the query receives the XML response and processes the result at its convenience.
- f)If required, the authority's system in the destination country may individually query the data sets contained in each certificate using Process P3, Query process by system for the data set of the information contained in a certificate.
Additional Considerations Some restrictions that must be taken into account are:
0 The authorities must guarantee the high availability of the published services. This includes both the connectivity aspect and the computer system. Connectivity must be assured. The use of VPNs, web services with authentication, and IP restrictions is widely recommended.
0 The XML message refers to the minimum data to be received as mandatory; each country can send the optional data it deems necessary and pertinent for the process, and the countries receiving the information can decide which data will be useful for their processing.
Mainly because what this process aims for is the advance transmission of information, not the transmission of the certificates themselves.
0 The sending of the data set of the information contained in the certificates to the regional platform is automatic and synchronous, so it must be taken into account that if there is no connectivity (for any reason), the institutions involved must have alternate processes for data transmission or data retransmission, as well as query services from or to the regional platform to update the data sets contained in the certificates that were not transmitted or received.
0 Officials from the country of origin, the destination country, and transit countries (the latter inferred based on the country of origin and destination) may query and view the data set of the information contained in the certificates on a query portal on the regional platform at any time. Each institution must request SIECA to create the users it deems appropriate for access to the aforementioned query portal on the regional platform. Quarantine users and officials at border posts must be included here.
o The transmission log (message tracking) and the subsequent messages received (cancellation, error, replacement or modification, acceptance, etc.) will be stored for verification and follow-up of the process tracking and can be queried through the regional platform portal.
o It is recommended that mechanisms (whether web services or processes) be implemented to share catalogs and databases in order to standardize the information transmitted in the data sets.
o Each country must timely communicate to SIECA the dates on which it will perform system maintenance. Likewise, each country commits to performing improvements during hours of low data traffic so as not to affect interoperability and regional trade.
Similarly, SIECA will inform the countries when it performs work on its system.
Data Set Contained in the Certificates Data set of the information contained in the Phytosanitary Certificates
| DATA | INSTRUCTIONS |
|---|
(continued table rows verbatim as in source) | Ministerio | Mandatory. Name of the Ministry or successor that issues the certificate. | | Dirección | Mandatory. Address of the Ministry or successor that issues the certificate. | | Departamento | Mandatory. Department/Directorate that issues the certificate. | | PHYTOSANITARY CERTIFICATE FOR EXPORT | | | 1. Phytosanitary certificate for export No. | - Mandatory. Unique certificate identification number, which allows shipment traceability, facilitates audits, and serves for record-keeping | | 2. Plant protection organization - from: | Mandatory. Name of the country issuing the phytosanitary certificate for export along with the name of the NPPO of the exporting country. | | 3. To plant protection organization(s) - of: | - Mandatory. Name of the importing country. When a transit country and the importing country have specific phytosanitary requirements that include the need for a phytosanitary certificate for export, the names of both countries should be included, as well as that of the transit country. Care must be taken to ensure that the import and/or transit regulations of each country are met and indicated appropriately. In cases where the shipment is imported and re-exported to another country, the names of both importing countries may be inserted, provided that the import regulations of both countries have been met. | | 4. Exporter data: | - Mandatory. Full name and address of the exporter; according to the registry of the competent authority in the exporting State Party. | | 5. Consignee data: | - Mandatory. Full name and address in the importing country of the importing natural (individual) or legal person; which allows the NPPO of the importing country to confirm the identity of the consignee, and if necessary, to trace non-compliant imports. | | 6. Place of origin: | - Mandatory. Country of origin where the product was cultivated or produced and where it was possibly exposed to infestation or contamination by regulated pests. If requested by the importing country, the name or code of the pest-free area, pest-free place of production, or pest-free production site must be identified. In the additional declaration field, additional details may be provided about the pest-free area, pest-free place of production, or pest-free production site. | | 7. Declared point of entry: | - Mandatory. Name of the point of arrival in the destination country through which the shipment will enter and must correspond to the first point of arrival. If this is unknown, indicate the name of the country. When the shipment transits through another country, it may be necessary to record it if the transit country has phytosanitary requirements for shipments in transit | | 8. Declared means of transport: | - Mandatory. Means of transport as declared by the exporter (air, maritime, or land). The name of the ship and voyage number or the plane’s flight number may be indicated, if known. | | PRODUCT DATA | | | 9. Botanical name (Scientific name): | - Mandatory. Information that allows the identification of plants and plant products using accepted scientific names, at least at the genus level, but preferably at the species level. It may not be possible to provide botanical names for certain regulated articles and products of complex composition, such as animal feed. In these cases, the NPPOs of the importing and exporting countries may agree on a suitable common descriptive name, or "not applicable" or "NA" should be written. | | 10. Product name: | - Mandatory. Name of the plant, plant product, or other regulated article. The information should be sufficiently descriptive of the product (and include the type of product, i.e., fruit, plants for planting, etc.) so as to allow the officials of the destination country to adequately verify the contents of the shipment. International codes may be added to facilitate identification (for example, customs codes). Since different phytosanitary import requirements may apply to different intended end uses (for example, consumption vs. propagation) or level of processing (for example, fresh vs. dried), the intended use or level of processing should be specified. The annotations should not refer to trade names, sizes, or other commercial terms. | | 11. Declared quantity: | - Mandatory. The unit and quantity as accurately as possible to allow the NPPO of the importing country to verify the contents of the shipment. Internationally recognized units and terms should be used (for example, metric system). | | 12. Number and description of packages: | - Mandatory. The number of packages and their description should be included. Sufficient details should be included in this section so that the NPPO of the importing country can relate the phytosanitary certificate for export to the corresponding shipment. In some cases (for example, bulk grain and lumber), containers and/or wagons are considered the packaging and the number may be included (for example, "10 containers"). In the case of bulk shipments, the term "in bulk" may be used. | | 13. Distinctive marks: | - Optional. Distinctive marks on the packaging (for example, lot number, serial number, or brand names) as well as the identification numbers or names of the means of transport (for example, container and wagon identification numbers or the name of the ship in the case of bulk shipments) should be included if necessary for the identification of the shipment. | | 14. Additional declaration: | - Optional. Specific additional information required by the NPPO of the importing country regarding a shipment in relation to regulated pests. Additional declarations should be only those containing specific phytosanitary information required by the NPPO of the importing country or requested by the exporter for future phytosanitary certification purposes, and they should not repeat information otherwise noted in the certification statement or in the treatment section. When the phytosanitary import requirements allow several alternative measures, the NPPO of the exporting country should specify in its additional declaration the option that has been applied. In cases where the importing country requires an import permit, the import permit number may be referenced in this section to assist with cross-referencing. When a transit country requires an additional declaration for this transit, the additional declaration indicating the requesting country must be included in this space. | | 15. DISINFECTION AND/OR DISINFESTATION TREATMENT | | | 15.1 Treatment: | - Optional. Type of treatment applied to the shipment (for example, heat treatment, irradiation, fumigation). The treatments indicated should only be those acceptable to the destination country and applied in the exporting or transit country, to meet the phytosanitary requirements of the destination country. For irradiation treatments, the provisions established in ISPM No. 18 should be considered. | | 15.2 Chemical product (active ingredient): | - Optional. Active ingredient of the chemical that has been applied in the treatment. | | 15.3 Concentration: | - Optional. The concentration and dose of the treatment that was applied. | | 15.4 Duration and temperature: | - Optional. Duration of the treatment and temperature of the treatment. | | 15.5 Date of treatment: | - Optional. Date on which the treatment was applied to the shipment. Months should be written with their full name so that there is no confusion with month, day, and year. | | 15.6 Additional information: | - Optional. Any additional information that is pertinent. | | It is certified that the plants, plant products, or other regulated articles described herein have been inspected and/or tested according to appropriate official procedures and are considered to be free from the quarantine pests specified by the importing contracting party and to conform with the current phytosanitary requirements of the importing contracting party, including those for non-quarantine pests. | | | 16. Place of issue: | - Mandatory. Place where the duly authorized official of the NPPO issued the certificate. | | 17. Date of issue: | - Mandatory. The date of issue must be indicated, once the NPPO official verified compliance with the requirements to authorize the issuance of the phytosanitary certificate for export. The date shall be printed, typed, stamped, or handwritten in legible capital letters (when the language permits). The names of the months should be written in full so that there is no confusion between month, day, and year. | | 18. Name of authorized official: | - Mandatory. Name of the NPPO official duly authorized to issue the phytosanitary certificate. The name of the public official shall appear printed, typed, stamped, or handwritten in legible letters and in capital letters (when the language permits). | | 19. Signature: | - Optional. Signature of the official authorized by the competent authority issuing the certificate in the exporting country. | | 20. Seal: | - Optional. The official seal, stamp, or mark identifying the issuing phytosanitary authority should be included on the phytosanitary certificate for export. The public official should add it once the form has been completed, or it may be printed on the phytosanitary certificate for export. Care must be taken to ensure that the stamp, seal, or mark does not obscure essential information. | | Financial responsibility statement: | - Optional. The inclusion of a financial responsibility statement of the NPPO on the phytosanitary certificate for export is optional and at the discretion of the NPPO of the exporting country. | | NOTE: For fields where more information is required, ISPM No. 12, Phytosanitary Certificates of the International Plant Protection Convention (IPPC), in its current version, should be taken as a reference. | |
| DATA | INSTRUCTIONS |
|---|---|
| Ministerio | Mandatory. Name of the Ministry or successor that issues the certificate. |
| Dirección | Mandatory. Address of the Ministry or successor that issues the certificate. |
| Departamento | Mandatory. Department/Directorate that issues the certificate. |
| HEALTH CERTIFICATE FOR EXPORT | |
| 1. Certificate No.: | - Mandatory. Unique identification number of the health certificate for export. |
| 2. Full name, address, and telephone number of the exporter: | - Mandatory. Full name, address, and contact telephone number of the exporting natural/individual or legal person; according to the registry of the competent authority in the exporting State Party. |
| 3. Date and time of departure: | - Mandatory. Date of departure of the export is mandatory for all goods. The scheduled departure time of the export will be mandatory only in the case of trade in live animals. |
| 4. Full name, address, and telephone number of the importer: | - Mandatory. Full name, address, and contact telephone number of the importing natural/individual or legal person; which allows the competent authority in the importing State Party to quickly locate the importer. |
| 5. Country of origin: | - Mandatory. Country from which the merchandise being exported originates (live animals, products and by-products of animal origin, animal genetic material, biological products, animal feed, and pathological material). |
| 6. Country of provenance: | - Mandatory. Applies to merchandise entering from third countries that will be re-exported under the same conditions in which they were imported. |
| 7. Border post of exit: | - Mandatory. Place in the country of provenance through which the merchandise departs. |
| 8. Name and number of the producing establishment (for live animals or genetic material): | - Mandatory. Name of the producing establishment and registration number of the authorized establishment (Epidemiological Unit). The registration number of the establishment producing live animals shall be recorded only when required by the competent health authority of the importing country. Authorized establishment is understood as follows: a) In the case of day-old birds (defined by the OIE), the data of the egg-producing farm must be indicated, as well as the data of the hatchery. b) In the case of fingerlings and larval stages of aquatic animals, the data of the laboratory must be indicated. c) In the case of semen, embryos, and oocytes, the data of the insemination center must be indicated. d) For other animal species not specified above, the data of farms, ranches, breeding centers, or corresponding collection centers must be indicated. |
| 9. Name and number of the processing establishment: | - Mandatory. Name and registration number of the authorized processing establishment (slaughterhouse, processing plant, factory, collection center, among others). |
| 10. Identification of the means of transport: | - Mandatory. Identification of the transport unit (Container/wagon No., truck license plate No., name of the ship, flight No., among others). |
| 11. Seal or lock number: | - Mandatory. Number of the official sanitary seal or lock, or that of the transport company duly declared/authorized by the health authority. |
| 12. Country of destination: | - Mandatory. Name of the destination country of the merchandise. |
| 13. Border post of entry: | - Mandatory. Name of the foreseen border post through which the merchandise will enter, authorized by the destination country, and must correspond to the first point of arrival. |
| 14. Quantity: | - Mandatory. Number of packages, containers, or units, according to the International System of Units (SI). |
| 15. Type of packaging/container: | - Mandatory. Name of the packaging used to pack or containerize the merchandise (boxes, cans, jars, sacks, among others). Not applicable for live animals. |
| 16. Description of the merchandise: | - Mandatory. Specify the type and use of the merchandise. The species, breed, sex, age, color, zootechnical purpose shall be declared as applicable. |
| 17. Scientific name: | - Mandatory. Must be indicated only in the following cases: a) wild animals or CITES. b) eggs, semen, embryos, or oocytes of wild species or CITES. c) aquatic animals, bees, and other arthropods. d) For domestic animals or their genetic material, only the species shall be indicated. Ex.: Equine, bovine, ovine, caprine, swine, day-old birds, leporids, among others. e) Products and by-products from items a, b, c subject to CITES. |
| 18. Net weight in Kg or volume: | - Mandatory. Net weight in kilograms, for the quantity of merchandise indicated in box No. 14. |
| 19. Observations: | - Optional. This part must be completed taking into account the requirements agreed upon by the competent authorities of the importing State Party and the exporting State Party, which may be expanded in annexed sheet(s) to the health certificate for export, for example: lot number, laboratory test results, veterinary medical certificate, treatments, vaccinations, among other declarations requested by the importing country. |
| It is certified that on the indicated date, the merchandise described above was examined, being found at the time of inspection to be in good sanitary conditions and with a normal appearance, typical of the merchandise, which comes from establishments with official authorization. | |
| 20. Name of the official issuing the certificate: | - Mandatory. Name of the official of the competent official health Authority who subscribes to the health certificate for export. |
| 21. Signature of the official issuing the certificate: | - Optional. Signature of the official authorized by the competent authority issuing the certificate in the exporting country. |
| 22. Seal: | - Optional. Emblem of the competent official health authority, which is stamped on the document to authorize it. |
| 23. Date of issue: | - Mandatory. Date on which the official health certificate was issued. Placing the time of issue is optional. |
| 24. Expiration date: | - Mandatory. Expiration date of the health certificate for export. |
| This certificate will be void if it presents erasures or amendments and must comply with legal requirements. |
Use of the Regional Platform Messaging Service Below, the accesses to the messaging service and its method of use are detailed.
| WEB SERVICE ACCESS URL | Test Environment URL pending PDCC Production (real environment) URL pending PDCC |
|---|---|
| Transmission format | <?xml version='1.0' encoding='ISO-8859-1'?> <ns:ENVOLTORIO_MENSAJE xmlns:ns='http://www.sieca.int/Ce rtificadosSM' Servicio='FS001' Usuario='usuario' Contrasena='contraseña'> <ns:MENSAJ E _XML> <![CDATA[EI_Mensaje_XML]]> </ns:MENSAJE_XML> </ns:ENVOLTORIO_MENSAJE> This structure must be respected with each transmission and include the XML Message in the place where it says EI_Mensaje_XML. |
| Messaging service to use | Must include one of the following service codes: · FS001 for transmission of the data set of the information contained in phytosanitary certificates. · FS002 for transmission of the data set of the information contained in health certificates. · FS003 for transmission of events associated with certificates. · FS010 to query the list of transmissions. · FS011 to query the data set of the information contained in a certificate. |
| Username and Password | Must be requested beforehand from the IT Directorate of SIECA. Email addresses of the support area: soporte externo (@sieca.int. |
| Service test utility | Can be downloaded from the URL: URL pending PDCC. See the instructions for using the utility for Windows Operating System in ANNEX 2. |
Schemas and Structures of the Data to Transmit Here are presented the schemas of the XML data structures to transmit and receive.
E1. XML Message for transmitting the data set of the information contained in Phytosanitary Certificates | Fields | | | | Format | Description and permitted values | | --- | --- | --- | --- | --- | --- | | <MENSAJE_CERT_FITO> | | | | | | | | <ENCABEZADO> | | | GROUP, Mandatory | | | | | <MINISTERIO/> | | ALPHANUMERIC (100) Mandatory | Name of the Ministry, use uppercase MINISTERIO | | | | <DIRECCION/> | | ALPHANUMERIC (100) Mandatory | Name of the Directorate, use uppercase DIRECCION | | | | <DEPARTAMENTO/> | | ALPHANUMERIC (100) Mandatory | Name of the Department, use uppercase DEPARTAMENTO | | | | <TIPO_CERTIFICADO/> | | ALPHANUMERIC (3) Mandatory | FIT=Phytosanitary | | | | <CERTIFICADO_NO> | | ALPHANUMERIC (20) Mandatory | Certificate number Auto Generated by the system of the country of origin | | | | <DE_ORGANIZACIÓN_DE_PROTECCIÓN_FITOSANITARIA> | | ALPHANUMERIC (2) Mandatory | Country of origin (exporting country), where the certificate is registered. Possible values: GT, SV, HN, NI, CR, PA (FIELD: Plant protection organization of:) | | | | <PARA_ORGANIZACIÓN_DE_PROTECCIÓN_FITOSANITARIA> | | ALPHANUMERIC (2) Mandatory | Country that must receive the dataset contained in the certificate (Importer). Possible values: GT, SV, HN, NI, CR, PA. Must be different from PAIS_PROCEDENCIA (FIELD: To plant protection organization(s) of) | | | | <PAIS_TRANSITO/> | | ALPHANUMERIC (10) Optional | Possible values: GT, SV, HN, NI, CR, PA (FIELD: To plant protection organization(s) of) | | | | <PAIS_TRANSITO/> | | ALPHANUMERIC (10) Optional | Possible values: GT, SV, HN, NI, CR, PA (FIELD: To plant protection organization(s) of) | | | | <FECHA_HORA_ENVIO/> | | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time the transmission is made. Example: 31/12/2017 23:59:59 | | | </ENCABEZADO> | | | | | | <DATOS> | | | GROUP, Mandatory | | | | | <EXPORTADOR_NOMBRE/> | | ALPHANUMERIC (100) Mandatory | Name of the exporter, use uppercase EXPORTADORA COMERCIAL S.A. | | | | < EXPORTADOR_DIRECCION/> | | ALPHANUMERIC (150) Mandatory | Address of the exporter. Example: Avenida 8 Espino, Colonia San Benito, #345 | | | | <IMPORTADOR_DIRECCION/> | | ALPHANUMERIC (150) Mandatory | Address of the importer. Example: 20 Calle, 22-84, Zona 10, Guatemala | | | | <PAIS_ORIGEN> | | ALPHANUMERIC (2) Mandatory | Country of origin of the goods. Mandatory. See the Country Catalog in ANEXO 1 (FIELD: place of origin) | | | | <PUNTO_ENTRADA_DECLARADO/> | | ALPHANUMERIC (4) Mandatory | FIELD: Declared point of entry. Mandatory. Border, maritime, or air entry post in PAIS_DESTINO. See the catalog in ANEXO 1 | | | | <PUNTO_ENTRADA_DECLARADOTRANSITO> | | ALPHANUMERIC (4) Optional | FIELD: Declared point of entry. Border, maritime, or air entry post in PAIS_DESTINO. See the catalog in ANEXO 1 | | | | <MEDIO_TRANS_DECLARADO> | | ALPHANUMERIC (2) Mandatory | FIELD: Declared means of transport. 1=Maritime, 3=Land (Road), 4=Air, 6=Multimodal, 9=Other | | | | <EMPRESA_TRANSPORTISTA/> | | ALPHANUMERIC (100) Optional | Name of the company. Optional. Example: TRANSPORTE JEREZ | | | | <DATOS_PRODUCTO> | | GROUP, | | | | | | <NUMERO_LINEA> | NUMERIC (3) Mandatory | Consecutive integer starting at one | | | | | <NOMBRE_CIENTIFICO/> | ALPHANUMERIC (100) Mandatory | Botanical name (scientific name). Example: ANNONA SQUAMOSA | | | | | <NOMBRE_PRODUCTO/> | ALPHANUMERIC (150) Mandatory | Product name. Example: ANNONA SQUAMOSA | | | | | <CANTIDAD/> | NUMERIC (18,2) Mandatory | Quantity of goods, greater than zero (corresponds to the DECLARED QUANTITY field). Example: 9,000,000.00 | | | | | <EMPAQUE_EMBALAJE> | ALPHANUMERIC (50) Mandatory | Description of the packaging or packing of the goods. Example: CAJAS | | | | | <NUMERO_BULTOS/> | NUMERIC (18,2) Mandatory | FIELD: Number and description of packages. Example: 20 | | | | | <DESCRIPCION_BULTOS/> | ALPHANUMERIC (100) Mandatory | FIELD: Number and description of packages. Description of the goods. Example: ANONAS | | | | | <MARCAS_DISTINTIVAS/> | ALPHANUMERIC (100) Optional | FIELD: Distinctive Marks | | | | | <DECLARACION_ADICIONAL> | ALPHANUMERIC (4000) Optional | Additional declaration regarding the goods. Specific phytosanitary information required by the NPPO of the importing country. | | | | | <USO_PREVISTO> | ALPHANUMERIC (50) Optional | Intended use of the goods. Example: Consumo | | | | </LINEA> | | | | | | | </DETALLE> | | | | | | | <TRATAMIENTO_APLICADO> | | GROUP, Optional | | | | | | <TRATAMIENTO/> | ALPHANUMERIC (200) Optional | Name of the applied treatment. Example: FUMIGACION | | | | | <PRODUCTO_QUIMICO/> | ALPHANUMERIC (200) Optional | Active ingredient of the applied treatment. Optional. Example: DIOXIDO DE AZUFRE | | | | | <CONCENTRACION/> | ALPHANUMERIC (200) Optional | Concentration of the active ingredient. Example: 0.1 % | | | | | <DURACION_TEMPERATURA> | ALPHANUMERIC (100) Optional | Duration and temperature. 5 minutes, 50 degrees Celsius | | | | | <NOMBRE_RESPONSABLE> | ALPHANUMERIC (100) Optional | Name of the responsible person. Example: Ricardo Antonio Cáceres | | | | | <FECHA_TRATAMIENTO/> | DATE, Optional dd/mm/yyyy | Date of treatment. Example: 31/12/2017 | | | | | <INFORMACIÓN_ADICIONAL> | Optional | End of the INFORMACIÓN_ADICIONAL group | | | | <LUGAR_EXPEDICION> | | ALPHANUMERIC (100) Mandatory | Place of issuance: place where the duly authorized official of the NPPO issued the certificate. | | | | <FECHA_EXPEDICION> | | DATE, dd/mm/yyyy Mandatory | Date of issuance. Example: 31/12/2017 | | | | <NOMBRE_FUNC_AUTORIZADO> | | ALPHANUMERIC (100) Mandatory | Name of the authorized official: name of the NPPO official duly authorized to issue the phytosanitary certificate. Example: Ricardo Antonio Cáceres | | | | <DECLARACION_RESPONSABILIDAD_FINANCIERA> | | ALPHANUMERIC (100) Optional | Declaration of financial responsibility: the inclusion of a financial responsibility statement from the NPPO on the export phytosanitary certificate is optional and at the discretion of the NPPO of the exporting country. | | | | </LINEA> | | | | | --- | --- | --- | --- | --- | --- | | | | </DETALLE> | | | | | | | <TRATAMIENTO_APLICADO> | | GROUP, Optional | | | | | | <TRATAMIENTO/> | ALPHANUMERIC (200) Optional | Name of the applied treatment. Example: FUMIGACION | | | | | <PRODUCTO_QUIMICO/> | ALPHANUMERIC (200) Optional | Active ingredient of the applied treatment. Example: DIOXIDO DE AZUFRE | | | | | <CONCENTRACION/> | ALPHANUMERIC (200) Optional | Concentration of the active ingredient. Example: 0.1 % | | | | | <DURACION_TEMPERATURA> | ALPHANUMERIC (100) Optional | Duration and temperature. 5 minutes, 50 degrees Celsius | | | | | <NOMBRE_RESPONSABLE> | ALPHANUMERIC (100) Optional | Name of the responsible person. Example: Ricardo Antonio Cáceres | | | | | <FECHA_TRATAMIENTO/> | DATE, Optional dd/mm/yyyy | Date of treatment. Example: 31/12/2017 | | | | | <INFORMACIÓN_ADICIONAL> | Optional | End of the INFORMACIÓN_ADICIONAL group | | | | <LUGAR_EXPEDICION> | | ALPHANUMERIC (100) Mandatory | Place of issuance: place where the duly authorized official of the NPPO issued the certificate. | | | | <FECHA_EXPEDICION> | | DATE, dd/mm/yyyy Mandatory | Date of issuance. Example: 31/12/2017 | | | | <NOMBRE_FUNC_AUTORIZADO> | | ALPHANUMERIC (100) Mandatory | Name of the authorized official: name of the NPPO official duly authorized to issue the phytosanitary certificate. Example: Ricardo Antonio Cáceres | | | | <DECLARACION_RESPONSABILIDAD_FINANCIERA> | | ALPHANUMERIC (100) Optional | Declaration of financial responsibility: the inclusion of a financial responsibility statement from the NPPO on the export phytosanitary certificate is optional and at the discretion of the NPPO of the exporting country. | | | <DATOS> | | | | | | </MENSAJE_CERT_FITO> | | | | | | E2. XML Message for transmitting the dataset of the information contained in Sanitary Certificates Used for Animals, Products and By-products, and Concentrated Feed.
| Fields | | | | Format | Description and permitted values | | --- | --- | --- | --- | --- | --- | | <MENSAJE_CERTZOO> | | | | | | | | <ENCABEZADO> | | | GROUP, Mandatory | | | | | <MINISTERIO> | | ALPHANUMERIC (100) Mandatory | Name of the Ministry, use uppercase MINISTERIO | | | | <DIRECCION> | | ALPHANUMERIC (100) Mandatory | Name of the Directorate, use uppercase DIRECCION | | | | <DEPARTAMENTO/> | | ALPHANUMERIC (100) Mandatory | Name of the Department, use uppercase DEPARTAMENTO | | | | <TIPO_CERTIFICADO/> | | ALPHANUMERIC (3) Mandatory | 200= Veterinary, Sanitary or both | | | | <CERTIFICADO_NO> | | ALPHANUMERIC (20) Mandatory | Certificate number Auto Generated by the system of the country of origin | | | | <FECHA_HORA_ENVIO/> | | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time the transmission is made. Example: 31/12/2017 23:59:59 | | | </ENCABEZADO> | | | | | | | <DATOS> | | | GROUP, Mandatory | | | | | <EXPORTADOR_NOMBRE/> | | ALPHANUMERIC (100) Mandatory | Name of the exporter, use uppercase EXPORTADORA COMERCIAL S.A. | | | | <EXPORTADOR_DIRECCION/> | | ALPHANUMERIC (150) Mandatory | Address of the exporter. Example: Avenida El Espino, Colonia San Benito, 11345 | | | | <EXPORTADOR_TELEFONO/> | | ALPHANUMERIC (50) Mandatory | Telephone numbers of the exporter, separated by commas. (+503)12345678, 3456-7890 | | | | <FECHA_SALIDA> | | DATETIME Mandatory dd/mm/yyyy HH24:MM:ss | Departure date of the export. Example: 31/12/2017 23:59:59 | | | | <HORA_SALIDA> | | DATETIME Optional dd/mm/yyyy HH24:MM:ss | Departure time of the export. Example: 31/12/2017 23:59:59 | | | | <IMPORTADOR_NOMBRE/> | | ALPHANUMERIC (100) Mandatory | Name of the importer, use uppercase IMPORTADORA COMERCIAL S.A. | | | | <IMPORTADOR_TELEFONO/> | | ALPHANUMERIC (50) Mandatory | Telephone numbers of the exporter, separated by commas. (+502)1234-5678, 3456-7890 | | | | <PAIS_ORIGEN/> | | ALPHANUMERIC (2) Mandatory | Country where the merchandise being exported originates. | | | | <PAIS_PROCEDENCIA> | | ALPHANUMERIC (2) | Country of origin, where the certificate is registered. Optional in cases of export. Mandatory in cases of re-export. | Possible values: GT, SV, HN, NI, CR, PA | | | | <PUESTO_FRONTERIZO_SALIDA> | | ALPHANUMERIC (5) Mandatory | Border, maritime, or air departure post in PAIS_PROCEDENCIA. See the catalog in ANEXO 1. | | | | <NOMBRE_ESTABLECIMIENTO_PRODUCTOR> | | ALPHANUMERIC (150) Mandatory | Name of the producing establishment for live animals or genetic material. | | | | <NUMERO_ESTABLECIMIENTO_PRODUCTO> | | ALPHANUMERIC (150) Optional | Number of the producing establishment for live animals or genetic material. | | | | | <DATOS_INCUBADORA> | ALPHANUMERIC (150) Optional | For day-old birds (defined by the OIE), the data of the egg-producing farm and the hatchery data are mandatory. | | | | | <DATOS_LABORATORIO/> | ALPHANUMERIC (150) Optional | For fry and larval stages of aquatic animals, it is mandatory to indicate the laboratory data. | | | | | <DATOS_CENTRO_INSEMINACION/> | ALPHANUMERIC (150) Optional | For semen, embryos, and oocytes, it is mandatory to indicate the data of the insemination center. | | | | | <DATOS_FINCAS/GRANJAS/ZOOCRIADEROS/CENTRO_ACOPIO/> | ALPHANUMERIC (150) Optional | For other animal species not specified above, it is mandatory to indicate the data of the corresponding farms, ranches, breeding centers, or collection centers. | | | | <NOMBRE_ESTABLECIMIENTO_PROCESADOR> | | ALPHANUMERIC (150) Mandatory | Name of the processing establishment. Includes the number that identifies it in the exporting country. Must be different from ESTABLECIMIENTO_PRODUCTOR. | | | | <NUMERO_ESTABLECIMIENTO_PROCESADOR> | | ALPHANUMERIC (150) Mandatory | Number of the authorized processing establishment (slaughter plant, processing plant, factory, collection center, among others). | | | | <IDENTIFICACION_TRANSPORTE> | | ALPHANUMERIC (10) Mandatory | Identification (License Plate) of the means of transport. Uppercase, without hyphens, only letters and numbers. | | | | <MARCHAMOS_PRECINTOS/> | | ALPHANUMERIC (20) Mandatory | Seals or tags on the transport. Uppercase, only letters, numbers, and hyphens. The value N/A may be reported when the information is not available. | | | | <PAIS_DESTINO> | | ALPHANUMERIC (2) Mandatory | Destination country of the goods. Possible values: GT, SV, HN, NI, CR, PA. Must match ENCABEZADO/PAIS_RECIBE. | | | | <PUESTO_FRONTERIZO_INGRESO> | | ALPHANUMERIC (5) Mandatory | Border, maritime, or air entry post in PAIS_DESTINO. See the catalog in ANEXO 1. | | | | <MODALIDAD_TRANSPORTE/> | | ALPHANUMERIC (2), Optional | 1=Maritime, 3=Land (Road), 4=Air, 6=Multimodal, 9=Other | | | | <DETALLE> | | LIST, Mandatory | | | | | <LINEA> | | GROUP, 1 to many | | | | | | <NUMERO_LINEA> | NUMERIC (3) Mandatory | Consecutive integer starting at one | | | | | <CANTIDAD/> | NUMERIC (18,2) Mandatory | Quantity of goods, greater than zero. Example: 9,000,000.00 | | | | | <EMPAQUE_EMBALAJE/> | ALPHANUMERIC (50) Mandatory | Description of the packaging or packing of the goods. Example: UNIDADES. Consider that it does not apply for live animals. | | | | | <DESCRIPCION/> | ALPHANUMERIC (100) Mandatory | Description of the goods. Mandatory. Example: CABRAS | | | | | <USO_PREVISTO> | ALPHANUMERIC (50) Optional | | | | | | <NOMBRE_CIENTIFICO/> | ALPHANUMERIC (100) Optional | However, it is mandatory for the cases described in Sections A, B, C, D, and E of the filling instructions. Scientific name. Example: CAPRA AEGAGRUS HIRCUS. Consider that it is only mandatory for the following cases: a) wild animals or CITES. b) eggs, semen, embryos, or oocytes of wild or CITES species. c) aquatic animals, bees, and other arthropods. d) For domestic animals or their genetic material, only the species will be indicated. E.g.: Equine, bovine, ovine, caprine, swine, day-old birds, leporids, among others. e) Products and by-products of sections a, b, c subject to CITES. | | | | | <PESO_NETO/> | NUMERIC (18,2), greater than zero Mandatory | Net weight in kilograms or volume, greater than zero. Example: 9,000,000.00 | | | | </LINEA> | | | | | | | </DETALLE> | | | | | | | <OBSERVACIONES/> | | ALPHANUMERIC (1000) Optional | Observations on the certificate. | | | | <NOMBRE_FUNCIONARIO_EMISOR/> | | ALPHANUMERIC (100) Mandatory | Name of the official issuing the certificate. Example: Mandatory Ricardo Antonio Cáceres, Inspector | | | | <FECHA_EXPEDICION/> | | DATE, Mandatory dd/mm/yyyy | Issuance date of the goods. Example: 31/12/2017 | | | | <FECHA_VENCIMIENTO/> | | DATE, Mandatory dd/mm/yyyy | Expiration date of the goods. Example: 31/12/2017 | | | </DATOS> | | | | | | </MENSAJE_CERTZOO> | | | | | | E3. XML Message for transmitting events associated with Certificates (including cancellation, modification, or replacement). See comment 6.
| Fields | | | Format | Description and permitted values | | --- | --- | --- | --- | --- | | <MENSAJE_CERT_EVENTOS> | | | | | | | <ENCABEZADO> | | GROUP, Mandatory | | | | | <TIPO_CERTIFICADO/> | ALPHANUMERIC (3) Mandatory | FIT=Phytosanitary, ZOO=Sanitary | | | | <CERTIFICADO_NO> | ALPHANUMERIC (20) Mandatory | Certificate number Auto Generated by the system of the country of origin | | | | <PAIS_PROCEDENCIA> | ALPHANUMERIC (2) Mandatory | Country of origin, where the certificate is registered. Possible values: GT, SV, HN, NI, CR, PA | | | | <PAIS_RECIBE/> | ALPHANUMERIC (2) Mandatory | Country that must receive the dataset contained in the certificate. Possible values: GT, SV, HN, NI, CR, PA. Must be different from PAIS_PROCEDENCIA. | | | | <FECHA_HORA_ENVIO/> | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time the transmission is made. Example: 31/12/2017 23:59:59 | | | </ENCABEZADO> | | | | | | <EVENTOS> | | LIST, Mandatory | | | | <EVENTO> | | GROUP, 1 to many | | | | | <CODIGO_EVENTO/> | ALPHANUMERIC (3) Mandatory | ANU=Cancellation | | | | <FECHA_EVENTO/> | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time of the event. Example: 31/12/2017 23:59:59 | | | | <PAIS_EVENTO/> | ALPHANUMERIC (2) Mandatory | Country that originates and reports the event. Possible values: GT, SV, HN, NI, CR, PA or 99 for the Regional Platform. | | | | <REFERENCIA/> | ALPHANUMERIC (20) Optional | Reference or related document number for the event. | | | | <OBSERVACIONES/> | ALPHANUMERIC (400) Optional | Reason or comment about the event. | | | </EVENTO> | | | | | | </EVENTOS> | | | | | <MENSAJE_CERT_EVENTOS> | | | | | E4. XML Response to the transmission of the dataset or events | Fields | | | Format | Description and permitted values | | --- | --- | --- | --- | --- | | <RESPUESTA_CERT> | | | | | | | <TIPO_CERTIFICADO/> | | ALPHANUMERIC (3) Mandatory | Same as the message | | | <CERTIFICADO_NO> | | ALPHANUMERIC (20) Mandatory | Same as the message | | | <PAIS_PROCEDENCIA> | | ALPHANUMERIC (2) Mandatory | Same as the message | | | <PAIS_RECIBE/> | | ALPHANUMERIC (2) Mandatory | Same as the message | | | <OCURRIO_ERROR/> | | ALPHANUMERIC (1) Mandatory | S=Yes or N=No | | | <ERRORES> | | LIST, Optional | Returned when OCURRIO_ERROR is Y(es) | | | <ERROR> | | GROUP, 0 to many | | | | | <CODIGO/> | ALPHANUMERIC (5) Mandatory | Error code. See the Error Catalog in ANEXO 1. Example: 001 | | | | <DESCRIPCION> | ALPHANUMERIC (200) Optional | Custom error description. Example: Element EXPORTADOR_NOMBRE does not exist | | | </ERROR> | | | | | | </ERRORES> | | | | | </RESPUESTA_CERT> | | | | | ES. XML Message for querying the dataset in a Certificate | Fields | | Format | Description and permitted values | | --- | --- | --- | --- | | <MENSAJE_CONSULTA_CERT> | | | | | | <TIPO_CERTIFICADO/> | ALPHANUMERIC (3) Mandatory | Type of certificate to query. FIT=Phytosanitary, ZOO=Sanitary | | | <CORRELATIVO_TRANSACCION/> | ALPHANUMERIC (20) Mandatory | Certificate number to query | | | <PAIS_PROCEDENCIA> | ALPHANUMERIC (2) Mandatory | Country of origin, where the certificate was registered. Possible values: GT, SV, HN, NI, CR, PA | | | <PAIS_RECIBE/> | ALPHANUMERIC (2) Mandatory | Country that makes the query and will receive the response with the dataset. Possible values: GT, SV, HN, NI, CR, PA. Must be different from PAIS_PROCEDENCIA. | | </MENSAJE_CONSULTA_CERT> | | | | E6. XML Response to the query of the dataset in a Certificate One of the following three messages is returned as a response:
- E1 XML Message for transmitting the dataset of the information contained in Phytosanitary Certificates. - E2 XML Message for transmitting the dataset of the information contained in Sanitary Certificates. - E3 XML Response to the transmission (UPON THE OCCURRENCE OF AN ERROR) E7. XML Message for querying a list of transmissions | Fields | | Format | Description and permitted values | | --- | --- | --- | --- | | <MENSAJE_CONSULTA_LISTA> | | | | | | <TIPO_CONSULTA> | ALPHANUMERIC (2) Mandatory | | | | <TIPO_CERTIFICADO/> | ALPHANUMERIC (3) Optional | | | | <PAIS_CONSULTA> | ALPHANUMERIC (2) Mandatory | | | | <FECHA_CONSULTA> | DATE, Mandatory dd/mm/yyyy | Date to query. Example: 31/12/2017 | | </MENSAJE_CONSULTA_LISTA> | | | | | Fields | | | Format | Description and permitted values | | --- | --- | --- | --- | --- | | <RESPUESTA_CONSULTA_LISTA> | | | | | | | <TIPO_CONSULTA/> | | ALPHANUMERIC (2) Mandatory | Same as the message | | | <TIPO_CERTIFICADO/> | | ALPHANUMERIC (3) Optional | Same as the message | | | <PAIS_CONSULTA/> | | ALPHANUMERIC (2) Mandatory | Same as the message | | | <FECHA_CONSULTA> | | DATE, Mandatory dd/mm/yyyy | Same as the message | | | <CUENTA_CERTIFICADOS/> | | NUMERIC (4) Mandatory | Number of records returned in the CERTIFICADOS group. Equal to or greater than zero. | | | <CUENTA_EVENTOS> | | NUMERIC (4) Mandatory | Number of records returned in the EVENTOS group. Equal to or greater than zero. | | | <OCURRIO_ERROR> | | ALPHANUMERIC (1) Mandatory | S=Yes or N=No | | | <CERTIFICADOS> | | LIST, Optional | Returned when CUENTA_CERTIFICADOS is greater than zero | | | <ENCABEZADO> | | GROUP, 0 to many | | | | | <TIPO_CERTIFICADO/> | ALPHANUMERIC (3) Mandatory | FIT=Phytosanitary, ZOO=Sanitary | | | | <CORRELATIVO_TRANSACCION/> | ALPHANUMERIC (20) Mandatory | Certificate number | | | | <PAIS_PROCEDENCIA/> | ALPHANUMERIC (2) Mandatory | Country of origin, where the certificate was registered. Possible values: GT, SV, HN, NI, CR, PA | | | | <FECHA_HORA_ENVIO/> | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time the dataset transmission was made. Example: 31/12/2017 23:59:59. The truncated date must match FECHA_CONSULTA. | | | </ENCABEZADO> | | | | | | </CERTIFICADOS> | | | | | | <EVENTOS> | | LIST, Optional | Returned when CUENTA_EVENTOS is greater than zero | | | <EVENTO> | | GROUP, 0 to many | | | | | <TIPO_CERTIFICADO/> | ALPHANUMERIC (3) Mandatory | FIT=Phytosanitary, ZOO=Sanitary | | | | <CORRELATIVO_TRANSACCION/> | ALPHANUMERIC (20) Mandatory | Certificate number | | | | <PAIS_PROCEDENCIA/> | ALPHANUMERIC (2) Mandatory | Country of origin, where the certificate was registered. Possible values: GT, SV, HN, NI, CR, PA | | | | <CODIGO_EVENTO/> | ALPHANUMERIC (3) Mandatory | ANU=Cancellation | | | | <FECHA_EVENTO/> | DATETIME, Mandatory dd/mm/yyyy HH24:MM:ss | Date and time of the event. Example: 31/12/2017 23:59:59. The truncated date must match FECHA_CONSULTA. | | | | <PAIS_EVENTO/> | ALPHANUMERIC (2) Mandatory | Country that originated and reported the event. Possible values: GT, SV, HN, NI, CR, PA or 99 for the Regional Platform. | | | | <REFERENCIA/> | ALPHANUMERIC (20) Optional | Reference or related document number for the event. | | | | <OBSERVACIONES/> | ALPHANUMERIC (400) Optional | Reason or comment about the event. | | | </EVENTO> | | | | | | </EVENTOS> | | | | | | <ERRORES> | | LIST, Optional | Returned when OCURRIO_ERROR is Y(es) | | | <ERROR> | | GROUP, 0 to many | | | | | <CODIGO/> | ALPHANUMERIC (5) Mandatory | Error code. See the Error Catalog in ANEXO 1. Example: 001 | | | | <DESCRIPCION/> | ALPHANUMERIC (200) Optional | Custom error description. Example: Element FECHA_CONSULTA not valid | | | </ERROR> | | | | | | </ERRORES> | | | | | </RESPUESTA_CONSULTA_LISTA> | | | | |
Error Catalog
| Code | Transport Mode |
|---|---|
| 0** | ERRORS GENERATED ON THE REGIONAL PLATFORM |
| 001 | Message schema error. |
| 002 | Error processing the message. |
| 003 | Error persisting the message in the database. |
| 010 | Error in the header data. |
| 011 | Error validating a message data. Incorrect format data. |
| 012 | Error validating a message data. Incorrect value data. |
| 013 | Error validating a message data. Data must be greater than zero. |
| 014 | Error validating a message data. Invalid date. |
| 020 | Unknown Country of Origin code. |
| 021 | Exit Post code is not valid or does not correspond to the Country of Origin. |
| 022 | Entry Post code is not valid or does not correspond to the Country of Destination. |
| 030 | Service and dataset type do not match. |
| 040 | Unknown event code. |
| 050 | Transaction correlative (certificate) does not exist. |
| 090 | Controlled but unknown error. |
| 100 | ERRORS GENERATED IN THE DESTINATION COUNTRY OF THE MESSAGE |
| 101 | Message schema error. |
| 102 | Error processing the message. |
| 103 | Error persisting the message in the database. |
| 110 | Error in the header data. |
| 111 | Error validating a message data. Incorrect format data. |
| 112 | Error validating a message data. Incorrect value data. |
| 113 | Error validating a message data. Data must be greater than zero. |
| 114 | Error validating a message data. Invalid date. |
| 120 | Unknown Country of Origin code. |
| 121 | Exit Post code is not valid or does not correspond to the Country of Origin. |
| 122 | Entry Post code is not valid or does not correspond to the Country of Destination. |
| 130 | Service and dataset type do not match. |
| 140 | Unknown event code. |
| 150 | Transaction correlative (certificate) does not exist. |
| 190 | Controlled but unknown error. |
Country Catalog The 2-digit alphabetic coding of the ISO 3166-1 standard will be used.
See: http://es.wikipedia.org/wiki/ISO_3166-1.
| Code | Country |
|---|---|
| AD | Andorra |
| AE | United Arab Emirates |
| AF | Afghanistan |
| AG | Antigua and Barbuda |
| AI | Anguilla |
| AL | Albania |
| AM | Armenia |
| AO | Angola |
| AQ | Antarctica |
| AR | Argentina |
| AS | American Samoa |
| AT | Austria |
| AU | Australia |
| AW | Aruba |
| AX | Åland Islands |
| AZ | Azerbaijan |
| BA | Bosnia and Herzegovina |
| BB | Barbados |
| BD | Bangladesh |
| BE | Belgium |
| BF | Burkina Faso |
| BG | Bulgaria |
| BH | Bahrain |
| BI | Burundi |
| BJ | Benin |
| BL | Saint Barthélemy |
| BM | Bermuda |
| BN | Brunei |
| BO | Bolivia |
| BQ | Caribbean Netherlands |
| BR | Brazil |
| BS | Bahamas |
| BT | Bhutan |
| BV | Bouvet Island |
| BW | Botswana |
| BY | Belarus |
| BZ | Belize |
| CA | Canada |
| CC | Cocos Islands |
| CD | Democratic Republic of the Congo |
| CF | Central African Republic |
| CG | Republic of the Congo |
| CH | Switzerland |
| CI | Ivory Coast |
| CK | Cook Islands |
| CL | Chile |
| CM | Cameroon |
| CN | China |
| CO | Colombia |
| CR | Costa Rica |
| CU | Cuba |
| CV | Cape Verde |
| CW | Curaçao |
| CX | Christmas Island |
| CY | Cyprus |
| cz | Czech Republic |
| DE | Germany |
| DJ | Djibouti |
| DK | Denmark |
| DM | Dominica |
| DO | Dominican Republic |
| DZ | Algeria |
| EC | Ecuador |
| EE | Estonia |
| EG | Egypt |
| EH | Sahrawi Arab Democratic Republic |
| ER | Eritrea |
| ES | Spain |
| ET | Ethiopia |
| FI | Finland |
| FJ | Fiji |
| FK | Falkland Islands |
| FM | Micronesia |
| FO | Faroe Islands |
| FR | France |
| GA | Gabon |
| GB | United Kingdom |
| GD | Grenada |
| GE | Georgia |
| GF | French Guiana |
| GG | Guernsey |
| GH | Ghana |
| GI | Gibraltar |
| GL | Greenland |
| GM | Gambia |
| GN | Guinea |
| GP | Guadalupe |
| GQ | Equatorial Guinea |
| GR | Greece |
| GS | South Georgia and the South Sandwich Islands |
| GT | Guatemala |
| GU | Guam |
| GW | Guinea-Bissau |
| GY | Guyana |
| HK | Hong Kong |
| HM | Heard Island and McDonald Islands |
| HN | Honduras |
| HR | Croatia |
| HT | Haiti |
| HU | Hungary |
| ID | Indonesia |
| IE | Ireland |
| IL | Israel |
| IM | Isle of Man |
| IN | India |
| IO | British Indian Ocean Territory |
| IQ | lrak |
| IR | Iran |
| IS | Iceland |
| IT | Italy |
| JE | Jersey |
| JM | Jamaica |
| JO | Jordan |
| JP | Japan |
| KE | Kenya |
| KG | Kyrgyzstan |
| KH | Cambodia |
| KI | Kiribati |
| KM | Comoros |
| KN | Saint Kitts and Nevis |
| KP | North Korea |
| KR | South Korea |
| KW | Kuwait |
| KY | Cayman Islands |
| KZ | Kazakhstan |
| LA | Laos |
| LB | Lebanon |
| LC | Saint Lucia |
| LI | Liechtenstein |
| LK | Sri Lanka |
| LR | Liberia |
| LS | Lesotho |
| LT | Lithuania |
| LU | Luxembourg |
| LV | Latvia |
| LY | Libya |
| MA | Morocco |
| MC | Monaco |
| MD | Moldova |
| ME | Montenegro |
| MF | Saint Martin |
| MG | Madagascar |
| MH | Marshall Islands |
| MK | Macedonia |
| ML | Mali |
| MM | Myanmar |
| MN | Mongolia |
| MO | Macao |
| MP | Northern Mariana Islands |
| MQ | Martinique |
| MR | Mauritania |
| MS | Montserrat |
| MT | Malta |
| MU | Mauritius |
| MV | Maldives |
| MW | Malawi |
| MX | Mexico |
| MY | Malaysia |
| MZ | Mozambique |
| NA | Namibia |
| NC | New Caledonia |
| NE | Niger |
| NF | Norfolk Island |
| NG | Nigeria |
| NI | Nicaragua |
| NL | Netherlands |
| NO | Norway |
| NP | Nepal |
| NR | Nauru |
| NU | Niue |
| NZ | New Zealand |
| OM | Oman |
| PA | Panama |
| PE | Peru |
| PF | French Polynesia |
| PG | Papua New Guinea |
| PH | Philippines |
| PK | Pakistan |
| PL | Poland |
| PM | Saint Pierre and Miquelon |
| PN | Pitcairn Islands |
| PR | Puerto Rico |
| PS | Palestine |
| PT | Portugal |
| PW | Palau |
| PY | Paraguay |
| QA | Qatar |
| RE | Réunion |
| RO | Romania |
| RS | Serbia |
| RU | Russia |
| RW | Rwanda |
| SA | Saudi Arabia |
| SB | Solomon Islands |
| SC | Seychelles |
| SD | Sudan |
| SE | Sweden |
| SG | Singapore |
| SH | Saint Helena, Ascension and Tristan da Cunha |
| SI | Slovenia |
| SJ | Svalbard and Jan Mayen |
| SK | Slovakia |
| SL | Sierra Leone |
| SM | San Marino |
| SN | Senegal |
| SO | Somalia |
| SR | Suriname |
| SS | South Sudan |
| ST | São Tomé and Príncipe |
| SV | El Salvador |
| SX | Sint Maarten |
| SY | Syria |
| SZ | Swaziland |
| TC | Turks and Caicos Islands |
| TD | Chad |
| TF | French Southern and Antarctic Lands |
| TG | Togo |
| TH | Thailand |
| TJ | Tajikistan |
| TK | Tokelau |
| TL | East Timor |
| TM | Turkmenistan |
| TN | Tunisia |
| TO | Tonga |
| TR | Turkey |
| TT | Trinidad and Tobago |
| TV | Tuvalu |
| TW | Taiwan (Republic of China) |
| TZ | Tanzania |
| UA | Ukraine |
| UG | UG Uganda |
| UM | UM United States Minor Outlying Islands |
| US | United States |
| UY | Uruguay |
| UZ | Uzbekistan |
| VA | Vatican City |
| VC | Saint Vincent and the Grenadines |
| VE | Venezuela |
| VG | British Virgin Islands |
| VI | United States Virgin Islands |
| VN | Vietnam |
| VU | Vanuatu |
| WF | Wallis and Futuna |
| WS | Samoa |
| YE | Yemen |
| YT | Mayotte |
| ZA | South Africa |
| ZM | Zambia |
| ZW | Zimbabwe |
Catalog of Border, Maritime, and Air Posts The coding provided by each customs administration in Central America will be used. An initial catalog is provided below. It should be noted that these codes are added over time and may occasionally change in coding.
| Country | Code | Customs Office |
|---|---|---|
| CR | 002 | ADUANA DE CALDERA |
| CR | 003 | ADUANA DE PEÑAS BLANCAS |
| CR | 005 | ADUANA SANTAMARÍA (serves the airport) |
| CR | 006 | ADUANA DE LIMÓN |
| CR | 007 | ADUANA DE PASO CANOAS |
| CR | 034 | LAS TABLILLAS |
| CR | 091 | PUESTO SIXALOA |
| CR | 013 | LA ANEXIÓN |
| GT | ST | ADUANA SANTO TOMAS DE CASTILLA |
| GT | PQ | ADUANA PUERTO QUETZAL |
| GT | PB | ADUANA PUERTO BARRIOS |
| GT | TU | ADUANA TECUN UMAN |
| GT | EC | ADUANA EL CARMEN |
| GT | LM | ADUANA LA MESILLA |
| GT | MM | ADUANA MELCHOR DE MENCOS |
| GT | H8 | ADUANA INTEGRADA EL FLORIDO |
| GT | PA | ADUANA PEDRO DE ALVARADO |
| GT | VN | ADUANA VALLE NUEVO |
| GT | se | ADUANA SAN CRISTOBAL |
| GT | H7 | ADUANA INTEGRADA AGUA CALIENTE |
| GT | LE | ADUANA LA.ERMITA |
| GT | CA | ADUANA CENTRAL DE AVIACION |
| GT | CB | EL CEIBO |
| GT | H6 | ADU.ANA INTEGRADA EL CORINTO |
| HN | 0002 | ADUANA LA CEIBA |
| HN | 0003 | ADUANA PUERTO HENECAN-SN LORENZO |
| HN | 0004 | ADUANA PUERTO CORTES |
| HN | 0006 | ADUANA ROATAN |
| HN | 0009 | ADUANA PUERTO CASTILLA |
| HN | 0011 | ADUANA LA MESA (serves the S.P.S. airport) |
| HN | 0014 | ADUANA DE TONCONTIN (serves the airport of |
| HN | 0016 | ADUANA INTEGRADA EL CORINTO |
| HN | 0020 | ADUANA AGUA CALIENTE |
| HN | 0023 | ADUANA EL AMATILLO |
| HN | 0024 | ADUANA EL FLORIDO |
| HN | 0025 | ADUANA EL POY |
| HN | 0027 | ADUANA LA FRATERNIDAD |
| HN | 0029 | ADUANA GUASAULE |
| HN | 0034 | ADUANA LAS MANOS |
| NI | 0110 | ADUANA CENTRAL DE CARGA AEREA |
| NI | 0180 | AEROPUERTO COSTA ESMERALDA |
| NI | 0220 | EL ESPINO |
| NI | 0230 | GUASAULE |
| NI | 0240 | LAS MANOS |
| NI | 0250 | PEÑAS BLANCAS |
| NI | 0270 | SAN PANCHO |
| NI | 0315 | EL BLUFF |
| NI | 0330 | POTOSI |
| NI | 0335 | PUERTO CABEZAS |
| NI | 0340 | PUERTO CORINTO |
| NI | 0350 | PUERTO SANDINO |
| NI | 0640 | EL RAMA (PUERTO ESPERANZA) |
| PA | 0103 | AEROPUERTO DE BOCAS DEL TORO |
| PA | 0104 | GUABITO |
| PA | 0201 | AEROPUERTO CARGA TOCUMEN |
| PA | 0302 | ZONA LIBRE DE COLON |
| PA | 0402 | AEROPUERTO ENRIQUE MALEK-DAVID |
| PA | 0403 | PASO CANOAS |
| PA | 0867 | AEROPUERTO DE ALBROOK |
| SV | 02 | MARÍTIMA DE ACAJUTLA |
| SV | 03 | AÉREA MONSEÑOR ÓSCAR ARNULFO ROMERO |
| SV | 04 | TERRESTRE LAS CHINAMAS |
| SV | 05 | TERRESTRE LA HACHADURA |
| SV | 07 | TERRESTRE SAN CRISTÓBAL |
| SV | 08 | TERRESTRE ANGUIATÚ |
| SV | 09 | TERRESTRE EL AMATILLO |
| SV | 10 | MARÍTIMA LA UNIÓN (Puerto Cutuco} |
| SV | 11 | TERRESTRE EL POY |
| SV | 33 | PUERTO SARILLAS |
| Country | Border Post | Country | Border Post |
|---|---|---|---|
| Guatemala | La Ermita | El Salvador | Anguiatú |
| Guatemala | San Cristóbal | El Salvador | San Cristóbal |
| Guatemala | Valle Nuevo | El Salvador | Las Chinamas |
| Guatemala | Pedro de Alvarado | El Salvador | La Hachadura |
| Guatemala | Corinto | Honduras | Corinto |
| Guatemala | Agua Caliente | Honduras | Agua Caliente |
| Guatemala | El Florido | Honduras | El Florido |
| Honduras | Guasaule | Nicaragua | Guasaule |
| Nicaragua | Peña Blanca | Costa Rica | Peña Blanca |
| Nicaragua | San Pancho | Costa Rica | Las Tablillas |
| Costa Rica | Sixaola | Panamá | Guabito |
| Costa Rica | Paso Canoas | Panamá | Paso Canoas |
The data transmission utility works as follows:
1. In the transmission utility directory, the following files are located:
Run the application SIECA.BizTalk.Utílities.App.exe (by pressing the mouse button twice on the file or locating and pressing the Enter key).
2. When the program starts, it will display the following screen:
3. You must click on the configuration tab to enter the username and password provided for data transmission and verify the web service parameters (i.e., its address and method). This latter information is already entered in the application.
The username and password you currently have is a test user and must be replaced by the provided usernames and passwords; if you use this user, the information will be registered only as a test and will not reflect the transmission flow.
4. When clicking on the Web Service tab, you can load an XML message (sample message XML files are attached in the directory to replicate the information at the time of transmission).
The XML load is entered, and the XML gives a response indicating whether the transmission was successful or if any issues occurred during sending.
1a. The XML message to be transmitted, containing the dataset of the information contained in the certificate, is entered by clicking on the Browse tab and then locating the prepared XML.
1b. It displays the XML to be transmitted; the XML is for viewing only.
After loading the XML, the Test Web Service button is pressed, and it will carry out the transmission of the XML message.
(02) Web Service message Request indicates 5. The History tab shows us the transactions that have been carried out in the current transmission session.
6. The Code & Decode tab allows us to encode the XML to base 64 to transmit it encoded.
Updated as of February 2018.
| Country | Officials | Position | Institution | Email | | --- | --- | --- | --- | --- | | GUATEMALA | Mynor Alarcón | Advisor | Ministerio de Economía | [email protected] | | Estuardo Arriaga | Manager | VUPE | estuardo .a [email protected] | | | Eddy Méndez | IT Technician | VUPE | eddy. [email protected] | | | Leónidas | Advisor | Ministerio de Agricultura | [email protected] | | | Valenzuela | IT Technician | Ministerio de Agricultura | [email protected] | | | Ludwig Mas | IT Technician | Ministerio de Agricultura | [email protected] | | | Kenneth Coronado | Advisor | Ministerio de Economía [email protected] | [email protected] | | | EL SALVADOR | José Camelio Deras | Department Head | Centro de Trámites de Importaciones y Exportaciones | [email protected] | | Emérita Castro | Head of the Imports Section | Centro de Trámites de Importaciones y Exportaciones | [email protected] | | | Juan Carlos Laug Milla | Technician | Banco Central de la Reserva de El Salvador | [email protected] | | | Juan Carlos Abarca Domínguez | IT | Ministerio de Agricultura | [email protected] | | | Romeo Romero | Coordinator of Tariff Policy and Trade Facilitation Measures | Banco Central de la Reserva del Salvador | [email protected] | | | HONDURAS | Diego Reyes | IT Manager | Servicio Nacional de Sanidad e Inocuidad Agroalimentaria (SENASA) | [email protected] | | Karen Mirtala Sosa Salgado | Trade Facilitation Technical Coordinator | Secretaría de Desarrollo Económico | [email protected] | | | Orlin Ramírez | Technical Director of Agricultural Quarantine | Servicio Nacional de Sanidad e Inocuidad Agroalimentaria (SENASA) | [email protected] | | | José Luis Salgado | Phytosanitary Inspector | Servicio Nacional de Sanidad e Inocuidad Agroalimentaria (SENASA) | [email protected] | | | NICARAGUA | Marvin Moraga | Supervisor of Agricultural Quarantine | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | Jairo Flores | Director of Agricultural Quarantine | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Ramón Noguera | Certification Officer | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Ramón Torrentes | Animal Quarantine Directorate | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Vanessa Quijano | Phytosanitary Certification Coordinator | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Lidia Torrez | Plant Quarantine Officer | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Sadia Guevara | IT Officer | Instituto de Protección y Sanidad Agropecuaria (IPSA) | [email protected] | | | Xiomara Mena | Executive Director | Centro de Trámite de las exportaciones (CETREX) | [email protected] | | | Dwayne Hodgson Cash | Information Systems Development Officer | Centro de Trámite de las exportaciones (CETREX) | d [email protected] b. ni | | | Gérman Macías Cano | Systems Programmer Analyst | Centro de Trámite de las exportaciones (CETREX) | gmacias@cetrex!gob.ni | | | Walkyría Aburto | Director of Central American Economic Integration | Ministerio de Fomento Industria y Comercio | waburtoc@m ific.gob. ni | | | Fátima Orozco | Specialist and Negotiator for Trade Facilitation | Ministerio de Fomento Industria y Comercio | [email protected] | | | COSTA RICA | Karen Fernández | Officer in Charge of Registration and Special Legends for Phytosanitary Certification | Servicio Fitosanitario del Estado (SFE) | [email protected] | | Gina Monteverde | Head of the Phytosanitary Certification Area | Servicio Fitosanitario del Estado (SFE) | [email protected] | | | Byron Guardián García | Directorate of Safety of Animal-Origin Products | Servicio Nacional de Salud Animal (SENASA) | [email protected] | | | Marvin Salas | Manager of the Single Window for Foreign Trade | Promotora de Comercio Exterior (PROCOMER) | [email protected] | | | Lannier Sosa | Project Coordinator | Promotora de Comercio Exterior (PROCOMER) | [email protected] | | | Juan Diego Chavarría | VUGE Services Advisor | Promotora de Comercio Exterior (PROCOMER) | [email protected] | | | Paola Orozco | Trade Facilitation Coordinator | Ministerio de Comercio Exterior (COMEX) | [email protected] | | | María Arévalo | Trade Facilitation Advisor | Ministerio de Comercio Exterior (COMEX) | [email protected] | | | Angie Vega | Trade Facilitation Advisor | Ministerio de Comercio Exterior (COMEX) | [email protected] | | | PANAMÁ | Concepción González | IT | Ministerio de Desarrollo Agropecuario | [email protected] | | | Wilma Othon | IT | Ministerio de Desarrollo Agropecuario | [email protected] | | | Daphne Gómez | National Directorate of Animal Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Johanna Juliao | National Directorate of Animal Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Alexis Villarreal | National Directorate of Animal Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Ruben Serrón | National Directorate of Plant Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Deyanira Michelle Núñez Marciaga | National Directorate of Plant Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Noel Cedeño | National Directorate of Plant Health | Ministerio de Desarrollo Agropecuario | [email protected] | | | Nathaniel Kadoch | Executive Directorate of Agricultural Quarantine | Ministerio de Desarrollo Agropecuario | [email protected] | | | Dania Villarreal | General Directorate of Administration of International Trade Treaties, Economic Analyst | Ministerio de Comercio e Industrias | [email protected] |