Read one role-aware ledger built from operational evidence
Finance Analytics connects the projects already visible to the signed-in cabinet with their client invoices, supplier billing packs, confirmed payments, approved expenses, project commitments and authorized CRM opportunities. It does not maintain a second set of financial records or fill missing evidence with demonstration values.
Each movement retains its project, team, client, document lifecycle and dates. Company totals can therefore be narrowed to one project without mixing that project's expenses with supplier cost or borrowing totals from another team or client.
Business Architect provides the first company-level scope. Selecting one operating model recalculates the complete view across all of its activated root-process projects; selecting a root process below it isolates that project's economics. Subprocesses remain analytical dimensions inside their root process and never become duplicate projects. A draft operating model remains visible but is labelled as not activated until its teams and Process Owners are complete.
Understand how the same document changes by cabinet role
| Source | Partner or company owner | Specialist | Client |
|---|---|---|---|
| Client invoice | Revenue, receivable and collection | Not part of personal earnings | Project cost, payable and payment |
| Supplier invoice | Cost and payable only for company-managed supplier billing; direct client-to-specialist packs remain observed pass-through | Earnings, receivable and receipt | Supplier obligation where authorized |
| Approved expense | Operating or project expense and cash outflow | Not exposed unless the specialist is authorized | Visible only inside the client's authorized project scope |
| CRM opportunity | Probability-weighted forward value | Hidden | Available when Project Workspace is used as the company's operating cabinet |
Keep project purpose and settlement responsibility explicit
| Finance model | Typical use | Financial behavior |
|---|---|---|
| Internal operations | Business Architect process or another internal company project | No customer invoice is inferred; employee payroll, company contractor payables and explicit operating expenses remain available |
| Client direct | A client manages delivery and pays specialists directly | Each eligible specialist owns a supplier invoice; the client records the payable and payment |
| Company principal | A Team Studio company or agency sells managed delivery | The company invoices the customer at client rates and records specialists or suppliers at separate internal rates |
| No finance | Operational work that intentionally has no monetary workflow | Tasks and delivery remain visible without creating invoices, payroll or costs |
Choose the customer identity once in CRM
CRM is available in Team Studio and Project Workspace. A process-operating company can therefore manage its own external customers even when its internal work is organized through Business Architect process projects.
Collty client means the customer already participates in the connected Collty client project. That customer owns and maintains its legal billing identity in its own cabinet, and the project remains the source of invoice and payment state.
External customer means the relationship does not need a Collty customer account or client project. Save its legal name, address, tax identity, billing contact, currency, payment terms and e-invoice delivery profile once; CRM reuses the versioned bill-to profile for later standalone sales invoices.
Linking an internal Business Architect process project to a CRM relationship does not change the relationship into a Collty client. Only a real client-financed project can use the connected-client billing path.
Keep accrual and cash timing separate
P&L recognizes an issued invoice or approved cost in its evidence month. Cash flow records money only in the month where payment is confirmed. A document issued in July and paid in August therefore affects July operating performance and August cash movement.
Open receivables and payables remain separate from cash. Commitments and weighted opportunities remain separate from recognized revenue. This prevents an issued, due or planned amount from being presented as money already received or paid.
For a supplier invoice, earnings use the invoice subtotal. Confirmed receipt uses the gross settlement, which can also contain tax collected for a third party. Team Studio preserves that distinction when it summarizes direct payments without treating either amount as company revenue.
When the payer reports a transfer, the payment is Pending. When the supplier confirms receipt, the final status becomes Paid, paid_at is recorded and the invoice PDF displays a PAID stamp with that confirmation date.
Use each view for a specific decision
| View | What it answers |
|---|---|
| Overview | What changed in revenue, operating result, net cash and the open position |
| Profit & loss | How issued revenue becomes gross and operating result by month |
| Cash flow | When confirmed money enters and leaves and how closing cash develops |
| Projects | Which ordinary or process-project creates contribution and open exposure |
| Teams | Which team carries company-booked economics, or—when clients pay specialists directly—which team delivered the work, how much its specialists invoiced, received and are still owed |
| Clients | Which relationships drive revenue, collection and concentration |
| Invoices | Which documents are draft, open or paid and which project produced them |
| Costs & payouts | Which supplier invoices and expenses create cost or cash outflow |
| Forecast | How contracted commitments and weighted CRM evidence extend the actual history |
| Calendar | When accrual, due and confirmed payment events occur without collapsing them into one date |
Inspect the evidence instead of reading static cards
- Switch the active curve between revenue, operating result, cash in, cash out and closing cash.
- Select any reporting month to inspect its value and cash movement.
- Select a complete Business Architect operating model, one root-process project, one ordinary project or one team to recalculate every total, chart and register from the selected records.
- Search and select a project, team or document to open its contribution and lifecycle context.
- Use the financial calendar to distinguish invoice issue, payment due and confirmed payment events.
Resolve missing or unexpected values at the source
| What you see | Likely reason | What to check |
|---|---|---|
| Projects are visible but financial evidence is incomplete | No issued invoice, confirmed payment or approved expense was returned | Open the project's Invoices and Expenses records and check their lifecycle state |
| P&L contains a value but cash is empty | The document is issued but payment is not confirmed | Check payment status and the receiving party's confirmation |
| Cash appears in a later month | Payment was confirmed after the issue date | Compare Issued and Paid dates in the invoice register or calendar |
| A supplier invoice is a cost instead of revenue | You are viewing the partner or company cabinet | Switch only if you are authorized to use the specialist cabinet; the direction is intentionally role-aware |
| Team delivery is visible but company revenue is zero | The client paid specialists directly and the company did not issue the invoice | Use team delivery and settlement for operational analysis; use company-invoiced revenue only for the company's own P&L |
| A Business Architect operating model is visible but has no process projects | The operating model is still a draft | Assign teams and concrete Process Owners, resolve blocking validation and activate the model |
| A project scope differs from the company total | The scope excludes other projects, teams and clients | Return to Company or select the required project |