Payroll Reporting Guide

Reviewing payroll charges on your index

HRREPT005A — Gross Earnings by Index Org is the source of truth for who got paid, from which index, when, and why. Most index managers use it to investigate reallocations — labor cost that’s been moved over from another department’s funding to theirs — and to reconcile charges they didn’t initiate. This guide focuses on that use case.

About HRREPT005A
Attribute Detail
Report ID HRREPT005A
Format WebFOCUS — Excel output
Source Banner HR / Payroll
Use case Reviewing and reconciling labor charges on an index
Frequency Run after every biweekly close; monthly minimum

Contents

  1. Why run this report
  2. Quick start in three steps
  3. Filter values, explained
  4. The output, column by column
  5. Pay types and what they mean
  6. Sequence numbers
  7. A few common earn codes
  8. Common questions
  9. Other reports and resources

Why run this report

Most of what posts to your index from payroll is exactly what you’d expect — regular wages on people you know. The charges that catch your attention are usually the ones you didn’t initiate, and the most common version of that is a reallocation: labor cost that originally hit another department’s funding and has since been moved to yours (or away from yours).

HRREPT005A explains those events. It breaks the General Ledger’s bundled labor line back into the underlying pay records — one row per employee, per pay number, per earn code, per index — so you can see what hit, when, and what kind of event it was.

The typical workflow

  1. You spot an unfamiliar charge. Usually on a Banner Finance budget query or during monthly reconciliation.
  2. You run HRREPT005A. Filter to your index and the period in question. Each row is a single pay event.
  3. You read the Pay Type column. If it says Reallocation, the dollars were moved from another dept’s funding. The Financial Manager field on the row tells you who to contact if you need the reason.

Quick start in three steps

  1. Open WebFOCUS and find HRREPT005A. Go to the MTU WebFOCUS portal, navigate to HR Reports, and select Gross Earnings by Index Org — Excel Version. The Filter Values panel opens on the left.
  2. Set your filters and run. At minimum, set the Fiscal Year, choose your Starting and Ending Period, and put your index (or partial match) in Index Like. Leave anything you don’t care about as %. Click the run button to download an Excel file.
  3. Read it row by row, or pivot it. For a quick review of a single period the file reads fine as-is. For monthly or annual summaries, drop it into an Excel PivotTable to total by employee, earn code, or pay type. (Not familiar with pivots? See Common questions.)

Filter values, explained

The Filter Values panel in WebFOCUS has seven fields. Below is a typical full-year run for a single index, with what each field controls.

Filter Values panel — fields and what they do
Field Example What it does
Fiscal Year [YYYY] 2026 MTU’s fiscal year runs July 1 through June 30. Enter the year the period ends in (FY 2026 = July 2025 through June 2026). Always four digits.
Starting Period 01-July First pay period to include. The MTU pay calendar runs from Period 01 (1st July biweekly) through Period 14 (Year End).
Ending Period 14-June Year End Last pay period to include. Together with Starting Period, these define the time window.
VP or College or Dept Like % Filters by VP area, college, or department code. Most coordinators leave this as % and filter by Index Like instead. To look up codes, run FZGCHT001A — VP, College and Department.
Index Like A11929 The workhorse filter. An index is the 6-character code (e.g. A11710, E40235) that identifies a budget bucket. Use one specific index, a partial match like E40%, or % alone for everything you have access to.
Account Code Like % Banner Finance account codes — four-character codes like P141 that distinguish regular salary from overtime from fringes. Leave as % unless you’re hunting for a specific category.
M Number Like % Filter to a single employee using their M number (e.g. M41334856). Use % for everyone or partial matches like M413%.

The output, column by column

The Excel file you download has 31 columns. Most are self-explanatory; here are the ones worth understanding before you go investigating a charge, grouped by what they tell you.

Where the charge landed

Columns identifying where a charge was posted
Column Meaning
Index / Index Title The six-character index the pay was charged to, plus its plain-English title.
Dept / Area The department and VP area the index rolls up to.
Financial Manager The person responsible for that index. If you don’t recognize a charge, this is who to ask first.
Fund / Fund Group Banner fund and its group: General, Research, Designated, Scholarship, Auxiliary, R&I, Other.
Acct / Acct Pool Account code and its rollup pool (e.g. P141 in pool P006).

Who got paid

Columns identifying the employee
Column Meaning
ID Employee M number.
Last / First Employee name.
POSN / SUFF Position number and suffix. Distinguishes multiple jobs the same person may hold.
Group / ECLS Bargaining/employee group and the finer employee class code. For descriptions of every ECLS code, run HRINST003B — ECLS Codes and Descriptions.

