A many-to-many relationship between a business entity and a virtual account, with effective dating and a relationship type.

Fields

• id — integer() — primary key (e.g. 1)
• business_entity_id — integer() — FK to business_entities (e.g. 1)
• virtual_account_id — integer() — FK to virtual_accounts (e.g. 10)
• relationship_type — String.t() — one of relationship_types/0 (e.g. "owner", "beneficiary")
• valid_from — Date.t() — when the relationship became active (e.g. ~D[2026-07-07])

• valid_to — Date.t() | nil — when it ended; nil while still active (e.g. nil or ~D[2026-12-31])

• metadata — map() — extensible key/value store (default %{}, e.g. %{"note" => "joint account"})

• inserted_at — DateTime.t() | nil — set by Ecto (e.g. ~U[2026-07-07 12:00:00Z])

• updated_at — DateTime.t() | nil — set by Ecto

Associations

• business_entity — belongs_to Logistiki.BusinessEntities.BusinessEntity
• virtual_account — belongs_to Logistiki.VirtualAccounts.VirtualAccount

Unique constraint

The pair (business_entity_id, virtual_account_id, relationship_type) is unique — but multiple relationship types between the same entity and account are allowed (e.g. :owner and :beneficiary).

Example

%Logistiki.Relationships.EntityAccount{
  id: 1,
  business_entity_id: 1,
  virtual_account_id: 10,
  relationship_type: "owner",
  valid_from: ~D[2026-07-07],
  valid_to: nil,
  metadata: %{"note" => "primary owner"}
}