Skip forward into hiring notes
RosterAcorn

Minnesota employer records: 4 retention steps

Minnesota employers generally must keep required wage records for three years, with worksite storage or an arrangement that allows compliance within 72 hours.

Key takeaways

  • Label files by employee and year.
  • Keep a retention calendar for each record category.
  • Give a backup access to the written retrieval process.
  • Run a timed drill and fix any access gaps.

Timecards, pay stubs, hiring files and schedules all count as records in the everyday sense. The harder questions are how long you have to hold them, where they have to be kept, and how fast you have to produce them when a state official asks.

This post walks through the Minnesota rule in Minnesota Statutes section 177.30. That section sets out the records an employer must keep and the commissioner's power to inspect them. It answers the three questions small employers ask first: how long to keep records, how fast to produce them, and what a shortfall can cost. Where a number, date or deadline matters, I quote the statute directly. Read the full section yourself before you change any process, because a blog post can only cover the parts most employers need first.

How long do Minnesota employers have to keep records?

The general rule is three years. The statute says the records "must be kept for three years in the premises where an employee works," and that sentence is the starting point for most small employers ( Minnesota Statutes section 177.30).

The same sentence carries two exceptions. The first names each employer subject to sections 177.41 to 177.44. The second names work on public works projects funded in whole or in part with state funds. For those projects, the statute says the three years run "after the contracting authority has made final payment on the public works project." That changes the date you count from. The clock on those projects starts after final payment, not when the employee's work ended.

Confirm the start date that applies to your records before setting a destruction date. Document that basis in your retention policy, and apply it the same way to every file in that category. Keeping a file longer than the minimum costs some storage space. Destroying one too early can leave you unable to show what was paid or hired. When the start date is unclear, keep the file until you have worked out the answer for your situation.

Where do the records have to be kept?

Employers can keep records at the worksite or arrange storage that meets the statutory response window. The records must be "either kept at the place where employees are working or kept in a manner that allows the employer to comply with this paragraph within 72 hours" ( Minnesota Statutes section 177.30).

Keeping records at the worksite is the simplest choice for a shop, a restaurant or a job site office. The second option gives you room to store records somewhere else, such as a home office, an accountant's office or a cloud account, as long as your setup lets you comply within 72 hours. Test the storage method you use with an actual retrieval drill. It sets a test of speed: can you get the records in front of the commissioner in time? A setup that fails that test does not meet the rule, even if the files exist somewhere in your business.

Illustrative example: test access to off-site files

An off-site folder holds 10 pay records for a retrieval drill. The backup retrieves all 10, checks that the copies are complete, and logs how long the task took. If access depends on the usual keeper being available, fix that dependency and test again. This is an illustrative access check, not a separate legal deadline.

The quoted language is about location and speed. Test how quickly you can retrieve records in whichever format you use. If you move files to a new system, run the same test again, because the old answer no longer holds.

How fast do I have to produce records when asked?

Required records must be readily available for inspection upon demand. The statute says records "must be readily available for inspection by the commissioner upon demand" ( Minnesota Statutes section 177.30). That is the standard to plan around. When the commissioner asks, the records should be ready to show, not something you begin looking for.

The practical test is simple. Pick a former employee and a recent pay period, then time how long it takes to pull the full set of records for that person: the hiring file, the pay records, the timekeeping and any schedules. Ask someone other than your usual keeper of the files to do it. If off-site retrieval takes longer than 72 hours, or worksite records are not readily available for inspection upon demand, fix the access gap. Fix it now, while the only cost is an internal drill rather than an inspection.

For records you keep off-site, build a staging step into your process. Keep an index that says where each category lives and how to get a copy. When a request comes in, the person handling it should be able to start copying from the index on the same day, instead of first working out which system holds the file. A short index costs little to maintain, and it removes the search step, which is often where the time goes.

When you produce copies, make them complete and label each one with the date it was made. A partial copy with no date invites questions about what was left out and when it was pulled.

What happens if my records fall short?

The commissioner may fine an employer "up to $1,000 for each failure to maintain records as required by this section, and up to $5,000 for each repeated failure" ( Minnesota Statutes section 177.30).

Two parts of that sentence shape your planning. First, the amount applies to each failure, so the total depends on how many failures the commissioner finds. Treat both a single missing file and a run of missing files as problems to investigate and correct. Second, the higher ceiling applies to repeated failures. The cap for a repeat is five times the cap for a first failure, which means a second problem can carry a far higher ceiling than the first one did.

The practical lesson is that a records gap is easier to handle when your own drill finds it rather than an inspector. Once a gap has come up, the question should change from "how do we find the file" to "what in our process let this happen." The fix is what keeps the next gap from becoming a repeat.

Can a records fine be added to other penalties?

Yes. The statute says the penalty "is in addition to any penalties provided under section 177.32, subdivision 1" ( Minnesota Statutes section 177.30).

Read section 177.32, subdivision 1 before you estimate the total exposure from one violation. The records fine on its own shows only part of the picture, and the total cost of a problem depends on what else the statute attaches to the same conduct.

How does the commissioner decide how big a fine should be?

