Skip to content

Travel Expenses — Transactions

Overview

Travel Expenses is a read-only ledger of corporate card transactions. Finance teams import card statements issued by the company's travel card provider (SiVale) and SARA matches each transaction to the corresponding project or department based on the collaborator's logistics calendar.

For the import process and assignment logic, see: Workflow.

Note

For common UI patterns used across SARA (tables, filters, dynamic columns, naming conventions), see: Common Features

Travel Expenses

Overview

The Travel Expenses screen (/travel-expenses) displays all corporate card transactions imported into SARA. Each row represents one card movement — a charge or payment — tied to a collaborator and optionally attributed to a project or department.

What you will see

  • Year filter — Multi-select picker that filters transactions by year. Defaults to the current year. Covers the last four years.

  • Custom columns selector — Choose which columns are visible in the table. Available columns: Card, Date, Movement, Payment, Charge, Currency, Sheet, Description, Event, Collaborator. Selections persist per user.

  • Event column — Shows the project or department assigned to each transaction. If SARA could not automatically match the transaction to a logistics calendar entry, the cell displays an Unassigned button instead.

What you can do here

  • Import (requires edit) — Opens a drag-and-drop modal to upload card statements. Accepted formats: XML (SiVale CFDI) and CSV. Transactions are processed immediately and inserted into the ledger. Duplicate UUID records are skipped automatically.

  • Download CSV format (requires edit) — Downloads the official CSV template used to prepare card statement files for import.

  • Assign unassigned expense — Clicking the Unassigned button on any row opens a modal where the user selects whether to attribute the transaction to a Project or a Department, then picks the specific record. This action is available to all users with view access.

Permissions

Permissions

Access and actions are permission-driven. See: Permissions