Four levels, two legal.
Most telecom expense tools are built for multiple sites. A group is multiple legal entities, and that decides where money is denominated and where permission stops.
Request a pilotThe fit
- The reader
- Groups holding several legal entities, usually across several countries, each with its own carriers and its own books.
- The question
- What does the group pay across every operating company, and can two of them be compared on the same terms?
- The constraint
- An operating company is a legal entity that may trade in many countries, and it is where money is denominated and where permission stops. Sites are premises and services are the billed and delivered things.
- Where it starts
- One operating company and one carrier is a valid pilot. The hierarchy is there from the first row, so the second entity is configuration rather than migration.
Outcomes
Currency per operating company
Each entity holds a functional currency of its own, and it is a property of the entity rather than a display toggle. Amounts are held as billed, in the entity's functional currency and in the group's presentation currency, each naming the rate it used.
Permission follows the law
Isolation sits at the operating company, and only there. A group administrator sees every entity through one audited path, and an entity administrator can hold several entities that need not be neighbours.
Comparison inside the group
Cost per megabit delivered, compared between your own entities, on your own contracts, where you already hold the right to make the comparison. Pricing-confidentiality clauses make anything wider a consent question.
The first month
One operating company, one carrier, three invoices, and the hierarchy in place from the first row.
- The shapeThe group's entities, sites and currencies are entered as the hierarchy they are: HoldCo, operating company, site, service, with each operating company's functional currency set as a property of the entity.
- The first entityThree invoices from one operating company are parsed and matched. The services on them are the first rows on the spine, each with its provenance.
- The queueUnresolved lines, unclassified charges and ambiguous identifiers sit in one review queue, ranked. The implementation lead decides, and the decisions are recorded.
- The second entityA second operating company is added as configuration: its currency, its carriers, its memberships. Its invoices run through the same path, and the first cross-entity row appears in the group view.
Capabilities that serve this role
Questions from multi-entity groups
Our entities use different charts of accounts. Does that matter?
Cost centre is a real column on the service, per operating company, and allocation rules are explicit, so each entity keeps its own coding and the group rolls up across them without editing any of it.
What is the difference between functional and presentation currency here?
Functional currency belongs to the entity and is where its amounts are held after the billed currency. Presentation currency belongs to the group and is where consolidation is read. Every figure holds all three layers, each naming its rate id.
Can one person hold several operating companies?
Yes. Memberships are per operating company, and a person may hold several that need not be neighbours in the hierarchy. What they see is the union of their memberships, and the group path is separate.
Does the hierarchy handle an entity that trades in several countries?
Yes. An operating company is a legal entity and may hold sites in many countries. Country is a property of the site and the carrier, so spend by country and spend by entity are two cuts of the same rows.
Intercompany is two-sided
- Stance
- An intercompany recharge is evidence in two ledgers, so it is readable by the entity that sent it and the entity that received it, bounded to the same group. Shares sum exactly and the remainder lands on the largest share, so an allocation conserves to the minor unit and never edits the invoice it came from.
