Brand, entity, and unit reporting
One set of books structured three ways, so a multi-brand group can see a single unit, an entity, or the whole portfolio without rebuilding spreadsheets.
Our franchise partner solution is live across 500+ franchisee locations.
For franchise operators
Keep bookkeeping and close moving across your locations.
Recurring finance work in the systems you already use, with context for your locations and approval rules.
Accounts payable · two samples
Sample B: above the threshold. Not posted; waiting for a person to decide.
| Task | Status |
|---|---|
| Sample AVendor bill · Harbor Produce Co.Within threshold | Posted |
| Sample BVendor bill · Ridgeline EquipmentAbove threshold | Needs your input |
Finance workflows
Finance work across locations, with your operating rules.
Different locations, entities, and approval requirements add complexity. Start with one recurring finance workflow configured around that context.
Workflow in motion
Illustrative example · not a product screen or customer result
Keep recurring bookkeeping and reconciliation moving, with exceptions routed for review.
- Input
- Bills, receipts, and bank or card activity.
- Context
- Location or entity, chart of accounts, and the coding rules agreed for your business.
- Supported action
- Code transactions and match them toward reconciliation using your business rules.
- Output
- Coded entries in your accounting system, such as QuickBooks, ahead of close.
- Review condition
- Unmatched items, or those outside the agreed rules, wait for your team.
Workflow in motion
Illustrative example · not a product screen or customer result
Keep recurring bookkeeping and reconciliation moving, with exceptions routed for review.
- Input
- Bills, receipts, and bank or card activity.
- Context
- Location or entity, chart of accounts, and the coding rules agreed for your business.
- Supported action
- Code transactions and match them toward reconciliation using your business rules.
- Output
- Coded entries in your accounting system, such as QuickBooks, ahead of close.
- Review condition
- Unmatched items, or those outside the agreed rules, wait for your team.
Have another recurring process holding up the business?
Show us the steps, systems, and decisions involved. We’ll show you which parts Lieutenant can take on.
The franchise solution
Built for the way franchise groups actually report.
Several brands, many entities, dozens of units, and fees that depend on sales. Lieutenant structures the books around that, then does the recurring work inside it.
Royalties, ad fund, and tech fees
Fees charged by each brand checked against reported sales for the period, with differences surfaced before they are paid.
Intercompany
Shared services, management fees, and cash moved between entities recorded on both sides and reconciled at close.
New-unit setup and calendars
A new location gets its accounts, dimensions, and reporting calendar from a template, so it closes with the rest from its first month.
Unit 312 · period P&L · sample
Sample data- Revenue100.0%
- Food and paper29.4%
- Labor27.8%
- Occupancy8.6%
- Royalty and ad fund10.0%
Royalty billed on sales that differ from the POS close. Held for the controller with both reports.
Illustrative unit view with sample percentages. Not a customer result.
01 · Connected inputs
- POS by unit
- Brand fee statements
- Bank and card feeds
- Intercompany activity
02 · Lieutenant does the work
- Post by brand, entity, unit
- Check fees against sales
- Record intercompany both sides
- Apply new-unit template
03 · A person reviews
- Fee differences
- Intercompany out of balance
- New-unit setup sign-off
04 · You get
- Unit P&L: food, labor, occupancy
- Entity statements
- Brand rollups
Illustrative flow. Connections and reviewers are agreed in scope; payroll stays with your payroll provider.
Why it matters
More locations shouldn’t mean more manual work.
Each location adds transactions, entity differences, and reporting needs. Lieutenant takes on recurring bookkeeping and finance steps so your team can keep up with the work across locations.
Where work gets stuckWhat Lieutenant helps complete
Transactions pile up across locations and entities
Coded records with location and entity context, plus exceptions to resolve.
Location reports arrive after decisions are due
Reports assembled with the location and entity detail your team needs.
Completed work waits for billing
Invoices prepared from the relevant work and customer details.
How to evaluate a workflow
- Exception resolution time and close preparation time
- When reports become available each period
- Invoice preparation time; issuance time only where issuance is in scope
Suggested measures, not customer results. Invoice preparation does not establish faster collection, and time released does not automatically mean lower payroll costs.
How it works
The work moves. The decisions stay with you.
Each location and entity can carry its own rules. Items that meet them move; items that need a decision wait for the right person.
Two samples: one meets the rule, one needs review.
Systems
Where the work comes in and goes
Input
A recurring item arrives
Context
Location and entity
Your rules
Conditions set for your business
Rule check · one path or the other
Path A · Within your rules. It’s done.
Lieutenant completes the step
The work is carried out in your system, following the rules you set.
Output
Completed work in your system
Path B · Outside your rules. It waits for you.
- The item is heldNothing moves until you decide.
- You see what needs a decisionThe item, its context, and the rule that applied.
- Your decision sets the next stepThe work continues or stops based on what you decide.
Getting started
Start narrow. Judge it on your own work.
Choose
One recurring process
A workflow that consumes staff time, creates a backlog, or delays information.
Map
Systems, rules, and review points
The systems involved, the rules that apply, and where a person decides.
Assess
Representative output and a measure
Review what the workflow would produce, and agree how to judge it.
Managed together.
Lieutenant and your team share responsibility for setup, exception handling, and ongoing updates. We agree who does what for each workflow.
- Setup
- Exception handling
- Ongoing updates
Your team keeps the decisions and approvals.
Practical questions
Before we start
Do we need to replace our existing software?
We work with your existing systems. We confirm the required connections, permissions, and workflow scope before deployment.
Can we start with one workflow?
Yes. We define one recurring process, agree on the steps and approvals, and evaluate the result before expanding.
What stays under our control?
You set the decisions and approvals for the workflow. Items that need a person are routed for review.
How do you measure success?
We agree on the measure before launch, such as the time a workflow takes, the backlog it clears, or the hours it returns to your team. The measure depends on the work in scope: invoice preparation is different from collection, and time released is different from payroll savings.
Does Lieutenant only do finance?
No. Lieutenant supports finance, operations, and custom workflows. Lieutenant Finance is our dedicated finance offering; operations workflows are scoped around your process, systems, and approvals.
What can Lieutenant see in our systems?
The source systems, required permissions, and actions are defined for your workflow before deployment. Read our Security & Data Handling overview, and ask us to confirm the details for your deployment.
Start with one workflow.
Bring one costly finance process across your locations. We’ll show you what it takes to hand it off.