CSV import and validation

Give the next reviewer a clearer starting point.

Bring bank, invoice and recorded-payment exports into a controlled record set. Check the rows, retain their source identifiers and see which records need attention before reconciliation begins.

Demonstrable locally

The current demonstrated receipt workflow covers one UK company, one GBP bank account and CSV imports. Public production access and USD support are not yet available. Screens use synthetic records.

Ordvex · CSV import validation

Choose a layout, then zoom in to explore the details.

01

01 / Prepare the files

Keep the source behind every record.

The local workflow accepts bank, invoice and recorded-payment CSVs. Map columns and select the date format while retaining the original file and source identifiers for later investigation.

  • Use one entity, account and completed period for the review set.
  • Keep invoice IDs and existing payment allocations in the exports.
  • Treat each file as a complete snapshot for its record type.
02

02 / Check the records

See invalid rows before they enter the set.

Validation separates included, excluded and invalid records and shows the totals. Duplicate identifiers and formatting errors remain visible so the preparer can correct the source file.

  • Inspect the validation result and affected rows.
  • Resolve blocking errors before committing the snapshot.
  • Keep repeated imports and deliberate replacements distinct.
03

03 / Retain the history

Make a corrected import traceable.

A replacement is an explicit step. Previous versions and import history remain available in the local implementation, so the team can distinguish the active record set from earlier files.

  • Review the active snapshot and its source file.
  • Use search and filters to inspect the imported records.
  • Keep reconciliation and accounting sign-off in your existing process.

THE NEXT QUESTION

A little more detail.

Does a validated import mean the books are reconciled?

No. Import validation checks the records against the supported format and rules. It does not match bank receipts to invoices, approve accounting treatment or post journal entries.

Can we use USD or multiple currencies today?

The documented receipt workflow currently uses GBP for one UK company and one bank account. US and other currency requirements can be discussed, but production support needs verified currency, format and security checks before agreement.

Do separate CSV files automatically append to each other?

No. Each CSV is a complete snapshot for its record type. A corrected dataset follows an explicit replacement flow; previous versions are retained.

Can our team start using this in production from the website?

The import workflow is demonstrable in a local authenticated workspace. The public website accepts enquiries. Access, eligible data and production readiness must be confirmed before any paid rollout.

A FOCUSED FIRST STEP

Make it relevant to your team.

Walk through your requirements and see where Ordvex could fit.

Discuss your import workflow