VayuDocumentationIntegrationsAPI ReferenceChange Log
SupportGet started now
GuidesCustomers

Related Entities

Create a hierarchy between entities and associate child entities

It is possible to create a hierarchy between entities and associate "child" entities with a parent account. This provides a high level of customization for how usage, pricing, and invoicing flow between related entities — from keeping every entity fully separate, to combining usage or charges, to billing everything through the parent, to syncing the child's invoices to the ERP under the parent.

Relationship Types

Each relationship type controls how the child's usage, pricing, and invoicing relate to the parent — choose the one that matches how you want the accounts billed. The label in the product includes the parent customer's name. In this guide, <parent> stands for that name. Aggregate usage is the default when you add a child.

Relationship typeUsagePricingInvoice
Aggregate usage to <parent>Aggregated with the parent's usagePriced using the parent's contractParent receives and pays
Aggregate charges to <parent>Calculated separately, per entityEach entity priced by its own contractChild's charges are added to the parent's invoice; parent pays
Invoice sync to <parent> (ERP)Billed on the childBilled on the childChild's invoices sync to the ERP under the parent's ERP customer and are not marked as issued by the parent
Bill to <parent>Calculated separately, for the child onlyPriced by the child's own contractChild's invoice is billed to the parent; parent pays

Aggregate usage to <parent>: The child's and parent's usage are combined and priced using the parent's contract. The parent receives and pays the invoice. The child's usage isn't billed separately — it is simply priced through the parent's contract, rather than the two entities sharing a contract.

Aggregate charges to <parent>: Each entity is priced independently — the child through its own contract, and the parent through its own contract. The charges calculated for the child are then added to the parent's invoice, so the parent receives and pays a single invoice that includes the child's charges alongside its own.

Aggregate charges is always paired with a Partnership / Reseller agreement contract on the parent. The contract type is what establishes that the parent represents the child commercially; Aggregate charges is the mechanism that actually rolls the child's charges onto the parent's invoice. On their own, neither one produces a working reseller billing setup — see Contract Type for how to set it on the contract.

Invoice sync to <parent> (ERP): The child's invoices sync to the ERP under the parent's ERP customer. The child is otherwise billed on its own, and its invoices are not marked as issued by the parent.

Bill to <parent>: The child keeps its own contract, pricing, usage calculation, and invoice — nothing about how the child is priced or invoiced changes. The only difference is who the invoice is sent to: instead of billing the child, the invoice generated at the child level is billed to the parent, who pays it. This lets a child's invoices be billed to its parent without setting up a Reseller contract.

Setting or Editing a Relationship

Relationships are always set from the parent customer record — there is no separate field on the child record for this. A customer already linked to another parent cannot be selected, so each child has one parent.

  1. In the main menu bar, click Customers and select the customer that will act as the parent.
  2. Click Customer settings in the top-right corner of the customer's page.

Customer settings button in the top-right corner of the customer page

  1. In the settings sidebar, open Advanced > Related entities. Advanced is a group in that sidebar, with Company details and Configuration. Under Advanced are Aliases, Related entities, and Custom fields.

Related entities in the Advanced group of Customer settings, empty, with the Add entities button

The section is titled Related entities and shows a count of linked children. The description under the title is Child customers linked to this account. When no children are linked, the empty state reads No related entities and Add child customers to link them to this account.

  1. Click Add entities. The Add related entity dialog opens. Its subtitle is Add related entities and subsidiaries to this parent account. The dialog has a searchable Select entity field and a Confirm button.

Add related entity dialog with the Select entity field and Confirm

  1. Select the child customer in Select entity, then click Confirm. You can add an unlimited number of entities. A customer already linked to another parent cannot be selected.
  2. The child is listed in the Related entities table. In the Relationship type column, choose the type. A new child defaults to aggregate usage to the parent. The other choices are aggregate charges to the parent, invoice sync to the parent (ERP), and bill to the parent.
  3. Click Save at the bottom of the settings page. Save stays disabled until something on the page changes.

The table columns are Customer, External ID, and Relationship type. Each row has a menu (⋮) with Remove, which unlinks that child. Search by name or external ID filters the list. Long lists include a Show all link.

To change the type for a child that is already linked, choose a new value in the Relationship type column and click Save. To unlink a child, open its row menu (⋮), choose Remove, and click Save.

Parent customer on the Customers list

The Customers list can show which children belong to a parent.

Open Filters and add Parent customer. The operator is Contains, and the value is free text. In Column settings, show the Parent customer column.

Customers list Filters menu with Parent customer and the Contains operator

On this page