Customer story · Gaming & Gambling
A betting & gaming operator
Supplier invoice reconciliation for a betting & gaming operator
Finance reviews invoice packages from many gaming suppliers in a purpose-built interface. AI reads. Deterministic rules verify. Humans decide.
Executive summary
The situation
Varied supplier PDFs and workbooks carry mixed currencies. Reading a figure does not verify its relationship to tax, bonus, revenue share or the document total.
What was built
AI extracts document-present figures with provenance, confidence and currency. Rules verify relationships using document-stated conversion rates. Analysts validate, correct or reset unverifiable values with decisions kept auditable.
Why it matters
Gives analysts a review context where uncertainty and evidence remain visible. Supplier configurations require approval; reviewer corrections are recorded decisions, not autonomous learning.
- Primary users
- Finance analysts
- Core systems/data
- Supplier PDFs, workbooks and document-stated FX
- Human control point
- Analyst decisions and configuration approval
- Nexus role
- Extraction, verification and review routing
The challenge
Many suppliers. Different documents. One finance review.
Supplier invoice packages vary across PDFs and workbooks and contain mixed currencies. Tax, bonus, revenue share, effective rates and totals need to be understood together rather than read as unrelated fields.
A plausible amount is not sufficient evidence. Reviewers need its source, currency and verification context. When the relationships cannot be checked, the process must expose uncertainty instead of manufacturing a complete answer.
What we built
Extraction with provenance, verification by rules.
AI extracts only figures present in the documents, keeping provenance, confidence and currency attached. Deterministic calculations check tax, bonus, revenue share, effective rates, totals and cross-checks. Conversion uses rates stated in the source documents, not external FX introduced to fill a gap. Reading the number and verifying it are separate tasks.
Values that cannot be verified go to analyst review in a dedicated finance interface. Validate, correct and reset decisions remain auditable with the evidence. Supplier configuration can be drafted from first documents, but a person must approve it before use. AI reads. Deterministic rules verify. Humans decide.
How the workflow runs
Step by step.
01
Intake
Supplier invoice packages arrive as PDFs and workbooks. AI extracts document-present figures with source, confidence and currency.
02
Verify
Rules check tax, bonus, revenue share, effective rates, totals and cross-checks. Currency conversion uses rates stated in the documents.
03
Route to review
Unverifiable values go to analyst review. Reviewers validate, correct or reset values, and every decision is recorded.
What the business team sees
A dedicated place to review supplier documents.
The reviewer sees supplier, billing period, extracted figures and flagged values with their source evidence. An analyst can investigate why something needs attention instead of working from an unexplained warning. Validate, correct and reset are review decisions, not signals for autonomous retraining. The illustrative panel uses example records to show that decision pattern.
- Supplier / provider
- Example provider A
- Billing period
- Example monthly statement
- Document status
- Validated
Fields checked
- Revenue share
- Fees
- Promotional deductions
- Taxes
- Document totals
Example provider B · Currency conversion
Flagged
Reason: the extracted conversion logic needs confirmation against the supplier document.
How Nexus works underneath
Separate reading, checking and deciding.
Nexus connects intake to provenance-preserving extraction, deterministic verification and analyst review. AI stays within the document-present boundary; rules handle calculations and document-stated FX. Analysts handle what cannot be verified, with auditable decisions and a separate approval requirement for new supplier configuration.
Architecture
How the layers fit together.
Business team
Finance review interface
Flagged values · source evidence · validate / correct / reset
Nexus orchestration
- 01Package intake
- 02Extraction with provenance
- 03Deterministic verification
- 04Document-stated FX
- 05Review routing
- 06Audit trail
Connected systems and data
- Supplier PDFs
- Workbooks
Human control and audit
Every decision traces back to evidence.
Reviewer decisions to validate, correct or reset a value remain auditable alongside the source evidence.
New supplier configurations are drafted from documents and approved by a human. Reviewer corrections are recorded as decisions; they do not silently change how future invoices are processed.
What this changes
Evidence stays with the figure. Provenance, confidence and currency give reviewers context.
Uncertainty becomes review work. Unverifiable values reach a person rather than appearing as settled calculations.
Decisions remain auditable. Review actions retain their evidence, and new configuration requires approval.
Your process
Discuss a similar workflow
Tell us about the documents, systems and decisions involved. We will discuss where Nexus orchestration fits and where your team stays in control.