Export-Import Management & Documentation

Chapter 13
Digital Trade, Automation and Artificial Intelligence

Graduate Program in International Business
Export-Import Management & Documentation   •   Graduate

Digital Trade, Automation and Artificial Intelligence

Introduction and Context

International trade is increasingly conducted through digital records, interoperable platforms, automated controls and data-driven decisions. A shipment may be contracted electronically, classified by machine-assisted systems, screened against sanctions lists, financed through a digital trade platform, released through a port community system and evidenced by an electronic bill of lading. These developments can reduce transaction costs and improve visibility, but they also create new risks involving legal recognition, data quality, cyberattacks, algorithmic bias, operational dependency and unclear accountability.

Digitalisation does not eliminate the underlying obligations of export-import management. The exporter must still establish the correct product classification, origin, customs value, licensing status, documentary evidence and contractual responsibilities. Digital systems change how information is created, transmitted, validated and audited. Effective managers therefore need both technological literacy and a strong understanding of trade law, customs procedures, logistics, finance and internal control.

This chapter evaluates the principal technologies used in international trade and develops a governance-oriented approach to artificial intelligence (AI). It treats automation not as a substitute for professional judgment but as a means of improving speed, consistency and decision quality under appropriate supervision.

Learning Objectives

By the end of this chapter, the reader should be able to:

  1. Distinguish electronic documents, EDI, APIs, single windows, port community systems and trade platforms.
  2. Evaluate the legal, operational and evidentiary characteristics of e-bills of lading and blockchain-based records.
  3. Explain how AI supports classification, document extraction, screening, forecasting and anomaly detection.
  4. Design controls for data quality, cybersecurity, model risk, bias, explainability and human accountability.
  5. Assess the strategic and managerial implications of digital trade adoption.
  6. Apply a structured digitalisation framework to an international trade case.

1. Digital Trade as an Information and Control System

A trade transaction generates information before, during and after the movement of goods. Typical data include buyer and seller identities, product descriptions, Harmonized System (HS) codes, quantities, values, currencies, origin, transport details, licences, certificates, insurance, payment terms and delivery events. Traditionally, these data were entered repeatedly into invoices, packing lists, customs declarations, bills of lading, certificates and bank documents. Re-keying creates delay and inconsistency.

Digital trade seeks to make information:

  • Structured: represented in defined fields rather than only free text;
  • Interoperable: transferable between systems using agreed standards;
  • Authentic: attributable to an identifiable person or organisation;
  • Integral: protected against unauthorised alteration;
  • Available: accessible to authorised users when required;
  • Auditable: linked to a history of actions and approvals.

The distinction between digitisation, digitalisation and digital transformation is important. Digitisation converts analogue information into digital form, such as scanning a paper certificate. Digitalisation uses digital information to improve a process, such as automatically populating a customs declaration. Digital transformation redesigns the process and its governance, such as replacing fragmented documentary exchanges with a trusted, interoperable trade network.

The business case usually rests on lower administrative cost, faster clearance, fewer errors, improved compliance visibility and better working-capital management. However, benefits depend on adoption across the network. A perfectly designed exporter system cannot create end-to-end efficiency if a carrier, customs authority, bank or overseas buyer cannot exchange or legally rely on the data.

2. Core Digital Trade Architectures

2.1 Electronic documents

An electronic document is information created, stored or transmitted digitally. It may be a structured data file, a digitally signed PDF, a scanned image or a record in a platform. These forms are not equivalent.

A scanned invoice may be easy to transmit but difficult for software to interpret and may provide weak evidence of provenance. A structured invoice can be automatically validated, but it requires agreed data fields. A digitally signed document can provide stronger evidence of origin and integrity, provided that the signature system, identity credentials and applicable law are trusted.

Managers should evaluate an electronic document against five questions:

  1. Is it legally recognised in the relevant jurisdictions?
  2. Can the recipient verify the issuer and detect alteration?
  3. Can the data be read by the recipient's system?
  4. Is there a retention and retrieval mechanism?
  5. Can the organisation demonstrate who approved or changed it?

Legal recognition may arise from electronic-transactions legislation, sector-specific rules, customs regulations, contract terms or international instruments. Recognition is not universal, and a document accepted by one customs administration or carrier may not be accepted by another.

2.2 Electronic data interchange (EDI)

