Duplicate Invoice Intelligence Demo Script

Step-by-step validation click path for the live use case.
Duplicate Invoice Intelligence Demo Script
Refreshed: 2026-07-19 09:24:02 UTC
SOURCE
bp Sphere validation click path
Scope: Step-by-step presenter guidance
POLICY
Narrative first · proof second · action third
EVIDENCE
SAP, Ariba, invoice archive, vendor history, prior AP decisions
RECORDS
6 guided steps
ACTION
Launch Duplicate Invoice Intelligence
Validation Click Script
Duplicate Invoice Intelligence
Prove that duplicate prevention is a governed decision surface with source-backed evidence, financial impact, and human review.
Audience
AP lead, controller, procurement leader
Duration
4-5 minutes
Default role
operator
Live launch
Launch Duplicate Invoice Intelligence
Back To Use Case Introduction Launch Duplicate Invoice Intelligence View Duplicate Evidence

Step-By-Step Click Script

1
Open the launch page
Click/ui/use-case-launch?case=duplicate_invoice
What to say
Start with the business problem. This is not generic AI search. It is duplicate-payment decision intelligence.
What proof to land on
Business Problem and matching-factor narrative.
2
Explain the operating model
ClickStay on the launch page and point to What This Use Case Proves
What to say
Show the sequence: signal, context, evidence, policy, impact, human judgment, and memory.
What proof to land on
Signal-to-memory flow and credibility bullets.
3
Launch the live use case
ClickLaunch Duplicate Invoice Intelligence
What to say
Move into the live exception surface only after the room understands the trust contract.
What proof to land on
P2P exception flow opens with duplicate context.
4
Open the duplicate evidence
ClickView Duplicate Evidence
What to say
Answer the first finance question immediately: why was this flagged?
What proof to land on
Duplicate Type, Matching Factors, Duplicate Confidence, Potential Duplicate Exposure.
5
Show source-backed records
ClickOpen Invoice PDF or matched prior evidence from the viewer links
What to say
Show the current invoice, the matched prior invoice, and the exact evidence basis.
What proof to land on
Invoice image, prior invoice, vendor history, and source attribution.
6
Close on business impact
ClickReturn to the evidence panel
What to say
Make the value explicit: this is about avoided payment leakage and better spend control, not just anomaly flagging.
What proof to land on
Annual Duplicate Avoidance, budget / forecast impact, and prior recovery memory.

How To Use This In The Room

  • Start on the introduction page, not the live workspace.
  • Use the script to control the order: business problem, trust model, live proof, then action.
  • Spend most of the time on source-backed evidence rather than UI chrome.
  • If the room asks a skeptical question early, jump directly to the step that answers it.
Presenter note:
The recommendation is not the product. The product is the governed combination of context, evidence, policy, impact, human judgment, and memory.