RelayERP implementation operations

Public demoView-only · fictional data

Brightwater Provisions, Inc.

LedgerPro to new ERP

Cutover: 2026-06-30
Go-live: 2026-07-01
Books: USD

Overview
Work queue

Migration data

Setup
Imported data
Mappings

Checks & reconciliation

Verification runs
Accounting checks
Reconciliation
Issues
Duplicate parties

Changes & approvals

Approvals
Applied corrections

Go-live

Readiness
Audit log
Policy

Loading this view

Portfolio prototype · Fictional accounting data · No real company, ledger or person is represented here. This demo is one shared copy of a fictional implementation, so anything that would change it for the next visitor is left out. Everything else — the evidence, the reconciliation trail and the governed workflow behind each decision — is real and explorable.

Issues
BWP-31

BWP-31: MONTHLY MAINTENANCE FEE -45.00 USD on 2026-02-27 is not recorded in the ledger

●medium•open

Nature: source anomaly
Category: Cash
Raised by: Rule
Amount at risk: 45.00USD
Rule or reconciliation: BANK.UNRECORDED_ACTIVITY
Last seen: run

Subjects

Normalized record

bank:4471:2026-02-27:65324449289b

Latest finding

Relay check result

MONTHLY MAINTENANCE FEE -45.00 USD on 2026-02-27 is not recorded in the ledger

Source rows Original source

row 591, line 592

Finding detail

{
  "amount": "-45.00",
  "description": "MONTHLY MAINTENANCE FEE",
  "posted_date": "2026-02-27"
}

Workflow

Ownership and progress. Issues become resolved only when a current run no longer reports them.

Owner: unassigned

View-only in public demo

Assigning an owner or moving an issue's status is ordinary operator work here.

View-only in public demo

A disposition records a decision about a real legacy misstatement — carry it forward, adjust it, or rule it out — as a change request two people approve.

Related issues

No linked issues.

Links are created when a disposition or decision covers more than one finding.

Comments

View-only in public demo

Commenting is how the implementation team works an issue between runs.

History

Every governed change to this issue, in order.

2026-09-22 05:11:47ZIssue created

Investigate with AI

The investigator reads this migration with read-only tools and cites its evidence. It cannot change anything.

In this public demo every visitor shares one copy, so a finding is investigated once and everyone sees that same result. The tools really run against this database — the evidence is genuine — and the reasoning is a scripted transcript, not a model.