Transactions

The Transactions tab is the detailed finance ledger in Aerolync. Every financial movement -- whether generated automatically from a booking, a payment, a flight log, or entered manually -- appears here as a line item with its debit or credit value, category, and linked relation.

When to use Transactions

Open Transactions when you need to:

• Understand exactly which financial movement was created and why
• Trace a specific debit or credit back to its source
• Review all finance lines for a given date range or category
• Export a filtered set of transactions for reporting or external accounting
• Verify that a payment, booking, or flight log created the expected finance entry

Understanding the transaction list

Each row in the transaction list represents a single financial movement. The columns provide the following information:

Using the filter bar

The filter bar at the top of the Transactions tab helps you narrow down the list to exactly what you need.

Search

Type a keyword, relation name, or description fragment into the search field. The list updates to show only matching transactions.

Category filter

Select one or more categories from the category dropdown to isolate specific types of financial movements. This is useful when you want to review only flight costs, only top-ups, or only manual entries.

Date range

Set a start and end date to limit the list to a specific period. This is especially helpful for monthly or quarterly reviews.

Exporting transactions

The export function lets you download the current transaction list as a file for use in external accounting software or spreadsheets.

1. Apply any filters you need (date range, category, search term) so the export contains only relevant data.
2. Click the Export button in the filter bar.
3. The system generates a file with the currently visible transactions.
4. Save the file to your local machine.

Common tasks

Finding a specific transaction

1. Open the Transactions tab.
2. Type the relation name, description, or reference into the search field.
3. If needed, narrow the results further using the category or date filter.
4. Review the matching rows to find the transaction you are looking for.

Reviewing all transactions for a relation

1. Open the Transactions tab.
2. Search for the relation by name.
3. Optionally set a date range to focus on a specific period.
4. Review the debit and credit columns to understand the financial activity.

Investigating a missing or unexpected transaction

1. Open the Transactions tab.
2. Filter by the expected date and category.
3. If the transaction is missing, check whether the source event (booking, flight log, or payment) was completed successfully.
4. If an unexpected transaction appears, review the description field for its source and check the linked relation.

Preparing a monthly export

1. Open the Transactions tab.
2. Set the date filter to the first and last day of the month.
3. Optionally filter by category if you only need certain transaction types.
4. Click Export.
5. Use the downloaded file in your external accounting workflow.

How transactions relate to other tabs

• In-App Payments -- each successful payment creates a credit line in Transactions. If a payment shows as completed in In-App Payments but you cannot find the matching transaction, check the date and category filters.
• Wire Transfers -- when a wire transfer is linked to a finance item in the Wire Transfers tab, a corresponding transaction is created or updated.
• Balances -- the Balances tab aggregates all transactions per relation into debit totals, credit totals, and a current balance.
• Invoices -- invoice amounts in the Invoices tab correspond to one or more transaction lines.

Good practice

• Filter before exporting. An unfiltered export contains every transaction in the system and is rarely useful. Apply date, category, or relation filters first.
• Use the description field. When investigating a transaction, the description often tells you exactly where it came from -- a booking number, a flight log, or a manual note.
• Cross-reference with Balances. After reviewing individual transactions, check the Balances tab to confirm the net result for the relation.
• Review regularly. Do not wait until the end of the quarter to review transactions. A weekly check helps catch errors early.
• Check the category. If a transaction appears in the wrong category, investigate the source event. Miscategorised transactions usually point to a configuration issue in the source module.