Closing a Minnesota Trust: The 30-Day Objection Window Only Works If the Proposal Says It Exists

A trustee winding up a Minnesota trust has one cheap, fast, non-judicial tool for buying finality, and most trustees who use it use it wrong.

Minn. Stat. § 501C.0817(a) lets a trustee send beneficiaries a proposal for distribution and extinguish their right to object to it after 30 days. No petition, no hearing, no court file. But the sentence granting that power carries a condition at its end that swallows the whole mechanism when it is missed: the cutoff operates “but only if the proposal informed the beneficiary of the right to object and of the time allowed for objection.”

A proposal that lists the assets and states the shares — a perfectly sensible-looking document — does nothing. Thirty days pass and no objection right has terminated, because the proposal never told anyone one existed. The trustee closes the trust believing he is protected and is not.

That is the whole article in one paragraph, but the section does more than that, and the second half — the reserve — is where a trustee who distributes too fast creates personal exposure of a different kind.

What does a Minnesota trustee actually have to do when a trust terminates?

Two things, in two paragraphs, and they pull against each other.

Paragraph (b) imposes the duty:

(b) Upon the occurrence of an event terminating or partially terminating a trust, the trustee shall proceed expeditiously to distribute the trust property to the persons entitled to it, subject to the right of the trustee to retain a reasonable reserve for the payment of debts, expenses, and taxes and to secure a right of reimbursement if the reserve is inadequate.

Paragraph (a) supplies the optional protective step:

(a) Upon termination or partial termination of a trust, the trustee may send to the beneficiaries a proposal for distribution. The right of any beneficiary to object to the proposed distribution terminates if the beneficiary does not notify the trustee of an objection within 30 days after the proposal was sent but only if the proposal informed the beneficiary of the right to object and of the time allowed for objection.

Read the verbs. Paragraph (b) is “shall proceed expeditiously.” Paragraph (a) is “may send.” Distribution is mandatory and prompt; the protective proposal is discretionary and takes 30 days. A trustee who wants both has to run them in the right order and accept that “expeditiously” and “wait out the objection window” are in tension. The statute does not resolve that tension, and it does not define “expeditiously.” What it does tell you is that a trustee who has sent a compliant proposal has a defensible reason for the 30 days he spent, and a trustee who has not sent one is simply late.

Note also that paragraph (a) applies on “termination or partial termination.” Partial terminations — a subtrust distributing on a beneficiary reaching an age, a fractional share vesting — get the same tool. Trustees routinely leave it on the table for those, and those are exactly the events that come back years later as a dispute about how a share was computed.

What has to be in the proposal for distribution?

The statute names two required disclosures and no others:

1. The right to object.
2. The time allowed for objection.

That is the entire statutory content requirement, and it is a low bar — which is precisely why failing it is inexcusable. Two sentences, added to a document the trustee was already producing, convert a courtesy letter into a limitation on rights.

Everything else about the proposal is left to the trustee, and that discretion cuts both ways:

Substance is not prescribed, so substance is your risk. Section 501C.0817(a) does not require the proposal to show the trustee’s fees, the computation of shares, the disposition of specific assets, the basis for valuations, or anything else. A one-page proposal that satisfies the two disclosure requirements terminates the right to object to the proposed distribution. It does not follow that a threadbare proposal is a good idea. A beneficiary who cannot tell from the document what is being proposed has an easy argument that whatever he lost the right to object to was not this. The safer proposal shows the arithmetic.

“Sent,” not received. Paragraph (a) runs the 30 days “after the proposal was sent.” Minn. Stat. § 501C.0109(a) defines what sending requires: it “must be accomplished in a manner reasonably suitable under the circumstances and that is likely to result in receipt of the notice or document,” and permissible methods “include first-class mail, personal delivery, delivery to the person’s last known place of residence or place of business, or a properly directed facsimile or electronic message.” Proof of mailing carries the burden; proof of delivery is not required. The trustee should keep the mailing record anyway, because on this section the sending date is the only date that matters.

Objection is by notice to the trustee. The beneficiary’s move is to “notify the trustee of an objection.” No filing, no form, no court. Which means a trustee must treat any communication within the window that reads as an objection as one — and a beneficiary who calls rather than writes has created a proof problem for himself.

Who counts as “the beneficiaries” for this purpose?

This is the trap that ruins otherwise careful terminations.

Section 501C.0817(a) says “the beneficiaries.” It does not say “qualified beneficiaries.” Chapter 501C uses both terms and they mean very different things. Under Minn. Stat. § 501C.0103(c), a “beneficiary” is a person who “has a present or future beneficial interest in a trust, vested or contingent,” or who, in a capacity other than trustee, “holds a power of appointment over trust property.” Under § 501C.0103(m), a “qualified beneficiary” is a narrower group defined by present distribution status and by who would take if current interests or the trust terminated on the measuring date.

