Finance is the largest area of the platform and the one with the most going on underneath. It handles money coming in, money going out, and the books that account for both.
Five parts
Overview. The command centre, and an assistant that answers questions about your numbers.
Receivables. Invoices and what customers owe you. Subscriptions for anything recurring.
Payables. Expenses, payroll approval, and the queue where both wait for a decision.
Accounting. The chart of accounts, the general ledger, financial statements, tax, budgets, period close and reconciliation.
Workflows and insights. Boards, an inbox, and reporting.
That fourth part is the one that distinguishes this from an invoicing tool, and it has its own set of articles.
The property that matters
An invoice here is not a document about a deal. It is attached to the deal, drawn from the same record, and when it is paid the deal knows.
The same holds throughout. An expense belongs to a person who exists in People. A payroll run approves against the same employees. A customer's payment history sits on the customer, not in a separate ledger you reconcile by hand.
The practical consequence: there is no monthly exercise of making Finance agree with the rest of the business, because there is nothing separate to agree with. That exercise is where most of the effort goes in a stack where the CRM and the accounting system are different products.
Money in
An invoice is raised from a deal or from scratch, in any currency, with tax handled per line.
It moves through states you can see: draft, sent, paid, overdue. Payment can be collected through a gateway or recorded by hand when somebody pays by transfer, and a partial payment is a first-class thing rather than a note in a field.
Subscriptions handle anything that repeats, and roll up into recurring revenue.
Money out
Expenses come from the company or from a person claiming back. Both route into an approval queue where whoever is responsible approves or rejects, with more than one level where your organisation requires it.
The same queue carries payroll, commissions and advances, so a manager has one place to look rather than four.
The books
This is a genuine double-entry system, not a reporting layer.
A chart of accounts, journal entries that post to it, a trial balance that has to balance, a profit and loss, a balance sheet, budgets with variance against actuals, tax rates, a monthly close that locks the period, and a reconciliation that checks the sub-ledgers against the general ledger.
Most of it happens without anybody making entries by hand. Raising an invoice, paying an expense and running payroll all post automatically, and the mapping that decides which account each one hits is inspectable and editable.
Who does what
Anybody raises an invoice or claims an expense, from wherever the work is.
Managers approve, from one queue.
Somebody owns the books. The chart of accounts, the mappings, the close. Usually one person, and the accounting articles are written for them.
Everybody else can safely ignore the accounting section. It is doing its job when nobody notices it.
What it costs
Nothing per invoice, per expense, or per journal entry. Finance is a licensed module rather than a metered one.
Payment gateways charge their own fees on collections, which are the provider's rather than the platform's. The AI assistant spends credits when asked a question.
Currency
Every amount is stored in the currency it happened in and in your base currency alongside it.
That is what makes a total honest in a business trading in several currencies: figures sum the base amount rather than adding dirhams to dollars. Your base currency is set once for the organisation, and each hub carries its own where it trades in a different one.
The one thing that is automatic
Almost every business event that involves money posts to the general ledger on its own.
An invoice sent, a payment received, an expense approved and paid, a payroll run released. Nobody makes a journal entry for any of them.
That is worth stating early because it changes what the accounting section is for. It is not somewhere you enter transactions; it is somewhere you inspect what was entered, correct the occasional exception, and close the month.
Where to start
If you send invoices, read Invoices and AR, then Getting Paid.
If you approve things, read The Approval Queue. It is short.
If you own the books, read Chart of Accounts first, then the General Ledger. Everything else in the accounting section assumes those two.
If you are setting this up from scratch, read Bringing Your Books In, which covers getting existing data into the system in the right order.
What the AI assistant does here
The Finance overview carries an assistant that answers questions against your own numbers rather than against a general model of accounting.
Useful for the questions that would otherwise mean building a report: what is outstanding over sixty days, which customer owes most, how this month compares with last. It reads the same records the statements do, so its answer and the statement agree.
It costs credits, like the assistant anywhere else. Reading the surfaces does not.
Boards and inbox
Finance carries the platform's standard per-area surfaces alongside its own.
Boards are dashboards scoped to Finance, built from the same measures Analytics uses.
Inbox is the department inbox for finance correspondence, so supplier and customer email lands where the records are rather than in one person's mailbox.
Neither is Finance-specific in how it works, and both are covered in their own sections.
What it is not
It is not a substitute for an accountant. It produces the statements; whether your treatment of something is correct in your jurisdiction is a professional question.
It does not file anything. Tax is calculated and recorded, not submitted.
It is not a bank. Payment gateways collect money; the money lands in your own accounts.
Did this answer your question?
No, ask a person