EDI is the structured, computer-to-computer exchange of standardised business messages. Common messages include purchase orders, order acknowledgements, advance shipping notices, invoices and transport status updates. EDI is generally reliable for stable, high-volume transactions, but implementation may be costly and message formats can be rigid.

EDI normally depends on agreed message standards, identifiers, validation rules, communication channels and exception procedures. A technically successful transmission does not guarantee a commercially correct transaction. For example, an EDI invoice may be accepted even though the HS code or quantity is wrong. Data validation must therefore include business rules, not only syntax checks.

2.3 Application programming interfaces (APIs)

An API allows one application to request or send data to another application in a defined manner. APIs are useful for real-time quotation, shipment tracking, tariff lookup, sanctions screening and customs status updates. Compared with traditional batch EDI, APIs can support more immediate interaction and modular integration.

API governance requires authentication, authorisation, encryption, rate limits, version control, error handling, logging and service-level expectations. An API that returns outdated or incomplete information can create a false impression of automation. Organisations should document data ownership, permitted uses and responsibilities when an external API fails.

2.4 Single windows

A single window is an arrangement through which traders submit standardised information and documents through a single entry point to fulfil requirements of multiple government agencies or other authorities. The objective is to prevent repeated submission of the same information.

A single window may integrate customs, agriculture, health, standards, licensing, port and other authorities. Its quality depends on legal authority, common data models, agency coordination, identity management and clear responsibility for decisions. It is not simply a website; it is an institutional and technical coordination model.

2.5 Port community systems

A port community system (PCS) connects participants in a port or logistics community, including shipping lines, terminal operators, freight forwarders, customs, truckers, rail operators, agents and cargo owners. It may coordinate vessel calls, gate appointments, manifests, cargo release, dangerous-goods information and status notifications.

A PCS can reduce congestion by synchronising information and physical activity. Its value is network-dependent: participation, data accuracy and agreed operating procedures matter more than the sophistication of the software alone. A PCS may complement a national single window but does not necessarily replace it. The single window generally coordinates regulatory submissions, whereas the PCS focuses on community logistics and port operations.

2.6 Trade platforms and marketplaces

Digital trade platforms may support contracting, quotations, document exchange, logistics booking, trade finance, insurance, identity verification or payment. Some are bilateral or consortium-based; others are open marketplaces. Platform governance determines who controls access, data, dispute resolution, fees, standards and liability.

A platform can reduce search and coordination costs but may increase concentration risk. If a firm becomes dependent on one platform, an outage, rule change or withdrawal of service can interrupt trade. Due diligence should cover financial stability, cybersecurity, data location, exit arrangements and the legal status of platform records.

3. Electronic Bills of Lading and Blockchain

A bill of lading traditionally performs three important functions: it evidences receipt of goods, records or incorporates the contract of carriage, and—when issued in negotiable form—may represent control of the goods. An electronic bill of lading (eBL) attempts to reproduce these functions electronically.

An effective eBL system should provide:

  • reliable identification of the document and its current holder;
  • exclusive control, so that only one party can exercise the rights attached to it;
  • secure transfer of control;
  • protection against unauthorised alteration;
  • a process for surrender, endorsement, amendment and cancellation;
  • continuity if the system changes or becomes unavailable;
  • evidence acceptable under the governing law and contractual arrangements.

A PDF sent by email is not necessarily an eBL in the legal or functional sense. A negotiable eBL requires a control mechanism that prevents simultaneous competing claims. Parties should examine the chosen rule set, carrier terms, governing law, applicable electronic-transactions legislation and compatibility with banks and insurers.

Blockchain or distributed-ledger technology records transactions across a network of participants. A permissioned ledger may allow only approved participants to validate and access records. Potential benefits include shared provenance, tamper-evident history and reduced dependence on a single database administrator. Smart contracts may automate actions when defined conditions are met.

Blockchain does not guarantee that the original data are true. It can preserve a false weight, incorrect HS code or fraudulent identity if inaccurate information is entered initially. Nor does immutability automatically solve privacy, correction or legal-jurisdiction problems. In many trade applications, a conventional database with strong access controls may be cheaper and more suitable. The relevant question is not whether blockchain is fashionable, but whether multiple parties require a shared, trusted record and lack a simpler governance solution.

4. AI Applications in Export-Import Management

AI systems identify patterns, classify information, generate predictions or recommend actions. In trade operations, the most useful applications are generally narrow and task-specific rather than fully autonomous.

