Skip ahead to the main page
Partner Huddle
Pages

Unclaimed property records: 3 holder duties

Partner Huddle Editorial Team · Published · 12 min read

Unclaimed-property holders need records that support state reporting, meet retention requirements, and can be produced for examination. That makes sense, since the report is what the state sees. But every line on it rests on records that show where the property came from, why it was treated as unclaimed, and what happened to it after. When those records are thin, late, or missing, a report that looks right can still be hard to defend.

Key takeaways

  • Record which entity is the holder for each client file, and why.
  • Tie every reported line to its accounting entry and classification note.
  • Confirm the current statute text in each state before you set a deadline or retention period.
  • Keep supporting records for the full retention period, and check whether an audit could end it sooner.
  • Keep the file clear enough that an examiner can follow it without the people who built it.

This post walks through three duties that holders commonly carry, and what each one means for the people who build the file. The first is reporting on time and in the form the law requires. The second is keeping supporting records for the period the law sets. The third is being ready for an examination and handling what the examiner sees with care.

Handoffs are where most of the friction in this work happens: from the person who pulls the accounting records to the person who builds the report, and from the partner who signs to the team that answers the examiner. The duties below are easiest to manage when each handoff leaves a record.

The examples come from two state statutes: Ohio's unclaimed funds chapter and Michigan's unclaimed property act provisions. They show how state rules are written. They are not a summary of every state's rule, and they are not advice for your client. Each client may have reporting duties in more than one state, and the statute that applies depends on the facts. Confirm the current text for each state before you set a deadline or retention period.

Duty 1: report to the state on time and in the required form

Ohio's statute states the reporting duty in plain terms. Every holder of unclaimed funds, and when requested, every person that could be the holder, "shall report to the director of commerce with respect to the unclaimed funds as provided in this section" ( Ohio Revised Code 169.03). The sentence is short, but it contains two points that matter for your work. The duty runs to the holder, not only to whoever happens to file. It can also reach a person who could be the holder, and only once the state asks.

For a partner or operations lead, that means each client file needs a clear answer to one question: which entity is the holder? A parent, a subsidiary, a successor company, or a service provider may each have a different connection to the property. If the answer is unclear, record why you reached the conclusion you did. That note will matter if a state asks a related party to report. For the Ohio rules in more detail, see Ohio unclaimed funds: 3 record duties a holder must meet.

Reporting also needs a source trail. Build the report from a file that ties each line to the underlying accounting entry, the date the property became reportable, and the status note that explains the classification. When someone asks why an amount appears, the answer should take minutes to find, not days.

Michigan's statute covers what happens after property leaves the holder's books. It says that "upon the payment or delivery of property to the administrator, the state assumes custody and responsibility for the safekeeping of the property" ( Michigan Legislature, MCL 567.241). The same section says a person who pays or delivers property in good faith is relieved of all liability, to the extent of the value paid or delivered, for claims that already exist or may arise later about that property. That is a good reason to keep a dated record of what was delivered, in what amount, and under which report.

Reviewer sign-off belongs in the reporting step too. A partner who signs the report should see the same support file the operations lead used. That review does two jobs. It catches mistakes in the numbers, and it creates a record that the signer saw the basis for the filing. If the signer only sees a summary, the summary becomes the thing that was checked, and gaps in the underlying file can go unnoticed until someone outside the firm asks for it. Make sure the sign-off is dated and tied to a specific version of the report, so a later change does not look like it was approved.

Keep a current register of states for each client. For every state, note the form the state uses, who receives the report, the contact for questions, and where the statute text is kept. Check the register at the start of each cycle. Statutes change, and a register that was right two years ago may now point to the wrong office.

Duty 2: keep supporting records for the full retention period

Ohio's retention rule is specific about the clock. Holders "shall retain records, designated by the director as applicable to unclaimed funds, for five years beyond the relevant time period provided in section 169.02 of the Revised Code, or until completion of an audit conducted pursuant to division (G) of this section, whichever occurs first" ( Ohio Revised Code 169.03). Read it closely and three things stand out.

First, the five years are counted beyond a time period specified in another section, not from the date you filed the report. Second, the director designates which records count, so the list you keep for Ohio should match that designation. Third, the period can end early. If an audit under division (G) is completed first, the statute's "whichever occurs first" language means the retention duty can end then, which is earlier than five years after the time period.

Because of that structure, a single retention date in a spreadsheet is not enough. Build a retention calendar for each Ohio client file with three columns: the date the relevant time period ended under the applicable statute, the date five years later, and a column for any audit that closes the retention duty sooner. Keep the calendar owned by someone who can answer questions about it.

Illustrative example: a retention clock

Suppose a relevant time period ends on a given date. Under the five-year rule quoted above, the retention duty would run until five years after that date. Now suppose an audit under division (G) is completed 3 years after the period ends. Under the "whichever occurs first" language, the duty ends at the audit, which is earlier than the five-year mark. A calendar that shows both dates keeps a file from being deleted too early or kept longer than the rule requires.

The records themselves are a separate question. The items that follow are working practice, not a legal checklist. Keep the accounting extract used for each report, the classification decision and who approved it, the record of owner contact attempts and their outcomes, any returned mail, and the calculations behind each figure in the filing. Keep the final filed version and every draft that changed a number. Do not let a clean-up project delete anything that falls inside an open retention window.

Where you keep the records matters as much as how long. Scattered copies on personal drives, email attachments, and old shared folders are hard to defend. Pick one controlled repository for each client, with version history and a clear folder structure by report year. Confirm that deletion requires sign-off, and that automatic clean-up routines do not run on files still inside a retention window. A routine that deletes old email on a schedule can remove the only copy of a support document.

