Reconcile blanket quantities across call-off releases and receipts

The problem

A blanket agreement can have several releases, cancellations and receipts with different link quality. Treating goods received as agreement consumption, or restoring cancelled quantities without a policy, can hide outstanding releases and misstate the quantity still available before expiry.

Agent job

Reconstruct an agreement-line to release-line to receipt-line roll-forward using explicit references and owner-approved commercial rules; isolate orphan releases, invalid dates and terms requiring buyer review.

Expected output

A draft agreement roll-forward CSV, release/receipt bridge and expiry-question memo showing gross releases, allowed restorations, net release consumption, open deliveries and unresolved linkage.

Why an agent / simpler alternative

An agent may extract line-specific terms from supplied agreement copies and explain why a release, amendment or cancellation lacks authority. The commitment/release/receipt bridges and date checks should be deterministic. Use the existing blanket-order report or a simple relational query when IDs and rules are complete. Do not use an agent merely to subtract orders from a ceiling, and do not treat text extraction as a legal interpretation.

Who this helps

1. Purchasing coordinator

2. Contract administrator

Before a pilot — required, unexecuted

1. Obtain a specific owner-authorized synthetic test scope and independent expected-result oracle before executing the proposed workflow.

2. Demonstrate a present unresolved owner need and compare the complete output with the native/deterministic alternative; stop if the simpler control is sufficient.

3. Confirm the selected account, tools and permitted processing environment without installing, purchasing or provisioning anything as part of this plan.

4. Before an authorized fixture, define canonical gross-as-amended versus original-submitted fields, versioned signed amendment ordering, unique cancellation IDs, return signs and status transitions; use independent event-by-event expected balances rather than deriving the oracle from the plan text.

5. Test partial and duplicate cancellations, cancellation after receipt, unknown restoration authority, negative agreement residual, late/out-of-validity changes and competing agreements. Keep the orphan block on operational remaining capacity even where the explicitly linked arithmetic is reproducible.

Evidence boundary

Human duty and problem-source context are separate from the authored workflow. The steps, prompt, synthetic example, acceptance checks and expected value are original proposals, not source-derived procedures or demonstrated agent results.

Setup requirements

1. Verify a current manual reconciliation need and compare the current native blanket-order report; the 2017 missing-feature discussion is historical, and current official documentation confirms the feature exists.

2. Supply one agreement version per effective interval, explicit agreement-line/release-line references, amendment and cancellation events, receipt/return links and a common cutoff; agreement header matching alone is insufficient.

3. Buyer states whether each quantity is a ceiling, minimum, firm commitment or forecast, what events consume it, and whether each cancellation or return restores release capacity. Unknown semantics block an operational remaining-to-order conclusion.

4. Separate release-state quantities from fulfilment quantities. Draft orders do not consume capacity under the test policy; receipts never consume it a second time.

5. Commercial-rate comparisons require exact unit, currency and valid rate version. Keep legal entity and currency partitions separate; do not infer taxes, FX, liability or purchase authority.

Inputs and access

1. Name

   agreement_lines_and_terms.txt

   Source or owner

   Buyer/contract owner

   Sensitivity

   Synthetic fixtures first. Later copies may contain confidential operational data; retain only the stated fields and exclude personal/contact/payment data, credentials and unrelated text.

   Permission needed

   Planning only. Before a future pilot the owner must authorize the exact minimized files, processing environment and retention; no live access, connector, upload or provisioning is assumed.

   Scope

   Agreement/line/version IDs, legal-entity and supplier codes, item/unit, validity dates, quantity type, ceiling/commitment, supplied rate/currency and limited referenced term excerpts.

2. Name

   release_lines_and_changes.csv

   Source or owner

   Purchasing owner

   Sensitivity

   Synthetic fixtures first. Later copies may contain confidential operational data; retain only the stated fields and exclude personal/contact/payment data, credentials and unrelated text.

   Permission needed

   Planning only. Before a future pilot the owner must authorize the exact minimized files, processing environment and retention; no live access, connector, upload or provisioning is assumed.

   Scope

   Release-line ID, explicit agreement line, item/unit, status, order date, quantity, rate, and amendment/cancellation events with effective timestamp and source IDs.