4.1 Product classification

HS classification is a legal and technical determination based on the characteristics of the goods and the applicable nomenclature, interpretative rules, section and chapter notes, and national tariff provisions. AI can compare product descriptions with historical classifications, technical specifications and rulings. Natural-language processing can identify relevant attributes such as material, function, composition and degree of processing.

AI should normally recommend a classification rather than make an unreviewed final decision. Product descriptions are often incomplete, and similar commercial descriptions may have different legal classifications. A controlled workflow should require evidence, confidence indicators, reviewer approval and periodic review when tariff schedules or products change.

4.2 Document extraction

Optical character recognition and intelligent document processing can extract fields from invoices, packing lists, certificates, licences and transport documents. Modern systems combine layout recognition, language processing and validation rules. Extraction quality should be measured field by field because an overall document accuracy percentage can conceal serious errors in high-risk fields such as value, origin, quantity or consignee.

A useful control is cross-document reconciliation. For example, the quantity on the invoice should be compared with the packing list, purchase order and transport record. Exceptions should be routed to a human reviewer rather than silently corrected.

4.3 Sanctions and restricted-party screening

Screening systems compare parties, vessels, banks, addresses and beneficial owners against sanctions and other watchlists. AI can improve name matching by handling transliteration, spelling variation, word order and aliases. It can also prioritise alerts using contextual information.

False positives are a major operational problem. Excessive alerts create alert fatigue and encourage inappropriate dismissal. Screening decisions should preserve the matched data, list version, time, algorithm or rule used, reviewer action and rationale. A screening tool is not a substitute for legal analysis of ownership, control, jurisdiction, goods and transaction context.

4.4 Forecasting

Forecasting can support demand planning, inventory positioning, port-capacity planning, expected transit time and cash-flow management. A basic time-series model may express a forecast as:

ŷt+h = f(yt, yt-1, …, xt, xt-1, …)

Here, ŷt+h is the predicted value h periods ahead, yt is the observed historical outcome at time t, xt represents explanatory variables such as bookings, seasonality or exchange rates, and f is the selected forecasting method. The notation is general rather than a single algorithm. Its applicability depends on representative historical data, stable definitions and an explicit forecast horizon.

Forecast accuracy should be evaluated on out-of-sample data. For actual value yt and forecast ŷt, mean absolute error is:

MAE = (1/n) ∑t=1n |yt − ŷt|

Here, n is the number of evaluation observations, and MAE is expressed in the same units as the outcome. MAE is appropriate when absolute error has a direct managerial meaning and does not disproportionately weight large errors. It should not be compared across products with different units or scales without care.

4.5 Anomaly detection

Anomaly detection identifies transactions that differ materially from expected patterns. Examples include an unusual route, duplicate invoice, unexpected unit price, inconsistent weight, unusual payment instruction or sudden change in a supplier's banking details.

A simple statistical control may flag observations outside an expected range. If a variable has mean μ and standard deviation σ, a standardised score is:

z = (x − μ) / σ

The variable x and μ must have the same units, so z is dimensionless. This method assumes that μ and σ are estimated from a relevant reference population and that the distribution is sufficiently stable for the selected threshold. It is unsuitable as a universal fraud rule: skewed data, seasonality and legitimate structural changes can produce misleading alerts. More advanced methods include clustering, isolation-based methods and supervised fraud models.

5. From Automation to Accountable Decision-Making

Automation should be designed as a control system. A practical model has six stages:

  1. Define the decision: identify the business and legal consequence of the output.
  2. Assess the data: establish source, ownership, quality, completeness, timeliness and permitted use.
  3. Select the level of automation: distinguish information, recommendation, approval and execution.
  4. Test performance: evaluate accuracy, false positives, false negatives, drift and subgroup performance.
  5. Create human oversight: assign qualified reviewers and escalation thresholds.
  6. Monitor and improve: retain logs, investigate incidents and update the model and procedures.

The level of human involvement should reflect risk. Automatic formatting of a document may require limited supervision. Classification affecting duty liability, sanctions screening or cargo release requires stronger review. A useful principle is that the person accountable for the legal or commercial decision must be able to understand the basis of the recommendation and override it when evidence warrants.

Bias and fairness

