Step-by-step instructions
Managers can record money movement with a type, account, date, category, amount, comment, and optional receipt or invoice attachment.
Use the interactive screenshot walkthrough first. Switch steps with the step dots, then read what to fill and why it matters.
Fields on this screen
Transactions list
How to fill: Start from the list and check the current total before adding a manual transaction.
Why: The list is the finance ledger surface for manual movements and loaded operation totals.
Add
How to fill: Click Add in the top-right area to open the real Transaction form.
Why: The form creates a new transaction ID and starts a draft with the current date.
Transaction type
How to fill: Choose Income for incoming money, Expense for outgoing money, or Transfer when money moves between two company accounts.
Why: The type changes whether SABSUS asks for To account, From account, or both.
To account
How to fill: For Income, select where money is received, such as Acquiring Account, Cash, or Bank.
Why: This is the account whose balance should increase.
From account
How to fill: For Expense, select the account where money leaves. For Transfer, select both source and destination accounts.
Why: This is the account whose balance should decrease.
Transaction date
How to fill: Open the calendar and confirm the real posting day and time.
Why: Reports, daily totals, shifts, and reconciliation depend on this date.
Transaction category
How to fill: Select the reason for the movement. If the dropdown is empty, complete Transaction Categories first.
Why: Categories explain why money moved; payment methods only explain how money was paid.
Amount
How to fill: Type only the numeric amount, for example 42.51.
Why: The amount is used in account totals, reports, and reconciliation.
Comment
How to fill: Write a short note in the active interface language.
Why: A clear comment helps humans and AI agents explain the row later.
Invoice / receipt
How to fill: Upload a receipt, invoice, or confirmation image when the transaction needs evidence.
Why: Attachments reduce confusion during audits, refunds, and dispute review.
Save
How to fill: Save only after all visible fields are checked.
Why: Unsaved transaction data does not become reliable finance history.
Common mistakes
- Creating an income transaction for money that actually left the business.
- Selecting the wrong account and making the wrong balance increase or decrease.
- Leaving Transaction category empty even though finance categories were already created.
- Using the payment method as the category instead of the business reason for the movement.
- Typing comments in the wrong language for the active interface version.
- Saving without a receipt or invoice when the operation needs evidence for accounting.
- Expecting a transaction category to appear before it has been created in Transaction Categories.
AI Agent Field Reference for implementation
This block is intentionally below the human instructions. It explains storage names and downstream dependencies for automation, support, and future AI agents.
| Field | Stored as | Purpose | Why it matters |
|---|---|---|---|
| Transaction ID | transactions.id / TransactionStruct.ID | Unique finance transaction identifier. | Reports, support, imports, and AI agents need a stable ID for each money movement. |
| Company | transactions.company | Company workspace that owns the transaction. | Prevents one company's finance rows from appearing in another workspace. |
| Transaction type | transactions.type / TransactionStruct.Type | Direction of money movement: + for Income, - for Expense, = for Transfer. | Controls which accounts are required and how the transaction affects finance totals. |
| To account | transactions.to_account / TransactionStruct.To | Account receiving money. | Required for income and transfers so SABSUS knows where the balance increases. |
| From account | transactions.from_account / TransactionStruct.From | Account money leaves from. | Required for expenses and transfers so SABSUS knows where the balance decreases. |
| Transaction date | transactions.date / TransactionStruct.Date | Date and time of the real money movement. | Daily cash, reports, shift review, and reconciliation depend on the correct posting date. |
| Transaction category | transactions.category / TransactionStruct.Category | Finance category that explains why money moved. | Reports and agents group income and expenses by category, not only by payment method. |
| Amount | transactions.amount / TransactionStruct.Amount | Numeric transaction amount. | The amount changes account totals and is used in reports and reconciliation. |
| Comment | transactions.comment / TransactionStruct.Comment | Short operational note for the transaction. | Helps managers, accounting, support, and AI agents understand the business context. |
| Invoice / receipt attachment | transactions.invoice / TransactionStruct.Invoice[] | Uploaded receipt, invoice, or bank confirmation files. | Attachments provide evidence and make payment reviews easier. |
| User | transactions.user_id / TransactionStruct.User | Employee or owner who created the transaction. | Useful for audit history and responsibility. |
| Currency | transactions.currency / TransactionStruct.currency | Currency value when present on the transaction. | Prevents finance review from mixing amounts in different currencies. |
| Created at | transactions.created_at | Timestamp when the row was created. | Useful for audit history and support investigation. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.