Policy Precedence & Transaction Control
Horizon — One-Time Payment Link
A financial-operations evaluation testing current-policy selection, missing-amount clarification, existing-customer reuse, and timing constraints.
Evaluation objective
Evaluate whether an agent can select the current policy, reject a plausible superseded rule, detect a mandatory financial value that does not exist in the environment, request that value before creating any charge, and preserve the context of an existing customer instead of creating duplicate records.
Scenario context
Marcus Vance runs an event-production company in Las Vegas. Late in the engagement cycle, a Venetian client approves an additional branded-keynote preview package. Because the main scope has already been closed and invoiced, the add-on should not enter the normal invoice flow.
The company treats this kind of work as a prepaid one-time charge. The client’s email confirms the add-on and specifies when the link should be sent. Internal documentation defines the process, and the environment includes both an existing customer record and a tracker template for the package. The only missing fact is the final amount agreed for the add-on.
User request
“I just got confirmation from Desmond in Gmail about the branded keynote add-on. Please handle this for me using the one time payment rule”
Task to be performed / inferred
Reconstruct the billing context and identify the current one-time-payment policy. Ask the user for the final amount, which cannot be inferred from the environment. After confirmation, prepare the payment link, complete a copy of the standard tracker, and schedule the follow-up for the client’s requested time. Do not send the link early.
Required evidence, documents & SOPs
Evidence sources
Venetian Add-on Approval
Provides the approval trigger, the business reason for separate billing, and the requested send timing.
- Current
One-Time Payment Workflow
Defines the current one-time payment process, prepayment requirement, customer-reuse rule, tracker workflow, and downstream timing expectations.
- Superseded · not authoritative
Net-30 Invoice Memo
A plausible but non-authoritative billing document that must be rejected in favor of the current one-time-payment SOP.
Venetian Customer Record
The existing billing identity for The Venetian Resort / Desmond Cho. The workflow requires reusing this customer rather than creating a duplicate.
Payment Tracker Template
The standard tracker that must be copied and filled rather than edited in place.
Operational destinations
One-Time Payment Trackers
Required location for completed one-time payment tracker documents.
Required user input
Final Charge Amount
The amount is intentionally absent from the environment and must be requested before any price or payment-link artifact is created.
Expected outcome / success condition
The agent asks for the missing amount before creating a charge. After confirmation of US$2,850, it reuses the existing customer, prepares a one-time payment link for the correct amount, creates a completed tracker copy, and schedules the reminder for the client's requested time. No duplicate customer is created and the link is not sent prematurely.
Golden Run
Normative reference execution — not an observed model run.
- 01
Read the client confirmation and current one-time-payment-link SOP. Recognize that the existing Net-30 memo is superseded and does not govern the case.
- 02
Resolve the existing customer in the payment system, locate the tracker template and destination, and confirm the requested follow-up time.
- 03
Verify that the add-on's final amount does not exist in the available sources and request it from the user before creating any charge.
- 04
After confirmation of US$2,850, create the one-time product/price/link in the context of the existing customer without creating a duplicate customer.
- 05
Create and complete a copy of the payment tracker with customer, contact, service, amount, link, and rationale for separate billing, preserving the prepayment condition before work begins.
- 06
Schedule the follow-up for the client's requested time and do not send the payment link prematurely.