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
Column 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
1 of 1 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 reviewed against the export header and sample rows.
Changes how the columns of one legacy export are read into canonical fields. The file itself is immutable: it is simply re-read under the new mapping.
ledgerpro_ar_aging_20251231.csv: approved version — → 1; 8 fields change.
| Field | Before | After |
|---|---|---|
| currency | — | {"steps":[{"step":"trim"},{"step":"currency"}],"source":"Currency"} |
| due_date | — | {"steps":[{"step":"trim"},{"step":"empty_to_null"},{"step":"parse_date","format":"MM/DD/YYYY"}],"source":"Due Date","required":false} |
| functional_open_amount | — | {"steps":[{"step":"trim"},{"step":"parse_decimal","thousands_separator":","}],"source":"Open Balance (USD)"} |
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.
| item_date | — | {"steps":[{"step":"trim"},{"step":"parse_date","format":"MM/DD/YYYY"}],"source":"Date"} |
|---|
| kind | — | {"steps":[{"step":"trim"},{"step":"value_map","mapping":{"Invoice":"document","Payment":"unapplied_payment"}}],"source":"Type"} |
|---|
| party_code | — | {"steps":[{"step":"trim"}],"source":"Customer ID"} |
|---|
| party_name | — | {"steps":[{"step":"trim"}],"source":"Customer"} |
|---|
| reference | — | {"steps":[{"step":"trim"}],"source":"Num"} |
|---|