A contract signed without board approval can bind a Minnesota corporation. By default, the chief executive officer’s duties under the Minnesota Business Corporation Act include signing contracts that pertain to the company’s business, and even an officer who acted beyond actual authority can bind the company through apparent authority or a later ratification. In Truck Crane, the facts did not establish “an affirmative course of conduct by the principal that would constitute holding out,” so the Minnesota Supreme Court found no apparent authority. In Losinski, the articles required a shareholder vote that never took place, and “any valid ratification was required to take the same form,” so the same court refused to find implied ratification. Chapter 302A sets who holds signing power; whether the company is bound beyond it is Minnesota agency law built by the courts. This page is for directors and officers of Minnesota business corporations and is part of my Minnesota corporate governance practice materials.

What decides whether a contract signed without board approval binds the company?

Three routes decide it: the officer’s actual authority, apparent authority created by the company’s conduct, and ratification after the fact. Minnesota law does not require a board vote for every contract, so the question is whether one of the three routes reaches this deal.

Board approval is not a general precondition because Minn. Stat. § 302A.201, subd. 1 provides that “The business and affairs of a corporation shall be managed by or under the direction of a board, subject to the provisions of subdivision 2 and section 302A.457, and except as may be otherwise provided in the articles.” Management “under the direction of” the board leaves room for officers to run daily operations and sign the contracts that come with them.

When an officer goes past actual authority, the test turns on the other side’s belief and its source. In Powell v. MVE Holdings, Inc., 626 N.W.2d 451 (Minn. App. 2001), the Court of Appeals put it this way: “Holdings can be held to O’Halloran’s agreement only if Powell’s belief that O’Halloran had authority to make that agreement is reasonable and traceable to Holdings.”

What signing power does a Minnesota CEO have without a board vote?

By default, a Minnesota CEO’s statutory duties include signing the company’s contracts. Under Minn. Stat. § 302A.305, subd. 2, the chief executive officer shall “sign and deliver in the name of the corporation any deeds, mortgages, bonds, contracts or other instruments pertaining to the business of the corporation,” except where “the authority to sign and deliver is required by law to be exercised by another person or is expressly delegated by the articles or bylaws or by the board to some other officer or agent of the corporation.” The same subdivision gives the CEO “general active management of the business of the corporation.”

The board controls the default. Subdivision 1 provides that the duties apply “Unless the articles, the bylaws, or a resolution adopted by the board and not inconsistent with the articles or bylaws, provide otherwise.” Other officers, such as a COO or vice president, hold only the powers “provided for in the articles or bylaws or determined by the board” under Minn. Stat. § 302A.311. An officer may also pass duties down: under Minn. Stat. § 302A.351, “Unless prohibited by the articles or bylaws or by a resolution approved by the affirmative vote of a majority of the directors present, an officer may, without the approval of the board, delegate some or all of the duties and powers of an office to other persons.” A written shareholder control agreement under Minn. Stat. § 302A.457, subd. 2 can also govern “the management of its business” and “the election of directors or officers,” and it “is binding upon and enforceable against only those persons and other persons having knowledge of the existence of the agreement.”

For a board that wants dollar limits or a list of contracts that need its vote, I suggest putting them in a written resolution or the bylaws, because those are the documents subdivision 1 says can change the default. My page on written authority limits for officers covers the drafting. An internal limit controls the officer; whether it protects the company against an outside party is the apparent-authority question in the next section.

A Minnesota LLC works differently. Minn. Stat. § 322C.0301, subd. 1 provides that “A member is not an agent of a limited liability company solely by reason of being a member,” and an LLC can publicly state who may bind it by filing a statement of authority under Minn. Stat. § 322C.0302, subd. 1. Membership alone does not make a member an agent, but subdivision 2 of § 322C.0301 preserves other law, such as agency law, that can make the LLC answer for a member’s conduct.

How does apparent authority bind the company to an officer’s deal?

Apparent authority binds the company when the company’s own conduct leads the other side to believe the officer could sign, and the other side knew of that conduct. I found no Minnesota statute that codifies the rule for corporate officers; it comes from Minnesota Supreme Court decisions.

