Skip to main content

Find expenses, journals and payments

The application uses an expense register, expense detail, a linked journal page and an employee reimbursement payment page. These are different views of related records.

ScreenApplication path
Register/expenses
Expense detail/expenses/:id
Linked journal/expenses/:id/journal/:journalTransactionId
Linked payment page/expenses/:id/journal/:journalTransactionId/payment

The paths belong to Trade Manager, not this documentation site. Use the links from actual records; placeholder IDs are not interchangeable.

Search procedure​

  1. Open Expenses and enter a relevant keyword in the search box.
  2. Open Filters for Category, Status, Employee, Account, Vendor and Date from/to.
  3. Select actual autocomplete options for identity/account/vendor filters.
  4. Choose Apply and inspect active filter chips.
  5. Remove unintended chips or clear filters before concluding a record is absent.
  6. Check pagination, then use the row's View action.

Global search matches stored expense text/enums such as description, category, currency, Paid By, payment method, status and notes. It does not join User or Supplier display names for a name search. Use dedicated Employee/Vendor filters for those references. Date boundaries are inclusive.

The register defaults to 20 per page and offers 5, 10, 15 and 20. Displayed table amounts normally show two decimals even though stored values can have four. Inspect exact evidence when precision matters.

Empty/error handling​

An empty result is scoped to the current tenant, filters and allowed units. A missing journal can mean no posting, denied journal rights or a failed load; the detail component clears its journal display on an error. Likewise, the journal payment count can fall back to zero after a failed read. Neither is proof that no related record exists.

The payment page verifies the journal ID against the expense's linked journal. Company-paid records do not get the normal employee PAY navigation. See Company posting for that current UI boundary.