In the OpenStax accounting example, a business called CBS sells 20 desktop computers to a customer on credit on July 7. The books record the sale that day. Accounts Receivable goes up, and Sales goes up by the same amount: $15,000, which is $750 for each computer times 20.
The textbook's product listing shows why the unit matters. It lists prices for packages and individual units. Read a price as the amount for each unit, multiply by the quantity, and you have the amount your invoice has to carry.
The same OpenStax page includes a second sale that makes a related point. "On July 1, CBS sells 10 electronic hardware packages to a customer at a sales price of $1,200 each."
Translate that to your work. The sale date is the day your office commits the customer to a bill. For a field-service firm, that is usually the day the job is finished and the invoice goes out, or the day the customer signs off. Pick one rule, write it in your procedures, and do not leave it to whoever is at the desk that day.
The sale date matters in two places. The invoice should carry it, and the books should use it. If the invoice says one day and the books say another, the customer will ask which is right, and your staff will spend time digging through paperwork that should have been settled on day one.
Keep the sale date fixed. If an invoice was wrong, issue a correction, note what changed and why, and leave the original visible. Changing an old date to make an aging report look better produces a record nobody can trust.