The Minnesota Supreme Court restated the elements in Truck Crane Service Co. v. Barr-Nelson, Inc., 329 N.W.2d 824 (Minn. 1983):

  • “The principal must have held the agent out as having authority, or must have knowingly permitted the agent to act on its behalf”
  • “the party dealing with the agent must have actual knowledge that the agent was held out by the principal as having such authority or had been permitted by the principal to act on its behalf”
  • “the proof of the agent’s apparent authority must be found in the conduct of the principal, not the agent.”

Powell shows the elements working against a company. The CEO there agreed to buy back the shares of an executive he was firing, without express board approval. Six months earlier, with board approval, the same CEO had signed an agreement buying other shareholders’ stock at the same price. The court found the executive’s belief reasonable, noting that “Holdings’ board acted informally and secretly, generally preparing board resolutions only when a third party such as the IRS required them.” The court also said that “unless there is contrary evidence, contracts made by a corporation’s president in the ordinary course of business are presumed to be within the president’s authority,” while cautioning that “a job title alone will not conclusively establish apparent authority for a contract.” The Court of Appeals affirmed the judgment for the executive.

Inattention counts against the company too. In Duluth Herald & News Tribune v. Plymouth Optical Co., 176 N.W.2d 552 (Minn. 1970), the court quoted its earlier decision that the scope of apparent authority “is determined not only by what the principal knows and acquiesces in, but also by what the principal should, in the exercise of ordinary care and prudence, know his agent is doing.” Powell adds that “Whether an agent is clothed with apparent authority is a question of fact,” so these disputes are decided on the evidence of how the company actually operated.

When does the other side lose an apparent-authority claim?

The other side loses when the company’s own conduct does not support its belief, or when it had reason to question the officer’s authority and did not check. A job title alone, without more from the company, may not be enough.

In Truck Crane, a former secretary-treasurer who was answering phones signed a guarantee for a disputed bill. His name and old title were still printed on company checks, but the supplier could not show it had noticed them, and the company president had already written to the supplier denying liability. The court held there was no apparent authority as a matter of law, explaining that the president’s letter “put the plaintiff on inquiry as to the authority of any other Barr-Nelson employee to countermand such a position.” It sent the case back to decide the amount the company did owe.

The duty to check comes from West Concord Conservation Club, Inc. v. Chilson, 306 N.W.2d 893 (Minn. 1981): “Every person who undertakes to deal with an agent is put on inquiry and must discover whether the agent has the authority to complete the proposed act.”

That duty has a practical limit. In Powell, even accepting that the executive knew a stockholders’ agreement required board approval for a repurchase, the court said “it is unclear what Powell could have done to ascertain whether O’Halloran had the necessary approval,” because the board rarely documented its decisions. For a company on the defending side, my page on defending an apparent-authority claim covers the evidence that matters.

Which deals need more than an officer’s signature?

A sale of all or substantially all of a corporation’s assets outside the usual and regular course of business needs more than an officer’s signature. Under Minn. Stat. § 302A.661, subd. 2, the board must act, written notice of the meeting must go to all shareholders, and the sale must be approved “at a regular or special meeting of the shareholders by the affirmative vote of the holders of a majority of the voting power of the shares entitled to vote.”

The statute has two limits. “Shareholder approval is not required under paragraph (a) if, following the sale, lease, transfer, or other disposition of its property and assets, the corporation retains a significant continuing business activity.” Under subdivision 1, a board vote alone covers a disposition “in the usual and regular course of its business” and a security interest in all or substantially all of the assets.

Chapter 302A also conditions financial assistance and share issuances on board approval: under Minn. Stat. § 302A.501, subd. 1, a corporation “may lend money to, guarantee an obligation of, become a surety for, or otherwise financially assist a person, if the transaction, or a class of transactions to which the transaction belongs, is approved by the affirmative vote of a majority of the directors present,” along with one of the further conditions that subdivision lists, and under Minn. Stat. § 302A.401, subd. 1(a), “Subject to any restrictions in the articles, a corporation may issue securities and rights to purchase securities only when authorized by the board.”

The articles can add their own approval requirements, and the Minnesota Supreme Court has enforced one against an officer’s deal. In Losinski v. American Dry Cleaning Co., 281 N.W.2d 884 (Minn. 1979), a vice president signed a lease that gave her son an option to buy the real estate that made up substantially all of the company’s assets. The articles required a shareholder vote to sell substantially all the assets, and the shareholders never voted. The Minnesota Supreme Court reversed a ruling that the company had impliedly ratified the option, because “any valid ratification was required to take the same form.” Bylaws and shareholder agreements can carry similar requirements; my page on board approval for major transactions covers them.

