Transaction settings

Settings → Finance & Business → Transactions holds two organization-wide choices about bank transactions: whether people may enter transactions by hand, and whether Flowtly may apply its own suggestions to imported transactions without waiting for review. It is separate from the Transactions list where the transactions themselves are worked.

Who can change it

An administrator or a user with the transactions manager role can open this screen. Only an administrator can change anything on it: for everyone else the switches and the field are disabled and there is no save button.

The controls on this screen

Transactions

Allow manual transactions: lets people add transactions by hand, to cash and manual bank accounts. It is on by default and saves as soon as you flip it, with a Success message. While it is off, Flowtly refuses to create a manual transaction.

Automatic categorisation

Apply confident suggestions automatically: when on, Flowtly applies a suggested category to a transaction on its own when it is confident enough. When off, which is the default, every suggestion waits for your manual review. Nothing is saved until you click Save changes.

Confidence threshold: shown only while the switch above is on. It takes a whole number of percent and is the minimum confidence a suggestion needs before it is applied automatically. A higher value applies fewer, safer suggestions. The field refuses anything that is not a whole number between 1 and 100.

Save changes: stores the automatic categorisation settings. It is available only to administrators and stays disabled until something changed and the threshold is valid.

Only suggestions that rest on an exact identifier are ever applied automatically: a counterparty matched by its bank account, or by the client of an invoice. Suggestions below the threshold, or without a clear match, are always left for you to review. A threshold above the confidence of these matches would never apply anything, so the highest value the server accepts is 93 percent.

Example use cases

• An administrator turns off Allow manual transactions once every account is fed by a bank connection, so no one adds a transaction by hand.
• An administrator turns on Apply confident suggestions automatically at 91 percent so payments from known counterparties are categorised on import.
• A finance lead with the transactions manager role opens the screen to see which of the two behaviours is on, without being able to change it.