What this domain asks
The end-to-end handling of supplier invoices from creation and exchange through identity, semantic and policy validation, matching, exception resolution, approval, accounting handoff, payment status, correction, and retention.
The domain should retain its own evidence, decision owner, materiality criteria, exception path, and consequence even when it shares organization identity, workflow, or technology with adjacent domains. Aggregation can support oversight; it should not erase the evidence behind different risks or operating outcomes.
Buyer questions
- Which formats, networks, countries, and supplier channels are supported?
- How are identity and bank changes governed?
- Can validation distinguish syntax, tax, policy, contract, receipt, and accounting rules?
- How are corrections and disputes preserved?
- Can every invoice state reconcile with ERP and payment records?
Mapped workflows
Supplier Onboarding And Master-Data Governance
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for supplier onboarding and master-data governance within this domain.
Purchase Order And Change-Order Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for purchase order and change-order management within this domain.
Supplier Network, Portal, And Transaction Collaboration
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for supplier network, portal, and transaction collaboration within this domain.
Receiving, Matching, And Exception Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for receiving, matching, and exception management within this domain.
Invoice Capture, Validation, And Approval Workflow
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for invoice capture, validation, and approval workflow within this domain.
Electronic Invoicing And Interoperability
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for electronic invoicing and interoperability within this domain.
Savings Pipeline, Value Tracking, And Performance Analytics
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for savings pipeline, value tracking, and performance analytics within this domain.
ERP Integration, Data Lineage, And Access Governance
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for ERP integration, data lineage, and access governance within this domain.
Authority context
Peppol BIS Billing 3.0
Peppol BIS Billing 3.0 defines semantic and technical rules for interoperable electronic invoices and credit notes exchanged through the Peppol environment.
EU e-invoicing Directive 2014/55/EU
Directive 2014/55/EU establishes a European standard approach for electronic invoicing in public procurement and acceptance of covered compliant invoices.
Relevant operating models
Evidence boundary
Procurement Technology Current is not a procurement consultancy, contracting authority, marketplace, standards body, certifier, auditor, payment processor, accounting firm, or law firm. Its records support market research and enterprise evaluation; they do not establish product performance, realized savings, legal compliance, tax treatment, accounting accuracy, payment authority, supplier fitness, or buyer-specific suitability. A provider's documented capability can identify a research candidate but cannot establish buyer-specific adequacy for this domain.