Ledger
Every order captured or added by hand — spend, stock, caps and realized profit.
What it's for
The Ledger is your purchase record — every order Umbra captured from a confirmation page, brought in from your sales tool, or added by hand, as its own page under Records. Orders you place on Ticketmaster, AXS, SeatGeek, Live Nation and major retail and Shopify stores are captured on your machine as checkouts complete; connect Lysted sales sync and your buys and sold prices fill in from there too, so the record is complete without the manual entry. Everything stays on this device.
Come here to see what the season has actually cost and returned: what you spent per currency, what's still unsold, whether you're inside the caps you set, and what you actually made week by week.
Reading your money — three views
The Ledger opens on three pictures, each answering a different question. All read the whole book, and — wherever money is shown — each is per currency, never merged, because a pound is not a dollar. A currency toggle on the first and third switches which one you're reading; the middle one counts tickets, which, unlike money, do add up across every currency.
Open Performance detail below the charts for the figures the pictures don't spell out, for whichever currency you've picked:
The portfolio table
Below the charts, one row per currency states the season at a glance — never merged, because a number that adds pounds to dollars is true of nothing.
The Orders table
One row per order: the event with its venue and date, the account, quantity and seats, then the money — Cost, what it Sold for, and the P&L between them (green for a gain, red for a loss, with the margin percent). A Fulfillment column reads the sale's status, or — for stock you still hold — how close the event is. Its stage — Unsold, Listed or Sold — sits last. On its own Umbra can't watch a marketplace, so for an order you capture or enter, a stage is a marker you set, never a guess. Rows brought in from Lysted sales sync are the exception: their Sold, price and stage are read from your own sales record, so there they are fact, not a mark.
A sold order that went across several marketplaces expands inline — click the chevron on its event and each sale shows on its own line (where it sold, how many, when, for how much), with a note when part of the order is still on your hands. A split sale is no longer one blurred figure.
Sort the whole list from a column header — Cost or P&L — or from the Sort menu (most-to-least profit, oldest to newest, and so on); a row with no answer for the sort, like an unsold order's profit, always sorts to the bottom rather than pretending to be the extreme. Narrow it with the stage strip (Unsold / Listed / Sold, plus Needs review when anything is flagged), the Held & unsold quick filter for everything still to move, the search box, and a real date range — pick a preset or type a from/to. The footer states exactly what you're looking at.
Change a stage from the row's ⋯ menu, or select several rows and mark them in one action — ten orders for one show marked Sold in one click. On a hand-entered order that sold, a Paid out line is offered beneath it (asked for net of marketplace fees, never required); imported rows carry their sale prices already.
Filling it from your sales tool
Entering thousands of sold prices by hand is the work this removes. Connect Lysted sales sync under Settings → Account, and Umbra reads your buys and sales straight from your Lysted account — each order's cost, the account it was bought on, the seats, and what every one sold for — and builds the ledger from them. It only ever reads: Umbra never lists a ticket, sets a price, or changes anything in Lysted.
The hard part is the sales that split. One purchase of four seats often sells as three separate orders at three different prices; Umbra stitches those back to the buy they came from, so a single row shows what the four seats cost and the sum of what they returned — your real margin, not four disconnected numbers.
Your first import replaces the ledger with what Lysted knows, so it becomes the one source of truth rather than doubling every order you'd also captured locally. A sale Umbra can't confidently place against a buy — usually one bought before you were on Lysted — is never dropped and never guessed onto the wrong order: it's kept as its own row and flagged, and the Needs review filter in the stage strip shows exactly those, so you can place them yourself.
After that, Umbra keeps the ledger current on its own. In the background it checks Lysted for new orders and sales, adds them without touching the rest of your ledger, and drops a line in your notifications — "3 new orders, 2 new sales" — so a sale that closes while you're away shows up by itself, no re-import needed. Nothing is ever wiped; the manual Import & replace stays there for a full reset whenever you want one.
Adding and correcting orders
Add an order opens the manual form — the ledger's fallback for the box office that emails a PDF, and the way to correct any captured row. The purchase date leads the form because it decides which tax year the order falls in. Blank is a fact: an order with no tax line had none — leave the field empty rather than typing 0.
Export range writes exactly what you're looking at — the current filters, search and date range, not always the whole book — and stamps the filename with the window (e.g. umbra-ledger-2026-01-01_2026-12-31.csv), so a year's file is named for its year and a partial export is never mistaken for your full records. It's the one control for "give me my 2026 orders for the accountant."
Accounts buying — and merging duplicates
Below the table, Accounts buying folds open into a ranked leaderboard of who you're buying through, most orders first. Click a row to filter the ledger to that Account; click it again to clear.
Budgets
Budgets — caps per currency holds the caps themselves: each is a per-currency limit over a window you pick — today, this week, this month or all-time — with a warn threshold. Its progress bar reads from the same ledger above it, so the figures tie out, and breach warnings fire in the background as orders land, not only while this page is open.