Bias can enter through incomplete training data, historical errors, proxy variables, unequal data quality or a target that reflects past administrative practice rather than legal correctness. For example, a screening model trained on previous investigation outcomes may reproduce inconsistent historical attention.

Mitigation includes representative data, documented feature selection, subgroup testing where legally and ethically appropriate, independent validation, review of false negatives and accessible challenge procedures. Fairness cannot be reduced to one universal statistical threshold; the relevant standard depends on the decision, affected parties, law and operational context.

Explainability and auditability

A model need not expose every technical detail to every user, but the organisation should be able to explain what data were used, what output was produced, when it was produced, the degree of confidence, the applicable version and who approved the final action. Records should support reconstruction of a decision.

Cybersecurity and resilience

Digital trade systems are attractive targets because they control cargo, money and commercially sensitive information. Threats include credential theft, ransomware, business-email compromise, API abuse, malicious document alteration, insider misuse and supply-chain compromise.

Controls should include multifactor authentication, least-privilege access, encryption in transit and at rest, network segmentation, secure software development, patch management, backups, incident response exercises, vendor assessments and anomaly monitoring. Business continuity plans should specify how cargo release, customs filing, payment and document transfer will operate during an outage.

AI introduces additional threats, including data poisoning, prompt manipulation in generative systems, model theft, adversarial inputs and leakage of confidential documents. Confidential trade data should not be entered into public AI tools without an approved legal and security basis.

Accountability and liability

Responsibility cannot be transferred to a software vendor merely because software produced the output. Contracts should address service levels, data ownership, security, audit rights, subcontracting, incident notification, model changes, retention and indemnities. Internally, a decision-rights matrix should identify the owner of data, system, process, legal compliance and final approval.

6. Implementation Framework for Managers

A successful programme begins with process mapping rather than technology procurement. The organisation should identify documentary pain points, repeated data entry, regulatory bottlenecks, error costs, high-risk decisions and dependencies on external actors.

A phased implementation may proceed as follows:

PhaseMain activityPrincipal control
1. DiagnoseMap processes, data and risksDocument current-state ownership
2. StandardiseDefine master data and message formatsControlled data dictionary
3. IntegrateConnect ERP, customs, logistics and finance systemsAPI/EDI authentication and testing
4. AutomateApply rules, extraction and AI recommendationsHuman approval thresholds
5. AssureMonitor outcomes and incidentsAudit logs and independent review
6. ScaleExtend to partners and jurisdictionsInteroperability and exit planning

Master data management is foundational. Product codes, units of measure, legal entities, addresses, currencies and party identifiers must be governed centrally. A system cannot compensate for ambiguous product descriptions or conflicting supplier records.

Performance should be measured with both efficiency and control indicators. Examples include clearance time, manual touches per transaction, document error rate, extraction precision, false-positive screening rate, unresolved alert age, forecast MAE, system availability, cyber incidents and audit findings. Cost reduction alone is an inadequate success measure if compliance risk increases.

7. Illustrative Case: Meridian Components Ltd.

Background

Meridian Components Ltd., a fictional mid-sized exporter of industrial valves, sells to customers in four regions. It uses an enterprise resource planning system, receives supplier documents as PDFs, exchanges shipment information by email and relies on a freight forwarder for customs submissions.

Problem

The company experiences repeated invoice discrepancies, slow document preparation and a high volume of sanctions-screening alerts. Product descriptions vary between engineers, sales staff and suppliers. A port congestion episode causes missed delivery commitments, while management lacks a reliable forecast of transit time.

Analysis

An initial process review finds that the same product data are entered into the quotation, commercial invoice, packing list, export declaration and transport instruction. The company also discovers that screening records do not consistently show which list version was used. Its proposed AI vendor promises “fully autonomous classification,” but cannot explain training data, model updates or liability for errors.

Approach and solution

Meridian first creates a controlled product master containing technical attributes, approved descriptions, unit conventions and reviewed HS classifications. Classification software is introduced as a recommendation tool; a customs specialist approves new or materially changed products.

An intelligent document-processing system extracts fields from supplier invoices, but extracted values are reconciled against purchase orders and goods-receipt records. Exceptions above defined risk thresholds go to procurement staff.

The company connects its ERP to the forwarder's platform through an authenticated API. Shipment milestones are received automatically, while failed messages enter an exception queue. Screening is redesigned to preserve list versions, match explanations, reviewer decisions and escalation records.

