Every Michigan exchange file eventually needs to answer a simple question for a CPA who was not in the room for any of it: what happened, in what order, and who can prove it. That is the whole job of documentation assembly, and it is easy to underestimate until the file is missing one signed page, usually discovered at the least convenient moment during tax preparation.
Why This Gets Harder in a Multi-County Exchange
A straightforward exchange with one sale and one purchase in the same county produces a manageable stack of paper. A statewide exchange, say a relinquished property in Wayne County funding a replacement in Kent County with a DST allocation from an out-of-state sponsor, produces documents from several title companies, at least two closing agents, and a qualified intermediary who has to tie all of it together. Different Michigan counties also have slightly different closing customs and certificate requirements, which means the paperwork rarely arrives in a consistent format even within one file.
We have assembled files spanning Wayne, Kent, Ingham, and Grand Traverse counties inside a single exchange, each with its own register of deeds naming conventions and its own local title company templates. None of that changes what the final record needs to show, but it does mean someone has to translate four different paperwork styles into one consistent story before an advisor ever opens the file.
What Actually Belongs in the Final Record
By the time an exchange is complete, the assembled file should include a defined set of documents pulled from every stage of the transaction.
- the relinquished and replacement property purchase contracts
- the qualified intermediary exchange agreement and assignment documents
- the written 45-day identification notice and proof of delivery
- closing statements and settlement records for every property involved
- wire confirmations and QI funding instructions
- any late-stage contract amendments that changed price or timing
The Difference Between a Draft and a Record
We keep drafts and signed final versions clearly separated, because it is common for a closing statement to go through two or three revisions in the final week before closing. Only the final, signed version belongs in the permanent exchange file, and we date-stamp each document as it is confirmed final so nobody downstream has to guess which version is authoritative. On multi-property Michigan exchanges this discipline matters even more, since three or four closing statements moving through revisions at the same time can create real confusion about which numbers are current if drafts and finals sit in the same folder.
Building the Chronology
Alongside the documents themselves, we build a plain chronology: the date the relinquished property transferred, the date the identification notice was delivered, and the date each replacement property closed. That timeline is often what a CPA reaches for first, before opening a single underlying document, because it tells the story of the exchange at a glance. For a statewide exchange with properties closing weeks apart in different counties, that single-page timeline is frequently the only thing that makes the sequence of events clear without cross-referencing four separate closing binders.
Handing the File to the Advisor
The final handoff includes the document index, the chronology, and a short note on anything unusual about the exchange, whether that is a multi-property identification, a DST allocation, or a closing that ran close to the 180-day deadline. A clean handoff here is what keeps the tax reporting step from turning into a document scavenger hunt months later. We deliver the package as a single organized file rather than a folder of loose attachments, since an advisor working through a busy tax season is far more likely to actually read a clearly indexed handoff than reconstruct one from scattered emails.
Common 1031 Exchange Questions
Why does a multi-county Michigan exchange need extra documentation work?
Different title companies and closing agents produce paperwork in different formats, and a statewide exchange often involves several of them, so someone has to reconcile everything into one consistent, chronological record.
What proof of delivery is needed for the 45-day identification notice?
We keep dated confirmation showing the written identification was delivered to the qualified intermediary or another eligible party before the deadline, since a missing proof-of-delivery record can raise questions later even if the identification itself was valid.
Should I keep draft closing statements in my exchange file?
No, we recommend keeping only the final signed version and clearly marking it as such, since multiple draft versions in a file can create confusion for anyone reviewing it after the fact.
Who typically needs the final assembled exchange file?
The investor's CPA or tax preparer needs it most directly for Form 8824 reporting, though it is also useful if the exchange is ever reviewed or questioned years later.
How do you handle documents that arrive in different formats from different Michigan counties?
We translate each county's closing paperwork into one consistent index and chronology, since register of deeds naming conventions and title company templates vary enough across counties that the raw documents alone do not tell a clear story on their own.
Should wire confirmations be part of the final exchange file?
Yes, wire confirmations tied to the QI funding instructions are part of the core record, since they are often the clearest proof that funds moved directly to or from the qualified intermediary rather than through the investor.
