Original Summary

When you move metered billing to a new system, the invoice total can look right while the usage underneath is wrong. Two checks I'd run first. Replay versus conflict. Say usage event evt_1042 arrives twice with the same customer and the same quantity. That's a retry, and it should not charge twice. Now say evt_1042 arrives again with a different quantity. That isn't a retry, and it shouldn't quietly replace the first one. It should be rejected and reported so a person looks at it. It's easy to build something that treats both cases the same way, and you only find out at month end. Shadow run. Before you switch, rate every subscription in the new system next to the old one and compare every price. Start with made-up numbers: a $20 seat plan, 10 seats, plus usage at $0.002 a call. Do both systems produce the same lines? Investigate any gap while nothing is billing from the new system yet. Two smaller ones. Late usage should land in the next period at the price in effect when it happened. And an issued invoice shouldn't change afterwards; fixes go through a credit note that can't exceed what the invoice still owes. I'm James, and I make Nectar at Just Every. It's a free, open-source (MIT) billing app for US software businesses, in USD, and it runs on your own Cloudflare account. It's built around these checks: https://justevery.com/nectar and https://github.com/just-every/run-nectar What do you check before you trust the first invoice run from a new billing system?   submitted by   /u/withmagi [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/19 11:53:38