A dev's cheatsheet for invoice-ready usage exports: keep billing data boring and stable
blaizedsouza · x · 2026-09-12
A developer shared a practical cheatsheet for exporting usage data finance can actually invoice: close the day at a fixed time, write one file per tenant and period, include a checksum, freeze files after publish, re-export only as new versions, and keep files through the audit window.
Core principle: billing data must be boring and stable — and never recompute last month just because a metric formula changed.
More from coding & agent
- When Facts Change: How Should an MCP Memory Server Update? Three Approaches Compared — izgorodin · 2026-09-12
- ADSP Ep. 303: Mark Saroufim on Open vs Closed Models, AI GPU Kernels and Autoresearch — blelbach · 2026-09-12
- Google releases free 2-hour course on agent graph & loop engineering — goyalshaliniuk · 2026-09-12
- Gemini CLI nightly patches indirect prompt injection and hardens sandbox filesystem — gemini-cli-robot · 2026-09-12
- Repurpose an old low-VRAM GPU just for mmproj in llama.cpp — an order of magnitude faster — inthesearchof · 2026-09-12
- Ollama vs llama.cpp: same request counts 85k vs 164k tokens in OpenCode — RadianceTower · 2026-09-12