For delivery forecasting, Meridian uses historical transit data segmented by route and carrier. It evaluates forecasts on a later holdout period using MAE rather than relying on a vendor's generic accuracy claim. A port community connection is added through the forwarder, but Meridian retains an outage procedure based on controlled manual submissions.

Outcome

The company reduces duplicate entry and improves document completeness. More importantly, it can demonstrate why a classification was approved, how a screening alert was resolved and which data supported a delivery forecast. The firm does not eliminate human review; it reallocates professional time from routine copying to exceptions and legally significant decisions.

Learning points

The case illustrates five principles. First, data standardisation precedes effective AI. Second, automation should target a defined control problem. Third, auditability is a business capability, not merely a compliance burden. Fourth, vendor claims must be tested against the organisation's own data and risk profile. Fifth, resilience requires a manual or alternative operating mode.

8. Contemporary Developments and Critical Evaluation

International organisations and regulators increasingly promote paperless trade, digital identity, interoperable data standards and legal recognition of electronic transferable records. Yet implementation remains uneven across countries, sectors and firms. Differences in privacy law, customs data requirements, electronic-signature rules, cybersecurity maturity and infrastructure can prevent seamless integration.

Generative AI may assist with drafting explanations, summarising regulations, translating documents and querying internal procedures. Its outputs can be fluent but factually unsupported, outdated or based on confidential information. It should therefore operate within retrieval controls, approved knowledge sources, access restrictions and human verification. Generative systems are particularly unsuitable for unreviewed legal classification or sanctions clearance.

A strategic evaluation should consider total cost of ownership, adoption incentives, interoperability, regulatory acceptance, vendor concentration, data portability and measurable risk reduction. The most advanced technology is not necessarily the best solution. In some settings, a standardised data dictionary and disciplined approval workflow produce more value than a complex AI platform.

Chapter Summary

Digital trade transforms the creation, transmission and control of information in export-import operations. Electronic documents, EDI and APIs provide different mechanisms for structured exchange; single windows coordinate regulatory submissions; port community systems coordinate logistics participants; and trade platforms connect commercial and financial activities. Their effectiveness depends on shared standards, legal recognition, data quality and network adoption.

Electronic bills of lading require control, authenticity, transferability and legal enforceability; a simple electronic copy does not necessarily perform the functions of a negotiable instrument. Blockchain can provide a shared, tamper-evident history but cannot guarantee the truth of data entered into the ledger and may not be superior to a conventional database.

AI can assist with classification, document extraction, screening, forecasting and anomaly detection. Its outputs must be evaluated using relevant data, appropriate performance measures and clearly stated assumptions. Automation requires governance covering bias, explainability, cybersecurity, auditability, human oversight, accountability and resilience. A sound implementation begins with process and data standardisation, proceeds through controlled integration and automation, and measures both efficiency and compliance outcomes.

Key Terms

API: A defined interface through which software applications exchange data or request services.

Anomaly detection: Identification of observations or transactions that differ from expected patterns.

Artificial intelligence: Computational systems that perform tasks involving pattern recognition, prediction, classification or decision support.

Blockchain: A distributed ledger in which records are linked and maintained across a network.

Data governance: Policies and responsibilities for data quality, access, security, use and accountability.

Digitisation: Conversion of analogue information into digital form.

Digital bill of lading: An electronic record intended to perform the functions of a bill of lading.

Digital signature: A cryptographic mechanism used to authenticate an electronic record and detect alteration.

Electronic document: A document created, stored or transmitted in digital form.

EDI: Structured computer-to-computer exchange of standardised business messages.

Electronic transferable record: An electronic record capable of being controlled and transferred in a manner recognised by applicable law.

HS classification: Assignment of goods to codes under the Harmonized System and applicable national tariff rules.

Intelligent document processing: Automated extraction, interpretation and validation of information from documents.

Model drift: Decline in model performance as data, behaviour or operating conditions change.

Port community system: A shared digital system connecting participants in a port and logistics community.

Single window: A coordinated entry point for submitting information required by multiple authorities.

Structured data: Information organised into defined fields that systems can validate and process.

Trade platform: A digital environment supporting commercial, logistics, documentary, financial or related trade activities.

Review Questions

Short Answer Questions

  1. Distinguish digitisation, digitalisation and digital transformation.
  2. What is the principal difference between a single window and a port community system?
  3. Why is a PDF emailed to a carrier not necessarily a negotiable electronic bill of lading?
  4. Identify two controls required for an API used in trade operations.
  5. Why should AI-supported HS classification normally include human review?

