Compare rental charge periods with approved stop events

Setup requirements

1. Owner specifies whether accepted off-hire, collection or physical receipt controls billing.

2. Do not infer damage charges, deposit deductions, taxes or entitlement from physical custody.

3. Before any pilot, confirm an actual unresolved need and approve minimized inputs, processing environment, retention and recipients. This design does not authorize execution.

Inputs and access

1. Name

   rental_lines.csv

   Source or owner

   Rental owner

   Scope

   Opaque asset/contract-line IDs, bill start, rate unit and draft charge interval.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

2. Name

   stop_and_return_events.csv

   Source or owner

   Operations owner

   Scope

   Request, accepted off-hire, collection and warehouse receipt events with exact authority.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

3. Name

   billing_rules.json

   Source or owner

   Finance/commercial owner

   Scope

   Approved stop-event type, boundary convention, proration and minimum-period rules.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

Human approval boundaries

1. Before a pilot, the accountable owner approves exact synthetic/minimized copies, processing environment, retention and allowed recipients.

2. Owner validates identity mappings, authority, status definitions and all unresolved evidence.

3. Any source mutation, account access, upload, external communication, commercial commitment, payment or changed permission requires separate appropriate authorization.

The problem

Recurring rental charges and physical return records can become disconnected when the hire end date changes.

Suggested task

Compare draft rental periods with owner-approved billing-stop evidence while keeping physical custody separate.

What you could produce

A rental-period review sheet with conditional proration differences and unresolved stop authority.

Why an agent / simpler alternative

Mixed narrative and structured evidence can benefit from assisted extraction and explanation. Identity joins, interval calculations and totals require deterministic checks. A supported native report, query or spreadsheet is preferable when it answers the owner’s question reliably.

When this work comes up

Role

Rental billing coordinator

Trigger

A return or off-hire event conflicts with a draft charge period.

Human approval

Owner approves scope, rules and evidence interpretation. Any operational action requires separate appropriate authorization.

Finished output

A rental-period review sheet with conditional proration differences and unresolved stop authority.

Proposed evaluation scope — no pilot authorized

Scope

At most 20 synthetic rental lines, one billing month and 50 stop/return events.

Limit origin

Editorial evaluation bound, not a verified platform limit.

Overflow action

Stop and ask for approved partitioning; no silent truncation.

Pilot authorized

No

Evidence boundary

Firsthand reports establish stated friction or concerns only. O*NET provides duty context. Official documents establish limited native features or general primitives. This workflow, safeguards, fixtures and outputs are original proposals, not source-documented executions.

Proposed steps

1. 1

   Freeze contract-line identity, month window and approved billing rule version.

   Output: rental_scope.json

   Expected output: rental_scope.json

   Checkpoint: A reused serial must retain distinct contract-line assignments.

   Approval gate: Owner approves exact inputs and rule scope before any pilot.

2. 2

   Extract stop requests, acceptances and physical handoffs as different event types.

   Output: rental_event_ledger.csv

   Expected output: rental_event_ledger.csv

   Checkpoint: A customer request alone is not accepted termination.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

3. 3

   Join each line to permitted stop evidence and flag missing or conflicting authority.

   Output: stop_basis.csv

   Expected output: stop_basis.csv

   Checkpoint: Warehouse receipt cannot silently replace the contracted stop definition.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

4. 4

   Compute conditional billable intervals and proration with deterministic arithmetic under supplied rules.

   Output: charge_period_workpaper.csv

   Expected output: charge_period_workpaper.csv

   Checkpoint: Minimum periods and inclusive/exclusive boundaries are explicit.

   Approval gate: Owner validates the calculation or decision rule before relying on its result.

5. 5

   Compare draft amount and period with the workpaper while showing the custody gap separately.

   Output: rental_charge_exceptions.csv

   Expected output: rental_charge_exceptions.csv

   Checkpoint: A later physical return does not itself justify a later charge.

   Approval gate: Owner reviews unresolved findings; no operational action is authorized.

6. 6

   Deliver owner questions and conditional differences without changing subscriptions, invoices or asset status.

   Output: rental_billing_review.json

   Expected output: rental_billing_review.json

   Checkpoint: No refund, collection, termination or external message is sent.

   Approval gate: Owner accepts the separate artifact; all live actions require separate authorization.

Original starter prompt — proposed

Origin

editorial_proposal

Execution authorized

No

Text