The commissioner must consider business size and the gravity of the violation. The statute says that in determining a civil penalty, "the appropriateness of such penalty to the size of the employer's business and the gravity of the violation shall be considered" ( Minnesota Statutes section 177.30). For a small employer, this is the part of the penalty rules that speaks directly to your size.

Two limits apply. The size factor is one of the two considerations the statute names, and it works within the dollar amounts quoted above rather than replacing them. A five-person shop and a fifty-person company can both face the same ceiling, but the size factor asks the commissioner to consider the size of the business. Gravity refers to how serious the violation was. Do not assume a particular records problem will produce a particular fine.

What you control is the evidence you can show. A written retention policy, a dated log of how you handled past requests, and quick corrections of errors give your team a record of how it handled the gap. Those records of your process are themselves a kind of record worth keeping.

What happens if the records do not show what was owed?

The commissioner may determine wages due using available evidence. The statute says that when records "do not provide sufficient information to determine the exact amount of back wages due an employee, the commissioner may make a determination of wages due based on available evidence" ( Minnesota Statutes section 177.30).

That sentence explains why records matter beyond the fine. If your records are thin, the commissioner does not need to stop. Incomplete records can leave you unable to support your own calculation of wages due.

The lesson is to keep records complete enough to support an exact figure. A pay record that shows hours, rates and payments for each period leaves little room for an estimate. A record that shows only a monthly total leaves more room for argument about what was earned in each period. Completeness helps avoid having to reconstruct the numbers later. For a related review of timekeeping gaps, use the time clock setup checks.

What else does the statute ask employers to keep?

The commissioner may require other information needed to enforce the named sections. The statute's list includes an item numbered (8), which allows the commissioner to require "other information the commissioner finds necessary and appropriate to enforce sections 177.21 to 177.435" ( Minnesota Statutes section 177.30).

Your process should therefore include a way to respond to requests outside your usual files, rather than assuming your standard folder covers every request.

In practice, that means keeping a short list of where unusual records might sit, such as a manager's notes, a supplier's invoice or a schedule change sent by text. You will not know in advance which of these an inspector wants, but you can make sure you know where to look.

What about hiring and personnel files?

Check the requirements for each hiring or personnel record before assigning its retention period. Read the full section and decide how to treat those files in your retention policy. Keep them under the same labeling and calendar as your pay records, so you are not searching two systems when a request arrives. Use the recruiting records audit to organize a separate review of employer files.

Federal tax and immigration records follow their own rules and are outside this post. A Minnesota rule should not stand in for a federal one, and a federal rule should not decide the Minnesota question. If you keep the same file for more than one purpose, check each set of rules separately before you decide when that file can go.

How do I build a retention process that holds up?

Pick one place where every record lives, and write down the start date and keep period for each category. A written policy lets anyone on your team know where files are and when they can be destroyed, so the process does not depend on one person's memory.

Build the process in four parts. Label every file by employee and year. Keep a retention calendar that marks the earliest date each category may be destroyed, based on the applicable start date. Assign one person to handle requests, with a backup who knows the steps. Run a timed retrieval drill on a regular schedule and write down the result, so you can see whether the time is getting better or worse.

Before anything is destroyed, check the calendar and confirm that no open request or dispute covers the files. A file that has passed its date is still needed if an open matter depends on it, so the calendar is a reminder to check, not permission to act. Keep a short log of each destruction too, listing the category, the date and who approved it. That log gives you a record of how the process actually ran.

Today, ask your backup to retrieve a former employee's pay records, time the attempt, and write down any access problem to fix.

Records questions

Who answers an inspector's request?

Assign one person to handle requests from the commissioner, and make sure a second person can do the same work. That person needs the written policy, the calendar and the index of where each category lives. Give the backup a real turn at the job, not just a folder to read, so the backup can act when the main person is out. Walk the backup through a practice request using the drill from earlier, so the first inspector request they handle is not the first time they have seen the files.

When a request arrives, log the date and time it came in, write down exactly what was asked, and start the retrieval work at once. A dated log also shows how quickly you responded, which is useful if the response is ever questioned.

Respond in writing, keep a copy of everything you produce, and note anything you could not produce and why. If a record is wrong, correct it with a dated note rather than overwriting the original. Changing an original to make it fit a request is the fastest way to turn a small records gap into a much larger problem.

Where should a small employer start?

Start with an inventory of what you keep and where it sits. List each category of record, the system or place it lives in, the person responsible for it, and the applicable start date. Records often live in places nobody has written down, such as a personal phone, a spreadsheet on one laptop or a paper binder in a truck. Those are the places to check first.

If you are both the owner and the person who holds most of the files, the inventory also shows you what depends on you alone. A records process that only works while you are in the building is a weak process, and the inventory is the quickest way to find out where that is true.

For each category, answer three questions: how long you keep it, where it is, and how long it would take to produce. Any category that fails the last question needs a fix. That gives you a short list of gaps to close, which is a better place to begin than a long policy document nobody reads.

Once the inventory is done, read the full text of section 177.30 with it in hand, and note every place where your current practice differs from the rule. Those differences are your to-do list. Close the largest gaps first, and schedule the retrieval drill for after the fixes are in place, so you measure the new process rather than the old one.

General information, not legal or tax advice.

Sources