CPA and Bookkeeping Plano Alternative.A neighbor rate on a local sale.
Picture one ticket. The counter never left the city. The code thinks it did.
Walk through a ticket.
The ticket, as a hypothetical
This is not a client and not your receipt. A customer pays 108.25 at a counter inside the city for a 100 dollar pre-tax sale. The right pack is 6.25 to the state, 1 to the city, and 1 to transit. The file, copied from Frisco, charges a rate that omits the transit piece. Two things might have happened, and they are not the same. Either the customer was charged 108.25 anyway by habit and the software buried the extra dollar in sales, or the customer was charged 107.25 and the transit dollar was never collected.
In the first case you are holding a dollar that is not income. In the second case you may owe a dollar you do not have. We ask which case the invoice shows before we journal anything. Looking at the customer's copy, or the invoice PDF, answers it. Guessing from the deposit alone does not.
Multiply that ticket by a year of Saturdays and the dollar becomes a number large enough to change owner pay, a loan conversation, and the May revenue figure. The emotion of it is not drama. It is the sour feeling of a year that looked better in June than it was. We would rather you feel that in a closed month than in a letter.
The reclass, in words
For the first case, income comes down by the transit dollars and a holding account goes up. The bank is untouched. Reconciliation stays green if it was green, which surprises people who think a reclass must "break the bank." It breaks a false story, not the cash. Then the next return remits what was collected, including the piece that had been hiding in sales.
For the second case, you have a compliance hole. The journal might still record a liability you now owe, and income might not change at all, because you never collected the dollar. Paying it later hurts, and pretending you collected it would invent cash. We will not invent cash. We will lay the hole next to the months it belongs to so you can decide, with the actual rule in front of you, how to file.
Neither repair needs a new set of books. We will not keep a second set of books so a lender sees a prettier year. One set, honest, is the product. If a lender wants a different presentation, that is a report built from the same set, not a quiet rewrite.
What we want on the table
One invoice PDF, one deposit, and the tax code screen. Three artifacts. If those three disagree, we have found the work. If they agree, we say so and we look elsewhere, because not every ache is a code.
Frisco, McKinney, and Allen remain perfectly good cities to sell in. A sale that is truly sourced there should wear their code, transit piece absent, and our pack should know the difference ticket by ticket. The failure mode is not "having a neighbor." The failure mode is one code for two maps. Delivery across the line is a sourcing question we will not answer with a folk rule. Tell us on the first call if the truck crosses a city line. The counter story and the delivery story should not share a paragraph in your file, and they will not share one in our close.
After the ticket makes sense, the month can finish, payday can be set up on its own track, and the return can follow. That order is the whole offer. It is also the order that keeps April from becoming an archaeological dig.
The Saturday after the repair
Once the code is the city's pack, the next Saturday is boring in the best way. The ticket prints the full pack on a 100 dollar sale, the deposit matches the batch, and nobody has to decide whether the extra dollar was income. Boredom is the product. The sour feeling from a proud June goes away because June's profit is no longer hosting tax you already collected from the customer.
Owner pay is where the repair shows up in ordinary life. If draws have been coming from a profit number that included transit dollars, those draws were spending money that belongs in a holding account. We do not claw a past draw back through guilt. We reset the next draw from the repaired profit and we show the difference on one line, so a later reader of the year sees the change instead of a silent restatement.
A smaller ticket makes the same point for a counter that rings all day. Forty dollars before tax, at the full pack, collects three dollars and thirty cents. At the neighbor rate that omits transit, forty cents of that never had a home. A Saturday of those tickets stops being a rounding story. We still will not invent cash you did not collect. We will count the tickets so the hole has a size you can decide about.
If the software lets you change the code on future invoices without touching history, make that future change the same day we agree on it. History stays in its own journal, dated to the months it belongs to. A settings change mixed with a backdated invoice edit turns the trail into a novel. We want a settings note and a journal, two different objects, both readable when October comes back around.
Bring a sample ticket.
A PDF of one invoice is enough to start. Do not send a full backup.
You will be talking to the Steven Palmieri practice.