Invoices
1673
Persisted vendor invoice rows available to P2P matching flows.
Duplicate Invoice Intelligence
Understand the operating model before opening the live use case.
Duplicate Invoice Intelligence Launch
Refreshed: 2026-07-18 22:54:44 UTC
SOURCE
bp Sphere use case launch spec + linked runtime proof surfaces
Scope: Understand → Experience → Verify
POLICY
Launch metrics are non-attestation unless a section is explicitly marked live
EVIDENCE
SAP, Ariba, invoice archive, vendor history, prior AP decisions
RECORDS
Scenario orientation with downstream runtime, evidence, lineage, and read-model links
ACTION
Launch Duplicate Invoice Intelligence
Launch Page Data Basis
T2/T3 MIXED READ MODEL
NON-ATTESTATION
FALLBACK DISCLOSED
The figures on this launch page are validation-orientation values unless a section is explicitly marked live.
They are not audit-attested SOR proof and must not be presented as production financial evidence.
A live compact read-model anchor is shown below for this launch page. Static launch metrics remain orientation-only.
Live Domain Read-Model Anchor
These values come from page-specific persisted read-models where available. Zeros mean no live rows were present, not a substituted demo value.
Invoice exceptions
12
Open/closed exception queue rows behind P2P analyst prioritization.
Payments
368
Payment rows available for duplicate/payment-history comparison.
Purchase orders
954
PO rows available for source-backed three-way match context.
Source Connector Readiness Anchor
Connector dependencies are loaded from tenant domain connector manifests for procurement, finance.
This is readiness metadata, not a successful SOR call; live proof still requires read-model rows, evidence, policy, replay, or source-system response records.
Mode distribution: declared: 1, live: 5, local_live: 10.
procurement · default_sor
declared
2 operations: read, write · freshness Not declared
finance · SAP S/4HANA
live
10 operations: get_journal_entries, post_journal_entry, get_gl_balances +7 more · freshness 60
finance · SAP S/4HANA Central Finance
live
5 operations: get_central_journal_entries, get_harmonized_trial_balance, get_replication_status +2 more · freshness 120
finance · SAP Ariba
local_live
6 operations: get_purchase_requisitions, get_purchase_orders, get_invoices +3 more · freshness 300
finance · Coupa
local_live
6 operations: get_invoices, get_purchase_orders, get_requisitions +3 more · freshness 300
finance · BlackLine
live
7 operations: get_reconciliations, get_reconciliation_detail, get_close_tasks +4 more · freshness 120
Live Platform Proof Anchor
These counts come from persisted runtime tables. Business figures elsewhere on this launch page remain non-attestation unless separately marked live.
Agent Executions5826289
Policy Evaluation Logs21474822
Decision Ledger Records5422407
Organizational Change Records7
Value Event Records39489
Business Problem
Why this use case matters before the demo starts
AP teams deal with resubmissions, OCR variants, invoice-number mutations, credit-memo confusion, and partial duplicates that are easy for humans to miss under close pressure.
bp Sphere Decision Operating System
Duplicate Invoice Intelligence
Stop duplicate settlement before release with factor-level evidence, duplicate type classification, and quantified financial impact.
Enterprise Signal
Invoice exception
This use case starts with a governed enterprise signal, not a generic AI prompt.
→
bp Sphere Assembles
Context + Evidence + Policy + Impact + Judgment + Memory
Source systems consulted: SAP, Ariba, invoice archive, vendor history, prior AP decisions. Consequences evaluated: Potential duplicate exposure, annual duplicate avoidance, budget and forecast posture.
Context Discovery
Evidence Assembly
Policy Evaluation
Impact Analysis
Human Judgment
Decision Memory
What This Use Case Proves
1
Signal
Invoice exception enters the operating model.
2
Context Discovery
SAP, Ariba, invoice archive, vendor history, prior AP decisions are assembled into enterprise context.
3
Evidence & Policy
Controls and source evidence shape the decision before recommendation.
4
Impact
Potential duplicate exposure, annual duplicate avoidance, budget and forecast posture are calculated before action.
5
Human Judgment
The operator approves, overrides, escalates, or requests more evidence.
6
Decision Memory
The same operating model extends from AP exceptions into spend forecasting, journal intelligence, contract validation, and credit decisions.
Launch Metrics · Non-Attestation Unless Marked Live
Enterprise Context Sources5
Evidence Records Evaluated39
Policies Applied5
Prior Decisions Referenced23
Data BasisLaunch orientation
Why This Is Credible
- Matching factors break down vendor, invoice, amount, PO, date, and line-item similarity
- Duplicate type is classified before recommendation and tied to policy and enterprise memory
- Potential duplicate exposure and annual duplicate avoidance are visible before payment release
Recommendation Is Not The Product.
The durable value is the governed combination of context + evidence + policy + impact + human judgment. The recommendation is merely the visible output.
The durable value is the governed combination of context + evidence + policy + impact + human judgment. The recommendation is merely the visible output.
What The Operator Needs To Answer
- Why did the system think this invoice is a duplicate?
- Is this an exact duplicate, a near duplicate, or a supplier resubmission?
- What is the financial exposure if payment is released?
Enterprise Context Consulted
SAPInvoice header, amount, posting, and vendor baseline
AribaPO and commitment lineage
Invoice ArchivePrior invoice image and extracted reference patterns
Vendor HistoryPrior duplicate incidents and repeat-submission behavior
Prior AP DecisionsPast holds, releases, and recovery outcomes
How This Use Case Lands In The Room
What the user sees
Matched prior invoice, duplicate type, matching factors, and financial exposure before release
What the system proves
Vendor, invoice, amount, date, PO, and line-item similarity are source-backed
Human judgment
The analyst holds, releases, escalates, or requests more evidence
Why it matters
Duplicate prevention becomes part of spend, budget, and supplier-governance intelligence
Evidence Intelligence Fabric
Evidence Discovery Service
Discover candidate evidence across enterprise systems.
Evidence Resolution Service
Resolve authoritative records, versions, and governing precedence.
Evidence Extraction Service
Extract clauses, approvals, milestones, tolerances, and decision-ready snippets.
Evidence Lineage Service
Build cross-system provenance from source records to recommendation.
Evidence Pack Service
Package immutable decision-specific bundles for replay and audit.
Evidence Viewer
Render contracts, emails, invoices, policies, and supporting records with source proof.
Controlled Truth Sources
SAP S/4HANA APSAP MM / GRIRSAP PaymentsAribaInvoice ArchiveVendor HistoryPrior AP Decisions
Policies Evaluated
Duplicate Invoice PolicyVendor Resubmission PolicyCredit Memo Policy
Evidence Discovery Timeline
08:41:02 · Invoice retrieved from SAP
INV-LIVE-DUP-1778594510 loaded with vendor, amount, date, and PO linkage.
08:41:04 · Candidate duplicates searched
Invoice archive and prior AP decisions scanned for vendor and invoice-pattern matches.
08:41:06 · Near-duplicate resolved
INV12345A linked to the original submission despite the mutated invoice number.
08:41:08 · Policy posture applied
Duplicate, resubmission, and credit-memo controls evaluated.
08:41:10 · Financial impact quantified
Potential duplicate exposure and budget/forecast posture calculated before release.
08:41:11 · Recommendation generated
Hold for analyst review as Potential Resubmission.
Runtime Proof Links
Evidence artifact
Open the evidence pack and lineage before treating any recommendation as source-backed.
Policy and replay artifact
Policy and replay claims must resolve to a platform surface, not just launch-page narrative text.
Value claim boundary
Protected, pending, and realized value stay separate. Realized value requires finance attestation.
Evidence Pack Viewer
Invoice · INV-LIVE-DUP-1778594510
99% · SAP S/4HANA AP
Version: Posted image v1
Retrieved: 08:41:02
Governing status: Anchor
Original supplier invoice with freight and services bundled under one submission.
Version: Posted image v1
Retrieved: 08:41:02
Governing status: Anchor
Original supplier invoice with freight and services bundled under one submission.
Matched Invoice · INV12345A
97% · Invoice Archive
Version: Archived PDF snapshot
Retrieved: 08:41:06
Governing status: Supporting
Invoice number mutation and identical amount pattern matched to the original business transaction.
Version: Archived PDF snapshot
Retrieved: 08:41:06
Governing status: Supporting
Invoice number mutation and identical amount pattern matched to the original business transaction.
Purchase Order · PO-7714
98% · Ariba
Version: Release 6
Retrieved: 08:41:03
Governing status: Supporting
Open commitment line set aligns to both the original and resubmitted invoice.
Version: Release 6
Retrieved: 08:41:03
Governing status: Supporting
Open commitment line set aligns to both the original and resubmitted invoice.
Goods Receipt · GR-4418
94% · SAP MM / GRIR
Version: GR/IR linkage snapshot
Retrieved: 08:41:04
Governing status: Supporting
Receipt proof exists for the original service milestone, but resubmitted invoice still requires duplicate validation before release.
Version: GR/IR linkage snapshot
Retrieved: 08:41:04
Governing status: Supporting
Receipt proof exists for the original service milestone, but resubmitted invoice still requires duplicate validation before release.
Prior Payment · PAY-20260501-88421
96% · SAP Payments
Version: Payment run audit snapshot
Retrieved: 08:41:05
Governing status: Supporting
Prior payment was executed inside the candidate duplicate window for the same supplier, PO family, tax profile, and amount band.
Version: Payment run audit snapshot
Retrieved: 08:41:05
Governing status: Supporting
Prior payment was executed inside the candidate duplicate window for the same supplier, PO family, tax profile, and amount band.
Vendor History · VEND-DUP-042
93% · Vendor Memory
Version: Current profile
Retrieved: 08:41:05
Governing status: Context
Supplier has repeated duplicate/resubmission patterns inside recent AP cycles.
Version: Current profile
Retrieved: 08:41:05
Governing status: Context
Supplier has repeated duplicate/resubmission patterns inside recent AP cycles.
Payment Terms · CT-OF-2026-017
95% · Ariba Contract Workspace
Version: Controlled contract terms
Retrieved: 08:41:07
Governing status: Context
Net 30 terms and payment-window constraints confirm the hold does not create an avoidable early-payment or discount leakage event.
Version: Controlled contract terms
Retrieved: 08:41:07
Governing status: Context
Net 30 terms and payment-window constraints confirm the hold does not create an avoidable early-payment or discount leakage event.
Policy · P2P-DUP-014
97% · Policy Library
Version: Controlled current copy
Retrieved: 08:41:08
Governing status: Authoritative
Potential resubmissions must be held when near-duplicate evidence and financial exposure exceed tolerance.
Version: Controlled current copy
Retrieved: 08:41:08
Governing status: Authoritative
Potential resubmissions must be held when near-duplicate evidence and financial exposure exceed tolerance.
Evidence Lineage
→
Recommendation
bp Sphere · Hold invoice for duplicate review.
→
Matched Invoice
Invoice Archive · Near-duplicate found despite invoice-number mutation.
→
Invoice INV-LIVE-DUP-1778594510
SAP S/4HANA AP · Current invoice under review.
→
PO-7714
Ariba · Common commitment and line-item family.
→
GR-4418
SAP MM / GRIR · Receipt proof validates the original service milestone but not duplicate release eligibility.
→
PAY-20260501-88421
SAP Payments · Prior payment anchors the duplicate exposure calculation.
→
CT-OF-2026-017
Ariba Contract Workspace · Payment terms confirm cash timing and supplier impact while the invoice is held.
→
Duplicate Policy
Policy Library · Resubmission hold posture applied.
→
Prior AP Decisions
Decision Memory · Recovered duplicate cases reused as precedent.
Validation Script
Step 1 · Open the launch page
Click: /ui/use-case-launch?case=duplicate_invoice
Step 2 · Explain the operating model
Click: Stay on the launch page and point to What This Use Case Proves
Step 3 · Launch the live use case
Click: Launch Duplicate Invoice Intelligence
Duplicate Invoice Intelligence demonstrates the operating model before you enter the live workspace.