Finances — Full Revenue and Cost Control
say.work connects operational and financial data. Client contracts, hourly rates, orders with billing line items, employee agreements, salary components and cost efficiency analysis — all in one system, with no need to export to spreadsheets.
Client Registry
Central client register — the foundation for contracts, orders and settlement. Each client is a separate record linked to their contracts and orders.
Company data
Name, tax ID, address, contact details. The client is the central point — contracts, orders and rates are all assigned to it.
Project links
Projects in say.work can be linked to a client. This means worklogs recorded in tasks automatically feed into contract settlements.
Cooperation history
Full history of contracts, orders and settlements linked to a given client — visible in one place.
Client contracts and multi-level rates
A contract defines the framework of cooperation with a client — its validity period and a set of hourly rates. Rates can be defined at many levels of granularity — from a flat rate to per-employee.
Contract structure
A contract is assigned to a client and has a validity period (from–to). One client can have multiple contracts — e.g. a separate one for development, another for maintenance.
Hourly rates (Contract Rates)
The most advanced part of the module. A rate can be defined at the flat level (one rate per contract), per project, per competency centre, per role in CC, per skill type / skill / level, or even per specific employee.
Billing parameters
Each rate has additional parameters: overtime multiplier (e.g. 150%), rounding method (up/down), rounding to minutes (e.g. to 15 min) and minutes to skip (skip first N minutes).
Rates with dates
Each rate has its own validity period — this allows changing the rate mid-contract without losing history. The system matches the rate based on the worklog date.
Orders — from commission to settlement
An order is a formal billing unit. It has an assigned client, type, value, billing line items and links to projects and employees.
Order header
Order number (internal and client's), order date, validity period (from–to), order type, order value and maximum value. Linked to client and type.
Order items
Each order is divided into line items — each with dates, description, value, invoice number, status, delivery date and settlement date. An item can be one-off or recurring.
Ingredients
Each line item can have cost components — employee assignment or a fixed amount. A component can consider working days only. The system calculates the item value based on its components.
Item statuses
Configurable billing line item statuses — e.g. "To settle", "Invoiced", "Settled". The is_settled and calculate_item_value flags control the calculation logic.
Project links
An order connects to projects (Order Projects) — client settlement is based on worklogs from linked projects.
Task links
Orders can be linked directly to specific tasks (Order Tasks) — precise scope-of-work billing.
Attachments & messages
An order can have attachments (PDFs, scans) and internal messages — comments and agreements between teams.
Employee agreements and salaries
Full employee agreement records — from agreement type, through contract value, to salary components. Data protected by 3FA verification.
Agreement types
Configurable agreement types with parameters: cost calculation method, full cost multiplier (employer overhead), FTE flag and link to billing unit (days/hours). E.g. employment contract, B2B, civil contract.
Employee agreement
Validity dates, agreement type, contract value, FTE, position, employing company. The system reminds about expiring agreements (remind_date + remind_text).
Salary components (Ren Elements)
Configurable components: gross, net, bonuses, allowances. Each component has a code, label, group, display order and add_to_total flag. A line chart on the employee profile shows history per component.
3FA security
Salary and agreement data protected by a lock. Unlocking requires two-factor verification — even an authorised manager must confirm their identity before viewing an employee's financial data.
Financial dictionaries
The finance module relies on configurable dictionaries — every aspect can be tailored to the company's specifics without code changes.
Job positions
Position dictionary linked to employee agreements. Code, name, level — used for cost reporting per position.
Order types
Order classification — e.g. "T&M", "Fixed Price", "Retainer". Each type can have different billing logic and colour.
Order item statuses
Define billing statuses with flags: whether the status means settlement, whether the system should calculate the value, whether it is the default.
Employee contract types
Employment contract, B2B, civil contract — each with full cost multiplier, calculation method, colour and flags (FTE, allowance, position).
Cost efficiency analysis
By combining worklog data, contract rates, employee agreement costs and orders, say.work delivers a complete profitability picture — per project, per client, per team and per employee.
Revenue from worklogs
The system automatically calculates revenue based on logged work time and the contract rate. Accounts for overtime, rounding and minutes to skip.
Employee cost
Full employee cost = contract value × full cost multiplier (employer overhead). The system calculates the hourly cost based on FTE and working days.
Project margin
Contract revenue minus team cost = project margin. Visible per project, per client and over time (month by month).
Engagement vs. billing
Comparison: how many hours an employee logged on a client project vs. how many of those hours are billed. Utilization rate at the individual and team level.
Want to see more?
A meeting is the fastest way to see how say.work can streamline your team's work.
calendar_month Book a demo