Maryland Business Disputes • When a Deal Goes Wrong
Fraud vs. Breach of Contract in Maryland: When a Broken Business Deal Becomes a Fraud Claim
Key Points
- Not every broken deal is fraud. A breach of contract is a failure to do what was promised. Fraud is a false statement of fact, made knowingly or with reckless indifference to the truth, for the purpose of defrauding, that the other side relied on and had a right to rely on, causing injury.
- In Maryland, each element of fraud must be proven by clear and convincing evidence, a higher standard than the preponderance standard that applies to most contract claims.
- A promise about the future is fraud only if the person had no intention of keeping it when it was made. Maryland courts will not infer that intent from the failure to perform alone.
- Silence is generally not fraud. Absent a fiduciary relationship or another source of a duty to disclose, Maryland recognizes no general duty to disclose facts to the other side of a transaction.
- Fraud can unlock remedies a contract claim cannot, including rescission, punitive damages, and personal liability for the individuals who made the statements. Punitive damages for fraud require actual knowledge of falsity; reckless indifference is not enough.
- Contract terms matter. An integration clause does not automatically bar a fraud claim in Maryland, but it can make reliance on statements outside the contract much harder to prove.
- Fraud must be pleaded with particularity. Labeling a contract dispute as fraud without specific facts can weaken a case rather than strengthen it. Learn more about our business disputes and litigation practice.
Why the label matters
The same facts can support very different cases
When a business deal goes wrong, the injured side often feels deceived. The seller said the business was profitable and it was not. The vendor promised a delivery date it never met. The partner said the money would be used for one thing and spent it on another. Owners in that position frequently say the same thing: “This is fraud.”
Sometimes it is. Often it is a breach of contract, which is a serious claim in its own right but a different one. The distinction is not a matter of vocabulary. It changes what must be proven, how strong the proof must be, who can be sued, what the plaintiff can recover, and which defenses apply.
| Issue | Breach of contract | Fraud |
|---|---|---|
| Core question | Did a party fail to perform a contractual obligation? | Did a party knowingly or recklessly make a false statement to induce reliance? |
| Burden of proof | Generally a preponderance of the evidence | Clear and convincing evidence |
| State of mind | Generally irrelevant | Knowledge of falsity or reckless indifference, and intent to defraud |
| Who can be sued | Generally the parties to the contract | Also individuals who personally participated in the fraud |
| Punitive damages | Generally not available | Available with clear and convincing proof of actual knowledge of falsity |
| Rescission | Limited | Available for fraudulent inducement, if elected promptly |
| Effect of contract terms | The contract defines the claim | Contract terms can affect reliance but do not automatically bar the claim |
Our guide on breach of contract in Maryland and Pennsylvania covers the contract side of this comparison. This post focuses on fraud and the claims closely related to it.
Both claims can be brought together. Fraud that induces a contract is a tort that exists apart from the contract itself. In Sass v. Andrew, 152 Md. App. 406 (2003), the Court of Special Appeals explained that fraudulent inducement does not arise out of the contractual relationship because it is the wrong that induced the contract in the first place. A single lawsuit often includes a breach of contract claim and a fraud claim, pleaded in the alternative, with the evidence determining which one succeeds.
The elements of fraud in Maryland
Five elements, proven by clear and convincing evidence
Maryland’s appellate courts have stated the elements of fraud consistently for decades. As set out in Nails v. S & R, Inc., 334 Md. 398 (1994), and repeated in VF Corp. v. Wrexham Aviation Corp., 350 Md. 693 (1998), a plaintiff must prove:
- That the defendant made a false representation to the plaintiff
- That its falsity was either known to the defendant or that the representation was made with reckless indifference as to its truth
- That the misrepresentation was made for the purpose of defrauding the plaintiff
- That the plaintiff relied on the misrepresentation and had the right to rely on it
- That the plaintiff suffered compensable injury resulting from the misrepresentation
The elements must be proven by clear and convincing evidence. As the Court of Special Appeals put it in Hoffman v. Stamper (2004), quoting VF Corp., “The elements of the tort of fraud must be proven by clear and convincing evidence.” That is a meaningfully higher bar than the preponderance standard that governs most contract claims.
What each element means in a business dispute
- A false representation. The statement must be one of fact, such as revenue figures, the condition of equipment, the existence of customers, or the absence of liens or lawsuits. Vague sales talk and opinions generally do not qualify. In Goldstein v. Miles, 159 Md. App. 403 (2004), the court held that plaintiffs who relied on vague statements lacked reasonable reliance.
- Knowledge or reckless indifference. The speaker must have known the statement was false or made it with reckless indifference to whether it was true. An honest mistake is not fraud, although it may support a negligent misrepresentation or contract claim.
- Purpose of defrauding. The statement must have been made to induce the plaintiff to act.
- Reliance and the right to rely. The plaintiff must actually have relied on the statement, and the reliance must have been justifiable. A sophisticated business that had the facts in front of it, or ignored obvious warning signs, will have difficulty proving this element. Whether reliance was reasonable is often a question for the factfinder, as the court noted in Hoffman.
- Compensable injury. The plaintiff must have suffered actual damage caused by the misrepresentation.
Broken promises: when they are fraud and when they are not
Present intent, not later failure
The most common situation in which owners believe they have been defrauded involves a promise about the future: a vendor promises a delivery date, a buyer promises to make payments, or a partner promises to contribute capital. When the promise is broken, it feels like a lie.
Maryland law draws a careful line. A promise to do something in the future can support a fraud claim only if the person making it had no intention of performing at the time the promise was made. If the person intended to perform and later could not or chose not to, the claim is for breach of contract.
In Dynacorp Ltd. v. Aramtel Ltd. (2012), the Court of Special Appeals affirmed a fraudulent inducement judgment where the evidence showed that the defendant, when he promised in an operating agreement to convey a business interest, never intended to perform. The court explained that fraudulent intent may be inferred from circumstantial evidence and later conduct, but that a preexisting intent not to perform “cannot be inferred from the failure to perform the promise alone.”
Evidence that can show intent not to perform
- Statements or documents showing the person never planned to perform
- Performance that was impossible when the promise was made, and the person knew it
- Promises made to multiple parties that could not all be kept
- Immediate steps after signing that contradicted the promise
- A pattern of similar promises to others that were not kept
Nonperformance alone is not enough. A business that adds a fraud count to every breach of contract case, based only on the fact that a promise was not kept, is likely to see that count dismissed. The fraud claim requires evidence about what the defendant intended when the promise was made.
Concealment and the duty to disclose
When silence can be fraud
Fraud does not always involve an affirmative false statement. Maryland law distinguishes between active concealment of a material fact and the mere failure to disclose information. Active concealment may involve conduct or statements intended to prevent another party from discovering the truth, such as deliberately hiding a defect or diverting attention from it. Mere nondisclosure, by contrast, generally is not actionable unless the defendant had a duty to disclose the information.
In Lloyd v. General Motors Corp., 397 Md. 108 (2007), the Court of Appeals of Maryland (now the Supreme Court of Maryland) explained this distinction and recognized that fraudulent concealment may involve affirmative conduct designed to mislead, while liability for nondisclosure ordinarily requires an independent duty to speak. Whether particular conduct constitutes actionable concealment depends on the circumstances, including the defendant’s conduct, intent, the plaintiff’s justifiable reliance, and resulting damages.
No general duty to disclose
For claims based on silence rather than active concealment, the duty question is where most cases succeed or fail. The Court in Lloyd, quoting Fegeas v. Sherrill, observed that “there is no general duty upon a party to a transaction to disclose facts to the other party.” The recognized exceptions include transactions between a fiduciary and the person to whom duties are owed. In an arm’s length business transaction between unrelated parties, the party claiming concealment must identify a source of the duty to disclose.
Where a duty to disclose may arise
- Fiduciary relationships. Business partners, LLC managing members, and corporate officers and directors may owe fiduciary duties that include disclosure. See our guide on breach of fiduciary duty by a business partner.
- Contract terms. A purchase agreement may require a seller to disclose specified information, such as litigation, liabilities, or material contracts. A failure to disclose may then breach the contract regardless of whether a tort duty exists.
- Statutes and regulations. Certain transactions carry disclosure obligations imposed by law. Franchise sales are an example. See our guide on franchise agreement review.
- Active concealment. Taking steps to hide a fact, rather than simply staying silent, presents a different situation from mere nondisclosure and is evaluated on its own facts.
This is one reason buyers of a business should not rely on the seller to volunteer bad news. Representations and warranties in the purchase agreement, combined with due diligence, are far more reliable protection than a concealment claim after closing. See our guide on how to buy a business in Maryland.
Negligent misrepresentation
The claim when the statement was careless rather than knowing
When a false statement was made carelessly rather than knowingly, Maryland law may provide a claim for negligent misrepresentation. As the Court of Appeals stated in Lloyd, quoting Virginia Dare Stores v. Schuman, the plaintiff must show that:
- The defendant, owing a duty of care to the plaintiff, negligently asserted a false statement
- The defendant intended that the statement would be acted upon by the plaintiff
- The defendant had knowledge that the plaintiff would probably rely on the statement, which, if erroneous, would cause loss or injury
- The plaintiff, justifiably, took action in reliance on the statement
- The plaintiff suffered damage proximately caused by the defendant’s negligence
Negligent misrepresentation does not require proof that the defendant knew the statement was false or intended to defraud. But it does require a duty of care owed by the defendant to the plaintiff. In an arm’s length negotiation between businesses, whether such a duty exists is frequently the central dispute. Negligent misrepresentation is often pleaded alongside fraud as an alternative theory in case the evidence shows carelessness rather than knowing deception.
Contract terms that affect a fraud claim
Integration clauses, non-reliance clauses, and “as is” provisions
Most well-drafted commercial contracts contain provisions designed to limit claims based on statements made outside the written agreement. How Maryland courts treat those provisions is one of the most important, and least settled, questions in business fraud litigation.
Integration clauses
An integration clause, also called a merger or entire agreement clause, states that the written contract is the parties’ complete agreement and supersedes prior discussions. In Central Truck Center, Inc. v. Central GMC, Inc. (2010), the Court of Special Appeals affirmed summary judgment against a buyer that claimed it had been misled by financial statements provided outside the written agreement. The court relied on the integration clause, together with the unreasonableness of the buyer’s reliance on extra-contractual information, in concluding that the buyer could not establish justifiable reliance. The court was careful to add, however, that “we do not hold that an integration clause bars a claim of fraud.”
The practical result is that an integration clause does not automatically defeat a fraud claim in Maryland, but it can make the reliance element much harder to prove, particularly for a sophisticated party that negotiated the contract with counsel.
Non-reliance clauses
A non-reliance clause goes further than an integration clause. It states that a party has not relied on any representations other than those expressly set out in the contract. These clauses are common in business purchase agreements. Courts in some states give them significant weight in defeating fraud claims based on statements outside the contract. Maryland’s appellate courts have not established a definitive rule for how far a non-reliance clause bars a fraud claim, so the effect of a particular clause depends on its language, the sophistication of the parties, and the facts.
“As is” provisions
An “as is” provision allocates the risk of the condition of what is being sold to the buyer. It can affect claims about the condition of equipment, inventory, or property. Like an integration clause, it is relevant to whether reliance on a statement was justified, and its effect on a claim of actual fraud depends on the circumstances.
For buyers: if a statement matters to your decision, put it in the contract as a representation and warranty, with an indemnification remedy and a survival period. Do not rely on statements in emails, pitch decks, or meetings that the integration clause will sweep away. For sellers: integration and non-reliance clauses are valuable, but they protect best when the seller’s disclosures were accurate. They are not a license to mislead.
These provisions are especially important in business sales. See our guides on how to sell a business in Maryland, letters of intent, and earnout disputes.
Remedies: rescission, damages, and punitive damages
What a fraud plaintiff can recover
Rescission or damages: an election
A party fraudulently induced to enter a contract generally has a choice. It may rescind the contract and seek to be restored to its position before the deal, or it may keep the contract and sue for damages. In Merritt v. Craig (2000), the Court of Special Appeals, relying on decisions of the Court of Appeals, explained that these remedies are mutually exclusive and that discovery of the fraud requires the defrauded party to elect promptly whether to rescind the contract or to ratify it and claim damages.
Timing matters. The right to rescind can be waived by failing to act promptly after the facts are discovered, and conduct that ratifies the contract, such as continuing to accept its benefits, can bar rescission. Rescission generally also requires notice to the other party and a willingness to return what was received. A business that discovers fraud should get legal advice before continuing to perform.
Compensatory damages
A plaintiff that affirms the contract may recover compensatory damages proximately caused by the fraud. Maryland follows a flexible approach to fraud damages, recognizing both out-of-pocket losses and, when supported by the circumstances and evidence, benefit-of-the-bargain damages. Under the out-of-pocket measure, damages generally reflect the difference between the amount paid and the actual value received. Under the benefit-of-the-bargain measure, damages may reflect the difference between the value of what was represented and its actual value.
In Hinkle v. Rockville Motor Co., 262 Md. 502 (1971), the Court of Appeals recognized this flexible approach, with the appropriate measure depending on the nature of the transaction and the certainty of the proof. Additional consequential losses may also be recoverable when sufficiently established and legally attributable to the fraud. A business buyer should therefore evaluate both available measures rather than assume recovery is limited to the difference between the purchase price and actual value.
Punitive damages
Punitive damages are generally not available for breach of contract. They can be available for fraud, but Maryland sets a high bar. The Court of Appeals in Owens-Illinois, Inc. v. Zenobia, 325 Md. 420 (1992), required clear and convincing evidence to support punitive damages. In Ellerin v. Fairfax Savings, F.S.B., 337 Md. 216 (1995), the Court of Appeals held that punitive damages in a fraud action require actual knowledge that the representation was false, coupled with an intent to deceive. Reckless indifference to the truth, although sufficient to establish liability for compensatory damages, is not enough to support punitive damages. The Court reaffirmed this distinction in Hoffman v. Stamper, 385 Md. 1 (2005), explaining that punitive damages require conscious and deliberate wrongdoing. The requisite state of mind must be established by clear and convincing evidence.
Why this matters for strategy. The possibility of punitive damages and personal liability is often what gives a fraud claim settlement value that a contract claim lacks. But that leverage exists only if the evidence can meet the clear and convincing standard. Overstating a fraud claim can reduce credibility with the court and the other side.
Attorney’s fees
Maryland follows the American Rule: each side generally pays its own attorney’s fees unless a contract or statute provides otherwise. A fraud claim does not by itself shift fees. See our post on the cost of business litigation in Maryland.
Personal liability of owners and officers
The corporate form does not shield an individual’s own fraud
A breach of contract claim is generally limited to the parties to the contract, which is usually the company. Fraud is different. Under longstanding Maryland law, an officer or agent who personally participates in a tort committed by the corporation can be held personally liable for it.
The Court of Special Appeals summarized the rule in Shipley v. Perlberg (2001), quoting Levi v. Schwartz, 201 Md. 575 (1953): an officer “who takes part in the commission of a tort by the corporation is personally liable therefor.” The court also relied on Tedrow v. Deskin, 265 Md. 546 (1972), which requires that the officer have been a participant in the wrongful act. Mere status as an officer, director, or owner is not enough, and an officer is generally not liable for torts of which the officer had no knowledge and to which the officer did not consent.
This is a different question from piercing the corporate veil. Veil piercing seeks to hold owners liable for the company’s obligations because of how the company was used. Personal liability for fraud rests on the individual’s own conduct. See our guide on piercing the corporate veil for the difference.
For owners and officers. If you sign contracts, sign disclosure schedules, or make statements to buyers, lenders, investors, or customers on your company’s behalf, the accuracy of those statements is your personal responsibility. Our guide on indemnification of officers and directors explains the protections that may be available, and their limits.
Deadlines for fraud claims
Three years, measured from discovery
Most civil claims in Maryland, including fraud, are subject to the general three-year limitations period in Courts and Judicial Proceedings Section 5-101. Maryland applies a discovery rule, under which a claim generally accrues when the plaintiff knew or reasonably should have known of the wrong. That rule matters in fraud cases because the wrong is, by definition, often concealed.
Courts and Judicial Proceedings Section 5-203 also provides that if a party is kept in ignorance of a cause of action by the fraud of the adverse party, the cause of action is deemed to accrue when the party discovered, or by the exercise of ordinary diligence should have discovered, the fraud.
The discovery rule is not a reason to wait. Once a business has reason to suspect fraud, the clock may be running, and a delay in acting can also waive the right to rescind. See our guide to Maryland statutes of limitations for business claims for a full discussion.
Pleading fraud: specificity and the risk of overreaching
Who said what, when, and why it was false
Fraud must be pleaded with particularity. In Maryland state court, the Court of Special Appeals has held in McCormick v. Medtronic, Inc., 219 Md. App. 485 (2014), that a fraud claim must identify who made the false statement, what was said, when and how it was made, why it was false, and facts supporting the defendant’s knowledge and intent. In federal court, Federal Rule of Civil Procedure 9(b) imposes a similar requirement. Conclusory allegations that a defendant “lied” or “acted fraudulently” are not enough.
The risk of overreaching
Adding a fraud count to a contract case has costs as well as benefits:
- A fraud claim without specific supporting facts is likely to be dismissed early, which can weaken the plaintiff’s credibility for the rest of the case.
- Fraud allegations against individuals often harden positions and make settlement more difficult.
- Maryland Rule 1-341 allows a court to award expenses, including attorney’s fees, against a party that maintains or defends a proceeding in bad faith or without substantial justification.
- Fraud claims generally require more discovery into intent, which increases cost.
The better approach is to assess the evidence first. If the facts support fraud, plead it carefully. If they support only a breach, a well-pleaded contract claim is often the stronger case. Our Maryland business litigation guide explains how cases proceed from the first demand through trial.
Fraud claims and arbitration clauses
Who decides a claim that the whole contract was induced by fraud
A party that claims it was fraudulently induced to sign a contract sometimes argues that the contract’s arbitration clause should not apply, because the entire contract was obtained by fraud. Under the separability principle the Supreme Court adopted in Prima Paint Corp. v. Flood & Conklin Manufacturing Co., 388 U.S. 395 (1967), a claim that the contract as a whole was induced by fraud generally goes to the arbitrator, while a claim that the arbitration clause itself was induced by fraud is for the court. The Court of Appeals applied the same separability concept in treating an arbitration agreement as separate from the broader contract in Cheek v. United Healthcare of the Mid-Atlantic, Inc. (2003).
In practice, this means a fraud claim does not by itself get a dispute out of arbitration. See our guide on arbitration versus litigation for Maryland business disputes.
How to protect your business
Before signing and after something goes wrong
Before signing
- Put important statements in the contract. Revenue, customer relationships, liabilities, litigation, and the condition of assets should be addressed in written representations and warranties.
- Add a remedy. Representations without an indemnification provision, survival period, and escrow or holdback may be difficult to enforce in practice.
- Verify. Due diligence makes reliance reasonable and catches problems before closing. A buyer that could easily have discovered the truth may struggle to prove justifiable reliance.
- Read the integration and non-reliance clauses. Understand what they exclude before signing.
- Document the negotiation. Keep copies of the financial statements, disclosure schedules, and communications that led to the deal.
After discovering a possible fraud
- Preserve evidence. Save emails, texts, financial records, and documents exchanged during the deal, and stop routine deletion.
- Do not ratify the deal without advice. Continuing to perform or accepting benefits may affect the right to rescind.
- Review the contract. Look at the representations, indemnification, notice, survival, limitation of liability, dispute resolution, and fee provisions.
- Calendar deadlines. Contractual notice periods for indemnification claims can be much shorter than the statute of limitations.
- Assess the evidence of intent. The decision whether to plead fraud should be based on evidence of what the other side knew and intended, not on the size of the loss.
- Consider who is collectable. Personal liability for participating individuals can matter if the company has no assets.
For a business that has been accused of fraud, see your business has been sued in Maryland: what to do now.
Common mistakes
The avoidable errors
- Calling every broken promise fraud. A promise is fraud only if there was no intent to perform when it was made, and that intent cannot be inferred from nonperformance alone.
- Relying on statements outside the contract. An integration clause can make reliance on emails, pitch materials, and conversations very difficult to prove.
- Assuming silence is fraud. Without a duty to disclose, nondisclosure in an arm’s length deal is generally not actionable.
- Waiting too long to decide whether to rescind. Delay and continued performance can waive rescission.
- Pleading fraud without specifics. Conclusory allegations invite dismissal and can damage credibility.
- Overestimating punitive damages. Maryland requires clear and convincing proof of actual knowledge of falsity.
- Forgetting the individuals. Officers and owners who personally made false statements may be liable even if the company is not collectable.
- Missing contractual notice deadlines. Indemnification claims often must be asserted within a survival period much shorter than three years.
How Iqbal Business Law can help
We represent Maryland and Pennsylvania businesses and owners on both sides of fraud and contract disputes: companies that believe they were misled into a deal, and companies and individuals accused of fraud. Because our practice includes business transactions as well as disputes, we also draft the representations, warranties, and indemnification provisions that prevent these disputes in the first place. Our work includes:
- Early evaluation of whether the facts support fraud, negligent misrepresentation, breach of contract, or some combination
- Pursuing and defending fraudulent inducement, concealment, and misrepresentation claims
- Rescission claims and post-closing disputes in business purchases and sales
- Defending owners and officers against personal liability claims
- Indemnification claims under purchase agreements
- Drafting representations, warranties, disclosure schedules, integration and non-reliance clauses, and indemnification provisions
- Ongoing contract and transaction support as outside general counsel
We serve companies throughout Maryland from our offices in Thurmont and Rockville, including clients in Rockville, Bethesda, Gaithersburg, Silver Spring, Frederick, Montgomery County, Frederick County, and the I-270 corridor, and we are licensed in Maryland and Pennsylvania.
Related reads and resources
Cases
- Hoffman v. Stamper, No. 560, Sept. Term 2002 (Md. Ct. Spec. App. Feb. 27, 2004) (elements of fraud; clear and convincing evidence)
- Dynacorp Ltd. v. Aramtel Ltd., No. 1077, Sept. Term 2011 (Md. Ct. Spec. App. Nov. 28, 2012) (promissory fraud)
- Lloyd v. General Motors Corp., No. 10, Sept. Term 2002 (Md. Feb. 8, 2007) (concealment; negligent misrepresentation)
- Central Truck Center, Inc. v. Central GMC, Inc., No. 1780, Sept. Term 2008 (Md. Ct. Spec. App. Sept. 7, 2010) (integration clause and reliance)
- Merritt v. Craig, No. 5831, Sept. Term 1998 (Md. Ct. Spec. App. Feb. 2, 2000) (rescission or damages)
- Le Marc Management Corp. v. Valentin (Md. 1998) (punitive damages standard for fraud under Ellerin)
- Shipley v. Perlberg, No. 1479, Sept. Term 2000 (Md. Ct. Spec. App. Sept. 6, 2001) (personal liability of officers)
Related Iqbal Business Law insights
- Breach of Contract in Maryland and Pennsylvania
- The Maryland Business Litigation Guide
- Maryland Statutes of Limitations for Business Claims
- How to Buy a Business in Maryland: A Due Diligence Guide
- How to Sell a Business in Maryland
- Piercing the Corporate Veil in Maryland and Pennsylvania
- Breach of Fiduciary Duty by a Business Partner in Maryland
- Arbitration vs. Litigation for Maryland Business Disputes
FAQ
What is the difference between fraud and breach of contract?
A breach of contract is a failure to perform a contractual obligation. Fraud is a false representation of fact, made with knowledge of its falsity or reckless indifference to its truth, for the purpose of defrauding, that the plaintiff relied on and had a right to rely on, causing injury. In Maryland, fraud must be proven by clear and convincing evidence. Fraud can support remedies a contract claim generally cannot, including punitive damages and personal liability for individuals who participated, while a contract claim is often simpler to prove.
Is breaking a promise fraud in Maryland?
Usually not. A broken promise is ordinarily a breach of contract. A promise about the future can support a fraud claim only if the person had no intention of performing when the promise was made. In Dynacorp Ltd. v. Aramtel Ltd., the Court of Special Appeals explained that intent may be inferred from circumstantial evidence and later conduct, but cannot be inferred from the failure to perform alone.
What do you have to prove to win a fraud case in Maryland?
The plaintiff must prove, by clear and convincing evidence, that the defendant made a false representation; that the defendant knew it was false or made it with reckless indifference to its truth; that it was made for the purpose of defrauding the plaintiff; that the plaintiff relied on it and had the right to rely on it; and that the plaintiff suffered compensable injury as a result.
Can I sue someone for not telling me something?
Sometimes. Maryland law distinguishes active concealment, meaning conduct intended to prevent the other party from discovering the truth, from mere nondisclosure. Mere nondisclosure generally is not actionable unless the defendant had a duty to disclose. Maryland recognizes no general duty to disclose facts to the other party to a transaction. A duty may arise from a fiduciary relationship, a contract term, or a statute, and active steps to hide a fact are evaluated differently from mere silence. In an arm’s length business deal, buyers are better protected by written representations and due diligence than by a concealment claim.
Does an integration clause prevent a fraud claim?
Not automatically. In Central Truck Center v. Central GMC, the Court of Special Appeals relied on an integration clause in holding that a buyer could not show justifiable reliance on statements outside the agreement, but stated that it did not hold that an integration clause bars a claim of fraud. The clause can make reliance on extra-contractual statements much harder to prove, particularly for sophisticated parties. The effect of a broader non-reliance clause in Maryland has not been definitively settled.
Can I get punitive damages for fraud in Maryland?
Possibly, but the standard is demanding. Punitive damages require clear and convincing evidence, and in a fraud case the Court of Appeals held in Ellerin v. Fairfax Savings that the defendant must have had actual knowledge that the statement was false. Reckless indifference to the truth can support compensatory damages for fraud but not punitive damages.
Can the owner or officer of a company be personally liable for fraud?
Yes, if the individual personally participated. Under Maryland law, an officer or agent who takes part in the commission of a tort by the corporation can be held personally liable for it. Being an owner or officer is not enough by itself; the individual must have participated in the wrongful act. This is separate from piercing the corporate veil.
Should I rescind the contract or sue for damages?
It depends on the deal and what you want. Rescission seeks to unwind the transaction and restore the parties to their original positions; damages leave the contract in place and compensate for the loss. Maryland treats the two as mutually exclusive and requires a prompt election once the fraud is discovered. Continuing to perform or accepting benefits can be treated as ratification. Get legal advice before taking further action under the contract.
How long do I have to file a fraud claim in Maryland?
Generally three years under Courts and Judicial Proceedings Section 5-101, measured from when the plaintiff knew or reasonably should have known of the wrong. Section 5-203 provides that when a party is kept in ignorance of a claim by the adverse party’s fraud, the claim accrues when the fraud was discovered or should have been discovered with ordinary diligence. Contractual deadlines for indemnification claims may be much shorter.
Does a fraud claim get me out of an arbitration clause?
Generally not. Under the separability principle from Prima Paint Corp. v. Flood and Conklin Manufacturing Co., a claim that the entire contract was induced by fraud is generally for the arbitrator to decide. Only a claim that the arbitration clause itself was induced by fraud is ordinarily decided by a court.
Yawar B. Iqbal is a Maryland and Pennsylvania business attorney and the founder of Iqbal Business Law. He represents business owners and companies in business disputes, commercial contracts, acquisitions and sales of operating businesses, formation and corporate governance matters, franchisee representation, and IRS and Maryland tax controversies.
Disclaimer: This post is for general informational and educational purposes only and does not constitute legal advice. The cases and statutes described here are current as of the date of this post and may change, and whether particular facts support a claim for fraud, concealment, negligent misrepresentation, or breach of contract depends on the specific circumstances and contract terms. Reading this post does not create an attorney-client relationship with Iqbal Business Law. If you believe your business was misled in a transaction, or your business has been accused of fraud, consult a qualified Maryland attorney promptly, because deadlines to rescind, give contractual notice, and file suit can be short.



