<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Concepts on The Bean Ledger</title>
    <link>https://thebeanledger.com/tags/concepts/</link>
    <description>Recent content in Concepts on The Bean Ledger</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Jul 2026 12:03:43 -0700</lastBuildDate>
    <atom:link href="https://thebeanledger.com/tags/concepts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recording Big-Ticket Purchases in Beancount: Asset or Expense?</title>
      <link>https://thebeanledger.com/posts/big-ticket-purchases/</link>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://thebeanledger.com/posts/big-ticket-purchases/</guid>
      <description>&lt;p&gt;You sign for a new car, and 30,000 USD leaves your checking account in a single transfer to the dealer. That night you open Beancount to record it, and the entry stalls on what feels less like data entry than a type error. Expense it, and &lt;code&gt;Expenses&lt;/code&gt; absorbs 30,000 USD in one month — the income statement now reports that you torched a year&amp;rsquo;s discretionary budget, when in fact a car worth nearly that much is sitting in the driveway. Capitalize it as an asset instead, and net worth jumps by the sticker price of something that began depreciating the instant it left the lot; leave that number frozen and, three years on, the balance sheet still asserts the car is worth exactly what you paid, long after it&amp;rsquo;s really worth closer to 15,000 USD. Neither entry reconciles with reality. That mismatch — a value that won&amp;rsquo;t sit cleanly in either bucket — is the signal worth debugging: the categories aren&amp;rsquo;t broken, they&amp;rsquo;re being applied to the wrong kind of thing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
