Northgate Advisory Ltd · 2 items

£4,290 on this register, and no cover for it appears in what we can see

A ledger shows a premium leaving an account, so it can show what is held and never the absence of anything. If cover for these is in place, the audit is where to say so.

What replacing all of this would cost

£4,290

Worked out from what each one cost and how old it is. Nobody typed it, and no form on this page offers to. That is the same as what they cost, and it is still the number a sum insured needs: a fixed asset register would have depreciated them by now.

Every line, and how each was valued

Lines nobody typed

2 of 2

A bank statement described them, and the engine worked out what they were and what they are worth to replace.

Still to fill in

2 lines

A serial number is the one thing a bank line can never carry, and it is what a theft claim turns on.

Fill it in

What only you can add

A bank line and a set of accounts can both say what you bought and when. Neither of them can say which exact unit is yours, and neither of them ever saw the things you paid cash for. That is the part below, and it is small.

2 items have no serial number

0 of 2 carry one

A serial number is what identifies a specific tool as yours once it has been taken, and it is the one thing a bank line can never carry. One box each. Adding one corrects the row the ledger already found rather than opening a second row for the same tool.

From the page you bought it from

Paste the address and the shop's own product data fills the form in: what it is, who made it, the model number and the list price. Nothing about it is guessed, and nothing about it is trusted either. It is a fact with a source, exactly like everything the audit extracts, and you confirm it.

No product page to hand? These two are served by this prototype, and say so on their face.

By hand

Cash purchases, gifts, anything bought before the ledger window, and anything a bank line cannot describe. Replacement value is not asked for: the engine derives it from the category and the purchase date, and shows its working on the row.

The register

Every line, and how it was valued. Open a row for the working, to correct it, or to take it off. Nothing here is deleted: taking a line off records that it came off, and it can be put back.

2 items 0 with a serial number

Item	Bought	Cost	Replacement	Source	Adjust
IT equipment from Apple UK Macbook PRO IT equipment · no serial number How this was valued Like-for-like replacement is treated as flat for this category, so cost stands after 0.6 years. Evidenced by 2026-03-02 · APPLE UK MACBOOK PRO · £2400.00, which is what a handler would ask for as proof of purchase.	2 Mar 2026	£2,400	£2,400	From a bank line	Correct Item Category What you paid Purchase date Serial number Taking a line off is recorded rather than done: it comes off the register and off every total, and the block below this table will offer to put it back.
IT equipment from Dell UK Latitude X2 IT equipment · no serial number How this was valued Like-for-like replacement is treated as flat for this category, so cost stands after 1.1 years. Evidenced by 2025-08-18 · DELL UK LATITUDE X2 · £1890.00, which is what a handler would ask for as proof of purchase.	18 Aug 2025	£1,890	£1,890	From a bank line	Correct Item Category What you paid Purchase date Serial number Taking a line off is recorded rather than done: it comes off the register and off every total, and the block below this table will offer to put it back.

Every line shows its own working, and a correction goes through the same check as something typed.

How this list keeps itself

Where the rows come from

From a bank line: 2 of 2, described by a bank statement and valued without anybody typing
From the books: 0 of 2, capitalised in your own accounts and copied here
Declared: 0 of 2, which is what this screen is for
With a purchase record: 2 of 2, being the bank line that proves the purchase at claim time

A line you declared is not the same as a line with nothing evidencing it, and a claims handler weighs them differently, so a claim says which it is rather than saying "none".

Where these edits live

In the address of this page, and nowhere else. A reload keeps them, the back button keeps them, and every link on this page carries them forward, including the one to the claim. Send someone this URL and they see the same register; open /register?demo=northgate-advisory without it and the ledger version comes back.

This business belongs to nobody: it is one of four fictional ones this prototype ships, so storing an edit against it would make one reader's register into everybody's. A business on an account keeps its register on the account instead, and no link carries anything.

No edits yet.

Two ways in that are not built

Both of them need somewhere to put a file. This deployment can keep a register and cannot keep a photograph of a receipt: a database row is not a filestore. Written up in full in asset-capture-concept.md, and stated here rather than drawn, because a picture of a working integration is the same class of overstatement as an audit that states something a ledger cannot show.

A receipt on an item: One invoice is routinely four tools, so the mapping is many to many and worth designing properly rather than bolting on. What the register can already say is which lines carry a purchase record and which do not, and it says it above.
A forwarding address: Forward an order confirmation and it files itself, at an address shaped like asset+<token>@docs.pickle.com. The token is the whole credential, so it has to be long, per target and revocable, and inbound mail is spoofable and has to be checked rather than trusted. Nothing receives that address today.

This is what the register is for.

The same register from the business's own side, carrying the same company and the same edits.

Illustrative only. This is a statement of demands and needs based on public records and information you confirm, not a personal recommendation or a quote. Prices are banded estimates derived from published rates and are not an offer of cover.