In this article
A useful pay-statement review separates what the record displays from what you think caused it. Start with the statement period, the specific entry and the question that remains. For the official access route, the San Francisco Controller’s public paystub page links City employees to the SF Employee Portal and distinguishes older statement access. Follow current official instructions, not a copied sign-in screen. This article is a reading method, not a calculation of what you should have been paid.
Choose the record you are actually reviewing
A payment date, the dates covered by a statement and the date you performed particular work are different reference points. Before comparing anything, write those labels in your own notes exactly as the record presents them. A complaint that begins “last month’s pay is wrong” can leave the recipient guessing which statement you mean. A question tied to one statement and one entry gives the payroll team a place to start.
Do not make a large personal archive merely because you are investigating one item. Use the approved workplace location and keep only the material needed for the question. If you already have an authorized copy, preserve it unchanged. Put your explanation in a separate note rather than altering the original. Our document-hygiene guide considers how to keep a useful reference without spreading a whole employment record.
Observation, expectation and explanation
These three categories are easy to blend together. An observation describes a visible label or amount. An expectation identifies what you thought would appear and where that expectation came from. An explanation proposes why the difference happened. Your first two categories may be well supported while the third remains unknown. That is a good reason to ask, not a reason to invent a cause.
- Observation: identify the line, statement and visible difference.
- Expectation: identify the relevant approved schedule, earlier explanation or comparison record, if you are authorized to use it.
- Question: ask which information or timing would explain the difference.
A confident label can send a request in the wrong direction. Calling an unfamiliar item a tax error, a missing benefit or an unauthorized deduction is a conclusion. If you do not know its meaning, say that. You can still be direct about the impact and ask for timely review. Precision does not require minimizing a concern.
Compare like with like
Two deposits are not necessarily a useful comparison on their own. If you compare statements, make sure you are comparing the same kind of value: a current-period amount with another current-period amount, for example, rather than a total accumulated over a longer span. Preserve the printed labels. When the meaning of a label is unclear, ask for its definition before building an elaborate spreadsheet around it.
Then ask whether the circumstances you are comparing were genuinely similar. Were the covered dates the same length? Was one record associated with an earlier adjustment? Did you recently change something that you already know is relevant? Treat these as questions for the record owner, not automatic explanations. A plausible story is not evidence that a line is correct.
It can help to isolate one difference at a time. Start with the item that prompted your concern, then expand only if the authorized reviewer needs more context. Sending years of statements can bury the relevant entry and expose information that nobody needs to resolve the immediate question.
A hypothetical question that is easier to answer
Hypothetical example: an employee notices that a line labeled with a familiar code differs between two statements. Their initial draft says, “The system removed my pay.” Their revised note says, “The entry with this label differs between the two identified statements. I expected it to reflect the approved record I have referenced. Could you explain what period and adjustment this line represents, and whether you need anything from me to review it?”
The revised version does not assume that the employee is mistaken or that the system is right. It exposes the uncertainty. The payroll team can explain the label, identify a different period, request an authorized supporting record or begin a correction. None of those outcomes is guaranteed by the wording; the benefit is that the question can be understood without reconstructing the employee’s reasoning.
Use the correct channel for the evidence
Ask your department’s established payroll contact how to provide the relevant information. Do not paste a statement into a public chat, send it to an independent publication or assume an unfamiliar email address is a payroll inbox. A short initial description may be enough to identify the responsible team. If a document is needed, confirm the approved submission route and the parts required before sending it.
Keep the message and the attachment distinct in your thinking. The message explains the question. The attachment, when requested and appropriately shared, supports it. More attachments do not necessarily make the question clearer. The safe support brief offers a structure for describing an issue without leading with a complete personal record.
Know what would count as resolution
A reply saying that a request has been received is not an explanation of the pay entry. A statement that an adjustment is being considered is not evidence that it has appeared in a later record. Ask what the next observable step will be and which official record or response will confirm it. Keep those expectations in the same place as your original question.
If you are told to check a later statement, note the instruction without turning it into a promise of a particular result. When that record becomes available, compare the identified entry and the explanation you received. If something still does not match, respond with the remaining difference rather than restarting the entire story.
Finish with a compact change record: the question, the responsible contact, the explanation or action, and the evidence that closed it. That record is more useful than a folder full of unlabeled screenshots. It preserves what you learned while leaving payroll decisions with the people authorized to make them.
Sources & scope
Public sources checked October 27, 2026. Sources establish only the limited public facts described above. The working methods and labeled hypothetical examples are original editorial analysis, not official City procedures or individual advice.