When and what kind

Columns identifying when the pay event occurred and what type it was
Column Meaning
FY / PD Fiscal year and period (01–14).
PayNo Sequential pay number within the calendar year.
SeqNo Important. 0 = the original pay run for that PayNo. 1+ = adjustments. See Sequence numbers.
Pay Type Original, Adjustment, Manual, Voided, Reallocation, Other. This is the column that tells you what kind of event the row represents. See Pay types.
Earn Code The category of pay — regular, overtime, vacation, sick, etc. See Common earn codes.
HOURS Hours associated with the pay event.
AMOUNT The dollar amount charged to the index for this row. This is the field you’re almost always summing.

Pay types and what they mean

The Pay Type column tells you the nature of the row — was it the original paycheck, or something that came after to fix, void, or move it? Six values are possible. Reallocation is the one most coordinators are trying to track down, so it’s first below.

Reallocation (Void and Reallocation)

The employee’s pay does not change. Reallocation simply moves the funding source — the original index is credited (negative amount), and a different index is charged (positive amount), so the total is zero across the pair. Used when the cost was originally posted to the wrong index and needs to land somewhere else.

This is the most common “weird charge on my index” you’ll investigate. If a Reallocation puts money onto your index, another department just sent labor cost your way; if it takes money off, your index has been correctly credited. The Financial Manager on the row is who to contact for the reason.

Original (SeqNo 0)

The regular biweekly payroll. This is what hit the employee’s bank account on payday for the listed PayNo. The vast majority of rows in any healthy report are Original. If you’re trying to answer “what did this person earn this period,” sum the Originals.

Adjustment (SeqNo 1+)

An after-the-fact correction to a pay event that already exists. The original pay record is kept, and the Adjustment row records the change — positive or negative — that needed to be made. Adjustments often come in pairs, or stack on the same PayNo as the SeqNo climbs (1, then 2, then 3).

Manual (SeqNo 1+)

A check that was not processed through the normal biweekly cycle and where there was no original pay event to adjust. Used when something has to be paid outside the cycle entirely — typically to make a person whole when they were missed in BW.

Voided (Void and Reissue)

A previously issued check that was canceled. The original BW row still appears in the report; the Voided row backs it out. If a corrected check was reissued in its place, you’ll see new rows under Pay Type Other carrying the replacement.

Other (Reissued Pay)

On this report, Other means reissued pay. When a paycheck is voided and then reissued (rather than void-and-reallocated), the reissue posts under Pay Type Other. Treat it as the “replacement check” — it should be paired with a Voided row that canceled the original.

Sequence numbers

SeqNo is small but tells you a lot. Every pay event for a person within a given PayNo gets a sequence number:

SeqNo values and what they mean
SeqNo What it means
0 The regular biweekly pay run. Every Original row has SeqNo 0.
1 through 9 Adjustments. The first correction posted against that PayNo gets SeqNo 1, the next gets 2, and so on. Voids, Reallocations, Adjustments, Manuals, and Others all get a non-zero sequence number.

Mental shortcut while scanning: SeqNo 0 = the paycheck. Anything else = correction activity.

A few common earn codes

The Earn Code column tells you what kind of pay each row is. MTU uses roughly a hundred earn codes in total, but five of them account for the bulk of what you’ll see on a regular biweekly:

The five most common earn codes
Code Description What it captures
001 Regular Rate Standard wages — the row you’ll see most often. Hourly people show their actual hours; salaried people show the standard 80-hour biweekly.
200 Overtime Overtime hours paid under MTU’s contract and policy rules.
300 Holiday Pay Pay for an observed university holiday.
400 Vacation Time Vacation hours used.
500 Sick Time Sick hours used.

For every other earn code — allowances, leaves, terminations, FLSA overtime, deferred pay, medical leave, and so on — run HRPAYR022E — Payroll Earn Codes with Description. It gives you the code and a one-line description for the full list.

Common questions

I’m seeing a charge with a name I don’t recognize on my index. Now what?

Check the Pay Type column first. If it’s a Reallocation, another department moved that cost onto your index — the reason is on their side, and the Financial Manager on the row is who to contact. If it’s Original or Adjustment, the labor was actively assigned to your index in HR; the Financial Manager is still the first point of contact, or escalate to Payroll Services if you believe the assignment was wrong.

Why is the total on this report different from what I see on my Banner Finance budget query?

