# See which branch, project or team actually makes money

> Tag invoices and expenses to a cost centre (a branch, project or team) or split a single invoice or journal LINE across several dimensions at once, and read a profit & loss per centre.

Canonical page: https://finocket.com/product/cost-centres

## What it solves

A single company P&L hides the truth that one branch subsidises another, or that a project is quietly loss-making. Finocket lets you tag each invoice and expense to a cost centre, so you can read a separate P&L per branch, project or team and see exactly where the money is really made and lost.

## How it is different

A per-centre P&L isn't a second set of books to maintain. It reads the same postings your company accounts already run on, so tagging a transaction is the only extra step and the centre-level view stays perfectly consistent with the whole.

## What it does

### Tag transactions to a centre

Attach each invoice and expense to a cost centre (a branch, a project or a team) as you record it.

### A P&L per cost centre

Read profit & loss for each centre on its own, so a subsidised branch or a loss-making project stops hiding inside the company total.

### One ledger, many lenses

The per-centre view reads the same postings as your company accounts, so tagging is the only extra work and the numbers always reconcile to the whole.

### Split one transaction by %

Attribute a single invoice or expense across several cost centres by percentage (they must sum to 100 and the amounts foot to the paise), so a shared cost lands where it belongs and the per-centre P&L still ties back exactly to the whole.

### Per-LINE, across several axes at once

Go a level deeper: split a single invoice line, or a single journal line, across a branch AND a project AND a fund simultaneously, with each axis footing independently to exactly 100%. A dimension is typed, so a branch split and a project split never contaminate each other, and the same distribution is readable over the REST API and by an AI agent. It's a reporting distribution: it changes how the number is sliced, never what posts to the general ledger.

## Works with

- [Real double-entry books your CA will accept](https://finocket.com/product/reports-and-books): A P&L per branch or project reads the same double-entry postings as your company accounts.
- [From estimate to collected cash, in one flow](https://finocket.com/product/invoicing-payments): Tag an invoice to a cost centre so its revenue lands in the right branch or project P&L.
- [Group work and expenses under client projects](https://finocket.com/product/projects): Attribute project work and expenses to a centre to see whether that engagement actually made money.

## Frequently asked questions

### What is a cost centre here?

Any slice of the business you want to measure on its own: a branch, a project or a team. Tag invoices and expenses to it and Finocket produces a profit & loss for that centre alone.

### Is it a separate set of books?

No. The per-centre P&L reads the same postings as your company accounts, so tagging a transaction is the only extra step and the totals always reconcile.

### Can one transaction go to more than one cost centre?

Yes. Split a single invoice or expense across several cost centres by percentage. The percentages must sum to 100, the amounts foot to the paise, and the per-centre P&L still ties back exactly to the unsplit total.

### Can I split one invoice LINE across a branch and a project at the same time?

Yes. A single invoice line, or a single journal line, can be distributed across several dimension axes at once, each axis footing independently to exactly 100%. Dimensions are typed, so a branch split and a project split can't contaminate each other, and the distribution is readable over the REST API and by an AI agent. It stays a reporting distribution: it never changes what posts to the general ledger.

---
This is the Markdown copy of https://finocket.com/product/cost-centres, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
