We’ve been doing pretty well with Beancount for our small CPA practice—clean ledgers, easy audits. But now I’m worried about the 2026 GAAP updates. I know ASC 842 (leases) and ASC 326 (credit losses) have been rolling out, but I can’t find a simple explanation of what changes affect us specifically in 2026.
Here’s my real problem: QuickBooks auto-updates to compliance. Beancount doesn’t. So either I manually refactor the chart of accounts (risky), or I do GAAP adjustments in a spreadsheet at year-end (tedious). My auditor keeps hinting that she’d feel better if our system showed compliance natively.
Has anyone else navigated this? How do you keep a Beancount chart compliant with evolving standards without rebuilding it every year?
Have you asked your auditor to list exactly which ASC sections apply to your practice? That might narrow the scope from “all 2026 changes” to just the ones that actually matter for you.
I implemented ASC 842 in my practice in 2022 and honestly didn’t find it that painful. Added a “Leases” section, tracked operating vs finance leases, moved on. Year-end adjustments happen in Beancount like any other entry—a quick BQL query, verify coding, post if needed.
The thing is, Beancount actually makes this clearer than QuickBooks. At least I can see what’s going on. My auditor prefers it because it’s transparent. Less hand-waving.
Fair point on the transparency. But tax side is messier—ASC 842 accounting doesn’t always match tax depreciation on leases. Anyone else juggling that gap?
My auditor prefers it because it’s transparent.
This is key. I’ve been worried about auditor reaction, but maybe the transparency is actually reassuring to them. Do you share the Git history with auditors, or just the end-of-year report? Trying to figure out how much audit trail is too much vs. just right.