Card Transactions
An unmatched card charge is not an outstanding claim — it is money gone with no explanation, and on a corporate-liability card the company has already paid it.
Where to find it
- Module: Accounting
- Group: Working Capital
- Section: Travel & Expense
- Screen: Card Transactions
Address in the console: /accounting/card-transactions
List · 13 columns · 18 fields on its form · 3 of them required · 3 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Date | Date | transaction_date |
| Card | Code | card_no_last4 |
| Holder | Text | employee_name |
| Merchant | Text | merchant |
| MCC | Code | merchant_category_code |
| City | Text | city |
| Ccy | Code | currency |
| Amount | Amount | amount |
| Liability | Status | liability |
| Claim | Code | report_no |
| Age | Number | age_days |
| Aged unmatched | Yes or no | aged_unmatched |
| Status | Status | status |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Card required | Choice | Looked up from existing records | |
| Holder | Choice | Looked up from existing records | |
| The scheme's own id | Text | What stops a re-imported statement doubling every charge. | |
| Date required | Date | ||
| Posted | Date | ||
| Merchant | Text | ||
| Merchant category code | Text | ||
| City | Text | ||
| Country | Text | ||
| Currency | Choice | Looked up from existing records | |
| Amount required | Number | ||
| Billed in | Text | ||
| Billed amount | Number | ||
| Exchange rate | Number | ||
| Claim line | Choice | Looked up from existing records | |
| Dispute reason | Long text | ||
| Statement | Text | ||
| Statement date | Date |
What you can do here
Match to claims primary
On amount, date, employee and card. Anything ambiguous is left unmatched rather than guessed — a wrongly matched charge is worse than an unmatched one, because it looks explained.
Asks for: Amount tolerance Day window
Tie to a line primary
Tie this charge to the claim line it paid for
Asks for: Claim line*
Untie
This charge was tied to the wrong line
Asks for: Why
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.