If you've scrolled through your Transactions page expecting to see a particular buy or sell and can't find it, you're almost certainly looking at one of two situations: the transaction is there but a filter or a portfolio scope is hiding it, or the transaction was never quite saved in the first place. Both are recoverable.
This article walks through the possibilities in roughly the order they account for missing-transaction reports. Work down the list — the answer is almost always in the first few steps.
Step 1: Check the portfolio selector
The global portfolio selector at the top of the app filters everything in view, including the Transactions list. If it's pointing at a single portfolio and your missing transaction was recorded against a different one, that's why you can't see it.
A quick check:
Look at the portfolio selector at the top of the page.
If it shows a specific portfolio name, switch it to All Portfolios.
Look at the Transactions list again with the wider scope in place.
If the transaction appears once you broaden the scope, the next question is whether it ended up in the right portfolio. If it's in the wrong one, you can edit the transaction to move it — see Editing a transaction after the fact.
For background on the selector, see Switching between portfolios.
Step 2: Check the filters on the Transactions page
The Transactions page has filters of its own — most commonly a date range, a transaction type (BUY / SELL), and a search box. Any of them, if set restrictively, will hide perfectly valid transactions from view.
Things to check:
Date range. If the filter is set to "last 30 days" and the transaction is from last quarter, it won't appear. Widen the range or clear it.
Type filter. If you're filtered to BUY only and the missing transaction is a SELL (or vice versa), it'll be excluded. Clear the type filter to see both.
Search box. A leftover search term — even a single character — narrows the list to matches. Clear it.
Other column filters. Any chip or tag-style filter active above the table is doing the same job.
The clearest test is to reset every filter on the page and look at the list with no constraints applied. If the transaction shows up then, you've found the filter that was hiding it.
Step 3: Check the sort order and pagination
If the list is sorted in an order you weren't expecting, the transaction may be present but scrolled off the visible page.
Sort order. The default is usually newest-first; if it's been switched to oldest-first, the most recent transactions will be at the bottom of the list rather than the top.
Pagination. If you've got more transactions than fit on one page, the missing one may live on the next page. Check the pagination controls at the bottom of the list.
If you can't tell at a glance, use the search box with the dealer name or the product to jump to it directly.
Step 4: Was it recorded against the right portfolio at the time?
If you have multiple portfolios, it's worth a glance at where the transaction was actually saved. The Add Purchase and Add Sale forms record against the portfolio that's selected in the global selector at the moment of submission.
If you switched portfolios after starting the form, or hadn't switched yet when you submitted, the transaction may have landed in a portfolio you weren't intending.
To check:
Switch the selector to All Portfolios.
Find the transaction in the now-broader list.
Look at the portfolio column or the transaction's detail view to see which portfolio it's actually in.
If it's in the wrong one, edit the transaction to move it to the right one. See Editing a transaction after the fact.
Step 5: Did the save actually complete?
Sometimes the answer turns out to be that the transaction was never saved in the first place. Common reasons a save doesn't finish:
The browser was closed mid-form. You filled out the Add Purchase form, got distracted, closed the tab, and never came back to click Submit.
A validation error blocked the save. If a required field was missing or a value was malformed, the form will have shown an error and held you on the page rather than saving. If you walked away thinking it had saved, it hadn't.
The connection dropped at the wrong moment. Rare, but possible — if the network blipped between clicking Submit and the form acknowledging the save, the click may not have reached us.
A quick way to confirm: search the full transaction list (with no filters, All Portfolios selected) for any other identifying detail you'd expect on the missing transaction — a unique dealer name, a specific product, a particular date. If nothing matches, the save didn't go through.
The fix is the same in every case: re-record the transaction. The data wasn't corrupted; it just wasn't created. See How to record a purchase or How to record a sale depending on which type went missing.
Step 6: Was it a bulk-imported row?
If you reached this article from a bulk-upload session, a missing transaction usually means the corresponding CSV row didn't make it through validation.
Bulk Import doesn't silently drop rows — every problematic row is surfaced on the preview screen with the specific reason it can't be imported, before anything is written. See Uploading and reviewing your CSV and Fixing common CSV errors.
If you noticed errors on the preview screen and proceeded anyway, only the valid rows would have been imported. The error rows are still sitting in your CSV waiting to be fixed and re-uploaded.
If you skipped past the preview without reading carefully, the easiest path is to re-open the original CSV, find the row in question, check what's in it, and re-import once the issue is corrected.
For the broader read on what a bulk import does and doesn't do, see Bulk import overview.
Step 7: Could it have been deleted?
Deleting a transaction in Gold Silver Ledger is deliberate — you'd have to open the transaction and click through a confirmation — but it does happen, especially if you've been cleaning up other entries around the same time.
A few signs to look for:
A BUY transaction you deleted by mistake also took the inventory items it created with it. If you notice both the BUY and its corresponding held items are missing, that's the fingerprint of a deletion. See Deleting a buy transaction.
A SELL transaction you deleted by mistake would have restored the previously-sold items to held status. If you have items that recently came back to held when you weren't expecting them, that's the fingerprint of a SELL deletion. See Deleting a sell transaction.
A deleted transaction can't be restored from inside the app — there isn't an undo button. The fix is to re-record it. The longer walk-through on intentional deletions and their effects is in Undoing a mistake.
When nothing on this list explains it
If you've worked through everything above — every filter cleared, both portfolios checked, no save-in-progress drama, no bulk-import quirk, no deletion fingerprints — and the transaction genuinely isn't in your account, that's worth flagging.
A note to [Contact support] with the approximate date of the transaction, the product or dealer it involved, and the portfolio you intended to record it against is enough for us to investigate.
This is rare. The overwhelming majority of missing-transaction reports turn out to be a filter or a wrong portfolio scope. But "rare" isn't "never," and if you're confident you recorded something that we can't find, we want to know.
Where to go next
Switching between portfolios: How the global portfolio selector works.
Editing a transaction after the fact: How to move a transaction to the right portfolio or correct other details.
How to record a purchase: The full flow if a save didn't go through and you need to re-record.
How to record a sale: The same, for SELL transactions.
Bulk import overview: Where to look if the missing transaction was part of a CSV upload.
Fixing common CSV errors: What to do when rows are getting rejected at the preview step.
Undoing a mistake: The broader article on recovering from unintended changes.