<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Billing on Nick Liu - Software Engineer</title>
    <link>/tags/billing/</link>
    <description>Recent content in Billing on Nick Liu - Software Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>nickboy@users.noreply.github.com (Nick Liu)</managingEditor>
    <webMaster>nickboy@users.noreply.github.com (Nick Liu)</webMaster>
    <copyright>2026 Nick Liu</copyright>
    <lastBuildDate>Sat, 21 Mar 2026 17:30:33 -0700</lastBuildDate><atom:link href="/tags/billing/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Case Study: Building AWS Billing&#39;s Unbilled Usage Auditor</title>
      <link>/posts/case-study-aws-billing-auditor/</link>
      <pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate>
      <author>nickboy@users.noreply.github.com (Nick Liu)</author>
      <guid>/posts/case-study-aws-billing-auditor/</guid>
      <description>&lt;div class=&#34;lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl&#34;&gt;&#xA;  I spent five years on the AWS Billing team. The hardest problem I tackled was detecting when customers used AWS services but weren&amp;rsquo;t charged correctly. This post walks through how I designed a system that reduced charge discrepancies by &lt;strong&gt;300x&lt;/strong&gt; and eliminated &lt;strong&gt;230 million&lt;/strong&gt; monthly false positives.&#xA;&lt;/div&gt;&#xA;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;The Problem&#xA;    &lt;div id=&#34;the-problem&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#the-problem&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;AWS billing is trickier than it looks. When a customer launches an EC2 instance, writes to S3, or queries DynamoDB, each action generates a usage record. These records flow through a pipeline that calculates charges based on the customer&amp;rsquo;s pricing plan, region, and service tier.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
