How to Read Your LES and Spot Pay Errors Fast

Military pay has gotten complicated with all the abbreviations, allotment codes, and monthly fluctuations flying around. I remember sitting down one Wednesday morning — coffee going cold, laptop open — staring at my LES like it was written in a foreign language. The net pay looked roughly right. But “roughly right” isn’t the same as correct, and I learned that the hard way. That’s when I figured out how to actually read one of these things and catch errors before they turned into a twelve-month headache.

Your Leave and Earnings Statement is the single most important document you get as a servicemember. It shows up monthly in myPay. Most people glance at the bottom number and close the tab. Don’t make my mistake. Wrong BAH rates, missing COLA, TSP contributions that changed overnight, promotion adjustments that landed in the wrong pay period — these happen constantly. A $300 overpayment you don’t catch now becomes a debt the military pulls from your check later, usually at the worst possible time.

So, without further ado, let’s dive in. This covers every major LES section, what normal versus broken looks like, how to compare month-to-month, and exactly who to call when something is actually off.

What Each Section of Your LES Actually Means

Your LES breaks into six major blocks. Knowing what each one controls means you can point to the problem before you spend forty-five minutes on hold describing something you can’t quite name.

Entitlements — What You Earned

Base pay, BAH, BAS, special pays. That’s the core of this section. Base pay is your rank times time in service — straightforward. BAH depends on your duty zip code and dependent status. Claimed a spouse or kids? BAH goes up. BAS runs almost identical every month unless you’re in the field. If any of these numbers shifted from last month and you didn’t get promoted, PCS, or update your dependent status, something’s wrong. Full stop.

Deductions — What Comes Out Automatically

Federal income tax, state income tax, FICA, TSP contributions. These are the big ones. Federal withholding can move if your taxable income shifted that month. TSP should match whatever percentage you elected — I’m apparently an 8% contributor and myPay shows that consistently, but I’ve had friends whose elections jumped to 12% without warning. If yours changed and you didn’t touch it, either the system glitched or someone processed a correction meant for a different account. State tax is its own mess, especially if you moved states mid-year.

Allotments — Money Sent Elsewhere

SBP premiums, SGLI, charitable donations, loan payments — anything you authorized finance to pull automatically. SGLI charges should be consistent month to month. If you see a spike and you didn’t request more coverage, call DFAS. Same goes for any allotment you don’t recognize. Unauthorized allotments aren’t common, but they happen, and they don’t fix themselves.

Leave Balance — Your Time Off Currency

Annual leave accrued, annual leave used, current balance. It’s not cash, but it converts to cash when you separate or retire. You max out at sixty days carried into a new fiscal year — anything above that evaporates. If your balance drops by four or five days and you didn’t take leave, that’s a data entry error somewhere. Write the dates down, report it to S1, and get it corrected before it compounds.

Tax Data — Year-to-Date Withholding

Federal withholding YTD, state withholding YTD, FICA YTD. These numbers should climb steadily each month. If your year-to-date federal withholding suddenly drops or resets mid-year, your W-4 was changed. Pull up your myPay tax withholding settings immediately and verify they match what you actually submitted.

Summary — The Bottom Line

Gross pay, total deductions, total allotments, net pay. Net is what hits your bank account. Lower than expected? Scan deductions and allotments first — that’s where surprises hide almost every time.

The Most Common LES Pay Errors and Why They Happen

Probably should have opened with this section, honestly. These five errors account for most of the calls DFAS fields every month.

BAH Rate Shows Wrong Zip Code or Dependency Status

You PCS’d to a new duty station or got married, and the BAH rate didn’t update. BAH is indexed to your current duty zip code and whether you have dependents — the S1 office submits that paperwork, but a human types it in. Processing delays between your move date and when finance actually updates the system can run four to eight weeks. Still showing the old zip code in March when you moved in January? You’re short by potentially hundreds of dollars per month. Call your unit S1, ask them to verify the duty zip and dependent status in the system, and confirm it matches your current situation.

Missing COLA for Overseas Duty

COLA — Cost of Living Allowance — kicks in for expensive overseas duty locations. Japan. Germany. South Korea. If you’re stationed in Okinawa and your BAH reflects the standard rate instead of the location-adjusted rate, COLA didn’t load when your orders updated. The system is supposed to handle this automatically. It doesn’t always. COLA can run $500 to $2,000 per month depending on location, so this one stings. Contact DFAS directly with your duty location and order number ready.

TSP Deduction Jumps Without Permission

You set your TSP contribution at 8% six months ago. This month it shows 12%. TSP elections rarely change on their own — either your election was altered or a payroll adjustment meant for someone else hit your account. Log into tsp.gov directly and check your current election percentage. If it doesn’t match your LES, call the TSP helpline at 1-877-968-3778. They can pull exactly who changed it and when. Then report it to your finance office so there’s a record of the unauthorized change.

Incorrect Base Pay After Promotion

