Skip to main content

​
Overview

Many businesses need to track profitability across multiple dimensions beyond just account categories, e.g. by location, product line, project, or department. Tight’s class tracking functionality enables this multi-dimensional reporting without requiring your users to maintain complex account structures. Your platform can define the class labels and hierarchies made available to the business on your platform, and the businesses can define the values against those classes. Your users can assign classes to transactions, invoices, and expenses, then generate Profit & Loss reports segmented by class to understand which locations, products, or projects are most profitable. This is particularly valuable for platforms serving multi-location businesses, project-based services, or any vertical where profitability analysis by segment drives business decisions. The class tracking integrates seamlessly with Tight’s accounting engine, so businesses get accurate profitability reporting by segment while maintaining a clean, simple Chart of Accounts structure.

​
Use Cases

​
Defining Class Segment Labels at the Platform-level

Your platform defines the class segment labels—the dimensions businesses on your platform can use to label their transactions. These labels serve as the framework for multi-dimensional reporting (e.g., Region, Location, Department). By standardizing these dimensions at the platform level, you create vertical-specific tracking capabilities that align with your users’ business models. For example, a construction platform might define labels like “Project,” “Phase,” and “Job Type,” while a retail platform might define “Location,” “Product Category,” and “Sales Channel.” Once you define these labels through the class segment labels API, all businesses on your platform can populate their own specific values under each label dimension. This approach gives you control over the reporting structure while giving your users flexibility in how they apply it. Class segment labels can be hierarchical, allowing for nested categorization (e.g., Region → Location → Department).
The Tight API lets you define which labels are required, enforcing consistency across your platform’s data

​
Allowing Businesses to name their own classes

Once you’ve defined the class segment labels at the platform level, individual businesses populate those labels with their own specific values. These business-level class segments represent the actual categories each business uses for tracking (e.g., under “Location”: “NYC Office,” “SF Office,” “Remote”; under “Department”: “Sales,” “Marketing,” ” Operations”). Your platform may already track these segments, in which case you can simply have your system push them to the class segments API. Once created, these segments can be assigned to transactions, invoices, expenses, bills, and mileage entries. When your users generate financial reports, they can filter and/or group by any class segment to see profitability broken down by those dimensions, all without creating separate accounts for each segment. This gives each business complete flexibility to organize their financial data according to their unique structure, while your platform maintains consistent reporting capabilities across all businesses.

​
Examples

​
Regions, Locations, and Departments

Multi-location businesses need to compare performance across regions, individual locations, and operational departments. Here’s a concrete example:
  1. Platform Setup: A coffee franchise platform defines two class segment labels:
    • Label 1: Location (hierarchical: Region → Location)
    • Label 2: Department
  2. Business Configuration: A franchise owner with 6 stores across two regions creates specific segments:
    • Region/Location:
      • Mid Atlantic → Georgetown DC, Silver Spring MD, Arlington VA;
      • Northeast → Boston Common, Cambridge Porter, Providence Downtown
    • Department: Retail Sales, Catering, Mobile Carts
  3. Transaction Tagging: Users select one segment from each label when tagging transactions like wholesale coffee purchases, catering supplies, mobile cart equipment, and store rent. They can assign to a specific Region or Location and Department, or just assign to a Location or Region alone when department-level detail isn’t needed.
  4. Reporting Outcome: The owner can generate P&L reports to understand performance:
    • Filter by a specific Location to see total performance across all departments at that location
    • Filter by both Location and Department to isolate specific operations (e.g., just catering at Georgetown DC)
    • Group by Location to compare profitability across all stores side-by-side and identify which locations perform best
Tight’s AI learns from tagging behavior and creates rules to automatically assign future transactions to specific class segments, reducing manual tagging over time.

​
Job Costing & Budget Tracking

Job codes let you assign all costs (labor, materials, equipment, and subcontractors) to specific parts of a project. Here’s a concrete example: A construction platform defines a “Job Code” class segment label. A general contractor working on a residential renovation project creates these job code segments:
  • 2010 – Concrete Foundations
  • 3020 – Framing & Structure
  • 4010 – Electrical Rough-In
  • 5030 – Plumbing Systems
  • 7050 – Interior Finishes
When timecards, supplier invoices, or purchase orders reference a job code, expenses automatically get tracked to that part of the project. Concrete materials invoices get assigned to Job Code 2010, electrician timecards to Job Code 4010, lumber deliveries to Job Code 3020, and plumbing subcontractor invoices to Job Code 5030. The contractor can then generate P&L reports filtered by job code to compare actual costs against budgets for each phase of work. This visibility helps identify which parts of the project are over or under budget in real time, enabling adjustments before budgets are exceeded.