Reconcile both billing sides of a partial drop shipment

Setup requirements

1. The commercial owner defines whether dispatch, receipt or another approved event is the billing basis on each side. A supplier’s invoice is not itself proof of customer receipt.

2. Preserve sales-order line to purchase-order line links, units and shipment IDs. Do not infer a conversion ratio or cancel the unshipped remainder.

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

Inputs and access

1. Name

   linked_order_lines.csv

   Source or owner

   Order owner

   Scope

   Synthetic sales and purchase line IDs, supplier/customer tokens, ordered units and exact permitted unit conversions.

   Sensitivity

   Synthetic fixture only. Real commercial, personal, location or financial records need approved minimization and handling. No credentials are required.

   Permission needed

   Specific owner approval before any real-data pilot; no live access, uploads or external transmission authorized.

2. Name

   direct_ship_evidence.txt

   Source or owner

   Shipping coordinator

   Scope

   Synthetic supplier dispatch acknowledgements, customer receipts and disputes with shipment IDs and quantities.

   Sensitivity

   Synthetic fixture only. Real commercial, personal, location or financial records need approved minimization and handling. No credentials are required.

   Permission needed

   Specific owner approval before any real-data pilot; no live access, uploads or external transmission authorized.

3. Name

   billing_lines.csv

   Source or owner

   Billing owner

   Scope

   Synthetic purchase/sales invoice line IDs, shipment/order links, quantities, credits and document states.

   Sensitivity

   Synthetic fixture only. Real commercial, personal, location or financial records need approved minimization and handling. No credentials are required.

   Permission needed

   Specific owner approval before any real-data pilot; no live access, uploads or external transmission authorized.

4. Name

   billing_basis_rules.json

   Source or owner

   Commercial and accounting owners

   Scope

   Explicit separate payable/receivable evidence rules, cutoff, approved cancellation treatment and unresolved-dispute handling.

   Sensitivity

   Synthetic fixture only. Real commercial, personal, location or financial records need approved minimization and handling. No credentials are required.

   Permission needed

   Specific owner approval before any real-data pilot; no live access, uploads or external transmission 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

A supplier’s short shipment can leave customer and supplier billing based on different quantities when there is no company warehouse receipt.

Suggested task

Build a quantity-conserving bridge from supplier-direct dispatch and customer receipt evidence to both purchase and sales billing copies, leaving disputed quantities and billing authority for review.

What you could produce

A line-and-shipment bridge with evidenced delivery, supplier-billed, customer-billed and unresolved residual quantities, plus a separate commercial decision queue.

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

Order and billing coordinator

Trigger

A supplier confirms less direct-delivery quantity than the linked customer order.

Human approval

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

Finished output

A line-and-shipment bridge with evidenced delivery, supplier-billed, customer-billed and unresolved residual quantities, plus a separate commercial decision queue.

Proposed evaluation scope — no pilot authorized

Scope

One synthetic direct-delivery order, at most ten lines, 20 dispatch/receipt events and ten invoice/credit lines.

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 the linked order, billing and evidence copies at one cutoff; verify required line identifiers and units.

   Output: drop_ship_scope_manifest.json

   Expected output: drop_ship_scope_manifest.json

   Checkpoint: No company warehouse movement is invented to fill a missing receipt.

   Approval gate: Owner approves exact scope, copies and rule definitions before any pilot.

2. 2

   Extract dispatch, customer acceptance and dispute quantities by shipment, preserving the source’s distinction between sent, received and claimed.

   Output: direct_delivery_evidence.csv

   Expected output: direct_delivery_evidence.csv

   Checkpoint: A supplier message saying shipped does not become customer acceptance.

   Approval gate: Owner resolves ambiguous source language and evidence authority.

3. 3

   Map each shipment to the approved purchase and sales line IDs and check cumulative quantities against the order.

   Output: drop_ship_lineage_graph.json

   Expected output: drop_ship_lineage_graph.json

   Checkpoint: Repeated acknowledgements with the same event ID are not counted as additional deliveries.

   Approval gate: Owner approves identity mappings and unresolved joins.

4. 4

   Apply the two owner-supplied billing-basis rules separately and compare eligible-evidence quantities with each invoice leg.

   Output: two_sided_billing_bridge.csv

   Expected output: two_sided_billing_bridge.csv

   Checkpoint: A difference on the payable side cannot be netted against a receivable-side difference.

   Approval gate: Owner validates the rule and calculations; no live decision is implied.

5. 5

   Calculate unshipped, disputed, billed-without-required-evidence and evidenced-but-unbilled quantities; retain cancelled or credited lines visibly.

   Output: drop_ship_exception_controls.json

   Expected output: drop_ship_exception_controls.json

   Checkpoint: Each quantity has one physical state at the cutoff; commercial eligibility stays a separate reviewed attribute.

   Approval gate: Owner reviews exceptions and accepts unresolved status where evidence is insufficient.

