A shop system can send the day's work as one summary or as the tickets themselves. The summary is shorter. It is also the version that hides the repair order. Once the repair order is gone, a payment that arrives next week has nothing specific to close, and two similar jobs become one lump that nobody can split.
Individual entries keep the ticket number in the file. The receivable is created when that ticket is sent to accounts receivable. The payment later closes that receivable, not a vague daily total. If the only record is the lump, we ask the shop system for the lines again rather than retyping the day from memory.
Retyping the day makes a second job.
Comparing the three shop reports to the file is the safe path. The end-of-day parts report, parts used, and parts purchased should be read against what the books already hold. Typing each job in by hand, on top of a batch that already arrived, duplicates the work. A duplicated job becomes a second receivable and a second sale.
The comparison is slower for an afternoon and faster for a year. A difference gets a mark and a date. It does not get a fresh invoice invented to force the totals together. If the batch and the file disagree by a core or by a supplies charge, that disagreement is the next page of the cleanup, not a reason to start over.
A payment closes what the ticket opened.
Cash in the drawer, a card batch, and a charge account are three different arrivals. The drawer has money in, money out, and adjustments that a tired close can book as income. An adjustment that makes the drawer match is not a repair. It needs its own line so the next morning does not inherit a fake ticket.
A customer payment closes the receivable the repair order created. It does not create income a second time. If the ticket never reached accounts receivable, the payment is sitting on a job the file cannot see. We look for that missing send before we look for a missing customer.
Name the months already filed.
Before a second send, name the months that already left. A batch that reaches into a filed period changes numbers a return may already rely on. We stop there and say so. Park the fix in the month that is still open, with a note that names the older day. Leave the filed month closed even when a report would look neater if you reopened it.
Changing a filed period is a return question. It is not a button on a cleanup. If the only copy of a ticket lives in that closed month and the batch was wrong, the conversation is about the return, and the books wait. Relief belongs in the month that is still open.
Name the batch that hid a job.
Say which send swallowed a repair order.
You will be talking to the Steven Palmieri practice.
