<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spreadsheet Skills on Ask Eijaz</title><link>https://askeijaz.com/series/spreadsheet-skills/</link><description>Recent content in Spreadsheet Skills on Ask Eijaz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://askeijaz.com/series/spreadsheet-skills/index.xml" rel="self" type="application/rss+xml"/><item><title>Excel 365: How to Find the LAST Matching Value (Not the First) in a List</title><link>https://askeijaz.com/blog/excel-365-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/excel-365-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>