Trustees who are used to sending statutory notices to qualified beneficiaries — the group named in the reporting and modification provisions — will default to that list. On a § 501C.0817 proposal that list may be short by exactly the people most likely to complain: contingent remaindermen, holders of powers of appointment, and future-interest holders whose interests have not vested.

The consequence is asymmetric and unforgiving. A proposal sent to five of seven beneficiaries terminates the objection rights of five. The other two are untouched, and their rights are the ones a trustee will hear about after the accounts are closed and the money is gone.

Where a beneficiary cannot be found, § 501C.0109(b) provides that a document otherwise required to be sent need not be provided to a person “whose identity is unknown or whose location is unknown and not reasonably ascertainable by the trustee after making reasonable efforts to locate the person.” That is a defense to the obligation to send. It is not a mechanism for terminating that person’s objection rights — the statute cuts off the right of a beneficiary who was sent a compliant proposal and did not object. If a missing beneficiary’s rights need to be resolved, that is a court proceeding, not a mailing.

Can a trustee hold money back after the trust ends?

Yes, and the authority is explicit. Paragraph (b) makes the duty to distribute “subject to the right of the trustee to retain a reasonable reserve for the payment of debts, expenses, and taxes and to secure a right of reimbursement if the reserve is inadequate.”

Three components, each doing separate work:

The permitted purposes are enumerated. Debts, expenses, and taxes. That list is the authority, and a reserve held for something outside it is not authorized by this paragraph. “In case a beneficiary sues me later” is not on the list. A trustee who wants protection against that risk is looking for a release or a court order, not a reserve.

The size must be “reasonable.” The statute supplies no formula, no percentage, and no cap. Reasonableness is measured against the identified debts, expenses, and taxes — which means the reserve should be documented against something: an estimated final fiduciary income tax liability, an unpaid professional invoice, an outstanding claim. A round number chosen for comfort is a number a beneficiary can attack, and holding an unreasonably large reserve is itself a failure to “proceed expeditiously to distribute.”

Reimbursement survives an inadequate reserve. The clause “and to secure a right of reimbursement if the reserve is inadequate” is the trustee’s backstop when the estimate proves low. It works together with Minn. Stat. § 501C.0709(a), under which a trustee “is entitled to be reimbursed out of the trust property, with interest as appropriate,” for expenses properly incurred in administration, and — to the extent necessary to prevent unjust enrichment of the trust — for expenses not properly incurred. Section 501C.0709(b) adds that an advance of the trustee’s own money “for the protection of the trust gives rise to a lien against trust property to secure reimbursement with reasonable interest.”

The practical difficulty is obvious and worth stating plainly: reimbursement “out of the trust property” and a lien “against trust property” are only worth something while trust property exists. A trustee who distributes everything and then receives a tax assessment has a right of reimbursement against assets that are now in seven different people’s bank accounts. That is why the reserve, not the reimbursement right, is the real protection. Set the reserve before the wire transfers, not after.

Does a proposal for distribution protect the trustee from being sued?

Not by itself, and this is the distinction that most needs drawing.

Section 501C.0817(a) terminates “[t]he right of any beneficiary to object to the proposed distribution.” That is a defined and limited thing. It is not a release, not a discharge, not an approval of the trustee’s accounts, and not a bar on claims for how the trust was administered over the preceding fifteen years. A beneficiary who lets the 30 days run has lost the ability to contest the proposed division. He has not lost a claim that the trustee overpaid himself in year six.

Three other mechanisms handle the broader problem, and a trustee closing a file should know which one he is actually using:

Paragraph (c) of § 501C.0817 is the warning label on the middle row: “A release by a beneficiary of a trustee from liability for breach of trust is invalid to the extent it was induced by improper conduct of the trustee.” That is narrower than the general rule in § 501C.1009, which makes a consent, release, or ratification binding unless it was induced by improper conduct or unless, at the time, “the beneficiary did not know of the beneficiary’s rights or of the material facts relating to the trustee’s conduct and the trustee did know of the material facts relating to the trustee’s conduct.” Note the conjunctive “and” in that second exception — it takes both the beneficiary’s ignorance and the trustee’s knowledge. The full analysis of what a Minnesota beneficiary’s release does and does not do is worth reading before you draft one, because a release solicited alongside a final distribution is the single most commonly challenged document in trust practice.

Where the real objective is comprehensive closure — approval of the accounting and resolution of liability and a fixed distribution — a nonjudicial settlement agreement under § 501C.0111 does in one instrument what § 501C.0817 was never designed to do. Its cost is that it requires the agreement of the interested persons, defined in § 501C.0111(a) as “persons whose consent would be required in order to achieve a binding settlement were the settlement to be approved by the court.” The § 501C.0817 proposal requires no one’s agreement — only their silence. That is its entire appeal and its entire limitation.

When should a trustee go to court instead?

