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-59

BWP-59: Entry date outside the history window

▲critical•open

Nature: migration defect
Category: Dates
Raised by: Rule
Amount at risk: 1,184.62USD
Rule or reconciliation: GL.DATE_IN_WINDOW
Last seen: run

Subjects

Normalized record

je:JE-AP-20455

Latest finding

Relay check result

JE-AP-20455 is dated 2062-03-14, outside 2026-01-01..2026-06-30

Expected: null
Observed: "2062-03-14"

Source rows Original source

row 9291, line 9292

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

Same root causeBWP-24 Posting period differs from the period of the entry date: je:JE-AP-20455open(both name je:JE-AP-20455 (run 01a0c786-cd2c-77f4-9cff-808e9f51079d))

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:48ZIssue 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.