Knowledge Base
Understand finance information
Understand finance information
The finance areas in Console can bring recorded transactions and plans into related views. The information visible to you depends on your role and the features configured for your organisation.
Identify the type of information
Distinguish a recorded bank transaction from an expected payment, a budget, or a planning scenario. An expected entry describes a future or outstanding event; it should not be treated as money already received or spent. Check the account, date, counterparty and category before using an entry in a report or decision.
Review transactions
Where your role permits, use the transaction area to inspect the original amount and its assigned details. If a transaction has been categorised incorrectly, follow the organisation's correction process. Internal transfers between the organisation's accounts should be identified separately from income and operating costs.
[Image: actual transaction view with amount, account, date and category labelled.]
Use plans carefully
Budgets and scenarios support decisions about future activity. Compare their dates, assumptions and included expected transactions before reading a projected balance. The same payment should not be counted twice when reviewing a plan alongside bank records.
Note: Use your organisation's agreed accounting and approval procedures for financial decisions. Console presents the records entered and connected for that environment.
Configured for your operation & supported by our team.
Manufacturing systems have to work across real people, established processes and existing technology. Private Client Services helps manufacturers introduce Console into that environment through planned configuration, guided implementation and ongoing support.
Register, Today.

Please fill out the form to see how our solutions could solve problems for your organisation


