Multi-Entity | Accountants | Kick Docs

[See what's new in the

Kick Changelog](/content/changelog/index.html)

For the complete documentation index, see llms.txt. This page is also available as Markdown.

Kick is built for clients with multiple businesses, holding companies, or any structure that requires separate books under one workspace. Each entity gets its own chart of accounts, financial statements, and transaction history — while shared tools like rules, categories, and the transactions feed work across all of them.

How entities work in Kick

A workspace contains one or more entities. The first entity is created when you add a client. Additional entities can be added at any time from the Clients tab or from within the client's workspace.

Each entity has its own:

Consolidated transactions feed

The Transactions tab shows transactions for all entities in a single feed. This is useful when entities share similar categorization — you can review and categorize across the entire workspace without switching context.

To focus on a single entity, filter by entity in the top right.

Tip: The consolidated feed is especially helpful for reviewing intercompany activity. Matched Transfers between entities are clearly surfaced, making it easier to confirm both sides are categorized correctly.

Intercompany journal entry automation

When you move a transaction from one entity to another — or split a transaction across entities — Kick automatically generates the intercompany payable and receivable journal entries on both sides. This means you don't need to manually create offsetting entries. The expense is booked to the correct entity, and the intercompany balances on each entity's Balance Sheet stay in sync.

This applies to:

Multi-entity rules

Rules can apply across multiple entities, so you don't need to recreate the same rule for each one. This includes:

Multi-entity Chart of Accounts

All entities in a workspace share a single Chart of Accounts view. You can see which accounts are shared across entities and which are unique to a specific entity. Custom accounts can be created and scoped as needed.

The Personal entity

Every workspace includes a Personal entity where clients can connect their personal bank accounts and credit cards. Transactions in the Personal entity do not post to the General Ledger — they sit on the Transactions tab for review.

When a personal transaction has a business purpose, move it to the appropriate business entity. The expense posts to that entity's books, and the other side is recorded as a contribution. The Personal entity can be disabled if not needed.