Portfolio / holdings

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Positions rather than transactions: what is owned and what it is worth now, which is the question a holder actually has.

Shows unrealised change per holding, so a portfolio that looks healthy in total but is carried by one position reads correctly.

Depreciation appears as a negative, which a transaction log never surfaces.

Mixed asset types sit in one table — equity, leases, equipment, cash — because that is how a small balance sheet actually looks.

How it works

1
Positions are recorded rather than transactions — what is owned and what it is worth now.
2
Change is derived from cost against current value, so it cannot disagree with its inputs.
3
Mixed asset types sit in one table, because that is how a small balance sheet looks.
4
Depreciation appears as a negative, which a transaction log never surfaces.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Holdingrequired	text	What is owned, named as the holder refers to it.
Unitsrequired	text	How much — a percentage, a count, or one. All three occur.
Costrequired	money	What was paid to acquire it, stated once when the position is opened.
Value nowrequired	money	What it is worth today, which is the question a holder actually has.
Change	text	Unrealised gain or loss, derived rather than stated.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Valuations are whatever somebody entered. Nothing fetches a market price.
No transaction history, so how a position was built is not recorded.
One currency, and mixing them produces a silently wrong total.
No tax treatment or realised-gain calculation.

Before it works

What you have to provide, if anything.

Update the valuations on a schedule, or Change becomes fiction.
Pair with Finance dashboard, which is where the total belongs.

In practice

A small syndicate holding a stake in one business and some equipment.

“The Atelier Nord stake is worth about sixty-eight now. We put in forty.”

What was said to the agent

What the agent built

A holding at 40,000 cost and 68,000 current, showing plus seventy percent.

What changed

The same table showed equipment down a third. The gain and the quiet loss were on one screen for the first time, which changed what got sold.

Better with

These do a different job on the same data. An agent can have all of them.

Finance dashboardLive

A decision is pending — a hire, a lease, a large order — and the answer depends on several numbers at once.

Assets / equipmentLive

Equipment is expensive, individually identifiable, and goes missing or out of service.

ReportsLive

Someone outside the day-to-day needs the picture periodically, with interpretation rather than raw figures.

Questions

What data does the Portfolio / holdings page use?

It reads holding records the agent has collected. Assets, positions, value. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.