Project · Directory
Route /finance/accounts · /project/accounts Menu Finance → Accounts

Accounts

Manage account/team/client hierarchy and monitor completeness through quality-centric charts.

Hierarchical account directory with data-quality and linkage analytics.

Account hierarchy

Team and client structure finance and delivery share

Accounts manages account / team / client hierarchy and completeness charts. Projects and POs hang off this directory; it is not a second CRM.

Finance → Accounts Route /finance/accounts Finance Manager · Admin

The job of this console

Keep the hierarchy true, watch completeness, open an account before attaching a PO or project. Do not rename an account in a project only — change it here.

Seat at the table

Finance administrators. PMs consume the names on projects. Employees do not maintain accounts.

The working rhythm

Search, edit hierarchy, save, confirm projects and POs still point at the right node.

Moments that bring you here

New client. A merger of teams. Completeness gaps. Before a PO import.

ⓘ
Directory, not invoices
Billing still happens on invoices and POs. This register is who they belong to.

Overview

The Accounts page stores organizational context used by projects and reporting. Healthy account data improves list filters and analytics grouping.

Screen layout

Header: Type chips, quality chips, search, sort.
Body: Account hierarchy/list with owners and metadata.

Header & filters

Type chips: All · Accounts · Teams · Clients · Salesforce
Quality chips: Needs attention · Complete only · Missing teams/clients/email · No owner · No description

Summary & charts

Summary analytics emphasize data quality: health mix, issue categories, hierarchy coverage, source split, and billing type distribution.

Main content & actions

Open records to maintain hierarchy and required metadata fields.

Complete feature list

Every control, panel, and workflow on this screen.

  • ✓
    Luxury UI shellEmerald-themed glass cards, sticky gradient header, module sidebar, and responsive layout.
  • ✓
    Documentation searchHeader search indexes all guide pages (docs site).
  • ✓
    Collapsible summary stripKPI row and chart gallery above the register; expand/collapse persists in browser storage.
  • ✓
    Account registerClient accounts with project counts.
  • ✓
    CREATE accountNew client record.
  • ✓
    Account summary chartsRevenue and project concentration.
  • ✓
    Row → account detailProjects and contacts on account.

Before you start

ℹ️
Single source of truth
Fix client name on account record — propagates to new bids, POs, projects.
⚠️
Duplicate accounts
Run search before CREATE — duplicates harm Top accounts charts.

Who uses this screen

Account managers and sales staff maintaining client master records — project counts, revenue concentration, and links to Sales POs and HRMS invoices.

ℹ️
Client register
Accounts are the client anchor — projects, bids, POs, and invoices reference the same account record.

Key concepts

Account register

Clients with industry, region, project count, active contract indicators.

CREATE account

New client record with billing contacts and terms.

Account summary charts

Revenue concentration and project count bars.

Row navigation

Drill to projects and contacts on account.

Cross-module linkage

Sales bids/POs and HRMS invoices share account picker.

Permissions

RoleAccess on this screen
Account managerCreate/edit owned accounts; view all projects on account.
SalesCreate accounts during bid flow; read register.
Project managerRead-only account on projects; cannot edit billing terms.
FinanceEdit billing address, tax IDs, payment terms.
📝
Administrator override
Org administrators and service accounts configured in the Admin console may bypass row-level scopes shown above. When in doubt, confirm access with your Tracopus administrator.

Controls reference

ControlDescriptionNotes
CREATE accountNew client wizard.Duplicate check by name.
SHOW / SORT / FilterActive accounts, search.Lux header.
Summary chartsRevenue and concentration.Team filter if enabled.
Row clickAccount detail/projects.May open modal or page.
Merge accountsAdmin action.Rare — dedupe duplicates.
ExportAccount list.CRM sync complement.
Link from projectAccount on project hero.Two-way nav.

Common mistakes

⚠️
Duplicate account names
Breaks invoice and PO search — merge or use distinct legal names.
⚠️
Stale billing contact
Invoice emails bounce — finance updates on account before send.
⚠️
Account without projects
Orphan from deleted projects — archive inactive accounts.

FAQ

Account vs project?

Account = client company; Project = one delivery engagement for that client.

Who can merge duplicates?

Typically admin — request via ticket.

CRM sync?

Salesforce account ID field when integration enabled.

Multiple contacts?

Contacts tab on account detail — primary used on invoices.

Workflows

  1. Start with Needs attention chip.
  2. Fix missing owner/email/description issues.
  3. Review hierarchy coverage chart.
  4. Validate Salesforce-linked records.

Tips & best practices

Tip: Resolve missing teams/clients first; those gaps impact downstream project/account dashboards most.

More guidance

💡
Remember
Clients with industry, region, project count, active contract indicators.
ℹ️
Account vs project?
Account = client company; Project = one delivery engagement for that client.