Demand test — not available yet
Do you need to reconcile reordered Excel rows by invoice number or ID?
This proposed mode would match reordered rows by invoice number, order ID, SKU, employee ID, email, or another stable key, then show changed amounts, missing records, duplicate keys, and added records. It is not a live comparison feature yet.
Observed reconciliation pattern
Two exports contain the same business records, but the row order changed
A coordinate diff treats every moved row as noise. The proposed workflow would first match a stable key—preferably an invoice number, order ID, SKU, or another unique identifier—then compare fields such as amount, date, status, or email. A composite key such as email plus invoice value is useful only when that pair is genuinely unique.
One anonymous choice
Which recurring reconciliation job should we solve first?
Choose the closest task. This records only a broad use-case category and traffic-source category as a daily aggregate. It does not collect an email address, IP profile, filename, spreadsheet, or workbook content.
No choice recorded yet.
Concept output
A reconciliation report should show exceptions, not positional noise
Planned boundaries: browser-local processing, explicit key selection, no AI access to workbook contents, and honest handling of duplicate keys. These are proposed requirements, not currently shipped features.