Configuration screenshots age poorly. When a regulator or partner asks why a tariff applied on Tuesday but not Wednesday, you need an audit trail that proves who changed what, with which effective dates, and against which approved request.
Minimum pack
- Before/after tariff or rule export with checksums.
- Change ticket referencing the commercial approval.
- Deployer identity and timestamp in the engine’s own log — not only in chat.
- Sample rated events that demonstrate the intended boundary.
Backdated corrections
Backdating is sometimes legitimate; hiding it is not. Record the commercial reason, the periods recomputed, and the financial impact estimate. Financial auditing for telecom billing governance treats silent backdates as a control failure even when revenue “looks better.”
Privileged access
Shared admin accounts destroy trails. If your vendor still requires them, compensate with break-glass procedures and dual control on production pushes. Document the compensation; do not pretend the ideal exists.
Teaching the habit
Connectapicloud’s rating-change workshop (Settlement Floor) forces learners to assemble a pack from messy lab files. Alumni often discover their production process fails the same checklist. That discovery is the point.
Continue with when governance beats another spreadsheet tab, or review the full module list on the flagship course page.