Trusting an import: the verification summary and undo

An import you can't verify is an import you can't trust. Nexxus treats verification as part of the import itself.

The Summary step

After writing, the importer re-reads the database and compares it against your source files:

• Per-tenant ledger totals — what the files said each ledger should hold vs what the database actually holds, matched to the cent.
• Tenant-by-name differences — anyone present in the files but not the database (or vice versa) is listed by name with the reason.
• A verdict — pass, or a specific list of what to look at.

It also states when owner payouts through Nexxus begin, so the payout baseline is never a surprise.

Reading a mismatch

A named difference usually traces to the export, not the import — a tenant whose file was missing a page, or a history range that didn't reach far enough back (check the "Go back" selector). Fix the export and re-run; re-imports merge safely.

Undo

Every import runs as a batch, and Settings → Data & imports lists them with an undo. Undo removes everything the batch created — in one atomic operation, so it can never leave a half-undone import. Records that existed before the batch are untouched.

The intended rhythm for a tricky migration: import → read the Summary → if anything's off, undo → fix the export → re-run. There's no penalty for iterating.

When to call for help

If the Summary passes but a number still looks wrong to you, that's worth a support conversation rather than manual edits — ask in the support chat or post privately on NexxusHub with the batch date.