When the objection is real, when a beneficiary cannot be located, or when the trustee wants a discharge rather than a defense.

Minn. Stat. § 501C.0202 lists the matters a judicial proceeding may address, and several are built for a wind-up: clause (2), “upon the filing of an account, to settle and allow the account”; clause (3), to determine the persons having an interest and the nature and extent of their interests; clause (8), to require a trustee to account; clause (20), to terminate a trust; and clause (24), to instruct the trustee “regarding any matter involving the trust’s administration or the discharge of the trustee’s duties, including a request for instructions and an action to declare rights.”

A trustee holding a contested computation, an unlocatable remainderman, or a beneficiary who has objected within the window should stop mailing and file. The 30-day tool is designed for the uncontested case; it does nothing once someone has said no.

The checklist

If you are the trustee.

1. Identify all beneficiaries under § 501C.0103(c) — not just the qualified beneficiaries. Contingent interests and powers of appointment count.
2. Draft the proposal so a reader can follow the arithmetic, even though the statute does not require it.
3. Include, in terms, both required disclosures: that the beneficiary has a right to object, and that the time allowed is 30 days after the proposal was sent. Without these the 30 days is legally inert.
4. Send by a § 501C.0109(a) method and keep the record of what went to whom on what date.
5. Set the reserve before distributing, tie it to identified debts, expenses, and taxes, and document the estimate.
6. Do not confuse the objection cutoff with a release. If you want a release, ask for one and understand § 501C.1009’s exceptions. If you want finality on the accounting and on liability, use § 501C.0111 or the court.
7. Distribute expeditiously once the window closes.

If you are a beneficiary who just received one of these. Read the document for the two disclosures. If it does not state that you have a right to object and how long you have, the 30-day cutoff in § 501C.0817(a) does not operate against you. If it does, the clock started when it was sent, not when you opened it — so calendar it from the date on the letter and object in writing to the trustee. And separate the two questions you are being asked: whether this division is right, and whether you are also being asked to sign something releasing the trustee for everything that came before. Those are not the same document and should not be treated as one decision.

Madgett Law, LLC

We advise Minnesota trustees on closing trusts cleanly — what the proposal has to say, who has to receive it, how large a reserve the facts support, and when the mailing is not enough and the file belongs in front of a judge. We also represent beneficiaries who have received a proposal, a release, or both, and need to know what signing costs them before the 30 days runs. Call 612-470-6529 or send us a message.

Sources: Minn. Stat. § 501C.0817 (Distribution Upon Termination) — para. (a) (trustee may send beneficiaries a proposal for distribution on termination or partial termination; right to object terminates if no notice of objection within 30 days after the proposal was sent, but only if the proposal informed the beneficiary of the right to object and of the time allowed for objection), para. (b) (duty to proceed expeditiously to distribute, subject to the right to retain a reasonable reserve for the payment of debts, expenses, and taxes and to secure a right of reimbursement if the reserve is inadequate), para. (c) (release invalid to the extent induced by improper conduct of the trustee); § 501C.0103 (Definitions) — para. (c) (“beneficiary”: present or future beneficial interest, vested or contingent, or holder of a power of appointment other than as trustee), para. (m) (“qualified beneficiary”: narrower, defined by present or hypothetical distributee status); § 501C.0109 (Methods and Waiver of Nonjudicial Notice) — para. (a) (manner reasonably suitable and likely to result in receipt; first-class mail, personal delivery, delivery to last known residence or business, properly directed facsimile or electronic message), para. (b) (no obligation to send to a person whose identity or location is unknown and not reasonably ascertainable after reasonable efforts); § 501C.0111 (Nonjudicial Settlement Agreements) — para. (a) (definition of “interested persons”), para. (b)(2) (approval of a trustee’s report or accounting), para. (b)(6) (liability of a trustee for an action relating to the trust), para. (c) (valid only to the extent it does not violate a material purpose and contains terms a court could properly approve); § 501C.0202 (Subject Matter of Judicial Proceedings) — clauses (2), (3), (8), (20), (24); § 501C.0709 (Reimbursement of Expenses) — para. (a)(1)–(2) (reimbursement out of trust property, with interest as appropriate, for properly incurred expenses and, to prevent unjust enrichment, improperly incurred expenses), para. (b) (advance for the protection of the trust gives rise to a lien against trust property with reasonable interest); § 501C.1009 (Beneficiary’s Consent, Release, or Ratification) — clauses (1) and (2) — Minnesota Office of the Revisor of Statutes, 2025 edition. Section 501C.0817 carries no 2026 amendment banner; its history line reads 2015 Minn. Laws ch. 5, art. 8, § 14. No case law is cited in this article. This is general legal information about Minnesota law, not legal advice, and reading it does not create an attorney–client relationship. Whether a particular proposal satisfied § 501C.0817(a), and whether a particular reserve was reasonable, depend on the trust instrument and the facts. No outcome is promised or implied.