Supply Chain Visibility and Data Challenges - The Information Foundation

Supply chain transactions generate enormous amounts of data:

Transaction Data:

For a single purchase order → delivery → payment cycle:

- Purchase order
- Order acknowledgment
- Proforma invoice
- Commercial invoice
- Packing list
- Bill of lading
- Delivery receipt
- Payment instruction
- Remittance advice

- Certificate of origin
- Customs declarations
- Inspection certificates
- Insurance certificates
- Letters of credit (if applicable)

- Inventory levels
- Production status
- Shipment tracking
- Quality inspection results
- Warehouse receipts

Total Documents per Transaction: 15-30 (cross-border)
Data Fields per Transaction: 200-500
Parties Involved: 5-15

This data is scattered across incompatible systems:

System Landscape:

Party	Primary Systems	Data Stored
Buyer	ERP (SAP, Oracle), TMS, WMS	Orders, receipts, payments
Supplier	ERP, Production systems	Orders, invoices, shipments
Logistics	TMS, Carrier systems	Shipments, tracking, delivery
Banks	Core banking, Trade finance	L/Cs, payments, financing
Customs	Government portals	Declarations, duties
Insurers	Policy management	Coverage, claims

The Integration Reality:

Integration Status in Typical Supply Chain:

- Large buyer-supplier EDI connections
- Bank-to-ERP payment files
- Major carrier tracking APIs

- Email-based document exchange
- Portal-based submissions
- Manual data entry from structured sources

- Phone/fax communications
- Paper documents
- Spreadsheet reconciliation
- Email attachments

Multiple competing standards fragment the landscape:

Document Standards:

UN/EDIFACT: United Nations standard, widely used
ANSI X12: North American standard
GS1: Barcode and identification standards
ISO 20022: Financial messaging (XML)
SWIFT MT/MX: Bank messaging
UBL: Universal Business Language
Custom formats: Company-specific

The Translation Burden:

• A sends EDIFACT message
• Translation service converts to X12
• B receives and processes
• Response in X12
• Translation back to EDIFACT
• A receives and processes

Each translation: Risk of data loss/error
Cost per translation: $0.50-$5.00
Annual translation costs (large enterprise): $1-5M

---

Visibility decreases dramatically as you move deeper into supply chains:

Visibility by Tier:

• Full visibility into own operations
• Good visibility into Tier 1
• Limited visibility into Tier 2
• Minimal visibility into Tier 3+