3. Name

   receipts_returns_and_controls.csv

   Source or owner

   Receiving owner

   Sensitivity

   Synthetic fixtures first. Later copies may contain confidential operational data; retain only the stated fields and exclude personal/contact/payment data, credentials and unrelated text.

   Permission needed

   Planning only. Before a future pilot the owner must authorize the exact minimized files, processing environment and retention; no live access, connector, upload or provisioning is assumed.

   Scope

   Receipt/return IDs linked to release lines, posted status, quantity/unit, cutoff, exported control totals; no contact/payment information.

4. Name

   consumption_policy_and_current_rollforward.txt

   Source or owner

   Buyer/reporting owner

   Sensitivity

   Synthetic fixtures first. Later copies may contain confidential operational data; retain only the stated fields and exclude personal/contact/payment data, credentials and unrelated text.

   Permission needed

   Planning only. Before a future pilot the owner must authorize the exact minimized files, processing environment and retention; no live access, connector, upload or provisioning is assumed.

   Scope

   Documented capacity-consumption/restoration rule, treatment of draft/out-of-validity releases, receipt-return rule, expiry review window and snapshot being reconciled.

Proposed steps

1. 1

   Build one versioned agreement-line register with quantity meaning, unit, currency, validity boundary and consumption/restoration event rules; cite each supplied term and list ambiguities.

   Input: Agreement versions, limited terms and buyer rule sheet

   Output: Agreement authority register and unresolved-term questions.

   Expected output: Agreement authority register and unresolved-term questions.

   Checkpoint: A ceiling is not a mandatory minimum; blank terms cannot be filled with a standard practice assumption.

   Approval gate: Buyer/contract owner confirms quantity meaning, rule version and validity; no legal conclusion or agreement amendment is made.

2. 2

   Link releases only through explicit line IDs or an owner-approved mapping. Separate posted/submitted, draft, cancelled, out-of-validity and orphan records; retain contradictory item/unit/entity matches.

   Input: Release lines, change events and explicit agreement references

   Output: Release lineage and status ledger with orphan queue.

   Expected output: Release lineage and status ledger with orphan queue.

   Checkpoint: Every release appears once; matching supplier and SKU alone does not choose between overlapping agreements. Invalid dated releases remain visible.

   Approval gate: Buyer must resolve orphan or competing agreement references before an endorsed available-to-order quantity can be shown.

3. 3

   Apply each amendment/cancellation exactly once in effective order. Compute gross-as-amended submitted quantity as original submitted quantity plus signed amendment deltas; subtract only authorized cancellation restoration to obtain net consumption. Preserve negative residuals and uncertain branches.

   Input: Versioned rules and release-event ledger

   Output: Agreement consumption roll-forward with event arithmetic.

   Expected output: Agreement consumption roll-forward with event arithmetic.

   Checkpoint: Gross-as-amended = original submitted quantity + signed amendments; net release consumption = gross-as-amended - allowed restorations. Receipt quantities never consume capacity a second time.

   Approval gate: Buyer approves each restoration basis. Unknown cancellation effect propagates to remaining-capacity uncertainty.

4. 4

   Join posted receipts and returns to the release line, calculate net received separately, and show remaining release delivery. Flag overreceipt and returns that do not restore agreement capacity.

   Input: Net release lines and receipt/return events

   Output: Release-to-receipt fulfilment bridge and delivery exceptions.

   Expected output: Release-to-receipt fulfilment bridge and delivery exceptions.

   Checkpoint: Net releases = net received + open delivery for each complete line; an overreceipt yields a negative open-delivery exception rather than being clipped.

   Approval gate: Receiving confirms movements; no residual PO is closed, reopened or changed.

5. 5

   Reconcile agreement quantity into net releases plus unreleased arithmetic residual; show open delivery separately. Flag expiry-window, rate/version and out-of-validity discrepancies, retaining currency partitions.

   Input: Agreement and fulfilment bridges, dates and supplied rates

   Output: Agreement review table with expiry and commercial discrepancy queue.

   Expected output: Agreement review table with expiry and commercial discrepancy queue.

   Checkpoint: For complete same-unit records: agreement quantity - net received = unreleased + open delivery. Residual quantity is not a recommendation or obligation to purchase; unresolved orphans block endorsement.

   Approval gate: Buyer decides whether an expiry or terms discrepancy needs action; no release, extension, supplier contact or legal interpretation is authorized.

