Migrating off spreadsheet billing
A 3-week sequence that runs both until the new one produces a month you trust.
The risk in a billing migration is not the import. It is cutting over before anyone has watched the new system produce a full period. The sequence below runs both in parallel for one month, which costs a little duplicated review and removes the only failure mode that actually matters.
Week one: contracts in
Load every active agreement as signed. Extraction lifts each term for a person to review, and anything ambiguous is flagged rather than guessed.
Week 2: connect the ledger
Your ledger stays where it is. Map journal entries to your existing chart of accounts and import the journal file into it, so the system of record does not move and the comparison against last month is like for like.
Week 3: run in parallel
- Generate the billing run but do not send it; diff it against the spreadsheet.
- Investigate every difference: most are the spreadsheet, some are the mapping.
- Cut over only once a full run matches with no unexplained lines.
Keep reading
Closing the month on the first
Why a close takes 9 days, and which of them are just arithmetic waiting to happen.
Anubhav DubeyArticleMetering that reconciles
Usage billing fails between the event stream and the invoice. Counting each line against its usage records closes the seam.
Anubhav DubeyArticleThe close is a pipeline problem, not a people problem
Nine-day closes are not caused by slow accountants. They are caused by 5 tools that each hold a different version of the truth.
Anubhav DubeyArticle