Brightwater Provisions, Inc.
LedgerPro to new ERP
- Cutover
- Go-live
- Books
- USD
Loading this view
Public demoView-only · fictional data
Brightwater Provisions, Inc.
LedgerPro to new ERP
Account mapping set proposed by Maya Chen.
Financial data is never changed silently
Done
1. Proposed with evidence
Maya Chen submitted
Done
2. Approved by other people
2 of 2 required approvals recorded
Done
3. Applied in one transaction
The reason of record. It is written into the audit trail when the change is submitted, and cannot be edited afterwards.
Mapping agreed in the chart of accounts workshop.
Re-points legacy accounts at different accounts in the target chart. The legacy ledger is untouched; what changes is how Relay derives canonical records from it.
Replaces the account mapping file (127 accounts) with version 1 (127 accounts).
| Legacy account | Before | After | Compatibility of new target | Rationale |
|---|
Each role below has to be satisfied by a different person, and never by the requester. Segregation of duties is enforced by the API, not by hiding buttons.
Review is closed: this change request is applied
Decisions are final once recorded. A different outcome needs a new change request, which goes through the same approvals.
Reported by the API as: the change request is applied.
Applying a change does not decide anything by itself. A fresh pipeline run re-ran every deterministic validation and reconciliation over the new inputs, and those results are what the readiness gates read.
Every step above as it was written to the hash-chained audit log.