6. 6

   Prepare a draft packet with evidence links and exact questions for the buyer, including which unknown could change each remaining quantity; separate arithmetic values from approved commercial decisions.

   Input: Bridges, orphan queue and unresolved terms

   Output: Draft blanket-agreement reconciliation and expiry review packet.

   Expected output: Draft blanket-agreement reconciliation and expiry review packet.

   Checkpoint: No agreement is labelled fulfilled, expired without consequence, legally owed or safe to order solely from the arithmetic. All owner dispositions stay pending.

   Approval gate: Owner reviews before relying on it; purchase creation, order cancellation, contract changes and external communication require separate authorization.

Original starter prompt — proposed

Origin

editorial_proposal

Label

Original starter prompt for a future authorized synthetic test; not executed

Placeholders

1. agreements

2. releases_changes

3. receipts_returns

4. policy

5. cutoff

6. output_folder

Text

Using the saved copies {agreements}, {releases_changes}, {receipts_returns} and {policy} at {cutoff}, prepare a draft agreement-to-release-to-receipt roll-forward. Identify whether each quantity is a ceiling, minimum, firm commitment or forecast from owner-supplied terms; leave ambiguity unresolved. Apply only explicit agreement-line links and approved cancellation-restoration rules. Keep drafts, orphan releases, invalid dates and mixed units/currencies visible. Reconcile gross releases less restorations to net releases, and net releases to net receipts plus open delivery. Show unreleased arithmetic quantities separately from any endorsed available-to-order decision. Save new agreement_rollforward.csv, release_receipt_bridge.csv and expiry_questions.txt in {output_folder}. Do not create orders, change contracts, interpret liability, close POs or send messages.

Execution authorized

No

Expected output schema — proposed

Origin

editorial_proposal

Columns

1. agreement_line_id

2. version

3. entity_code

4. supplier_code

5. item_code

6. unit

7. quantity_type

8. agreement_qty

9. signed_amendment_qty

10. gross_submitted_release_qty

11. authorized_restoration_qty

12. net_release_qty

13. net_received_qty

14. open_delivery_qty

15. unreleased_arithmetic_qty

16. valid_through

17. days_to_expiry

18. currency

19. rate_ref

20. orphan_or_invalid_refs

21. operational_remaining_status

22. source_rows

23. owner_decision

Record status

draft_pending_owner_review

Synthetic output illustration — not an executed result

Label

Synthetic authored input/output expectation, not an observed run

Synthetic

Yes

Executed

No

Owner approval status

pending_not_obtained

Data

Agreement

Id

SYN-B1-L1

Entity

SYN-CA1

Supplier

SYN-S1

Item

SYN-PART1

Quantity type

quantity_ceiling_not_minimum

Qty

1000

Unit

each

Currency

CAD

Unit rate pretax

12.5

From

2026-10-01

Through

2026-10-31

Policy

Id

SYN-BP1

Cutoff local date

2026-10-14

Timezone

America/Toronto

Consumption

Submitted linked releases only

Cancellation

C1 is approved to restore 100 each once

Receipt return effect

Does not restore agreement release capacity

Expiry boundary

Valid through stated local date; remaining days is date subtraction

Releases

1. Id

   SYN-REL1

   Agreement line

   SYN-B1-L1

   Status

   submitted

   Date

   2026-10-02

   Qty

   300

2. Id

   SYN-REL2

   Agreement line

   SYN-B1-L1

   Status

   submitted

   Date

   2026-10-05

   Qty

   250

3. Id

   SYN-REL3

   Agreement line

   SYN-B1-L1

   Status

   draft

   Date

   2026-10-08

   Qty

   150

4. Id

   SYN-ORPHAN4

   Agreement line

   Not specified.

   Supplier

   SYN-S1

   Item

   SYN-PART1

   Status

   submitted

   Date

   2026-10-08

   Qty

   80

Cancellations

1. Id

   SYN-C1

   Release

   SYN-REL1

   Date

   2026-10-04

   Qty

   100

   Restoration approved by fixture rule

   Yes

Receipts

1. Id

   SYN-REC1

   Release

   SYN-REL1

   Date

   2026-10-06

   Qty

   200

2. Id

   SYN-REC2

   Release

   SYN-REL2

   Date

   2026-10-09

   Qty

   120

Illustrative expected release rows

1. Release

   SYN-REL1

   Gross

   300

   Restored

   100

   Net release

   200

   Net received

   200

   Open delivery

   0

2. Release

   SYN-REL2

   Gross

   250

   Restored

   0

   Net release

   250

   Net received

   120

   Open delivery

   130

