Latest / VoraPrep Audio — Professional Licensure & Certification Exam Prep / [CMA] CMA1: Contingencies and Subsequent Events: Applying ASC 450 and 855
Transcript
- Hey, welcome to VoraPrep Audio. Glad you could tune in. Today we're talking about one of those topics that can feel a little gray, a little subjective, but the exam questions are actually very black-and-white if you know the rules. We're covering contingencies and subsequent events. And this stuff really matters. Imagine you’re the management accountant at a big pharmaceutical company. A huge lawsuit has just been filed against your flagship drug. We're talking hundreds of millions of dollars on the line. What do you do? Do you book a massive loss right now and watch the stock price tank? Do you just add a quiet little footnote and cross your fingers? Getting this wrong isn't just bad accounting; it can trigger SEC investigations and a total collapse in investor trust. So, let’s get the rules straight, using ASC 450 and 855. The whole idea behind these rules is something you already know: conservatism. It’s a core principle of accounting. And it basically says: anticipate your losses, but don't count your chickens before they hatch. Don't recognize gains until they're real. We'll see this theme play out over and over. Let's start with loss contingencies. Think lawsuits, warranty claims, things that might cost you money later. For you to actually record a loss on your books—to accrue it—you have to meet a strict two-part test as of the balance sheet date. BOTH parts have to be true. First, the loss has to be probable. This means it's likely to happen. Not just a 50/50 chance, but probable. Your lawyers are saying, "Yeah, this doesn't look good for us." Second, the amount of the loss has to be reasonably estimable. You need to be able to put a reliable number on it. It doesn't have to be perfect, down to the penny, but you need a solid estimate. If you can check both of those boxes—it's probable AND it's estimable—then you have to make a journal entry. You'd debit a loss account and credit an estimated liability. Simple as that. Now, what about that estimate? Sometimes management has a single best number in mind. Great, you use that. But often, especially with lawsuits, your legal team will give you a range. They might say, "We think the damages will be somewhere between two and five million dollars." If they can't point to one number in that range as being more likely than any other, what do you do? You book the minimum. That’s conservatism in action. You book the two million, because that's the loss you know is probable. Then, in the footnotes, you'd disclose that the loss could potentially be as high as five million. Let’s walk through a classic exam scenario. Nova Manufacturing is being sued for patent infringement. It’s December 31st, their year-end. Their lawyers tell them it is probable they will lose the case. They also say the damages will be between $2 million and $5 million, but they can't narrow it down any further. What should Nova do? Let’s use a little framework. First, classify the event. It’s a potential loss. Okay. Second, apply the probability test. Is the loss probable? Yes, the lawyers said so. That’s our first green light. Third, apply the estimability test. Can we estimate it? Yes, we have a range: two to five million. That’s our second green light. So, we have to accrue. But for how much? Since we have a range with no single best estimate, we have to use the minimum. That's two million dollars. The journal entry would be a debit to Litigation Loss for two million, and a credit to Estimated Litigation Liability for two million. You'd also add a note to the financial statements explaining the lawsuit and the full potential range of the loss. A common wrong answer on the exam might be zero, or maybe the average of the range. If you picked zero, you probably confused 'probable' with 'reasonably possible'—we'll get to that in a second. And if you picked the average, you forgot the specific rule from ASC 450: when there’s a range, you book the minimum. Okay, so that's how we handle potential losses. What about potential gains? What if *we're* the ones suing someone else, and our lawyers say it's probable we'll win? This is where that conservatism principle really shows its teeth. The rule for gain contingencies is simple: you NEVER accrue them. Ever. Not until the money is actually in your hands. Recognizing a gain before it's a sure thing would overstate your income and your assets, and that's a big no-no. So, if a gain is probable, you can disclose it in the footnotes, but you have to be careful not to mislead anyone. You don’t book a single dollar of revenue until that contingency is resolved and the gain is realized. Now let's shift gears slightly to subsequent events. These are things that happen *after* the balance sheet date, but *before* you issue the financial statements. The key question here is: does this new event tell me something about a condition that *already existed* on my balance sheet date? I like to think of the balance sheet date as a snapshot, a high-resolution photo of the company's financial health on that one day. A Type 1 subsequent event is like finding out the camera lens was blurry when you took the picture. It reveals a flaw that was already there. For example, let's say on December 31st, you have a huge accounts receivable from a major customer. Then, in January, that customer declares bankruptcy. That bankruptcy confirms that your receivable was probably worthless back on December 31st. The problem already existed. So you have to go back and *adjust* your original photo—your financial statements. You’d increase your allowance for doubtful accounts. A Type 2 subsequent event is different. This is like the subject of your photo getting struck by lightning *after* you took the picture. The original photo is still accurate for that moment in time. For instance, if your factory burns down in February, well, it was perfectly fine on December 31st. That's a new condition. You wouldn't go back and change your December 31st balance sheet. But, because it’s a major event, you would disclose it in the footnotes so investors know what happened. So, for subsequent events, just ask yourself: does this new information relate to a condition that existed back then, or is this a brand new thing? If it existed back then, it's Type 1 and you adjust. If it’s a new thing, it's Type 2 and you just disclose. One of the biggest traps on the exam is confusing 'probable' with 'reasonably possible'. You'll see a question where a loss is described as 'reasonably possible,' and they'll give you a very precise, estimable number, like '$1 million'. It's so tempting to want to accrue that million dollars. But you can't. If a loss is only reasonably possible, it doesn't matter how well you can estimate it. You do not accrue it. It is a disclose-only event. Period. Probability is the first and most important hurdle. To keep it all straight, especially under exam pressure, you can use a little memory aid for losses. Just think PER: P-E-R. First, P for Probable. Is the loss probable? If yes, you move to the next letter. If no, but it's reasonably possible, you stop right there and just disclose. If it's remote, you usually do nothing. If it *is* probable, you move to E for Estimable. Can you reasonably estimate the amount? If yes, you accrue it. If no, you can't put a number on it, so you just disclose. Finally, if you can estimate it, you move to R for Range. Is there a range with no single best estimate? If yes, you accrue the minimum amount in the range. P-E-R. Probable? Estimable? Range? It's a simple decision tree that walks you right to the correct answer and reinforces that core idea: accrue losses early, recognize gains late. If you’re looking for a way to drill these concepts with practice questions and get instant feedback, check out VoraPrep. VoraPrep is a full exam-prep app — lessons, practice questions, and an AI tutor in one place. You can get started over at Vora Prep dot com. It’s free to try. So on exam day, when you see one of these scenarios, just take a breath. Apply that disciplined, two-part test for losses. First, is it probable? Only after you answer that question do you worry about whether it's estimable. Don't let a well-defined number distract you if the probability isn't there. You've got this. Thanks for studying with me today. Keep up the great work, and I'll catch you on the next one.