---
title: "Understanding inheritence in derived portfolios"
slug: "transaction-syncing-in-derived-transaction-portfolios"
updated: 2026-01-07T10:13:29Z
published: 2026-01-07T10:13:29Z
canonical: "support.lusid.com/transaction-syncing-in-derived-transaction-portfolios"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding inheritence in derived portfolios

A derived transaction portfolio is an exact replica of its parent at the moment it is created. The derived portfolio inherits:

- Every transaction
- Every portfolio property
- Portfolio settings such as the accounting method, amortisation method, transaction type scope, list of sub-holding keys and so on.

A derived portfolio continues to inherit all subsequent changes until such time as you directly edit the derived portfolio itself.

If you do this (for example, by changing a particular transaction or choosing a different accounting method), then the link between the two portfolios **for that attribute** is now broken. Subsequent changes made to the parent are *not* inherited.

## Transactions

If you directly edit a particular transaction in a derived portfolio then the link to the original transaction in the parent is broken, and subsequent changes are not inherited. This can be a change to any field, `Transaction` property, or [cancelling](/v1/docs/how-do-i-cancel-a-transaction) the transaction itself.

Once broken, it is not possible to reinstate the link between the two transactions. In summary:

- A derived portfolio inherits all transactions from the parent portfolio at the moment it is created: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/1e160c86-92ba-44bc-be35-ddffb28b1c9e.png)
- You can add new transactions to the parent portfolio and they are automatically synced to the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/647d61ba-96df-4f60-af36-e0ec8ae98c43.png)
- You can add new transactions to the derived portfolio but they are NOT synced back to the parent portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/e0ca53be-bc13-4a1d-902e-9f3b51365c47.png)
- You can update an existing transaction in the parent portfolio and the change is synced to the same transaction in the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/d5e6e215-1017-4733-a746-220dbb210bc7.png)
- You can update an existing transaction in the derived portfolio but the change is NOT synced back to the same transaction in the parent portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/10412f2f-17e9-407b-8a0f-e3eaa892e27f.png)
- Furthermore, the link between the two portfolios *for this transaction* is now broken; subsequent changes to the transaction in the parent portfolio are NO LONGER synced to the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/b10d16dd-2006-4b04-bef7-9941a8a26c92.png)

## Portfolio properties

If you edit a particular `Portfolio` property in a derived portfolio then the link to the original property in the parent is broken and subsequent changes are not inherited.

It *is* possible to reinstate the link between the two properties by explicitly [nulling the value](/v1/docs/updating-or-deleting-properties#deleting-properties) in the derived portfolio. In summary:

- A derived portfolio inherits all properties from the parent portfolio at the moment it is created: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-1.png)
- You can add new properties to the parent portfolio and they are automatically synced to the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-2.png)
- You can add new properties to the derived portfolio but they are NOT synced back to the parent portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-3.png)
- You can edit an existing property in the parent portfolio and the change is synced to the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-4.png)
- You can edit an existing property in the derived portfolio but the change is NOT synced back to the parent portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-A.png)
- Furthermore, the link between the portfolios *for this property* is now broken; subsequent changes to the property in the parent portfolio are NO LONGER synced to the derived portfolio: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-B.png)
- However, you can reinstate the link by explicitly nulling the value in the derived portfolio'; subsequent changes to this property in the parent portfolio are inherited again: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/DerivedPortfolios-Portfolio properties-C.png)