Illustrative expected agreement row

Agreement line

SYN-B1-L1

Gross submitted releases

550

Authorized restoration

100

Net releases

450

Net received

320

Open delivery

130

Unreleased arithmetic

550

Days to expiry

17

Formula checks

1. 550 - 100 = 450

2. 450 - 320 = 130

3. 1000 - 450 = 550

4. 1000 - 320 = 550 + 130

Draft excluded refs

1. SYN-REL3

Orphan refs

1. SYN-ORPHAN4

Operational remaining status

unendorsed_pending_orphan_mapping_and_buyer_review

Source rows

1. SYN-B1-L1

2. SYN-BP1

3. SYN-REL1

4. SYN-REL2

5. SYN-C1

6. SYN-REC1

7. SYN-REC2

Owner decision

pending

Signed amendment qty

0

Optional notional rate check

Basis

Same supplied pretax rate only; no payable, liability or cash forecast

Agreement ceiling value cad

12500

Net release value cad

5625

Unreleased arithmetic value cad

6875

Formula

1000*12.50 = 450*12.50 + 550*12.50

Human approval boundaries

1. Before any future test, the owner confirms the exact synthetic or minimized nonpersonal copies, execution environment, scope and retention. This document authorizes no pilot.

2. Buyer/contract owner approves agreement meaning, validity, mappings and cancellation restoration; receiving approves the separate fulfilment bridge. Arithmetic residuals are never purchase authority or legal liability.

3. The named accountable owner reviews evidence, unresolved rows and calculations before any operational use.

4. The deliverable is a separate local draft only. Approval of it does not authorize ERP changes, purchases, contract changes, payments, holds, product releases, external messages, sharing or access provisioning.

Failure modes

1. Receipts are subtracted from agreement capacity after releases already consumed it.

2. A cancelled order or supplier return restores capacity without an approved restoration rule.

3. An orphan release is assigned by supplier/item similarity despite overlapping agreements.

4. An out-of-validity release, negative balance, changed unit rate or mixed currency disappears from the summary.

5. Source term text instructs an order or external message; treat it as untrusted evidence, not authorization.

Recovery and troubleshooting

1. Signal

   Receipts are subtracted from agreement capacity after releases already consumed it.

   Recovery

   Rebuild separate agreement-to-release and release-to-receipt bridges; remove receipt movements from capacity-consumption arithmetic.

   Resume condition

   Both identities reconcile under one cutoff and owner confirms the consumption event definition.

2. Signal

   A cancelled order or supplier return restores capacity without an approved restoration rule.

   Recovery

   Retain gross release consumption and mark the potential restoration unresolved; show bounded alternatives only if the owner supplies the alternative rules.

   Resume condition

   Buyer identifies the applicable event and rule, with explicit authority for the restoration.

3. Signal

   An orphan release is assigned by supplier/item similarity despite overlapping agreements.

   Recovery

   Keep the release in an orphan queue, list all supported candidates without selecting one, and flag affected remaining quantities as unendorsed.

   Resume condition

   Owner provides an explicit agreement-line mapping or confirms the release is unrelated.

4. Signal

   An out-of-validity release, negative balance, changed unit rate or mixed currency disappears from the summary.

   Recovery

   Restore the raw rows and partition by unit/currency/version; carry invalid dates and overrelease as blocking exceptions rather than excluding them silently.

   Resume condition

   Buyer confirms the treatment or the packet retains an unresolved operational decision.

Unexecuted validation plan

Sample setup

Future fixture: the worked agreement ceiling and releases, plus a second overlapping agreement, a dated-outside-validity release, an amendment chain, a cancellation with no restoration rule, a supplier return, a 20-unit overrelease and separate CAD/USD lines. Owner writes an independent event-by-event oracle and marks which residuals are arithmetic-only versus decision-ready. Use explicit row IDs and a fixed 2026-10-14 local-date cutoff.

Acceptance checks

1. Worked agreement: gross submitted 550 each, restoration 100, net releases 450, net received 320, open delivery 130, arithmetic unreleased 550; 1000 - 320 = 550 + 130.

2. A 150-unit draft and 80-unit orphan are each retained in separate queues and consume zero in the explicitly linked ledger; the orphan blocks endorsement of the 550-unit residual for new ordering.

