Card Import - File Field Reference

Import File Field Reference

Overview

Import Cards accepts a CSV file for one supplier at a time — the supplier is chosen on screen, not supplied as a column in the file. This page lists every column the file supports in v1, how blank values behave on update, and what's explicitly out of scope for now.

How create vs. update is decided

Each row is matched using the supplier you selected on screen plus the row's card_number:

If a card already exists for that supplier and card_number, the row is processed as an update.
If no card exists for that supplier and card_number, the row is processed as a create.

This follows the same uniqueness rule Catch-e already applies to cards (one card per supplier + card_number combination).

Import file fields (v1 scope)

#	Field	Required	Description
1	`card_number`	Yes	Business key. Combined with the selected supplier to determine create vs. update.
2	`contract_id`	Conditional	One of `contract_id` or `reg_no` is required. If supplied, this contract is used directly.
3	`reg_no`	Conditional	One of `contract_id` or `reg_no` is required. If supplied, resolves to the active contract for that registration number. The row fails if more than one active contract is found.
4	`account_number`	No	Optional card account number.
5	`recharge_flag`	No	Optional override. On create, defaults from the linked Contract Type's "Expenses Other R" setting for class F (Fuel/Charging), then the imported value applies if supplied. `Y` recharges the client; `N` posts against budget.
6	`client_code_recharge`	No	Optional recharge client override. Defaults from the contract where applicable, but can be changed in the import.
7	`history_only_flag`	No	Optional — defaults to No.
8	`activated_date`	No	Optional — must be a valid, supported date if supplied.
9	`inactivated_date`	No	Optional — must be a valid, supported date if supplied.
10	`expiry_date`	No	Optional — must be a valid, supported date if supplied.
11	`status_flag`	No	Optional. Supports `active` and `inactive` only — `deleted` is not supported in this import.

Blank value behaviour on update

For update rows: a blank value means leave unchanged — it never clears an existing value in v1.

Out of scope (v1)

These fields are explicitly not supported by this import:

posting_flag — continues to default to Yes and doesn't need to be exposed here.
notes
card_sub_status_id