Relay

Stage 1 · Source systems

Where the legacy data comes from. One entry per system you will export files from.

LedgerPro Desktop 2014Legacy erp
First Cascade Bank (account ending 4471)Bank
Implementation teamOther

View-only in public demo

Declaring the systems a company is migrating from is the first step of a real implementation.

Stage 2 · Datasets

One dataset per exported file. The type tells Relay how to read it; agings need an as-of date and bank statements name the account they belong to.

View-only in public demo

Each dataset declares what a file is, which is how Relay knows an aging needs an as-of date and a bank statement needs the GL cash account it reconciles to.

account_mapping_v2.csvAccount mappingimportedcolumn mapping
ledgerpro_ap_aging_20251231.csvAp agingimportedcolumn mapping
ledgerpro_ap_aging_20260630.csvAp agingimportedcolumn mapping
ledgerpro_ar_aging_20251231.csvAr agingimportedcolumn mapping

Stage 3 · Run

A run reads the active import of every dataset through its approved mapping, then validates and reconciles the result.

Nothing here is destructive: a run recomputes results from the current inputs and leaves the imported rows untouched.

View-only in public demo

A run re-reads every dataset and recomputes every accounting control, reconciliation and readiness gate from scratch. The latest run is where every number on this demo comes from.