CPA and Bookkeeping Plano Alternative.The invoice left transit off.

Item setups often carry a single tax code. That is enough when a city has one local piece. It is not enough when the local bill is a city piece plus a transit piece and the code you inherited only knows the first. The invoice still prints a tax line. The line is just short. Nobody at the counter feels the shortage, because the customer was charged whatever the code said to charge.

The pain shows up later, in the liability account, or in the absence of one. You remit what you collected. If you collected only the city piece, the transit piece was never in the drawer, and it was never in sales either. That is a different problem from collecting both and then calling both a sale. We name which problem you have before we propose a fix. They do not share a journal entry.

A good month posts the sale at the pre-tax amount, posts the city piece to its holding account, and posts the transit piece beside it. Some files use one holding account and a memo. Either shape works if the report can still see both pieces. A single bucket with no memo is how October becomes a guessing game.

Bank feeds are loyal to the deposit and indifferent to your chart. A batch arrives. The feed suggests income. If you accept the suggestion, you have just recorded tax as revenue for the second time, or for the first time if the invoice never split it. Reconciliation can still go green. Green means the totals match. It does not mean the accounts mean what you think.

We treat a green reconciliation as the start of the question, not the end. Which accounts absorbed the batch? If income absorbed tax, the month is not finished, no matter what the software's check mark says. The same test applies to a processor fee netted inside the deposit. Net deposits hide two stories. We want both stories on the page.

Parker Road station is the north end of the Red Line, near the highway between Parker Road and Park Boulevard. We like knowing the line has a last stop, the way you do. A train that stops does not file anything. The code on the invoice does. A tidy station and a tidy reconciliation can both be true while the holding account is empty.

Changing the item code today fixes tomorrow's invoices. It does not rewrite March. We keep those as two tasks with two prices if the old months are many. You should hear that split before you agree, because a surprise rebuild is how trust dies.

Going forward, we want the code named in words a new employee can read. "Local" is not a name. The city piece and the transit piece are names. If you sell in more than one city, the items or the locations have to know which counter they are standing in. A single code for a company that delivers across a line will be wrong on half its tickets, and the wrong half will not announce itself.

Payday setup does not repair an invoice code, and an invoice code does not set up payday. If both are open, we sequence them. Usually the code comes first, because a payroll journal posted into a chart that calls tax a sale makes the next close louder. Once the provider account is ready, the clicks on payday stay yours.

A useful week has three deposits and three explanations. The first is a card batch that includes tax. The second is a check from a customer who paid an old invoice. The third is a processor deposit that already subtracted a fee. If all three land in one income account, the month can still tie to the bank and still be wrong. We write the three explanations in the month file in plain words, because a future close will not remember which deposit was the fee.

The batch date and the bank date often disagree by a day. A Thursday sale can post on Friday. The sale stays in the month the customer paid, and the holding accounts stay with that sale. Moving the income to Friday just to mirror the bank date is how a quarter picks up a day that belonged to the quarter before it. We match the bank with a timing entry when the cash has not landed, and we leave the sale where it happened.

If your items were built with one tax code and you now sell in two cities, the forward fix is a second code, not a smarter memo. Memos do not survive most sales tax exports. Amounts do. We would rather see two codes with boring names than one code with a paragraph nobody's report can read. Bring the item list as an export if you have it. A screenshot of one invoice helps, and the deposit that invoice flowed into helps more. Those two usually show whether the field is short or whether the field is right and the deposit coding is the whole problem.