Brightwater Provisions, Inc.
LedgerPro to new ERP
- Cutover
- Go-live
- Books
- USD
Public demoView-only · fictional data
Brightwater Provisions, Inc.
LedgerPro to new ERP
One record, twice: exactly what the legacy system exported, beside Relay's normalized reading of it. tb:6999:2026-04-30
Trial balance line
One account's balance on a control report the legacy system produced. Control reports are the independent side Relay checks the detail against.
The same record on both sides. The left is evidence and never changes; the right is Relay's interpretation of it, and is what every check reads.
Exactly what the export contained, stored append-only. Relay never edits it — a correction is an overlay recorded on top of it.
| Account | 6999 |
|---|---|
| Description | Suspense – Clearing |
| Period Ending | 04/30/2026 |
| Debit | 2,315.77 |
| Credit |
Produced from the exported row by the approved column mapping: the same values, parsed into typed fields. This is an interpretation, not evidence — when it looks wrong, the mapping or an approved override changes, never the row itself.
| Balance | 2315.77 |
|---|---|
| Period end | 2026-04-30 |
| Account code | 6999 |
{
"balance": "2315.77",
"period_end": "2026-04-30",
"account_code": "6999"
}Findings Relay's automatic rules and reconciliations raised against this record. They are produced by the run, never written or cleared by hand: a finding goes away when a run stops reporting it.
No issue names this record as a subject.
Relay's checks read this record on the current run and raised nothing against it.