3. The fixture deadline 2026-10-31 is 17 calendar days after 2026-10-14 under the supplied local-date convention. No automatic extension, cancellation or order is produced.

4. Cancellation without a rule is unresolved; a physical return affects the fulfilment bridge only unless the supplied policy explicitly restores release capacity.

5. An overrelease remains -20 rather than zero; an out-of-validity release and rate/currency mismatch remain visible and prevent an unqualified commercial conclusion.

6. Amendment events are applied once in effective order; identical file reordering does not alter totals, and overlapping agreements do not trigger fuzzy allocation.

7. Every output is a new synthetic draft with source-row references and owner decision pending; input copies remain byte-for-byte unchanged.

8. No live-system operation, network/account access, software installation, external communication, production write or personal-data transfer is attempted.

Stop conditions

1. A planted critical exception is missed, a blocked value is silently included, or a source link or policy is invented.

2. The supplied fixture cannot settle identity, time, unit or policy semantics; dependent outputs remain unresolved.

3. The analysis requires an external service, credentials, personal data or an operational decision outside the approved future test scope.

Executed

No

Fixture status

Unexecuted fixture and independent-oracle design. No workflow, fixture execution or acceptance test is claimed.

Approval status

not_requested_or_granted_for_execution

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Current account eligibility, tool availability, plan price, usage limits and per-run cost are unknown; verify before an authorized pilot.

2. Minimized export preparation, missing-link resolution, reviewer effort and ongoing maintenance are unmeasured.

3. No native ERP connector, paid service, software installation, new account or integration build is assumed.

4. Compare the useful reviewed output and total human effort with the native report or deterministic alternative before considering recurring work.

Caveat

No numerical cost, effort saving, financial return, income or market-demand claim is established.

Canadian adaptation — proposed

For Canadian buying teams, preserve the contracting legal entity, CAD or foreign-currency labels, item-specific units and English/French agreement text references. Have the buyer define the timezone and inclusive expiry boundary for each site. The synthetic rate is pretax CAD and creates no tax, FX, import-duty or legal-liability conclusion; qualified owners supply any later treatment. Canadian deployment and compliance remain untested.

Limits

1. Original editorial plan, not a source-documented agent case. No workflow, fixture or acceptance test was executed.

2. Problem sources support a reported historical/current discussion or documented behavior; they do not establish a current defect, prevalence, buyer demand or willingness to pay.

3. Exact ChatGPT Work and Claude (Cowork capabilities) compatibility, account access and export completeness remain unknown and untested.

4. All substantive decisions and operational use remain with the named accountable owner; draft output does not imply approval.

5. Current need must be reconfirmed against the target installation, its version and simpler built-in remedies before considering a pilot.

Candidate platforms — compatibility untested

1. Name

   ChatGPT Work

   Current access note

   Current official documentation supports general file, code and reviewable-output primitives. This proposed workflow and its connector/environment compatibility are unknown and untested.

   Setup caveat

   Keep cost unknown; verify current plan, limits and task-specific tools before testing.

   Workflow compatibility

   Unknown and untested for every proposed plan.

   Availability in canada

   Not assessed by this reference update.

   Required capabilities

   1. Read owner-supplied structured and text copies in the approved task workspace.

   2. Run inspectable deterministic joins, conservation checks and calculations using available tools.

   3. Create separate reviewable CSV and text files with source-row references.

   Capability source urls

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

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Selection basis

   Candidate from general documented primitives only; no ERP integration, account access or end-to-end compatibility is claimed.

2. Name

   Claude (Cowork capabilities)

   Current access note

   Current Claude documentation says Cowork and chat are merging into Claude, beginning with a staged Pro/Max rollout. Some accounts still show Cowork. Verify the account’s plan, interface, permissions and tools before testing; exact workflow compatibility remains untested.

   Setup caveat

   Use current help for actual runtime and permissions. Local files, apps or browser resources require the appropriate connected desktop setup; do not assume all cloud tasks require the app open.

   Workflow compatibility

   Unknown and untested for every proposed plan.

   Availability in canada

   Not assessed by this reference update.

   Required capabilities

   1. Read owner-supplied structured and text copies in the approved task workspace.

   2. Run inspectable deterministic joins, conservation checks and calculations using available tools.

   3. Create separate reviewable CSV and text files with source-row references.

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Selection basis

   Candidate from general documented primitives only; no ERP integration, account access or end-to-end compatibility is claimed.