How does a board ratify a contract it never approved?

A board ratifies an unauthorized contract by approving it, or by accepting it through conduct, after learning the material facts. Once ratified, the contract binds the company as though the officer had authority from the start.

The Minnesota Supreme Court defined the doctrine in Anderson v. First Nat. Bank of Pine City, 228 N.W.2d 257 (Minn. 1975). Ratification occurs when a person “having full knowledge of all the material facts” confirms, approves, or sanctions, “by affirmative act or acquiescence, the originally unauthorized act of another, thereby creating an agency relationship and binding the principal by the act of his agent as though that act had been done with prior authority.”

Losinski applies the rule to corporations. “If a corporate officer or agent performs an act or enters into a contract or other transaction without authorization but which could have been authorized in the first instance by the directors or stockholders, such contract or transaction may become binding on the corporation if ratified expressly or by implication.” Ratification can happen in three ways:

  1. A board resolution approving the contract, adopted with the material facts in front of the directors. This is the clearest record.
  2. Conduct. In Cooney v. Milwaukee Mutual Insurance Co., 397 N.W.2d 352 (Minn. App. 1986), the court said “A corporation may ratify unauthorized acts of its agent by accepting the benefits of the transaction.”
  3. The same form the original approval required. Where the articles or a statute required a shareholder vote, Losinski holds the ratification must take that form too.

My page on documenting a board ratification covers what the resolution should say.

What does the 2025 ratification statute add?

Minn. Stat. § 302A.166, added to chapter 302A in 2025, gives a Minnesota corporation a formal statutory procedure to ratify an act that was never properly authorized. A ratified act “is not void or voidable solely as a result of a failure of authorization” under subdivision 1.

The statute reaches an officer’s unauthorized contract. The definitions in Minn. Stat. § 302A.011, subds. 72 and 74 cover, in subdivision 72, “an act or transaction purportedly taken by or on behalf of the corporation” that was within the corporation’s power “but is void or voidable due to a failure of authorization,” and subdivision 74 defines a failure of authorization to include the failure “of the board or an officer to authorize or approve an act or transaction taken by or on behalf of the corporation that requires board or officer approval for the act or transaction’s due authorization.”

The procedure has four parts:

  • Board resolutions stating, among other things, the act, its date, and “the nature of the failure of authorization in respect of each defective corporate act to be ratified” (subdivision 2).
  • A shareholder vote in some cases: “A defective corporate act ratified under subdivision 2 must be submitted to shareholders for approval under subdivision 5, unless” an exception in subdivision 4 applies.
  • Retroactive effect. Under subdivision 7, “From and after the validation effective time, unless otherwise determined in an action brought pursuant to section 302A.167,” the ratified act “is no longer deemed void or voidable as a result of the failure of authorization described in the resolutions adopted under subdivision 2, effective retroactively from the time of the defective corporate act.”
  • Notice to shareholders. Under subdivision 8, “prompt notice of the ratification must be given to all shareholders of valid shares and putative shares, whether voting or nonvoting,” unless notice of the ratification was already given with the shareholder-meeting notice under subdivision 5. The notice must state that any claim that the ratified act “is void or voidable due to the failure of authorization, or that a court should declare in the court’s discretion that a ratification in accordance with this section is not effective or is effective only on certain conditions, must be brought within 120 days from the latter of the validation effective time or the time at which the notice required by this subdivision is given.” I suggest checking the current statute text for that period before sending the notice, because it controls when those claims are cut off.

A court can also decide the question. Under Minn. Stat. § 302A.167, subd. 1, a court may “determine the validity and effectiveness of any defective corporate act not ratified or not ratified effectively pursuant to section 302A.166.” Under Minn. Stat. § 302A.167, subd. 5, a time limit applies to an action asserting that a ratified act “is void or voidable due to a failure of authorization identified in the resolution,” or that a court “should declare in its discretion that a ratification in accordance with section 302A.166 not be effective or be effective only on certain conditions.” Such an action “is prohibited from being brought after the expiration of 120 days from the later of the validation effective time and the time notice, if any, that is required to be given pursuant to section 302A.166, subdivision 8, is given with respect to the ratification.” The limit covers those actions except in two cases. It “does not apply to an action asserting that a ratification was not accomplished in accordance with section 302A.166.” Nor does it apply to a person to whom notice of the ratification was required to be given but was not given. Because that period cuts off claims, I suggest checking the current statute text before relying on it.