A few common reasons: (1) timing — the report shows pay events as of when they posted in HR/Payroll, not necessarily when they posted to the GL; (2) accounts — your budget query may be filtering to one account code while this report shows all of them; (3) fringes — this report shows gross earnings, not the loaded labor cost, so any fringe charges hitting your index won’t appear here.

I see hours but no dollars (or dollars but no hours). Is that an error?

Usually no. Allowances and bonuses are typically posted with a dollar amount and 1 hour — not zero. If the employee has multiple default indexes set up in their labor distribution, that single hour will be split across those indexes according to their default split percentages. So instead of one row at 1 hour you may see, for example, two rows at 0.40 and 0.60 hours that add up to 1, each charging its share of the dollars to the corresponding index. If a regular-pay row (001) shows hours without dollars or vice versa, that’s worth a question to Payroll.

What’s the difference between Index Org and TS Org?

The Index Org is the org that owns the index the cost was charged to — i.e., who’s paying. The TS Org is the org that approved the timesheet — i.e., who supervised the work. They’re often the same, but they diverge when someone is doing work for one department on funding from another.

There’s a Workers Comp (740) or STD (820) charge on my index. Can I move it off?

Not on your own. These codes are set up by the Benefits Office when an employee is on a medical leave or a workers’ comp claim. If you think the charge is on the wrong index, contact Benefits — they own the configuration and they’ll move it if it’s incorrect.

What about deferred pay (800 / 810)?

Same idea — HR sets these up because they directly affect the employee’s BW job earnings record. If a faculty member’s 9-over-12 schedule isn’t right, that’s an HR ticket, not something a coordinator can adjust through the normal payroll cycle.

How do I summarize all these rows?

The report is line-level — one row per pay event. To turn it into something readable (totals by employee, by pay period, by earn code, by pay type), drop it into an Excel PivotTable. If you’re not familiar with pivots, a quick search for “excel pivot table tutorial” on YouTube or Google will get you going in 10–15 minutes; Microsoft also publishes a tutorial at support.microsoft.com. Pivot tables are a general Excel skill, not specific to this report — once you have them, you can use them on any data set.

How often should I be running this?

At minimum, after every biweekly close so things don’t pile up. Many coordinators run it on the first business day after each BW, filtered to just that pay period, and again at month-end for the full month. If you manage research grants where labor distribution accuracy matters, weekly is reasonable.

The file is huge and Excel is choking. Help.

You probably ran it too broadly. Narrow the Index Like field, or shorten the period range (e.g. one month at a time), and run multiple smaller files. If you genuinely need a year of activity for a whole college, save the file as .xlsb after opening it — the binary format is much faster for big pivot work.

Can I see prior-year data?

Yes — just change the Fiscal Year in the filter. Banner retains payroll history for many years; the report runs against whatever year you specify.

Other reports and resources

This guide intentionally sticks to the most common reason coordinators run HRREPT005A. When you need information that lives elsewhere — the full earn-code list, the ECLS descriptions, the department hierarchy, OBBBA tax details, or pivot-table training — run the report or visit the page below. If you don’t have access to one of these reports, contact FSO or HR Services.

Other reports and resources referenced in this guide
Resource What it’s for
HRPAYR022E — Payroll Earn Codes with Description The full list of MTU earn codes with one-line descriptions. Run this when you see a code on HRREPT005A that isn’t one of the five common ones above.
HRINST003B — ECLS Codes and Descriptions The full list of employee classification codes (the ECLS column on HRREPT005A) and what each one means — faculty, research, AFSCME, UAW, student variants, and the rest.
FZGCHT001A — VP, College and Department The current VP / college / department hierarchy with department chairs and coordinators. Run this when you need a code to use in the VP or College or Dept Like filter, or to find the right contact for a department you don’t recognize.
FSO Payroll — One Big Beautiful Bill Act Background and FAQ for the federal No Tax on Overtime provision and the FLSA OT earn codes (250, 260, 270). Useful context if you’re asked why those codes started appearing more frequently on your index. mtu.edu/fso/financial/payroll/one-big-beautiful-bill-act/
Excel pivot tables — external tutorials Pivots are a general Excel skill, not specific to HRREPT005A. Search “excel pivot table tutorial” on YouTube for free 10–15 minute walkthroughs, or use Microsoft’s own guide at support.microsoft.com.
FSO Payroll Services Authoritative for payroll-cycle questions, manual checks, void/reissue, and reallocation requests. mtu.edu/fso/financial/payroll/
HR and Benefits Contact HR for ECLS, position, job-record, and deferred-pay (800/810) questions. Contact Benefits for medical leave, workers comp (740), and short-term disability (820/821) entries.