All articles

Receipt review · Practical guide

Prepare bank, invoice and payment exports for receipt review

Get the right records into your review. Follow the fields, formats and checks that make an import ready to use.

In this guide

The short answer

Prepare three complete UTF-8 CSV files: bank transactions, invoices and recorded payment allocations. Keep the source IDs, choose one date format per file, and review included, excluded and invalid records before making a snapshot active.

This guide follows the current Ordvex workspace for one UK company and a GBP bank account. It covers preparing and validating records. Receipt-to-invoice matching and live bank connections are not part of this workflow. Access and rollout scope are confirmed with your team.

Before you export: a six-point checklist

  • Select one company and a recognisable bank account reference, such as “GBP operating account”. Use a label, rather than a full bank account number.
  • Choose a completed bank period and an “as of” date for the supporting records.
  • Keep stable record IDs from the source system. Spreadsheet row numbers are not stable IDs.
  • Prepare a complete file for each record type. A later snapshot replaces the active file; it does not append rows.
  • Use UTF-8 CSV with unique, non-empty headers. Each file can contain up to 100,000 data records and be no larger than 20 MiB.
  • Check your access. Owners, admins and accountants can import. Reviewers and viewers can read records and source files.

Step 01

Set the period before choosing the records

In your company, open Imports & invoices, then New review set. Enter a name, account reference, bank period and Records as of date. The bank period must have ended. The as-of date must be on or after the period end and cannot be in the future.

A September review
Bank period
1–30 September 2026
Records as of
30 September 2026

Bank records are checked against the bank period. Supporting invoices and recorded payments may be older; records after the as-of date are excluded.

Include older invoices that could explain receipts in the period. A September receipt may relate to an August invoice. Earlier recorded allocations can also matter when you prepare the supporting records.

Step 02

Export the three record types

Your CSV headers do not need to use Ordvex’s field names. You map the columns after upload. Each required field must map to a different column.

Fields to keep in each export
FileRequired fieldsOptional fields
Bank transactionsSource transaction ID, date, signed amountCounterparty, reference, bank account reference, currency
InvoicesSource invoice ID, customer ID, customer name, invoice number, issue date, amountDue date, currency
Recorded paymentsSource allocation ID, invoice source ID, receipt ID, date, allocated amountCustomer ID, reference, bank account reference, currency

A recorded payment row represents an allocation. If one receipt was allocated across two invoices in your source system, preserve the two allocation rows. Each needs its own source allocation ID; the receipt ID can repeat. Keep invoice source IDs separate from customer-facing invoice numbers.

Ordvex retains these references during import. Acceptance of the CSV does not establish that a payment, invoice and bank transaction have been matched.

Step 03

Check dates, amounts and IDs

Use one date format in each file

Choose YYYY-MM-DD or DD/MM/YYYY. Use that format for every date column in the file, including invoice due dates. For example, 2026-09-30 belongs to the first format and 30/09/2026 to the second.

Keep amounts in pounds, with up to two decimal places

Values such as 1200.50, £1,200.50 and (25.00) are accepted. Quote fields containing commas correctly in the CSV. Negative and zero amounts can be read, but are excluded from this incoming-receipts workflow. More than two decimal places or exponent notation makes an amount invalid.

If currency is blank or unmapped, Ordvex uses GBP. A supplied non-GBP currency is invalid. A supplied bank account reference must match the review set’s reference.

Resolve duplicate source IDs

Every occurrence of a duplicated source ID is marked invalid; Ordvex does not silently choose one. Correct the source data while preserving the identity of each real record.

Step 04

Upload, map and validate

Choose Bank transactions, Invoices or Recorded payments, then upload the corresponding file. Map the required fields, select the date format and inspect the original-record preview. Choose Validate file when the mapping is correct.

Validation runs in the background. You can return to the import from its history. Uploading or validating a file does not change the active snapshot.

Ordvex invoice validation results showing included, excluded and invalid record counts and their GBP totals.

Actual Ordvex workspace with illustrative records.

Step 05

Review the results before committing

Each record has one of three outcomes. Review the counts as well as the GBP totals.

Included
The record meets the import rules for this review set.
Excluded
The record can be read, but sits outside this scope. Examples include bank outflows, bank transactions outside the period, and invoices or payments after the as-of date.
Invalid
Something needs correcting: a missing required field, duplicate source ID, invalid date, non-GBP currency or mismatched account reference. Any invalid record blocks the commit.

Filter or search the rows, then expand a record to inspect its original values and review notes. Records are shown 50 at a time.

The results view separates included and excluded totals, plus known GBP amounts from invalid rows. A record without a valid amount cannot contribute to a total. Non-GBP amounts do not enter GBP totals. A zero invalid-row total therefore does not prove there are no invalid records: check the count too.

Fix invalid rows in the source CSV and upload the corrected complete file. A file with no included records cannot become active.

Step 06

Make the reviewed snapshot active

Once validation has finished, review the included records and totals. Acknowledge any exclusions, then choose Commit snapshot. If the same record type already has an active file, the action is Replace active snapshot and requires explicit confirmation.

The previous version remains in history, and the original uploaded file stays available to authorised company members. Repeat the process for the other record types. The review set links to each active snapshot.

Committing saves the reviewed import. It does not post journals, move money, update your source accounting system or reconcile a receipt to an invoice.

A little more detail

Common questions

Can I upload an Excel workbook or a PDF bank statement?

This workflow accepts UTF-8 CSV. Export your records to CSV first; Excel workbooks and PDFs are not supported import formats here.

Do I need to rename my export columns?

No. Keep unique, non-empty headers and map them to Ordvex fields after upload. Each required field needs its own column.

Can an older invoice be included in a new month’s review?

Yes. Invoices and recorded payments can predate the bank period. Their dates must not be after the review set’s as-of date, and they must satisfy the other validation rules.

Does importing recorded payments match them to invoices?

No. This step preserves the references and validates the imported records. It does not establish a match or prove the accounting treatment is correct.

Can a reviewer change the active snapshot?

No. Reviewers and viewers can inspect records and source files. An owner, admin or accountant must upload and commit the snapshot.

Bring your receipt workflow to the conversation.

Tell us where your invoices live, how you record incoming payments, and where the review gets stuck. We can discuss how the current workflow fits and what you need next.

Discuss your receipt workflow
About this guide

Written by the Ordvex product team and checked against the current import workflow on . Screenshots come from the running Ordvex workspace and use illustrative company records.