Using only {approved_synthetic_inputs} and {owner_rules}, Compare draft rental periods with owner-approved billing-stop evidence while keeping physical custody separate. Follow the six-step design. Preserve exact identities, evidence spans and uncertainty. Use inspectable calculations. Write only separate review artifacts described by the output schema. Stop for missing authority, ambiguous evidence or out-of-scope data. Do not change source records, contact anyone, access live accounts, post transactions or execute recovery actions.

Expected output schema — proposed

Primary key

1. contract_id

2. rental_line_id

3. billing_period_id

Columns

1. asset_id

2. bill_start

3. approved_stop_event

4. physical_return_time

5. billable_interval

6. proration_rule

7. conditional_amount

8. draft_amount

9. currency

10. authority_conflict

11. source_spans

12. owner_decision

Record status

draft_review_only

Common provenance columns

1. input_snapshot_id

2. rule_version

3. source_document_id

4. source_row_or_span

5. reviewer_decision

Unknown value policy

Unknown values remain null, not zero. Keep raw identities and evidence. Unresolved rows do not silently enter approved totals.

Synthetic output illustration — not an executed result

Label

Synthetic authored example, not observed output

Synthetic

Yes

Executed

No

Input

Monthly rate

300

Month days

30

Billable days

20

Draft

300

Receipt

2026-09-23

Expected

Conditional amount

200

Draft minus conditional

100

Automatic credit

No

Limits

1. Original proposed and untested design; no source documents this complete agent workflow.

2. A reported problem is not proof of prevalence, willingness to pay, harm magnitude or current demand.

3. Historical product reports require current-installation checks; a current capability document only establishes general primitives.

4. Native reports or a deterministic script may be simpler. Exports, identity mappings, context size, privacy controls and actual tool compatibility remain untested.

5. Numerical fixtures are synthetic and have not been executed. Owner review is necessary; no time saving, cost saving or revenue outcome is asserted.

Candidate platforms — compatibility untested

1. Name

   ChatGPT Work

   Required capabilities

   1. Assess this plan’s input, operation and output requirements before selecting an account.

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   Selection basis

   Editorial candidate only. Shared source facts are general primitives; this plan remains unexecuted.

   Workflow compatibility

   BotCurrent has not tested this workflow.

Failure modes

1. Asset serial appears on two simultaneous contract lines.

2. Off-hire acceptance has no effective time.

3. Daily proration conflicts with a minimum full-month clause.

Recovery and troubleshooting

1. Signal

   Asset serial appears on two simultaneous contract lines.

   Recovery

   Hold the identity join until the owner resolves assignment.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

2. Signal

   Off-hire acceptance has no effective time.

   Recovery

   Leave proration unresolved rather than using email receipt time.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

3. Signal

   Daily proration conflicts with a minimum full-month clause.

   Recovery

   Present the conflict to the commercial owner; do not choose the lower amount.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

Unexecuted validation plan

Sample setup

Monthly rate

300

Month days

30

Billable days

20

Draft

300

Receipt

2026-09-23

Acceptance checks

1. Rule: September300, actual-day proration, startSep1 inclusive and accepted stopSep21 exclusive yields20/30*300=200.

2. Physical receiptSep23 remains a custody event and does not change200 under that supplied rule.

3. Draft300 therefore differs by100, subject to owner review.

4. Removing accepted stop evidence leaves the calculation unresolved rather than using the request date.

5. Every conclusion traces to a source row or an explicitly labelled owner rule; repeated evaluation of identical frozen inputs must preserve identities and totals.

6. All original copies remain unchanged. Output is a draft review artifact, not an operational decision.

Stop conditions

1. Required identity, source coverage, calculation policy or owner authority is missing.

2. Unexpected real sensitive data is supplied without approved handling.

3. Requested work would require live access, upload, external communication, accounting posting, payment, permission change or irreversible action.

Executed

No

Fixture status

Designed specification only. No acceptance fixture or business workflow executed.

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Plan access, model usage, tool runtime and storage costs unknown.

2. Export preparation, evidence cleanup, review and correction effort unmeasured.

3. No native integration, paid service, new account or software installation assumed.

4. Case-specific effort is unknown: source extraction, identity repair, owner-rule preparation, fixture design and review may dominate model cost.

Caveat

No measured time saving, current demand, ROI or price claim. Compare the simpler remedy first.

Canadian adaptation — proposed

Verify local privacy and organizational record-handling requirements before any real-data pilot; preserve original currency, business calendars and time zones. No Canadian deployment or compliance claim.