Long Answer Questions

  1. Evaluate the advantages and limitations of EDI and APIs for a multinational exporter.
  2. Explain the legal and operational requirements of an effective electronic bill of lading.
  3. Discuss how data quality, bias and explainability affect AI-based sanctions screening.
  4. Develop an implementation roadmap for a firm seeking to establish a digital trade architecture.
  5. Critically assess whether blockchain is necessary for trusted trade-document exchange.

Analytical / Application Questions

  1. An exporter receives a machine-generated classification recommendation with high confidence, but the product description omits its material composition. What additional evidence and controls should be required before filing?
  2. A screening model reduces manual alerts by 60 percent but later misses a sanctioned beneficial owner. Analyse possible causes and propose a remediation plan.
  3. A port system becomes unavailable during a peak shipping period. Design a resilient operating procedure that protects cargo release, documentary compliance and auditability.

Multiple Choice Questions with Answers

Question 1

Which feature most clearly distinguishes a single window from an ordinary document-upload portal?

A. It coordinates information submitted to multiple authorities through a common entry point.

B. It is used only by private shipping companies.

C. It eliminates the need for customs laws.

D. It guarantees that all submitted data are accurate.

Correct Answer: A. It coordinates information submitted to multiple authorities through a common entry point.

Question 2

What is a principal functional requirement of a negotiable electronic bill of lading?

A. It must be printable in colour.

B. It must provide exclusive control and secure transfer of the rights represented by the record.

C. It must be stored on a public blockchain.

D. It must contain no commercial terms.

Correct Answer: B. It must provide exclusive control and secure transfer of the rights represented by the record.

Question 3

Which statement about blockchain in trade is most accurate?

A. Blockchain guarantees that all entered data are factually correct.

B. Blockchain removes the need for legal agreements.

C. Blockchain can provide a shared tamper-evident history but does not validate the truth of initial data.

D. Blockchain is identical to an API.

Correct Answer: C. Blockchain can provide a shared tamper-evident history but does not validate the truth of initial data.

Question 4

In AI-supported HS classification, the most appropriate default is to:

A. Allow the model to file every declaration without review.

B. Use the model as a recommendation tool with evidence and qualified approval for significant decisions.

C. Ignore product specifications because the commercial description is sufficient.

D. Change the classification whenever the model has low confidence, without investigation.

Correct Answer: B. Use the model as a recommendation tool with evidence and qualified approval for significant decisions.

Question 5

Which control most directly reduces the risk of unauthorised API use?

A. Multifactor authentication and authorisation controls

B. Using longer product descriptions

C. Printing API responses

D. Removing all system logs

Correct Answer: A. Multifactor authentication and authorisation controls

Question 6

If actual transit times are 10, 12 and 14 days and forecasts are 12, 11 and 15 days, what is the MAE?

A. 1 day

B. 2 days

C. 3 days

D. 6 days

Correct Answer: A. 1 day

Question 7

A z-score is dimensionless because:

A. It is always measured in days.

B. The numerator and denominator have the same units.

C. It contains no observed value.

D. It can only be used for financial data.

Correct Answer: B. The numerator and denominator have the same units.

Question 8

Which situation is an example of model drift?

A. A reviewer documents an alert decision.

B. A model's performance declines after shipping routes and carrier behaviour change.

C. An API uses encryption.

D. A company defines a product master.

Correct Answer: B. A model's performance declines after shipping routes and carrier behaviour change.

Question 9

Why can excessive false-positive sanctions alerts create compliance risk?

A. They make all sanctions lists legally invalid.

B. They may create alert fatigue and encourage inappropriate dismissal of genuine alerts.

C. They prevent electronic signatures from functioning.

D. They automatically classify goods incorrectly.

Correct Answer: B. They may create alert fatigue and encourage inappropriate dismissal of genuine alerts.

Question 10

Which implementation sequence is generally most defensible?

A. Purchase advanced AI first, then define the business problem.

B. Standardise processes and master data before controlled integration and automation.

C. Remove human approval before testing system performance.

D. Outsource accountability to the software vendor.

Correct Answer: B. Standardise processes and master data before controlled integration and automation.

Export-Import Management & Documentation
Chapter 13 of 15