> ## Content Index
> Fetch the complete content index at: https://abundance.alloconomy.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Sent, Received, Accepted: Three Different Claims
- URL: https://abundance.alloconomy.com/alloconomy/commerce-sent-received-accepted/
- Published: 2026-10-19T07:33:45.000Z
- Updated: 2026-10-22T22:20:21.000Z
- Description: Order lines, shipment assertions, receipt evidence and message status.
- Author: Sathya Narayanan
- Tags: Alloconomy, Supply Chain, Commerce, Behind the Buy Button, #series-detail, #Import 2026-10-18 23:22

Supply Chain · Sixteen essays

Behind the Buy Button

Complete reading path · You are in Part 4 of 16
1. Part 1 [I Bought a Book. What Had to Be Promised First?](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/) The cast, the cheat sheet, and the whole commercial system.
2. Part 2 [Maya Sells to eComm Inc. Maya Also Sells Through eComm Inc.](https://abundance.alloconomy.com/alloconomy/commerce-who-is-selling-to-whom/) Retail vendors, marketplace sellers, custody and direct fulfillment.
3. Part 3 [The Purchase Order Begins Before the Purchase Order](https://abundance.alloconomy.com/alloconomy/commerce-before-the-purchase-order/) Need, supplier identity, sourcing, approval and changing commitments.
4. Part 4 **Sent, Received, Accepted: Three Different Claims**Current essay Order lines, shipment assertions, receipt evidence and message status.
5. Part 5 [The $140 Disagreement Inside One Invoice](https://abundance.alloconomy.com/alloconomy/commerce-the-140-dollar-disagreement/) Two-, three- and four-way matching, disputes and settlement.
6. Part 6 [The Price After the Price](https://abundance.alloconomy.com/alloconomy/commerce-the-price-after-the-price/) Rebates, credits, working capital and realized supplier economics.
7. Part 7 [How Do You Receive an Hour of Work?](https://abundance.alloconomy.com/alloconomy/commerce-how-do-you-receive-an-hour/) Labor, maintenance and professional services need their own evidence.
8. Part 8 [Software Is a Promise Over Time](https://abundance.alloconomy.com/alloconomy/commerce-software-is-a-promise-over-time/) Access, usage, licenses, digital rights and renewal decisions.
9. Part 9 [A Printing Machine Is Not Yet Printing Capacity](https://abundance.alloconomy.com/alloconomy/commerce-a-machine-is-not-yet-capacity/) Manufacturing plans, advances, assets and readiness for use.
10. Part 10 [When the Project Changes, What Exactly Changed?](https://abundance.alloconomy.com/alloconomy/commerce-when-the-project-changes/) Scope, RFIs, approved changes, progress claims and retention.
11. Part 11 [Buying Power, Renting Space, Committing Time](https://abundance.alloconomy.com/alloconomy/commerce-power-space-and-time/) Electricity, financial energy settlements and leases.
12. Part 12 [Now eComm Inc Is the Seller](https://abundance.alloconomy.com/alloconomy/commerce-the-platform-becomes-the-seller/) Business purchasing, cloud billing and marketplace collection.
13. Part 13 [One Transaction, Several Accounting Clocks](https://abundance.alloconomy.com/alloconomy/commerce-one-transaction-several-clocks/) Commitments, accruals, cash, assets and financial-statement scale.
14. Part 14 [A System That Can Remember Why](https://abundance.alloconomy.com/alloconomy/commerce-a-system-that-remembers/) Linking documents, quantities, time, corrections and independent evidence.
15. Part 15 [Safety Before Speed: What a Green Tick Cannot Approve](https://abundance.alloconomy.com/alloconomy/commerce-safety-before-speed/) Payment authority, supplier changes, duplicates, incentives and AI limits.
16. Part 16 [Follow the Promises Back to My Book](https://abundance.alloconomy.com/alloconomy/commerce-follow-the-promises-home/) A worked capstone and the bridge to the inbound and outbound series.

**Illustrative examples. Public sources. Personal views.**

I am Sathya Narayanan, writing in a personal capacity as I learn in public. The views, interpretations and teaching models are my own; they do not represent my employer or any other organization and carry no employer approval or endorsement. No confidential, proprietary or nonpublic employer information is used. Factual background comes only from publicly available sources. Maya of Stories Inc, the book vendor; Mayan of Sapiens Inc, the printing-machine supplier; and eComm Inc, the ecommerce company, are fictional teaching characters and companies. I appear as the customer in imagined scenes, not as a report of my actual purchases. These scenes do not describe any real company or its internal systems. The cases are separate teaching examples, not one continuous ledger. Scenario amounts, rates, terms and policies are illustrative assumptions unless expressly identified as dated public facts. Actual contracts, regulations, operations and economics require case-by-case analysis.

**Visual guide: the steps and the records they create**

[Open the buying and selling graph and quick definitions →](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/#buyer-seller-construct-map) See the industry names for PO, sales order, ASN, receipt, invoice and payment, with the steps that create or update each record.

Companion maps: [Inbound receiving](https://abundance.alloconomy.com/alloconomy/before-the-shelf/#buyer-seller-construct-map) · [Customer fulfillment](https://abundance.alloconomy.com/alloconomy/from-click-to-doorstep/#customer-fulfillment-construct-map)

*Part 4 of 16 · Behind the Buy Button*

## Maya says sixty; the receiving team says fifty-eight

eComm Inc has ordered 100 books at $20 each. Maya's first shipment notice reports 60 books. The receiving team counts 58\. Of those, 56 pass the assumed inspection; two have damaged-looking covers and await a decision.

It is tempting to choose one number and call it “the quantity.” That would remove most of what we need to learn.

[![Part 4: books & evidence. 60 declared = 56 accepted + 2 held + 2 not counted Fictional teaching model.](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-04.png)](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-04.png?ref=abundance.alloconomy.com)

Four quantities. Four meanings. ORDERED — 100 — Whole order; DECLARED SHIPPED — 60 — First shipment; COUNTED — 58 — Receiving observation; ACCEPTED — 56 — Inspection so far. Forty books have not yet been declared shipped. Counts are illustrative. Fictional example; see the nearby table and prose for an accessible explanation.  
[View the full-size diagram →](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-04.png?ref=abundance.alloconomy.com)

## The evidence cheat sheet

| Observation               | Quantity | Who or what supports it?            |
| ------------------------- | -------- | ----------------------------------- |
| Ordered                   | 100      | Approved commercial order           |
| Declared shipped          | 60       | Maya's shipment assertion           |
| Counted at receipt        | 58       | Receiving team's observation        |
| Accepted so far           | 56       | Inspection decision in this example |
| Still awaiting inspection | 2        | Open quality record                 |
| Not yet declared shipped  | 40       | Remaining order quantity            |

The two missing books and the two held books are different problems. The remaining 40 books are not automatically part of the first shipment's shortage. Every quantity needs a scope: which order line, which shipment, which receipt and which date?

## A shipment notice makes a claim about departure

An advance shipment notice, or ASN, tells the recipient what the supplier says is on the way. Amazon's [Vendor Shipments documentation](https://developer-docs.amazon/sp-api/docs/vendor-retail-procurement-shipments-api?ref=abundance.alloconomy.com) explicitly names shipment confirmation as an ASN.

In our example, Maya's notice and eComm Inc's count are independent statements only if someone actually counted the books. A “receipt” copied automatically from the shipment notice cannot independently confirm that 60 arrived. Two agreeing screens can be repeating one assertion.

[**Before the Shelf**](https://abundance.alloconomy.com/alloconomy/before-the-shelf/) examines the physical handling and counting process. Here we need its commercial consequence: preserve what was declared and what was observed so the discrepancy can be investigated.

## A unit needs a meaning

Now suppose Maya ships ten cartons, while the receiver records 120 individual books. These quantities agree if each carton contains twelve copies.

**Normalized copies = cartons × copies per carton = 10 × 12 = 120.**

The conversion needs an effective date. If Maya later switches to ten-copy cartons, rewriting the master record must not turn the old receipt into 100 copies. Keep the submitted quantity, unit, conversion and normalized quantity together.

The same discipline applies to an edition identifier. A hundred copies of the wrong edition do not satisfy an order merely because the count matches. A monetary quantity used in a software integration is different again; Part 12 examines that trap.

## The message arrived; did the business event happen?

Maya's system submits an invoice and receives a technical processing status. That tells her something about the message. It does not, by itself, tell her whether the invoice was approved or the bank payment settled.

Amazon's [transaction-status documentation](https://developer-docs.amazon.com/sp-api/docs/get-transaction-status?ref=abundance.alloconomy.com) is particularly instructive: the available result depends on the operation, and the documented Success state is not supported for submitted invoices or acknowledgements. Reading all interface statuses as one universal business outcome would be a mistake.

For eComm Inc, I would keep separate observations for message receipt, commercial validation, accounting recognition and payment. That is a proposed model for this series. It is not a description of Amazon's internal implementation.

## Acceptance applies a requirement to evidence

The inspector might release the two held books after examining their covers. Accepted quantity would rise from 56 to 58; physically received quantity would stay 58\. No new books arrived. A decision changed.

If the two missing books are subsequently located, the receipt history should record the correction or additional event. It should not silently replace the original count. Maya and eComm Inc need to understand both the best current view and why yesterday's view differed.

For Maya, this supports a specific claim rather than a vague complaint that “the system is wrong.” For eComm Inc, it assigns the next task to the right person: count, quality, item identity or data interpretation. For me, it explains why a fulfillment status and the condition of the book in my hand can answer different questions.

Our next step is to put prices beside these quantities. That will turn the disagreement into dollars without making it disappear.

## Continue the series

Previous: [The Purchase Order Begins Before the Purchase Order](https://abundance.alloconomy.com/alloconomy/commerce-before-the-purchase-order/). Next: [The $140 Disagreement Inside One Invoice](https://abundance.alloconomy.com/alloconomy/commerce-the-140-dollar-disagreement/). Return to [the introduction and cheat sheet](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/).

*Evidence and method: public references were checked on October 18, 2026\. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.*