6. 6

   Deliver the bridge, owner questions and proposed manual document-review sequence without creating invoices or changing fulfilment.

   Output: drop_ship_billing_review.json

   Expected output: drop_ship_billing_review.json

   Checkpoint: No invoice, credit note, replacement, payment, warehouse receipt or customer promise is executed.

   Approval gate: Owner accepts the separate draft 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}, Build a quantity-conserving bridge from supplier-direct dispatch and customer receipt evidence to both purchase and sales billing copies, leaving disputed quantities and billing authority for review. Follow the six-step design. Preserve exact identities, evidence spans, explicit policy boundaries and uncertainty. Use inspectable deterministic comparisons. Write only separate draft 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, upload files, post transactions or execute any recovery action.

Expected output schema — proposed

Primary key

1. sales_line_id

2. purchase_line_id

3. shipment_id

Columns

1. sales_line_id

2. purchase_line_id

3. shipment_id

4. unit

5. ordered_qty

6. supplier_dispatched_qty

7. customer_received_qty

8. disputed_qty

9. supplier_billed_qty

10. customer_billed_qty

11. payable_basis_qty

12. receivable_basis_qty

13. unshipped_qty

14. review_status

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

Orders

Sales line

SO1-L1

Purchase line

PO1-L1

Qty

12

Unit

each

Events

1. Id

   SHIP1

   Type

   supplier_dispatch

   Qty

   7

2. Id

   REC1

   Type

   customer_receipt

   Shipment

   SHIP1

   Qty

   6

3. Id

   DIS1

   Type

   customer_dispute

   Shipment

   SHIP1

   Qty

   1

Invoices

1. Id

   PI1

   Side

   supplier

   Qty

   7

2. Id

   SI1

   Side

   customer

   Qty

   12

Owner rules

Supplier bill basis

supplier_dispatch

Customer bill basis

customer_receipt

Unknown remainder

retain_open_not_cancelled

Expected

Ordered

12

Dispatched

7

Received

6

Disputed in dispatch

1

Unshipped

5

Payable basis qty

7

Payable difference qty

0

Receivable basis qty

6

Customer billed above supplied basis qty

6

Warehouse receipt created

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. Read supplied text and files, compare evidence and calculate transparent checks in an owner-approved environment.

   Capability source urls

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

   Workflow compatibility

   Untested. Requires an owner-approved file-processing environment; no CRM, ERP, payment or transport connector is assumed.

Failure modes

1. A supplier combines several customer orders in one dispatch note.

2. Customer receipt differs from supplier dispatch.

3. Purchase and sales units differ without a validated conversion.

Recovery and troubleshooting

1. Signal

   A supplier combines several customer orders in one dispatch note.

   Recovery

   Require line-level allocation or owner-supplied mapping; hold pooled quantities rather than splitting proportionally.

   Resume condition

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

2. Signal

   Customer receipt differs from supplier dispatch.

   Recovery

   Show both measurements and the disputed interval; let the commercial owner decide its billing basis.

   Resume condition

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

3. Signal

   Purchase and sales units differ without a validated conversion.

   Recovery

   Keep separate unit totals and stop monetary/quantity comparisons for the affected line.

   Resume condition

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

Unexecuted validation plan

Sample setup

Orders

Sales line

SO1-L1

Purchase line

PO1-L1

Qty

12

Unit

each

Events

1. Id

   SHIP1

   Type

   supplier_dispatch

   Qty

   7

2. Id

   REC1

   Type

   customer_receipt

   Shipment

   SHIP1

   Qty

   6

3. Id

   DIS1

   Type

   customer_dispute

   Shipment

   SHIP1

   Qty

   1

Invoices

1. Id

   PI1

   Side

   supplier

   Qty

   7

2. Id

   SI1

   Side

   customer

   Qty

   12

Owner rules

Supplier bill basis

supplier_dispatch

Customer bill basis

customer_receipt

Unknown remainder

retain_open_not_cancelled

Acceptance checks

1. Dispatch7 and receipt6 remain distinct evidence states.

2. The output does not call all 12 units delivered.

3. The unshipped five units remain open, not silently cancelled.

4. Replaying the same SHIP1 event ID does not increase dispatched quantity.

5. Every conclusion traces to a source row or explicitly labelled owner rule; identical frozen inputs preserve identities and deterministic totals.

6. All source copies remain unchanged; no business workflow or synthetic acceptance evaluation has been run.

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 and separately authored answer key only. No model run, numerical acceptance execution or customer pilot performed.

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.

5. The case requires owner preparation of 4 input groups and review of 6 intermediate/final artifacts. Costs and effort remain unmeasured; these are design counts, not runtime estimates.

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.