Mini Case Solutions Corporate Finance 10 Edition

Navigating Mini Case Solutions Corporate Finance 10 Edition: What Actually Works

If you're working through Corporate Finance by Ross, Westerfield, and Jordan (10th edition), the mini cases scattered at the end of chapters can trip people up. They're different from the standard end-of-chapter problems. The math itself is usually straightforward. The trap is in how the questions are framed and what the instructors actually expect you to show. The mini cases are short applied scenarios. They don't just ask for a calculation. They want you to interpret a number in context, make a recommendation, and sometimes deal with messy real-world assumptions. A standard NPV problem asks you to compute one value. A mini case might give you three years of projected cash flows that include working capital changes, a salvage value with tax implications, and ask whether the project should proceed under two different scenarios. I've seen students spend 45 minutes on a mini case that should take 15 if they just knew how to structure it properly. Most of the time loss comes from missing something in the problem setup rather than struggling with the actual computation. The Excel work is usually ten minutes of work if you're comfortable with the formulas.

The solutions for these cases are not always available in the back of the textbook. Sometimes they're in a separate instructor resource manual. Sometimes your professor posts them on Canvas. The ones that circulate online are hit or miss on accuracy, and I'd recommend cross-checking any free version you find against your own work rather than just copying it.

How to Actually Work Through These Cases Step by Step

Start by identifying every cash flow the problem gives you. Write them out in a table before you touch Excel or a financial calculator. The mini cases deliberately bury numbers in paragraphs. I once had a case where the terminal year included both a recovery of net working capital AND a tax on the sale of equipment, and both were mentioned only in passing sentences. If you miss one, your final answer looks wrong and you can't figure out where the error came from. Here's a specific edge case I ran into recently. The problem stated that a machine would be sold at the end of Year 4 for $120,000, with an original cost of $200,000 and accumulated depreciation of $160,000. Standard approach is to calculate the book value, find the gain or loss, apply the tax rate, and adjust the salvage cash flow. But the problem also said the company could use the proceeds to reduce a loan balance rather than receive the cash directly. That changes the after-tax cash flow because you're saving interest expense rather than getting a check. The tax shield on the loan interest is essentially a separate cash flow you have to add. I spotted this by actually reading the sentence twice and then asking a straightforward question: who gets the money and in what form. The workaround was to model it as two lines—one for the after-tax salvage value and one for the interest savings over the remaining loan period. Took three extra cells in Excel and five minutes. After you've extracted the cash flows, set up your discount rate carefully. The textbook usually tells you to use WACC for these cases, but check whether the risk profile of the project matches the firm's overall risk. If the mini case is about a new product line in a completely different market, the beta and cost of equity might shift. Some professors build that into the case as a subtle testing point. If the problem doesn't give you enough information to recompute WACC, stick with the given rate but note the assumption in your write-up. That alone often distinguishes an average answer from a strong one.

Run the NPV, IRR, payback period, and profitability index if the case asks for them. Don't skip any just because one number seems obvious. The mini cases love to set up a situation where NPV says accept and IRR says reject, usually because of non-conventional cash flows or mutually exclusive projects. That tension is the whole point of the question. If both numbers agree, you might be looking at a simpler case than you think. Write up your answer in plain language. The calculation is half the grade. The other half is whether you can explain what the number means for the decision. I've graded enough of these to tell you that a student who writes "NPV is $47,000 so we should accept" loses points. A student who writes "The positive NPV of $47,000 indicates the project adds value above the required return of 12 percent, assuming the cash flow estimates are accurate" gets full credit. The difference is one sentence. That sentence costs nothing to write and saves you from looking like you don't understand the concept.

Where People Mess Up and How to Avoid It

The most common mistake with these cases is treating the numbers as purely mathematical without questioning the assumptions baked into them. Mini cases sometimes include irrelevant information on purpose. You need to identify what to ignore just as much as what to use. A mention of a past sunk cost of $50,000 spent on market research is not part of your cash flow analysis. I've seen students add it in anyway because they thought they were supposed to use everything in the problem. They weren't. Another pitfall is messing up the timing of cash flows. Everything happens at the end of the period unless the problem explicitly says otherwise. Inflation adjustments, tax payments, and working capital recoveries all have specific timing conventions that your professor expects you to follow. If you discount a mid-year cash flow as if it's end-of-year, your NPV will be off by a meaningful amount. For most mini cases in this textbook, the convention is strict end-of-period timing, and deviating from it without being asked will hurt your grade. There's also a stubborn habit of rounding too early. If you round your intermediate NPV or annuity factor to two decimal places, your final answer can drift by several thousand dollars on a larger case. Keep at least four decimal places through the calculation and round only at the very end. This isn't pedantry. It's the difference between an answer that matches the solution manual and one that looks like you made a calculation error.

Getting the Solutions Right

If you need to check your work against Mini Case Solutions Corporate Finance 10 Edition, look for versions posted by your course materials store, your university's academic resource center, or the official solutions manual that accompanies the textbook. The publisher typically lists the ISBN for the correct edition, so verify that before downloading anything. Incorrect editions exist where the cash flow numbers differ slightly between prints, and using a solution from a different edition will lead you down the wrong path. Free versions floating around the internet are frequently incorrect or incomplete. The people uploading them sometimes solved them themselves with errors, and other times they're partial answers that skip the discussion portions. I once used a free solution that had the right NPV but calculated the IRR incorrectly because they mistakenly used cash flows from Year 2 as if they occurred in Year 1. That kind of error is invisible unless you redo the problem yourself. The honest workaround is to solve the case first on your own, then compare your work to the solution to find where you diverged. That takes longer upfront but trains you for the exam, where you won't have access to any solution manual. If you're pressed for time, at least get the structure of your answer right before looking at the key. Don't read the solution first and then pretend you worked through it independently. Professors can tell when someone's explanation matches the solution wording exactly but doesn't reflect genuine understanding of the steps.

When the Mini Case Approach Doesn't Work

There are scenarios where the standard textbook method breaks down. If the mini case involves real options, scenario analysis with correlated variables, or sensitivity testing across multiple inputs simultaneously, the basic NPV framework from the earlier chapters isn't sufficient. You'll need to build a more elaborate model, sometimes incorporating Monte Carlo simulation or decision trees. The 10th edition touches on these topics later in the book, but if your course is moving fast, you might encounter them before you've fully covered the advanced material. In those situations, the best approach is to map out the decision nodes and probability branches on paper first, then translate that structure into Excel. The formula-heavy approach fails here because the relationships aren't linear. I've had cases where changing one assumption shifted the optimal decision entirely, and a standard sensitivity table didn't capture that because it only changed one variable at a time. Building a simple @RISK or even a manual scenario grid in Excel handles this better than trying to force a single NPV calculation to do all the work. Another limitation worth noting: these mini cases assume perfect capital markets in most of their setups. They don't typically account for transaction costs, asymmetric information, or financing constraints that would change the decision in practice. That's fine for a classroom exercise. It's not fine if you're applying the same logic to an actual corporate investment without adjusting for those frictions. Keep the distinction clear in your head and in your write-up if the professor asks about real-world applicability.

Bottom line, these cases are designed to test whether you can connect the finance tools to a coherent business decision. The math is the easy part. The writing, the assumption checking, and the ability to spot what's irrelevant are where most of the learning happens. Treat them that way and you'll save yourself a lot of unnecessary stress.