> ## 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.

# How Do You Receive an Hour of Work?
- URL: https://abundance.alloconomy.com/alloconomy/commerce-how-do-you-receive-an-hour/
- Published: 2026-10-19T07:33:22.000Z
- Updated: 2026-10-22T22:20:34.000Z
- Description: Labor, maintenance and professional services need their own evidence.
- 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 7 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](https://abundance.alloconomy.com/alloconomy/commerce-sent-received-accepted/) 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?**Current essay 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 7 of 16 · Behind the Buy Button*

## There is no box containing Tuesday's maintenance

Sapiens Inc. maintains eComm Inc's printing machines. A technician works on Tuesday, but the invoice arrives the following month. What would eComm Inc “receive” in this transaction?

The answer depends on what it bought. It may have bought hours, a completed repair, a coverage period, or an outcome. Treating these as interchangeable makes the paperwork look simpler while weakening the evidence.

[![Part 7: labor & services. Evidence must match the promise: time, output or coverage. Fictional teaching model.](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-07.png)](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-07.png?ref=abundance.alloconomy.com)

Which hours have supporting evidence? CLAIMED — 120 hours — 120 × $50 = $6,000; SUPPORTED — 112 hours — 112 × $50 = $5,600; UNDER REVIEW — 8 hours — 8 × $50 = $400\. Missing evidence is a question to investigate, not proof that no work occurred. 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-07.png?ref=abundance.alloconomy.com)

## The services cheat sheet

| Pricing basis      | Evidence that matters in our model                | Insufficient by itself        |
| ------------------ | ------------------------------------------------- | ----------------------------- |
| Time and materials | Approved time, agreed rates, authorized materials | A total on an invoice         |
| Fixed deliverable  | Defined output and acceptance criteria            | Time spent working            |
| Coverage period    | Evidence of the contracted coverage               | One successful service visit  |
| Outcome            | Measurement against an agreed outcome             | An enthusiastic status report |

These are proposed examples. Amazon's [Japan data-center security role](https://www.amazon.jobs/en/jobs/10544222/security-specialist-data-center-physical-security?ref=abundance.alloconomy.com) names work orders, requisition requests, purchase orders and invoice validation. A role description supports those terms in that operation; it does not publish a universal services-acceptance policy.

## Start with the service promise

Assume eComm Inc commissions 120 maintenance hours at $50 per hour. Mayan submits time records for all 120, but the authorized reviewer can presently substantiate 112\. The remaining eight hours need additional evidence.

**Claimed labor = 120 × $50 = $6,000.**

**Supported labor so far = 112 × $50 = $5,600.**

**Unresolved amount = 8 × $50 = $400.**

“Unresolved” does not mean the technician did no work. Perhaps the site record is late. Perhaps the work exceeded the approved scope. Perhaps a time entry is wrong. The reviewer should investigate the particular question rather than translate missing evidence into an accusation.

The supplier invoice is also not the technician's wage statement. Mayan may employ staff or use appropriately contracted providers; employment obligations and classification are separate matters. This essay models a business buying a contracted service, not a payroll or employment-law process.

## A work order and an acceptance decision do different jobs

The work order can identify the machine, fault and requested work. The service record describes what was done. The acceptance decision checks that evidence against the agreement.

For a fixed-fee repair, 120 hours do not necessarily establish success. The printer might still fail its agreed test. For an hourly troubleshooting engagement, failure to fix an uncertain problem does not automatically mean the hours are unbillable. The purchased promise determines the appropriate test.

I would want the decision to name the service period, site, requirement, evidence reviewed, authorized reviewer and exceptions. “Manager approved” is incomplete if we do not know whether the manager checked arithmetic, performance or both.

## Work, invoices and accounting can cross a month-end

Assume $5,600 of work was performed and meets the recognition criteria in September, while the invoice arrives in October. Under our simplified policy, September records the service expense and an accrued liability. October's invoice processing clears or reclassifies the accrual; it does not create the same expense a second time.

The unresolved $400 needs its own assessment. A payment hold and an accounting conclusion are different decisions. [Oracle's receipt-accounting documentation](https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/25c/faims/overview-of-receipt-accounting.html?ref=abundance.alloconomy.com) is an external illustration of accruals and later invoice matching, not evidence of Amazon's services accounting configuration.

## Approval to bill is not necessarily inspection

A second public example makes the distinction visible. [AWS Marketplace professional-services documentation](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-proserv-products.html?ref=abundance.alloconomy.com) describes manual and automatic payment-request approval before invoicing. An automatic approval is a configured billing event. It does not independently establish that a person inspected a deliverable.

In eComm Inc's fictional process, a billing request should link to the relevant performance evidence. If the contract permits a different approval mechanism, record that mechanism honestly. Do not rewrite it as a review that never occurred.

## What I would ask before calling the work complete

Mayan needs a service definition they can fulfill and evidence they can collect without discovering the requirements after the invoice is disputed. eComm Inc's manager needs an acceptance test appropriate to the promise. The technician needs a clear scope and a way to record exceptions.

As the eventual book buyer, I care that the printing system works. A maintenance invoice can be fully paid while the business still has a reliability problem. Keeping those two observations separate is how we notice it.

## Continue the series

Previous: [The Price After the Price](https://abundance.alloconomy.com/alloconomy/commerce-the-price-after-the-price/). Next: [Software Is a Promise Over Time](https://abundance.alloconomy.com/alloconomy/commerce-software-is-a-promise-over-time/). 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.*