Retention gets harder when a client changes shape. A company that is bought, splits, or moves its accounts may leave its old records with a former affiliate or a vendor. Before that happens, decide who will hold the supporting records for each period, put that decision in writing, and confirm the new custodian can produce them on request. A retention rule is only useful if the records still exist when someone asks for them. For the staff side of the same problem, see Retention clocks when staff leave.

Two records deserve extra care. The first is the proof that you tried to reach an owner, because a failed attempt can be as important as a successful one. The second is any change made after the report was filed. A correction without a dated note looks like an edit made to hide something, even when it was made to fix an error.

Duty 3: be ready for examination and protect what you find

A state can look at your records. Ohio's statute says the director "may, at reasonable times and upon reasonable notice, examine or cause to be examined, by auditors of supervisory departments or divisions of the state, the records of any holder to determine compliance with this chapter" ( Ohio Revised Code 169.03). The same section lets the director contract with outside persons for the sole purpose of examining holders' records, determining compliance, and collecting and delivering amounts found to be unclaimed. So the reviewer may be a state auditor or a contracted examiner, and you should prepare for either.

Use the comparison below to connect each file task with a practical check.

File taskIllustrative practice
ReportingIllustrative: tie each report line to its support
Retention Illustrative: check the calendar before deleting files
ExaminationIllustrative: log documents sent to the examiner
Records after delivery Illustrative: keep a dated delivery record

Ohio's statute also addresses confidentiality. It says that records audited under division (G) "are confidential, and shall not be disclosed except as required by section 169.06 of the Revised Code or as the director considers necessary in the proper administration of this chapter" ( Ohio Revised Code 169.03). Do not read that as a reason to loosen controls on your own copies. Keep internal copies behind access limits, name an owner for the examination file, and log who pulls each document for the examiner.

An examination request often arrives with a list of items to produce. Read the request twice before you respond. Note the scope, the period it covers, and any records it leaves out. Answer what was asked, in the form it was asked for, and avoid volunteering unrelated files. If the request is unclear, ask the examiner to clarify in writing. A written trail of questions and answers protects both the holder and the team that handled the file.

Preparing for an examination is mostly about the file being easy to follow. Keep the filed version in the form it was sent, with an index that maps each report line to its support. Have one person who knows the file available to answer questions. Keep a record of what was sent to the examiner and when. If a gap exists, document it with the reason and the date you found it. Do not fill a gap with a backdated document, because that turns a records problem into a credibility problem.

Delivery can also come up during or after an examination. That is one reason the file should show, for each amount, when it was identified and whether it was already paid. An examiner who finds an unpaid amount with no explanation has a harder conversation than one who finds a documented timing difference.

A review routine for each client file

The three duties work best as a routine rather than as a project that starts when a state letter arrives. A simple cycle for each client file looks like this:

  1. Before filing, confirm the holder and record why. Check that the entity named in the report is the one the statute treats as the holder, and note any related party who might be asked to report.
  2. Tie every reported line to its source. Each line should point back to an accounting entry and a classification note.
  3. After filing, store the filed version and the proof of delivery, and update the retention calendar with the dates that apply.
  4. When an examination notice arrives, check the index, name one contact, and log every request from the examiner.
  5. After any examination, review the gaps and update the controls for the next cycle.

The routine does not need special software. A shared checklist, a dated retention calendar, and an index for each file will cover most of it. What matters is that the same steps happen every cycle, and that someone reviews the list when the state's rules or the client's facts change.

Where the three duties meet in one file

Consider a simple case. A client files a report one year, and a state later asks a related company for its own records. The reporting team says the holder is the client. The related company says it only handled billing. Neither side can resolve that from memory. The file either answers the question, or it does not.

This is where the three duties meet. The reporting duty requires a clear view of who the holder is. The retention duty requires the records that answer that question to still exist when asked. The examination duty requires the file to explain itself without the people who built it in the room. A weak link in one duty tends to show up as a problem in the other two.

Partners and operations leads split the work well when each role has a clear job. Operations usually owns the source trail, the retention calendar, and the examination index. The partner usually owns the decision on who the holder is, the sign-off on each report, and the call on whether a gap needs to be disclosed. Write those splits down. A split that lives only in people's heads will break the first time someone is on leave.

When two parts of the file disagree, do not pick the version that looks cleaner. Find out which one is right, correct the file with a dated note, and tell the partner who signed the report. A disagreement that is explained is a much smaller problem than one that is hidden.

Duties like these are easy to meet in a busy filing season and easy to neglect the rest of the year. Use the calendar, not memory, to decide when to pull a file for review. If the file is clear to someone who was not there when it was made, the report is much more likely to hold up when the state comes asking.

Next step today: Pick one open client file and check that each reported line has a source note pointing to an accounting entry. If a note is missing, write it now and date it.

Frequently asked questions

Who is the holder for a client's unclaimed property report?

Each client file should record which entity is the holder and why, since a parent, a subsidiary, a successor company, or a service provider may each have a different connection to the property.

How long must Ohio holders keep unclaimed funds records?

Under the Ohio rule quoted above, holders keep designated records for five years beyond the relevant time period in section 169.02, or until an audit under division (G) is completed, whichever occurs first.

Related guides: Account deletion for firm records: 3 checks before removal · Audit log retention: 4 settings to check for your firm · Client inventory and property basis: 3 year-end checks.

Sources