<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Excel 365 on Ask Eijaz</title><link>https://askeijaz.com/categories/excel-365/</link><description>Recent content in Excel 365 on Ask Eijaz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0530</lastBuildDate><atom:link href="https://askeijaz.com/categories/excel-365/index.xml" rel="self" type="application/rss+xml"/><item><title>Build an ASC 842 Lease Modification Tracker That Auto-Remeasures Liabilities and ROU Assets</title><link>https://askeijaz.com/blog/build-an-asc-842-lease-modification-tracker-that-auto-remeasures-liabilities-and-rou-assets/</link><pubDate>Thu, 27 Aug 2026 00:00:00 +0530</pubDate><guid>https://askeijaz.com/blog/build-an-asc-842-lease-modification-tracker-that-auto-remeasures-liabilities-and-rou-assets/</guid><description>&lt;h2 id="who-this-quietly-bites"&gt;Who this quietly bites&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;re in corporate accounting, FP&amp;amp;A, or audit, you&amp;rsquo;ve seen this: a 60-month office lease gets renewed at month 36. The discount rate changes from 5.5% to 6.2%. The monthly payment jumps from $5,000 to $5,500. Under ASC 842, this is a &lt;strong&gt;modification&lt;/strong&gt; — and it triggers a full remeasurement of both the lease liability and the right-of-use (ROU) asset.&lt;/p&gt;</description></item><item><title>Build an ASC 606 Contract Modification Engine That Auto-Classifies and Calculates Catch-Up Adjustments</title><link>https://askeijaz.com/blog/build-an-asc-606-contract-modification-engine-that-auto-classifies-and-calculates-catch-up-adjustments/</link><pubDate>Wed, 26 Aug 2026 03:17:00 +0530</pubDate><guid>https://askeijaz.com/blog/build-an-asc-606-contract-modification-engine-that-auto-classifies-and-calculates-catch-up-adjustments/</guid><description>&lt;h2 id="who-this-quietly-bites"&gt;Who this quietly bites&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Separate contract&lt;/strong&gt; — if the new goods are distinct AND the price is commensurate with standalone selling prices.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prospective&lt;/strong&gt; — if goods are distinct but the price isn&amp;rsquo;t commensurate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cumulative catch-up&lt;/strong&gt; — if the goods aren&amp;rsquo;t distinct at all.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Here&amp;rsquo;s the problem: most finance teams classify these in email threads, sticky notes, or separate Word docs. The amortization schedule gets rebuilt manually in a new tab. Six months later, no one remembers why the numbers changed — and the catch-up adjustment that surprises the CFO in Q3 was actually a Q1 modification that was never properly documented.&lt;/p&gt;</description></item><item><title>Build a Loan Amortization Schedule in One Formula (No Helper Columns)</title><link>https://askeijaz.com/blog/build-a-loan-amortization-schedule-in-one-formula-no-helper-columns/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/build-a-loan-amortization-schedule-in-one-formula-no-helper-columns/</guid><description>&lt;p&gt;Okay, real talk: almost every loan amortization schedule in the wild is held together with hope. You type &lt;code&gt;PMT&lt;/code&gt; once, work out the interest and principal for row one, then drag the whole thing down 360 rows and call it a mortgage. It looks authoritative. It even reconciles to the penny — right up until someone inserts a row to add a note, changes the term from 30 years to 15, or refinances halfway through, and the entire ladder quietly comes apart at the seams.&lt;/p&gt;</description></item><item><title>Why Your NPV Is Wrong (and the XNPV Fix Analysts Swear By)</title><link>https://askeijaz.com/blog/why-your-npv-is-wrong-and-the-xnpv-fix-analysts-swear-by/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/why-your-npv-is-wrong-and-the-xnpv-fix-analysts-swear-by/</guid><description>&lt;p&gt;Okay, real talk: &lt;code&gt;=NPV(rate, values)&lt;/code&gt; is one of the most confidently wrong formulas in corporate finance. You select your cash flows, type the function, get a clean dollar figure, drop it in the board deck — and you&amp;rsquo;ve just discounted your entire project by one period too many. Excel&amp;rsquo;s &lt;code&gt;NPV&lt;/code&gt; assumes the &lt;em&gt;first&lt;/em&gt; number in your range arrives one full period from today, not today. Feed it your day-one capital outlay and it dutifully discounts money you&amp;rsquo;re spending &lt;em&gt;right now&lt;/em&gt; as if it happens next year. The result is off by thousands, and it never once shows an error.&lt;/p&gt;</description></item><item><title>Build a Dropdown List That Removes Items Once They're Picked</title><link>https://askeijaz.com/blog/build-a-dropdown-list-that-removes-items-once-theyre-picked/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/build-a-dropdown-list-that-removes-items-once-theyre-picked/</guid><description>&lt;p&gt;Here&amp;rsquo;s a sentence that should never be true, and yet: &amp;ldquo;Wait, didn&amp;rsquo;t we already give Laptop-04 to someone else?&amp;rdquo; Two people picked the same item from the same dropdown, on the same sheet, and Excel didn&amp;rsquo;t say a word — because a standard Data Validation list doesn&amp;rsquo;t know or care what&amp;rsquo;s already been chosen in the cells around it. It just shows the same static list, forever, to everyone. Fixing that isn&amp;rsquo;t hard once you know the trick, but almost nobody stumbles onto it by accident.&lt;/p&gt;</description></item><item><title>Fix Top-N Lists That Duplicate a Name When Scores Tie</title><link>https://askeijaz.com/blog/fix-top-n-lists-that-duplicate-a-name-when-scores-tie/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/fix-top-n-lists-that-duplicate-a-name-when-scores-tie/</guid><description>&lt;p&gt;Picture this: you build a &amp;ldquo;Top 5 Sales Reps&amp;rdquo; report with the classic &lt;code&gt;LARGE&lt;/code&gt; + &lt;code&gt;MATCH&lt;/code&gt; combo, send it out, and someone replies &amp;ldquo;hey, why am I not on here? I &lt;em&gt;know&lt;/em&gt; I beat Dana this month.&amp;rdquo; You check the raw numbers — they&amp;rsquo;re right, they tied with a teammate for third place. Your report doesn&amp;rsquo;t show them twice, and it doesn&amp;rsquo;t show an error. It just quietly shows their teammate&amp;rsquo;s name &lt;strong&gt;twice&lt;/strong&gt; instead, and their name never appears anywhere. That&amp;rsquo;s not a data problem. That&amp;rsquo;s &lt;code&gt;MATCH&lt;/code&gt; doing exactly what it&amp;rsquo;s documented to do — and it&amp;rsquo;s almost never what you want.&lt;/p&gt;</description></item><item><title>How to Find the LAST Matching Value (Not the First) in a List</title><link>https://askeijaz.com/blog/how-to-find-the-last-matching-value-not-the-first-in-a-list/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/how-to-find-the-last-matching-value-not-the-first-in-a-list/</guid><description>&lt;p&gt;Quick gut-check: if the same Order ID, ticket number or SKU shows up more than once in your data — because you log every status change instead of overwriting it — what does &lt;code&gt;VLOOKUP&lt;/code&gt; hand you back? Not the current status. The &lt;em&gt;oldest&lt;/em&gt; one. Every single time. It&amp;rsquo;s one of the sneakiest, most common lookup mistakes in Excel, and almost nobody notices it&amp;rsquo;s happening because the formula never throws an error — it just confidently reports yesterday&amp;rsquo;s news as today&amp;rsquo;s truth.&lt;/p&gt;</description></item><item><title>Tiered Commission Formulas in Excel 365: Why VLOOKUP Gets It Wrong</title><link>https://askeijaz.com/blog/tiered-commission-formulas-in-excel-365-why-vlookup-gets-it-wrong/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://askeijaz.com/blog/tiered-commission-formulas-in-excel-365-why-vlookup-gets-it-wrong/</guid><description>&lt;p&gt;Okay, real talk: if you&amp;rsquo;ve ever built a commission plan, a bulk-discount schedule or a tax provision in Excel, you&amp;rsquo;ve probably written this exact formula — a &lt;code&gt;VLOOKUP&lt;/code&gt; against a tier table. It looks confident. It returns a nice, clean number. And that number is quietly, cheerfully wrong, because it slaps one rate on the &lt;em&gt;entire&lt;/em&gt; amount instead of giving each &lt;em&gt;slice&lt;/em&gt; of it the rate it actually earned. Sales ops, RevOps and finance folks run into this all the time and don&amp;rsquo;t even notice, because the formula never errors out — it just over- or underpays and smiles about it.&lt;/p&gt;</description></item></channel></rss>