ConceptsCommon objects
Transactions
Every inflow and outflow lives in Transactions — imported, categorized, and attached to customers, vendors, files, and subscriptions.
A transaction is one money movement. The Transactions page (sidebar → Transactions) lists them with filters for account, date range, category, counterparty, and full-text search.
Where they come from
| Source | What lands as a transaction |
|---|---|
| Stripe | Charges, refunds, payouts, balance transactions, fees. |
| HubSpot | None (HubSpot data lands as subscriptions, not cash transactions). |
| DATEV Lohnjournal | One transaction per payroll line item per uploaded CSV. |
| Manual | CSV import or single-transaction entry via the Transactions page. |
Anatomy
A transaction has:
- A date, amount, and currency.
- An account (where the money moved through).
- A counterparty — resolved to a customer or vendor if SaaSFlow can match it.
- One or more categories — see categories. A transaction can be split across multiple categories.
- A link to a subscription event for subscription-related transactions (recognised revenue, refunds against a subscription).
- Attached files — receipts, contracts, invoices.
Categorization
New transactions land uncategorized. You categorize them by:
- Picking a category manually from the transaction's detail view.
- Setting a default category on the vendor — every matching future transaction inherits it.
- Bulk-editing from the Transactions list (multi-select → edit).