How can the company reject a contract it did not authorize?

A company that wants out should decide after learning the material facts, and should avoid accepting the contract’s benefits in the meantime. Accepting the benefits can ratify the contract, and a ratified contract binds the company as though the officer had authority from the start.

Three Minnesota rules shape that decision:

  1. Knowledge. In Gresser v. Hotzler, 604 N.W.2d 379 (Minn. App. 2000), the Court of Appeals said “ratification cannot occur when the principal does not have full knowledge of all material facts, unless constructive knowledge is imputed by the principal’s acceptance of a transaction’s benefits.” Accepting the transaction’s benefits can supply the knowledge the rule otherwise requires.
  2. Burden. In Anderson, the court explained that “As ratification was an affirmative defense, defendant had the burden of proving all material facts necessary to establish it.” The party claiming ratification has to prove it.
  3. Apparent authority survives. Avoiding ratification does not answer an apparent-authority claim, which turns on the company’s conduct before the deal. Powell bound the company through apparent authority even though the deal lacked board approval.

I suggest that the board record its decision in a resolution and notify the other party in writing, because in Truck Crane a written denial from the company president put the supplier on inquiry about any other employee who tried to reverse that position. I also suggest stopping any performance that would accept a benefit under the contract until the decision is made, because Cooney treats acceptance of benefits as ratification.

What happens to the officer who signed without authority?

An officer who signs without authority can be liable to the other party for breach of an implied warranty of authority, and may also answer to the corporation under the officer’s statutory duties.

In Wolfson v. Beris, 295 N.W.2d 562 (Minn. 1980), a co-owner signed for a building he had no power to sell. The Minnesota Supreme Court adopted the Restatement rule: a person who purports to contract on behalf of another “whom he has no power to bind, thereby becomes subject to liability to the other party thereto upon an implied warranty of authority, unless he has manifested that he does not make such warranty or the other party knows that the agent is not so authorized.” Losinski noted the same remedy for an innocent third party. My page on personal liability for signing without authority covers the officer’s side in more detail.

Inside the company, Minn. Stat. § 302A.361, subd. 1 provides that “An officer shall discharge the duties of an office in good faith, in a manner the officer reasonably believes to be in the best interests of the corporation, and with the care an ordinarily prudent person in a like position would exercise under similar circumstances.” An officer who hands signing power to a subordinate is held to that standard for “the act of delegation” and “the supervision of persons to whom those duties and powers are so delegated” under § 302A.351.

Why is ultra vires a different question from officer authority?

Ultra vires asks whether the corporation itself had the power to act, not whether a particular officer had authority to sign. A Minnesota business corporation has broad power to contract, and § 302A.165 protects even a contract outside that power except in three kinds of court proceedings, one of which reaches a party with actual knowledge of the lack of power.

Minn. Stat. § 302A.161, subd. 7 provides that “A corporation may make contracts and incur liabilities, borrow money, issue its securities, and secure any of its obligations by mortgage of or creation of a security interest in all or any of its property, franchises and income,” subject under subdivision 1 to “any limitations provided in any other statute of this state or in its articles.”

Even an act beyond that power is protected. Under Minn. Stat. § 302A.165, a contract “if otherwise lawful, is not invalid because the corporation was without the power to do, continue, or perform the act, contract, conveyance, or transfer, unless the lack of power is established in a court in this state” in one of three proceedings: a shareholder suit to enjoin the act (where a court may set aside the contract “if just and reasonable in the circumstances”), a suit by or for the corporation “against the incumbent or former officers or directors of the corporation for exceeding or otherwise violating their authority, or against a person having actual knowledge of the lack of power,” or an attorney general proceeding. An officer’s lack of authority is decided under the agency rules above. My page on the ultra vires doctrine covers the corporate-power question.

Can the board back out of a supplier deal the CEO signed alone?

