Skip to content
HeuriTel
Sign in

Partnerships, digital services and finance teams

Settle with a partner from the record the customer was billed on

Month end. The partner's statement says forty thousand activations. The operator's billing says thirty-eight. The revenue share is due on Friday.

Request a working session The product that runs it: Digital Commerce & Partner Ecosystem

Read the journey; a working session shows it running.

Seen by the customer · Partner portal

From the record, not a run: what would reach them, on Partner portal, Finance workbench.

The case

Annotated from the record

What happened

Month end: a partner's statement says forty thousand activations, the operator's billing says thirty-eight, and the revenue share is due.

Month end. The partner's statement says forty thousand activations. The operator's billing says thirty-eight. The revenue share is due on Friday.

What it reads

  • Delivery receipts and entitlement records
  • Refunds and reversals in the period
  • The contract's revenue-share terms
  • The partner's statement

Checks before anything is sent

Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass.

Every option considered, including doing nothing

  1. Settle the amount the delivery receipts supportConsidered
  2. Settle the agreed amount and route the difference with its receiptsConsidered
  3. Hold the settlement, where the receipts are incompleteConsidered
  4. No adjustment, where the difference is refunds and reversals both sides agree onConsidered

Doing nothing is one of the outcomes, and it is recorded with its reason. The options are the record's own; a run decides between them.

Evidence record

Preview
Reference
The reference of the saved run.
Decision
One of the options, including no action, with the reason.
Checks
Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass.
Evidence kept
  • Delivery receipts
  • entitlement records
  • refunds
  • reversals
  • contract terms
  • settlement computation
  • partner statement
  • dispute record
The measures
Settlements paid without dispute, against the differences reconciled.
Connection
Written on every record: the systems the run read, and the sample it ran on.

The shape of the record, with no values. A reference appears only after a run is saved.

The improvement, and how it is measured

Hypothesis

A settlement computed from the delivery receipts is paid once and agreed; one computed from two statements is negotiated every month.

Modelled

The mechanism that could produce the result, stated; the figure is measured in the pilot.

Observed

Measured in a pilot’s validate stage, on your systems, against a comparison agreed first.

The result, the mechanism, the measurement, and the record’s five answers
Desired result
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
Mechanism
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
Measurement

Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out

Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency

  1. 01
    Desired result

    The result wanted.

    Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails

  2. 02
    Mechanism

    The mechanism that could produce it.

    Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain

  3. 03
    Evidence required

    The records kept to show it.

    Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger

  4. 04
    Costs and risks

    The cost, and the ways it can go wrong.

    Costs: Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline

    If it fails: Fail closed on eligibility/consent/price; queue retryable events; do not duplicate orders; route exception to campaign operations

  5. 05
    Measurement approach

    The measure that shows it helped.

    Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out

    Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency

Measured in the pilot's validate stage, on your systems, with the comparison agreed first. Every line above is the record's own design intent.

The business side

The change
Settlements paid without dispute, against the differences reconciled.
Running cost
Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it
Delivery receipts, entitlement records, refunds and reversals, contract terms, settlement computation, partner statement and dispute record.

The journey in detail

Step by step, from both sides
What the customer experiencesWhat the operator does
The momentThe moment that started it.Month end: a partner's statement says forty thousand activations, the operator's billing says thirty-eight, and the revenue share is due.Reads delivery receipts and entitlement records, refunds and reversals in the period, the contract's revenue-share terms, the partner's statement.
The decisionThe decision to be made.The customer's screen is unchanged.Computes the settlement from the delivery receipts and the outcome ledger, quantifies the difference and assigns it an owner.
The safeguardsThe conditions that stop it.Still unchanged: the action waits until every check has passed.Delivery-receipt completeness, entitlement match, refund and reversal accounting and contract-term checks pass.
The actionThe action that reaches the customer.Settle the agreed amount through the finance system, and route the difference to the partner with the receipts behind it. Reaches them on Partner portal, Finance workbench.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the recovery.The partner counts activations at request and the operator counts them at confirmation, and the two thousand missing are customers whose activation failed after the charge.The reconciliation shows the failed activations by receipt, the charges are reversed to the customers, and the contract's counting rule is written down so the next month starts from one definition.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.Settlements paid without dispute, against the differences reconciled.
The proofThe proof anyone can check.Can be answered for, later, from the record.Delivery receipts, entitlement records, refunds and reversals, contract terms, settlement computation, partner statement and dispute record.

Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.

The failure, and the recovery

What goes wrong

The partner counts activations at request and the operator counts them at confirmation, and the two thousand missing are customers whose activation failed after the charge.

What happens then

The reconciliation shows the failed activations by receipt, the charges are reversed to the customers, and the contract's counting rule is written down so the next month starts from one definition.

The products in this journey

Available to see today

Read the journey; a working session shows it running.

Request a working session