Step-by-step instructions
Every payment and cash movement has a destination account, so reports and reconciliation are understandable.
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
Account list
How to fill: Start from the Accounts list and check existing rows before adding a new one.
Why: Duplicate finance accounts make payment method setup and reports confusing.
Add
How to fill: Click Add only when you need a new cash, non-cash, or acquiring account.
Why: The app creates a draft account, so the form must be completed before leaving it.
Title / account name
How to fill: Enter a clear account name in the active interface language.
Why: Staff see this name when selecting accounts and reviewing finance rows.
Name translations
How to fill: Expand the title field and fill the enabled languages the company uses.
Why: Multilingual companies need account names that are readable in every active interface.
Account type
How to fill: Choose Cash for physical money, Non-cash for internal or bankless methods, and Acquiring for card/provider settlement.
Why: The type controls reporting and whether banking details appear.
Currency
How to fill: Choose the currency used for this account, usually the company operating currency.
Why: Reports and reconciliation are reliable only when currency is explicit.
Opening balance
How to fill: Enter the real balance at the moment the account starts in SABSUS.
Why: Future finance totals are calculated from this starting value.
Comment
How to fill: Add a short manager note when the account purpose is not obvious.
Why: The note helps staff understand the account, but automations should verify whether it is persisted in the current backend.
Banking details
How to fill: For Acquiring accounts, fill account number, settlement account, bank code, and bank name.
Why: Invoices, deposits, payouts, and bank reconciliation depend on these details.
Save
How to fill: Save only after names, type, currency, balance, and bank details are checked.
Why: Unsaved accounts cannot be safely connected to payment methods.
Saved row
How to fill: Return to the list and verify type, currency, bank name, and account number.
Why: The list confirms the account can now be used by payment methods and reports.
Common mistakes
- Mapping cash and online payments to the same account.
- Deleting an account used by historical payments.
- Reconciling provider deposits without accounting for fees.
- Using one account for several establishments when cash should be separated.
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 |
|---|---|---|---|
| Account ID | accounts.id | Unique finance account identifier. | Payments and reports need a stable account reference. |
| Company ID | accounts.company_id | Company workspace that owns the account. | Prevents accounts from different companies being mixed in finance reports. |
| Account name translations | accounts.name | JSON list of account names by language. | The list and payment settings use this label, so enabled languages need readable names. |
| Account type | accounts.type | Cash, non-cash, or acquiring type; acquiring is saved as the provider/card settlement type. | Controls which fields appear and how finance reports group the account. |
| Currency | accounts.currency | Money symbol or currency selected for the account. | Prevents reconciliation from mixing USD, EUR, and other currencies. |
| Opening balance | accounts.start_summ | Starting account balance at creation time. | Finance totals use this value as the base before later payment movements. |
| Comment | AccountStruct.Comment / UI note | Operational note shown in the account form. | Use it for manager context, but verify persistence before relying on it for automation. |
| Bank name | accounts.name_bank | Readable bank or acquiring provider name. | Invoices, payout checks, and finance review need to know where the money settles. |
| Account number | accounts.number_account | Bank, card settlement, or provider account identifier. | Required when the business generates invoices or reconciles bank deposits. |
| Settlement account | accounts.settlement_account | Settlement or correspondent account value. | Accounting and bank transfer documents may require a separate settlement account. |
| Bank code | accounts.code_bic | Bank code, BIC, routing, or provider code. | Helps identify the financial institution and avoid sending payment details to the wrong place. |
| Created at | accounts.created_at | Time when the account row was created. | Useful for audit history and for explaining why the account appeared in reports. |
| Updated at | accounts.updated_at | Time when the account row was last changed. | Agents can use it to explain whether account data is fresh or outdated. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.