Not if the signing fell within the CEO’s default duties. Under Minn. Stat. § 302A.305, subd. 2, the chief executive officer’s duties include signing contracts pertaining to the business of the corporation, unless the law requires another person to sign or the articles, bylaws, or board expressly give that authority to someone else. Under subdivision 1, the articles, the bylaws, or a board resolution can also change those default duties. A written shareholder control agreement under Minn. Stat. § 302A.457, subd. 2 can also govern the management of the business and the election of officers, and it is binding upon and enforceable against only its parties and other persons having knowledge of the existence of the agreement. Even where the board had changed that default, the supplier may hold the company to the deal through apparent authority if its belief in the CEO’s authority was reasonable and traceable to the company’s own conduct. That answer can change for a contract between the corporation and one or more of its directors, or an organization in or of which one or more of its directors are directors, officers, or legal representatives or have a material financial interest, which Minn. Stat. § 302A.255, subd. 1 addresses.

Is the company bound if the vendor knew the board had to approve?

Not necessarily. The Minnesota Supreme Court has said that every person dealing with an agent is put on inquiry and must discover whether the agent has authority. In Truck Crane Service Co. v. Barr-Nelson, Inc. (Minn. 1983), the court found the company’s conduct insufficient to show it held the employee out as having authority, and added that the president’s letter denying liability put the supplier on inquiry. In Powell v. MVE Holdings, Inc. (Minn. App. 2001), the company was bound through the CEO’s apparent authority, which traced to an earlier board-approved stock redemption at the same price and to his position as top-ranking executive. Even accepting that the seller knew board approval was needed, the court said it was unclear what he could have done to confirm it, because the board generally prepared resolutions only when a third party required them.

Does paying the first invoice ratify the contract?

It can, if the company pays with full knowledge of the material facts. In Anderson v. First Nat. Bank of Pine City (Minn. 1975), the Minnesota Supreme Court said ratification occurs when one with full knowledge of all the material facts confirms, approves, or sanctions the unauthorized act by affirmative act or acquiescence. In Cooney v. Milwaukee Mutual Insurance Co. (Minn. App. 1986), the court said a corporation may also ratify by accepting the benefits of the transaction, and the Court of Appeals has said accepting the benefits can impute the knowledge. I suggest deciding whether to keep the contract before paying under it.

Can a board ratify a contract a year after it was signed?

It can. Minnesota common law lets a principal ratify an earlier unauthorized act once it has full knowledge of the material facts. Minn. Stat. § 302A.166 adds a statutory route: from the validation effective time, unless a court determines otherwise in an action under § 302A.167, a defective corporate act ratified under the section is no longer deemed void or voidable for the failure of authorization, effective retroactively from the time of the act. The ratification must be submitted to shareholders for approval unless an exception in subdivision 4 applies, and the notice to shareholders must state the deadline for a claim that the ratified act is void or voidable due to the failure of authorization, or that a court should declare the ratification not effective or effective only on certain conditions.

What if a vice president agreed to sell nearly all the company's assets?

That deal can need more than an officer’s signature. Under Minn. Stat. § 302A.661, subd. 2, a sale of all or substantially all of a corporation’s assets outside the usual and regular course of business needs board action and a shareholder vote, unless the company keeps a significant continuing business. In Losinski v. American Dry Cleaning Co. (Minn. 1979), the court refused to find implied ratification of an officer’s option to buy the company’s main asset because the articles required a shareholder vote.

Does an LLC member's signature bind the LLC?

Not by membership alone. Minn. Stat. § 322C.0301, subd. 1 provides that a member is not an agent of a limited liability company solely by reason of being a member. Whether the member’s signature binds the company depends on the operating agreement, the company’s conduct, and any statement of authority the LLC has filed with the Minnesota Secretary of State under Minn. Stat. § 322C.0302, which affects only the LLC’s dealings with people who are not members.

Board Signing-Authority Safeguards

A Minnesota board can limit this risk before any contract is signed, because § 302A.305, subd. 1 lets a bylaw or board resolution change the CEO’s default signing duties and § 302A.351 lets a board resolution limit delegation. The cases show where those limits fail: Powell bound a company whose board kept few records, and Truck Crane turned in part on a letter the company president had sent the other side denying liability. I suggest a written signing-authority resolution with dollar limits, a list of contract types that need a board vote, and a short letter to key counterparties when an officer’s authority changes, because each step gives the company the evidence these cases turned on.

I can review a contract an officer signed without board approval against your bylaws and board resolutions and tell you whether the officer had actual authority to sign it, or draft a signing-authority resolution for your Minnesota corporation. To start, email [email protected] with a brief, general description of the situation.