Anticipate the invoice.
Build expected billing before the document arrives.
Can agents explain divergence instantly because they already know what should arrive?
Why Invoice Alpha
The commercial opportunity often appears before the document.
Traditional AP becomes active when an invoice arrives. But performance, acceptance, usage, credits, scope and supplier context can change what should be owed days or weeks earlier. Invoice Alpha explores what happens when agents maintain that obligation continuously instead of discovering it at the payment queue.
Why nowOnce the invoice arrives, opportunities to prevent leakage, capture entitlements or prepare a supplier challenge may already be compressed by payment timelines.
The operating shift
Move from invoice handling to obligation intelligence.
The cohort is built around three changes in where the work starts, what the system maintains and how payment decisions are made.
01
Old frameMatch what arrived.
Invoice AlphaAnticipate what should arrive.
Build an expected obligation from contract terms, delivery, usage, performance and known adjustments before the supplier bills.
02
Old frameManage an exception.
Invoice AlphaMaintain the obligation position.
Separate authorized, committed, delivered, accepted, invoiced and paid value so the commercial state is understood before AP is forced to resolve it.
03
Old frameDecide pay or hold.
Invoice AlphaChoose the commercial move.
Pay deliberately, protect entitlements, re-scope, notify, challenge, accelerate or hold within clear authority boundaries.
What we built for Genesis
A synthetic enterprise where the obligation can move.
Acme Corporation lets us create realistic conflicts between contracts, POs, delivery, acceptance, performance and supplier behavior — without exposing customer data.
Acme Corporation / Synthetic scenario — illustrative data
A persistent buy-side world.
The six experiments share suppliers, commercial history and operating context, so the agents accumulate a coherent position rather than solve isolated invoice exceptions.
$135MSupplier spend
240Suppliers
680Open POs
Illustrative obligation stack
Orbit Managed Ops / October
Position evolvingOrbit Managed Ops / October
Contract / PO
Monthly service fee + SLA schedule
$540KSets the starting obligation and available rights.
Performance
Two service failures
−$42KCreates confirmed and contested credits before billing.
Obligation
Expected payable
$498KWhat Acme currently believes should be owed.
Invoice
Supplier bills full fee
$540KThe invoice becomes a variance event rather than the first moment of understanding.
Commercial move
Pay undisputed / protect balance
GovernedChallenge entitlement while preserving service continuity.
Six experiments
One question, pushed further upstream each week.
The experiment sequence moves from anticipating a recurring invoice to managing the supplier’s broader commercial position.
Establish the obligation.
Separate authorized, committed, delivered, accepted, invoiced and paid value.
Can a matching invoice still be commercially premature?
Capture entitlements.
Translate service performance into expected credits before billing.
Can operational evidence change what should be paid early enough to matter?
Prevent leakage.
Detect scope drift, spend trajectory and authorization gaps upstream.
Can agents change the spend before the next invoice merely reveals the overrun?
Pay deliberately.
Balance discounts, cash, disputes, due dates and supplier criticality.
When is early, on-time, partial or delayed payment commercially better?
Manage the position.
Connect invoice behavior to performance, leverage and renewal strategy.
When should invoice evidence change the broader supplier conversation?
What participants receive
Eight weeks of live work, judgment and designed takeaways.
Select a week to see the session focus, optional lab, Friday artifact and the practical idea participants can take back to their own teams.
Program dispatch / 8 weeks
Week 01 / Introduction
Rethink the invoice
Orient around Invoice Alpha, the Acme world, the three-position model and the questions the cohort will explore together.
Core session
Opening lab + Acme walkthrough
See the synthetic enterprise, obligation model, agent roles, authority boundaries and how the six experiments will run.
Cohort input
Baseline judgment + priorities
Share where invoice value is lost today, what you would delegate and which situations you most want pressure-tested.
Build window
Scenario + agent refinement
Our team turns the live session into the next scenario, capability and evaluation changes.
A practical framework for moving invoice work upstream — from transaction handling to continuous obligation intelligence.
Orientation week
Weekly rhythm
The cohort runs like a live commercial lab.
Participants see the experiment. Our teams build alongside it. The week ends with a designed evidence trail rather than a webinar recap.
Mon / Tue
Experiment session
Frame the question, reveal the scenario, show what the agents know and run the first live working session.
Tue → Thu
Build + challenge
Scenario logic, evidence, agent behavior and evaluation rules are refined using what the cohort surfaced.
Thu
Optional strategy lab
Introduce new evidence, test a supplier response, compare alternative moves and see how the position changes.
Fri
Invoice Alpha dispatch
Receive a shareable report with the position, alpha, failures, participant judgment, system changes and next experiment.
Evidence you take with you
The program produces artifacts, not just sessions.
Each week leaves behind a designed evidence record. The final report synthesizes what six experiments taught us about obligation intelligence, alpha, autonomy and the emerging operating model.
Kozmo Commercial / Week 04Entitlements before billing.Illustrative sample / 8 pages
Sample weekly report
One experiment, end to end.
Follow the managed-services experiment from performance signal to expected obligation, supplier challenge, disposition, outcome and learning review.
Kozmo Commercial / GenesisWhat six experiments taught us.Illustrative sample / 12 pages
Sample final report
The cohort’s accumulated point of view.
See the experiment map, alpha taxonomy, results, human + agent operating model, system evolution and the next questions to test.
How we judge progress
Better outcomes, earlier signals, clearer authority.
Genesis separates synthetic experiment results from customer claims. The point is to make the evaluation model visible and build evidence about where agents help, where they fail and where humans should retain authority.
01 / EconomicAlpha
Accuracy, entitlement, prevention, timing and commercial-position value.
02 / TimeLead time
How much earlier a material signal becomes visible and actionable.
03 / WorkflowHuman effort
Evidence chasing, manual touches, exception handling and preparation.
04 / GovernanceAuthority
What can be autonomous, bounded, governed or human-owned.
High autonomyObserve + calculate
Monitoring, forecasting and evidence collection can run continuously.
Governed autonomyAct within thresholds
Routine notice, challenge preparation, partial payment and bounded holds.
Human authorityOwn material commitments
Settlement, waiver and strategic supplier concessions remain human-owned.
Join the Genesis Cohort
Explore the new invoice operating model with us.
Designed for leaders who want to understand where AI and agents can genuinely improve buy-side obligation management — and where commercial judgment still matters.
01
Request a spot
Tell us your role and the invoice or obligation problems you want to explore.
02
Cohort-fit conversation
Selected applicants are invited to a short conversation about fit and relevant context.
03
Participation confirmed
Commercial terms and cohort details are shared before participation is confirmed.
After Genesis: the strongest obligation models, plays and agent capabilities can move into broader real-data experiments and ongoing supplier or invoice portfolios.