Practical software guides
A price change must be reproducible from the customer’s agreement and the version of the price that applied. A new value in a spreadsheet is not enough to explain an old invoice.
| Item | Example |
|---|---|
| Old price | B$40 per month; version 1 |
| Proposed price | B$45 per month; version 2 |
| Affected accounts | Only accounts with the approved agreement and effective date |
| Notice | Approved message; sent timestamp and delivery status |
| Exception | Account C-12 held for contract review |
| Invoice check | No retroactive rewrite of issued invoices |
Export an affected-account list for review before scheduling the change. Test an account due before the date, one on the date and one held as an exception. A failed notification must create follow-up rather than silently marking the customer informed.
Notice, fee and refund obligations depend on contracts and applicable rules; have the responsible adviser approve them. Keep permission to prepare a change separate from permission to approve it. The rollout recovery guide shows how to handle failed or incomplete migration steps.