How Do You Receive an Hour of Work?

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.

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 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 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 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. Next: Software Is a Promise Over Time. Return to the introduction and cheat sheet.

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.