What It Is
The EU Business Wallet is an organizational extension of the EUDI Wallet framework, designed for
companies, government agencies, and other legal entities. It stores verifiable business credentials—
company registration certificates, VAT numbers, trade licenses, compliance attestations, and transactional documents
like invoices and bills of lading.
Core Value Proposition: Automate business processes that currently rely on paper documents, manual verification,
and trusted intermediaries. Replace email attachments and PDF scans with machine-readable, cryptographically verifiable credentials
that flow seamlessly between ERP systems, customs platforms, banks, and regulatory authorities.
Unlike personal EUDI Wallets (controlled by individuals), Business Wallets are organizationally managed with
delegated authorities, role-based access control, and audit trails. A company's CFO might authorize invoice issuance, while
the logistics team handles trade documents—all using the same wallet infrastructure.
Technical Architecture
Organizational Identity Model
| Component |
Technology |
Purpose |
| Organization DID |
did:web, did:ebsi |
Root identity for the legal entity (e.g., did:web:company.fi) |
| Delegation Framework |
VC Authorization (VCA), OAuth 2.0 RAR |
Employees/systems act on behalf of organization |
| Credential Format |
W3C VC + UN/CEFACT semantics |
Trade documents (invoices, CoO, etc.) as VCs |
| Storage Backend |
Enterprise vault (HSM-backed) |
Secure key storage + credential repository |
| Access Control |
RBAC + ABAC policies |
Role-based permissions (who can issue/present what) |
| Audit Log |
Tamper-evident log (blockchain or append-only DB) |
Compliance trail for all credential operations |
| ERP Integration |
REST APIs, SAP BTP connectors |
Automated credential generation from business systems |
System Architecture Diagram
┌────────────────────────────────────────────────────────────────────┐
│ EU Business Wallet Ecosystem │
└────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ COMPANY A (Exporter) │
│ ┌──────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
│ │ SAP ERP │────>│ Business Wallet │<────│ Logistics Team │ │
│ │ (Invoices) │ │ (Org DID) │ │ (Human Auth) │ │
│ └──────────────┘ └────────┬────────┘ └─────────────────┘ │
│ │ Issues VC: │
│ │ - Commercial Invoice │
│ │ - Cert of Origin (CoO) │
│ │ - Packing List │
└─────────────────────────────────┼──────────────────────────────────┘
│
│ Credential Presentation
▼
┌──────────────────────────────────────────────────────────────────────┐
│ VERIFIERS │
│ ┌─────────────┐ ┌─────────────┐ ┌──────────────────┐ │
│ │ Customs │ │ Bank (L/C) │ │ Buyer (Import) │ │
│ │ Authority │ │ Processing │ │ Verification │ │
│ └──────┬──────┘ └──────┬──────┘ └────────┬─────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Trust Registry (Verify Issuer DID) │ │
│ │ - Is Company A authorized to issue CoO? │ │
│ │ - Is credential schema valid? │ │
│ │ - Has credential been revoked? │ │
│ └──────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────────────┘
Key Flow:
1. ERP generates invoice → Wallet transforms to VC (signs with org DID)
2. Logistics staff requests CoO → Chamber of Commerce issues as VC
3. All credentials presented to customs/bank via OpenID4VP
4. Verifiers check Trust Registry + signature validity → instant clearance
Business Credential Types
Core Organizational Credentials
| Credential Type |
Issuer |
Use Case |
| Company Registration |
National Business Registry (PRH in Finland) |
Prove legal existence, access services requiring company verification |
| VAT Registration |
Tax Authority |
B2B transactions, cross-border VAT compliance |
| Trade License |
Regulatory Authority (sector-specific) |
Prove authorization to operate in regulated industries |
| ISO Certification |
Certification Body (e.g., ISO 27001 auditor) |
Quality/security attestations for tenders and partnerships |
| EORI Number |
Customs Authority |
Economic Operator Registration for customs clearance |
| Power of Attorney |
Company (self-issued) |
Delegate authority to employees/agents (e.g., customs broker) |
Transactional Trade Documents
| Document Type |
Standard |
Benefit |
| Commercial Invoice |
UN/CEFACT Cross-Industry Invoice (CII) |
Machine-readable, auto-validates against PO, eliminates manual entry |
| Certificate of Origin (CoO) |
UN/CEFACT CoO + W3C VC |
Proves product origin for tariff preferences (e.g., EU-Japan EPA) |
| Bill of Lading (B/L) |
DCSA e-B/L standard + VC |
Digital title transfer, eliminates courier costs, faster payments |
| Packing List |
UN/CEFACT Packing Specification |
Customs pre-clearance, automated risk assessment |
| Letter of Credit (L/C) |
ICC eUCP (Electronic Presentation) |
Banks verify credentials automatically, instant payment release |
| Phytosanitary Certificate |
IPPC ePhyto + VC |
Agricultural product clearance (plant health compliance) |
International Trade Automation
Current Pain Points
The Paper-Based Reality: A single shipment generates 28-36 documents, 240+ copies, handled by
27+ parties (WEF estimate). Documents are:
- Printed, signed, scanned, emailed (or couriered)
- Manually re-keyed into 5-7 different systems
- Verified by human inspectors (slow, error-prone)
- Subject to fraud (fake certificates, altered invoices)
Cost: Document processing adds 15-20% to shipping costs. Time: 3-7 days for customs clearance.
Credential-Based Trade Flow
Automated Export Process (Finland → Japan)
- Order Placed: Buyer's ERP sends PO to exporter's ERP (API)
- Invoice Generated: SAP creates invoice → Business Wallet transforms to VC (UN/CEFACT CII format)
- CoO Requested: Exporter's wallet requests CoO from Chamber of Commerce
- Chamber Issues CoO: Automated verification (company registered, product eligible) → issues CoO as VC
- B/L Created: Shipping line issues e-B/L as VC (signed by carrier DID)
- Customs Declaration: AI agent reads all VCs → auto-generates customs filing (JSON submission)
- Pre-Clearance: Finnish customs verifies credentials → approves shipment before departure
- Payment Trigger: Bank receives presentation request (invoice + CoO + B/L VCs) → verifies → releases L/C funds
- Import Clearance: Japanese customs receives same VCs → instant clearance (no paper inspection)
Result: 7-day process reduced to
24 hours. Zero paper. 90% cost reduction.
Example: Invoice as Verifiable Credential
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://unece.org/trade/uncefact/vocab"
],
"type": ["VerifiableCredential", "CommercialInvoice"],
"issuer": "did:web:exporter.fi",
"issuanceDate": "2026-03-15T10:30:00Z",
"credentialSubject": {
"id": "urn:invoice:INV-2026-001234",
"invoiceNumber": "INV-2026-001234",
"issueDate": "2026-03-15",
"seller": {
"id": "did:web:exporter.fi",
"name": "Finnish Exporter Oy",
"vatId": "FI12345678",
"address": "Helsinki, Finland"
},
"buyer": {
"name": "Japanese Importer KK",
"vatId": "JP98765432",
"address": "Tokyo, Japan"
},
"lineItems": [{
"description": "Industrial Machinery Parts",
"quantity": 100,
"unitPrice": 50.00,
"currency": "EUR",
"total": 5000.00
}],
"totalAmount": 5000.00,
"currency": "EUR",
"paymentTerms": "Net 30, L/C at sight"
},
"proof": {
"type": "Ed25519Signature2020",
"created": "2026-03-15T10:30:00Z",
"verificationMethod": "did:web:exporter.fi#invoice-key",
"proofPurpose": "assertionMethod",
"proofValue": "z4Qn..."
}
}
ERP System Integration
SAP Integration Architecture
Existing ERP systems (SAP S/4HANA, Microsoft Dynamics, Oracle) generate business documents. Business Wallet acts as a
transformation layer: converting proprietary formats (IDoc, EDIFACT) to W3C VCs with UN/CEFACT semantics.
┌────────────────────────────────────────────────────────────────┐
│ SAP S/4HANA Integration │
└────────────────────────────────────────────────────────────────┘
SAP S/4HANA Business Wallet Connector Wallet
───────────── ────────────────────── ──────
[Invoice] ┌────────────────────┐
│ │ Format Transform │
├──> IDoc ────────────► │ IDoc → UN/CEFACT │
│ │ + VC Wrapper │
│ └─────────┬───────────┘
│ │
│ ┌─────────▼───────────┐
│ │ Signing Service │ ────> [VC]
│ │ (HSM-backed key) │ │
│ └─────────────────────┘ │
│ │
[Shipment] │
│ ┌────────────────────┐ │
├──> API ────────────► │ Event Listener │ │
│ │ (Order Status) │ ─────────┤
│ └────────────────────┘ │
│ │
│ ┌────▼────┐
│ ┌────────────────────┐ │ Wallet │
├──> Query ◄─────────── │ Presentation API │ ◄────┤ Storage │
│ │ (Verifier Request) │ │ + API │
│ └────────────────────┘ └─────────┘
Flow:
1. SAP creates invoice (standard process)
2. Connector intercepts IDoc, transforms to VC
3. Wallet signs with company DID, stores credential
4. External verifier requests presentation → Wallet responds
5. SAP receives confirmation (payment status, customs clearance)
Integration Options
| Approach |
Use Case |
Complexity |
| API Gateway |
Real-time credential issuance (SAP BTP + Wallet REST API) |
Low (no ERP modification) |
| Event-Driven |
Asynchronous processing (SAP Event Mesh → Wallet subscriber) |
Medium (event configuration) |
| BAdI Extension |
Deep integration (custom ABAP logic for VC generation) |
High (requires SAP dev skills) |
| Middleware (e.g., MuleSoft) |
Multi-ERP environments (orchestrate SAP + Dynamics + custom apps) |
Medium (integration platform required) |
Example: Automated CoO Workflow
# Scenario: Export order triggers CoO issuance
1. Sales order created in SAP (destination: Japan)
2. SAP Event Mesh publishes "ExportOrderCreated" event
3. Business Wallet Connector receives event:
- Extracts product details (HS codes, origin)
- Calls Chamber of Commerce API (credential request)
4. Chamber verifies:
- Company registered as authorized exporter
- Product meets origin rules (>50% EU value-added)
5. Chamber issues CoO as VC:
{
"credentialSubject": {
"exporter": "did:web:exporter.fi",
"product": "Industrial Parts (HS: 8483.50)",
"origin": "Finland (EU)",
"fta": "EU-Japan EPA (preferential tariff)"
},
"proof": { /* Chamber's signature */ }
}
6. Wallet stores CoO, links to SAP order (external reference)
7. When shipment ready → Wallet presents CoO to customs automatically
Deployment Roadmap
| Phase |
Timeframe |
Milestones |
| Standards Finalization |
2025 |
UN/CEFACT + W3C VC alignment, eIDAS 2.0 legal framework |
| Pilot Programs |
2026 |
Trade corridors (Finland-Estonia, Netherlands-Germany), CoO digitization |
| National Rollout |
2027 |
EU member states mandate Business Wallet for cross-border trade |
| ERP Integration |
2027-2028 |
SAP, Oracle, Microsoft release native Business Wallet connectors |
| Global Interop |
2028+ |
Mutual recognition with non-EU partners (US, ASEAN, Japan) |