iLumen
Board & Portfolio Reporting for CFOs

How do you report to the board and lenders with confidence?

Board packages are where inconsistent data becomes visible to people outside the finance team. A package that cannot survive a follow-up question costs credibility for several cycles.

Questions & answers

What does a strong franchise board reporting package look like?

Clean, standardized system-level metrics that let the board compare performance across locations on equal footing — not a stitched-together set of franchisee-submitted reports in different formats. It also carries unit-level detail behind every summary figure, drawn from the same mapped dataset, so a drill-down question during the meeting does not require reconciliation on the spot.

Why It Matters

Board packages are where inconsistent data becomes visible to people outside the finance team. A package that cannot survive a follow-up question costs credibility that takes several cycles to rebuild.

Key Factors

  • System-level metrics built from one consistent account structure
  • Unit-level detail available behind every summary figure
  • Trailing twelve-month views alongside current period
  • Comparable cohort context for any performance claim
  • Same underlying data supporting location, group, and system views

The iLumen Perspective

iLumen produces the standardized system-level metrics a board package requires, with the unit-level detail behind them drawn from the same mapped foundation — so a drill-down question does not require reconciliation on the spot.

Why is trailing 12-month data more reliable than monthly reporting?

Monthly financials are noisy — seasonality, one-time costs, and timing differences can make a healthy location look troubled or vice versa. TTM trend data smooths that noise out and reveals a location's real trajectory. Monthly reporting still matters for close discipline; it is simply the wrong basis for deciding whether a location needs intervention.

Why It Matters

Monthly reporting invites overreaction. A location has one heavy repair month or a timing difference on an invoice and gets flagged, while a genuinely deteriorating store with smooth monthly numbers goes unnoticed.

Key Factors

  • Seasonality distorts single-month comparisons
  • One-time costs and timing differences create false signals
  • TTM smooths noise and reveals direction of travel
  • Trend direction matters more than level for intervention decisions

The iLumen Perspective

iLumen supports monthly, period, YTD, trailing-twelve-month, quarterly, and annual views from the same standardized foundation, so a finance team can move between operational monitoring and strategic assessment without rebuilding the data.

At what point should a franchise system start managing locations like an investment portfolio?

Once a system crosses roughly 100 locations, store-by-store management becomes impractical. Portfolio-level rollups — by ownership group, region, or brand — let leadership manage performance and risk the way a sponsor would manage a portfolio of assets. Past that threshold, attention spreads thin enough that exceptions go unnoticed, and system performance becomes a function of which locations happened to get attention that quarter.

Why It Matters

Store-by-store management does not fail suddenly; it degrades. Leadership attention spreads thinner, exceptions get missed, and the system's performance becomes a function of which locations happened to get attention that quarter.

Key Factors

  • Roughly 100 locations as the practical inflection point
  • Rollups by ownership group, region, brand, and entity
  • Risk managed at the portfolio level rather than case by case

The iLumen Perspective

iLumen supports location, ownership group, brand, and entity rollups from one mapped dataset, which is what allows a system past the inflection point to manage by exception and by portfolio rather than store by store.

How do we roll financials up from location to ownership group to system?

Roll-ups require one shared account structure before aggregation, not after. Once every location is mapped consistently, the same underlying data supports a location view, an ownership-group view, and a system view without reconciliation — which is what makes all three defensible in the same board meeting.

Why It Matters

Roll-ups assembled after the fact require reconciliation, and reconciliation is where board confidence gets lost. If the location view and the system view are built from different treatments of the same costs, the two will not tie — and someone will notice.

Key Factors

  • One shared account structure applied before aggregation
  • Consistent treatment of intercompany and related-party items
  • Ownership group as a first-class reporting level, not a spreadsheet exercise
  • Same period basis across every entity in the roll-up
  • Drill-down from system figure to location line without adjustment

The iLumen Perspective

Because iLumen standardizes at intake, the location, ownership-group, and system views are all expressions of the same mapped dataset. That is what allows all three to be presented in one meeting without a reconciliation step between them.

How do we report consistently to boards and lenders across multiple brands?

Map each brand's locations to its own concept-specific structure first, then align the brands at the reporting layer on shared definitions — revenue, cost of sales, labor, occupancy, contribution margin. Forcing dissimilar concepts into one chart of accounts too early produces comparisons neither brand's operators recognize.

Why It Matters

Multi-brand operators and platform companies face a specific version of this problem: each concept has a legitimately different cost structure, and forcing them into a single chart of accounts produces comparisons the operators reject.

Key Factors

  • Concept-specific mapping preserved at the brand level
  • Alignment at the reporting layer on shared definitions
  • Revenue, COGS, labor, occupancy, contribution margin as common lines
  • Brand-level detail retained beneath the consolidated view

The iLumen Perspective

iLumen collects, standardizes, and validates financials across systems, locations, and entities — which lets a multi-brand portfolio keep concept-appropriate structure at the brand level while still producing a consolidated view the board and lender can rely on.

iLumen

Ready to trust the numbers you decide on?

See how iLumen collects, standardizes, and validates financials across every location — and turns that foundation into peer benchmarking and Performance Intelligence your team can act on.