Typical Large Company Visibility:
┌─────────────────────────────────────────────────┐
│ Tier 1: 95% of suppliers known │
│ 75% with regular data exchange │
│ 40% with real-time visibility │
├─────────────────────────────────────────────────┤
│ Tier 2: 40% of suppliers identified │
│ 15% with any data exchange │
│ 5% with real-time visibility │
├─────────────────────────────────────────────────┤
│ Tier 3+: <10% of suppliers known │
│ <2% with any data exchange │
│ ~0% with real-time visibility │
└─────────────────────────────────────────────────┘
```

Why Visibility Degrades:

1. No direct contractual relationship

2. Information treated as competitive advantage

3. Tier 1 suppliers protect their supplier base

4. Systems don't connect across tiers

5. Standards incompatible or absent

6. Cost to collect and share data

7. No clear benefit to sharing

8. Smaller suppliers lack systems

9. Integration ROI unclear

The visibility gap has concrete consequences:

Unknown Information (for typical buyer):

• Identity (who they are)

• Location (where they operate)

• Capacity (what they can produce)

• Financial health (whether they're stable)

• Compliance status (ESG, labor, etc.)

• Transaction history (payment patterns)

• Sub-contracting arrangements

• Inventory positions

• Production bottlenecks

• Quality issues at source

• Financial stress signals

Consequences for Finance:

What This Means for Supply Chain Finance:

- Whether Tier 2 invoice represents real transaction
- Whether goods described match goods shipped
- Whether supplier is creditworthy
- Whether other claims exist against receivables

- Tier 2+ suppliers (no visibility)
- Disputed transactions (no verification)
- Complex supply chains (no clarity)

Result: Finance flows only where visibility exists (Tier 1)

Information gaps create self-reinforcing problems:

The Spiral:

1. Buyer doesn't know Tier 2 suppliers
2. Can't extend reverse factoring to Tier 2
3. Tier 2 lacks financing, raises prices or delays
4. Tier 1 feels pressure, doesn't invest in visibility
5. Information gap persists
6. Return to step 1

Breaking the spiral requires coordinated action
that benefits all parties—a coordination failure.

---

At the heart of supply chain finance is a simple question: Is this invoice real?

What Verification Requires:

To verify an invoice is legitimate:

1. Confirm order exists

1. Confirm goods/services delivered

1. Confirm invoice is unique

1. Confirm parties are legitimate

Current Verification Methods:

Method	Reliability	Cost	Speed
Buyer confirmation	High	Low	1-5 days
Document matching	Medium	Medium	1-3 days
Third-party verification	High	High	3-7 days
Site inspection	Very high	Very high	1-4 weeks
Automated matching	Medium	Low	Minutes

Supply chain finance fraud is a significant concern:

Types of Fraud:

• Fictitious invoices (no real transaction)

• Inflated invoices (goods worth less than claimed)

• Duplicate invoices (same transaction, multiple financings)

• Diverted goods (invoice for goods going elsewhere)

• Impersonation of legitimate supplier

• Fake company creation

• Bank account substitution

• Buyer-supplier collusion to generate fake invoices

• Carousel schemes (circular trading)

• Shell company networks

Fraud Magnitude:

• Annual losses: $500M-$2B globally

• Percentage of volume: 0.5-1.0%

• Detection rate: 50-70%

• Average fraud size: $500K-$5M

• Greensill Capital (2021): $5B+ exposure to fraudulent invoices

• Hin Leong (2020): $800M in falsified documents

• Various commodity trading frauds: $100M+ each

The fraud risk creates systemic caution:

How Fraud Risk Affects Financing:

- Banks require buyer confirmation for all invoices
- Limits financing to where buyer relationship exists
- Excludes Tier 2+ where no confirmation possible
- Higher rates for less-verified transactions

- 5-15% of transaction value in verification costs
- Days to weeks of delay
- Paperwork burden on all parties
- Still doesn't catch all fraud

- Legitimate SMEs can't access financing
- Verification costs exceed financing benefit for small transactions
- Market concentrates in large, well-documented flows

---

Visibility improvements face a fundamental tension: the information that would enable financing is often competitively sensitive.

Competitive Sensitivity:

Information Companies Protect:

- Customer identities (their buyers)
- Pricing to different customers
- Capacity and utilization
- Cost structure
- Technology/process details

- Supplier identities (sourcing strategy)
- Volume commitments
- Pricing achieved
- Quality issues (competitive intelligence)
- Supply chain structure

- Financial difficulties
- Margin details
- Strategic plans
- Negotiation positions

More information enables better financing, but at privacy cost:

Trade-off Matrix:

Information Shared	Finance Benefit	Privacy Cost
Invoice only	Minimal (no verification)	Low
Invoice + PO	Moderate (order match)	Low-Medium
Invoice + PO + Delivery	Good (full verification)	Medium
Full transaction history	Excellent (patterns visible)	High
Cost/margin data	Very high (creditworthiness)	Very high

Emerging technologies attempt to balance transparency and privacy:

Zero-Knowledge Proofs:

• Prove something is true without revealing details

• "This invoice is for goods delivered" without showing goods

• "Supplier meets financial criteria" without showing financials

• Verify invoice within expected range

• Confirm delivery occurred

• Prove no duplicate financing

• Validate supplier identity

• Complex to implement

• Limited expressiveness

• Requires trusted setup

• Still emerging technology

---

Blockchain proponents argue it can solve supply chain visibility through:

Claimed Benefits:

1. Single Source of Truth

2. Provenance Tracking

3. Automated Verification

4. Trust Without Intermediary

However, blockchain faces significant limitations:

The Oracle Problem (Revisited):

Blockchain records what's submitted.
It cannot verify external reality.

- Invoice submitted to blockchain: Recorded accurately
- But: Does invoice match actual shipment?
- But: Were goods actually delivered?
- But: Did goods meet quality specs?

The blockchain can tell you the invoice exists.
It cannot tell you the invoice is truthful.

Adoption Coordination:

• All relevant parties must participate

• All must use compatible systems

• All must maintain data quality

• All must agree on governance

• Suppliers resist forced adoption

• Systems incompatible

• Data quality varies

• Governance contested

Evaluating XRPL against visibility challenges:

XRPL Capabilities:

• Payment settlement (immutable, fast)

• Asset tokenization (issued currencies, NFTs)

• Escrow (conditional payments)

• Multi-signature (shared control)

• Transaction history (visible but basic)

• Smart-contract-like logic (Hooks, developing)

• Document management (not designed for this)

• Complex business logic (limited programmability)

• Off-chain data verification (oracle problem)

• Privacy-preserving features (transparent ledger)

---

✅ Supply chain data is fragmented and costly to reconcile - $500B+ annually in operational overhead

✅ Visibility degrades dramatically across tiers - <10% of Tier 3+ suppliers known to buyers

✅ Information asymmetry prevents financing - Can't lend against what you can't verify

✅ Privacy concerns limit data sharing - Competitive sensitivity is rational, not paranoid

⚠️ Whether blockchain can achieve critical mass adoption - Coordination failures persist

⚠️ Whether privacy-preserving technologies mature sufficiently - Still early stage

⚠️ Whether verification can move to data entry point - Oracle problem fundamental

📌 Assuming blockchain creates truth - It records what's submitted, not reality

📌 Ignoring competitive sensitivity - Companies have rational reasons not to share

📌 Believing technology solves coordination failures - Incentives matter more than infrastructure

Supply chain visibility problems are real and costly, but they're fundamentally about incentives and trust, not technology. Blockchain can reduce reconciliation overhead and provide immutable payment records, but it cannot force data sharing, verify external reality, or solve the coordination failures that prevent multi-tier visibility.

---

Assignment: Map the data flows in a supply chain financing transaction, identifying where information is lost, duplicated, or manually reconciled.

Requirements:

• Define specific transaction type, parties, geography, value

• Create comprehensive diagram showing all documents, systems, transfers, and manual touchpoints

• Identify format issues, translations, error rates, reconciliation points, delays

• Evaluate where shared ledger helps vs. doesn't help

Time Investment: 4-5 hours

---

1. What percentage of Tier 3+ suppliers does a typical large company have visibility into?
Answer: C) Less than 10%

2. What is the "oracle problem" in blockchain supply chain visibility?
Answer: B) Blockchain records data accurately but cannot verify if it reflects external reality

3. Why do Tier 1 suppliers resist sharing Tier 2 information?
Answer: C) Supplier network is competitive advantage; sharing risks disintermediation

4. What is blockchain's strongest supply chain use case?
Answer: B) Recording payment transactions with immutability and clear audit trail

5. Which capability does XRPL provide strongest support for?
Answer: C) Immutable payment settlement and asset tokenization

---

End of Lesson 6

Total words: ~6,500