Promoted to E-5 in May. June and July LES still show E-4 base pay. Frustratingly common. The S1 submitted the promotion paperwork, but finance either missed the processing window or linked it to the wrong pay period. Always backpayable — you’ll get the difference eventually — but it takes phone calls to move. Contact your unit finance office immediately. Give them your promotion effective date and ask them to confirm it’s reflected in the system. Ask specifically when back pay will be processed so you’re not surprised.

SGLI Deduction Spikes Unexpectedly

Your SGLI premium jumped from $32 to $89 this month and you didn’t request a coverage increase. SGLI premiums are tiered by age bracket and coverage level. If you turned 30 or 35 during that pay period, your rate bracket changed automatically — that’s the system working correctly. Check your birth date against the date of the increase. If they align, you’re fine. If they don’t, either coverage was increased without your consent or a system error added coverage. Call DFAS and reference your SGLI certificate number, visible in myPay, and ask them to review your current coverage level on file.

How to Compare This Month’s LES to Last Month’s

Open both statements side by side — current month and previous month. Print them if you need to. Use myPay to pull both directly. Don’t rely on email summaries; they truncate information.

Start with gross pay. Same number? It should be unless something legitimately changed — promotion, PCS, new special pay. If gross shifted, find which line item changed. Base pay? BAH? BAS? A special pay that appeared or disappeared? Identify the specific entry before you pick up the phone.

Then go through deductions. Federal withholding, state withholding, FICA, TSP. Do they track with your gross pay? Gross held flat but federal withholding dropped 15%? Your W-4 changed. TSP dollar amount jumped even though the percentage looks the same? Your gross pay changed — verify that change is legitimate. I follow a simple rule: any unexplained change over $50 gets a phone call. That threshold has saved me three times.

Check allotments. SBP, SGLI, loan payments, charitable donations — these should be identical month to month unless you submitted a change. An allotment you don’t recognize needs to be flagged immediately. Contact whoever is listed as the recipient. If it’s SGLI-related, that’s DFAS. If it’s a loan or credit payment, call the creditor directly.

Look at the leave balance. Did you take days off this month? Balance should drop by exactly that number. No leave taken and it dropped anyway? Data entry error, almost certainly. Your unit S1 can typically fix this within a day or two once you report it with specific dates.

Finally, verify that gross minus deductions and allotments actually equals your net pay. Use a calculator — I’ve sat there doing mental math wrong more than once and convinced myself there was a problem that didn’t exist. Do the arithmetic properly before you escalate anything.

Who to Contact When You Find an Error and What to Say

Chain of contact matters here. Start at the unit level. If that stalls, move to the installation finance office. DFAS is the last resort — but also the final authority.

Step One: Your Unit S1

Dependent status updates, duty station changes, promotion effective dates — all S1 territory. Email or call them with something specific: “I found a discrepancy on my LES dated [month]. My BAH shows zip code 76544 but I’ve been stationed at Fort Cavazos since February. Can you verify the duty zip and dependent status in the system and submit a correction?” The more specific you are, the faster this moves. Give them three business days. If they don’t respond or push it back to finance, move to the next step.

Step Two: Installation Finance Office

The base finance office sees what S1 submitted and whether it was actually processed. Call the main number or walk in. Use this approach: “I submitted a correction request through my unit S1 on [date] for [specific error]. The following month’s LES still shows the discrepancy. Can you pull up the request and tell me the current status?” Ask them directly when you should expect the correction to appear on your next LES. Five business days is a reasonable turnaround. If they say it’s pending, get a name and a date.

Step Three: DFAS

Defense Finance and Accounting Service calculates the actual pay. Call 1-888-332-7411 or use the askDFAS portal inside myPay. Have your SSN, the erroneous LES date, and a plain description of the error ready before you dial. Something like: “I have a pay discrepancy on my LES dated [month]. [Describe the error clearly.] My unit S1 and the installation finance office haven’t resolved it after [timeframe]. I need you to review my account and identify the root cause.” DFAS maintains detailed records of every change — who made it, when, and why. They can also process manual corrections across multiple pay periods if needed.

How Long Pay Corrections Take and What to Do in the Meantime

Most corrections take one to three pay periods. A promotion back-pay adjustment might show up in the next cycle. A BAH rate error might need a full month to reprocess. Be patient — but call again every ten business days if you haven’t heard back. Reference your previous contact date every time. Document everything in writing where possible.

If the error was an overpayment — the military paid you more than you were owed — don’t spend that money. The government will recover it, typically by reducing a future paycheck. Spending overpayment funds you’re aware of creates legal exposure and has resulted in debt collection actions against servicemembers. If your net pay suddenly drops by a few hundred dollars and you can’t figure out why, pull the LES first. You may be repaying an overpayment from two or three cycles back that finance just caught.

If the error is an underpayment and you genuinely need that money now — more than $500 short and rent is due — talk to your commander about a hardship advance. These exist specifically for this situation. Your command can sometimes authorize an interest-free loan while DFAS processes the correction through normal channels.

Your LES is essentially a monthly contract between you and the federal government. Ten minutes of checking it now beats three months of phone calls later. Read it. Compare it. Fix it when it’s wrong.