Post a transaction
Posting turns a synced transaction into a ledger entry. It is a two-step rhythm: stage the rows you want, review them together, then post them in one action.
Posting is available in accounting entities only. See portfolio or accounting.
Start from the overview
Posting shows pending on-chain transactions grouped by chain, so you can see where the unposted work is.
Expanding a chain breaks the count down by wallet, and a wallet down by token, with a Post button per token that opens the pending list already filtered.
The overview also shows what is blocking transactions rather than counting them: missing tokens, missing token addresses, missing token cards, and unreconciled on-chain days. Those are setup work rather than posting work, and each is resolved from that page. See the posting overview.
Find the transactions
Go to Pending transactions and choose a chain and wallet, optionally a token card and date range too, then select Search. Nothing loads until you do; the page will not guess a selection for you.
Each row shows the on-chain amount alongside Value (EUR), converted at the transaction's own date rather than today's price. A row valued at zero usually means no token price is stored for that date.
Three toolbar actions sit above the table:
| Action | What it does |
|---|---|
| Apply Rules | Runs your saved posting rules over the listed transactions, categorising everything they match in one go. |
| Add Custom Transaction | Records an entry that never appeared on-chain. |
| Import CSV | Brings in transactions in bulk from a file. |
If something you expect is missing entirely, Report missing transaction raises a support ticket from this page, prefilled with the details support will ask for.
Stage the rows
Staging a row moves it into the Staged Transactions section below without committing anything. Think of it as a basket.
You can search by transaction ID to find a specific row.
Three things worth knowing while staging:
- Splitting. A single on-chain transaction that belongs across more than one category can be split before posting.
- Saving a rule. If you find yourself categorising the same kind of transaction repeatedly, save it as a posting rule so it is categorised automatically next time.
- Bills and invoices. If the entity uses bills and invoices, staging a row contra'd to the suspense account opens a picker of open QuickBooks bills or invoices first, so the payment settles the right document.
Post
The staged section lists what you are about to commit:
| Column | |
|---|---|
| Transaction ID | The on-chain identifier |
| Timestamp | When it occurred |
| Amount | Value being posted |
| Category | How it will be classified |
| Details | Context for the entry |
Select Post Transactions and confirm. The rows leave the pending queue and appear under All postings.
Rows linked to a QuickBooks bill or invoice also have their payment created in QuickBooks at this point. See bills and invoices.
Review before confirming
Check the category on every staged row. Categorisation is what determines where the entry lands in your books, and it is far easier to correct before posting than after.
Discarded transactions
Not everything should be posted: dust, spam token transfers, and internal moves you account for elsewhere. Discarding removes a transaction from the pending queue without posting it.
Discarded rows are not deleted. Discarded transactions lists them, and you can restore any row back into the posting queue.
All postings
All postings is the full record: every ledger posting for the entity across wallets and QuickBooks accounts, with search, filters, and pagination. This is where you go to confirm something was posted, or to find an entry you need to inspect.
Categories and rules
Categories defines how transactions can be classified for this entity, and controls which VAT codes each classification allows.
Posting rules automates that classification. A rule matches on transaction type and fills in the VAT code, category and contra, so recurring activity does not need categorising by hand each time. Apply Rules above the table runs them over everything listed.
Setting up rules early pays off. The alternative is categorising the same transfer shape every period.
Next
Categories and posting rules are what make the above repeatable. If your entity handles swaps or bridges, hold matches ties their two legs together after posting.