You're working through an 1120S in Lacerte. You get to Deductions, you find a field for compensation of officers, you type the number in, and next to it there's a small letter O.
That O is the whole story. It means override, and it means you just typed the number in the wrong place.
What the O actually tells you
Lacerte marks a field with O when the figure on that line is supposed to be calculated or carried in from somewhere else. The field still accepts what you type. The form will print your number. Nothing errors out.
What you lose is everything the software would otherwise do with it. An override is a value stamped onto a form. A real entry is a value that flows, feeds related schedules, and can be traced back to what produced it.
The habit worth building is simple. If you see the O, stop typing and go find where the number belongs.
Where officer compensation actually goes
Under Officer Information, on the same screen where you enter each officer's name, social security number, percentage of time devoted to the business, and percentage of stock owned. There's a compensation column right there.
The logic makes sense once you see it. Officer compensation isn't one number on an S corp return, it's a number per officer, and the return wants it attached to the person. Enter it on the officer screen and it flows to the deduction line on page 1 and populates the officer detail when that's required. Enter it as an override on the deduction line and you have a total with nobody behind it.
Do it while you're setting up the officer. That's the practical advice from anyone who has done a few of these. If you skip past it thinking you'll come back, you end up hunting for it later, and hunting for it later is exactly what leads people to type it into the Deductions screen.
Why "jump to input" sends you to the wrong field
Here's the part that catches people, and it's not their fault.
Lacerte lets you look at a form, right click a line, and jump to the input that feeds it. It's a genuinely good feature and it works most of the time. But on compensation of officers it drops you on the Deductions screen, at the override field, because technically that field does feed the line.
So the software's own navigation aid points at the trap. You follow it, you land on a field marked O, and unless you know what the O means, you type the number and move on.
Same when you use the search box. It'll find you a place to put the number. It will not always find you the right place.
The other 1120S fields with the same problem
Once you know the pattern you start noticing it everywhere on an S corp return.
Depreciation and amortization. There's an override on the Deductions screen. Don't use it. Depreciation belongs on the depreciation screen, asset by asset, where you pick the form it flows to, the category, the date placed in service, the cost, and the method. Enter it there and you get a depreciation schedule, prior year figures that carry forward, and the ability to mark an asset as sold so the disposition lands on the return correctly. Override the deduction line instead and you get a number, and next year you get to work out where it came from.
Retained earnings on Schedule L. Also an override, because the ending figure is built from the beginning balance plus income less distributions. If it isn't what you expect, the problem is upstream.
Percentage of stock owned. Calculated from the stock ownership screen, where you enter shares at the beginning and end of the year. Type over the percentage and you've hidden a disagreement between the two rather than resolved it.
Different fields, same rule. The O is telling you something.
Splitting the wages account in the first place
None of the above helps if you don't know what the officer compensation number is, and the client's books usually won't tell you. Most small S corps run payroll through a single salaries and wages account.
The split comes from the W-2s and the operating agreement. The W-2s say what each person was paid, the agreement says which of those people are officers or shareholders. If the wages account holds $30,000 and the shareholder's W-2 shows $20,000, officer compensation is $20,000 and salaries and wages is $10,000. Ask for the W-3 too, since it totals every W-2 the company filed and gives you something to reconcile the books against before you start.
That's a decision, and it has to be made every year, usually by whoever happens to be preparing the return.
Where this lands in a workpaper instead
Ledger IQ handles the part that happens before Lacerte opens. You upload the trial balance the client sent, and each account is mapped to an actual line on the return, with compensation of officers and salaries and wages as separate destinations. The split gets recorded rather than remembered, and next year it's already there, so a different preparer is reviewing a decision instead of reconstructing it.
If the books genuinely carry payroll in one account, the entry that breaks it apart posts against the trial balance with a reference, shows up in the adjustments column of the Working Trial Balance, and comes out in a journal entry report you can send to the bookkeeper so next year's books arrive already split.
The Tax Lines view then shows the return the way the return is organized, so compensation of officers appears as its own line with the accounts feeding it listed underneath. When you get to Lacerte, you already know which number goes on which line, which means you're less likely to be poking around a Deductions screen wondering why there's an O next to the field.
How the split gets recorded in Ledger IQ
- Upload the trial balance with payroll still sitting in one account.
- Post an adjusting entry to break it apart using the W-2 figures, with a reference attached so the entry is traceable.
- Map officer compensation and salaries and wages to separate return lines. The split becomes a recorded decision rather than something the next preparer has to work out again.
- Move the shareholder health insurance out of employee benefits into officer compensation with a second entry.
- Check the Tax Lines view, which shows the return organized the way the return is organized, with the accounts feeding each line underneath it.
- Send the bookkeeper the journal entry report so next year the books come in already split.
- Export the Lacerte file. You arrive at the Officer Information screen already knowing the number, which is how you avoid ending up on a Deductions field marked with an O.
Supports Forms 1065, 1120S and 1120, with exports for Drake, Lacerte and UltraTax CS. The walkthrough is in the Lacerte resource guide, and it is free during early access, so you can start at portal.ledgeriq.ai and run this on a live client without a credit card.