One ledger for every wallet, chain, custodian and exchange. Reconciled to source, approved before posting, with journals ready for Xero and QuickBooks.
Built for Malaysia and Singapore first. Good night from the team.
https://t.co/s7fw58Doxx
Which chain is hardest to reconcile for your team, and why?
EVM token transfers, Solana's account model, Bitcoin change outputs, Sui objectsโฆ We want the war stories.
Five roles, clear lines:
Owner, Admin, Accountant, Approver, Viewer.
Accountants prepare and post. Approvers approve but can't post directly. Viewers read and export. Nobody can change their own role.
Multisig tip: treat the Safe as one source in your books, not each signer's wallet.
Signers authorise. The Safe holds the assets. Your books should follow the assets, not the keys.
First audit with crypto on the balance sheet? Have these ready:
1. Every wallet, exchange and custodian, and its entity
2. Period-end balances from each source
3. Internal transfers matched
4. A written pricing policy
5. Journals locked after posting
6. An exportable audit log
Hello, Kuala Lumpur ๐ฒ๐พ
If you run finance at a Malaysian digital-asset business (an exchange, a fund, a Web3 startup), we'd love to hear how you close the books today. Our DMs are open.
Revaluation, done carefully:
The system proposes carrying value vs market. You review. You post one balanced entry for the net gain or loss.
Nothing posts automatically. If the price was wrong, reverse it.
Running several entities? Our planned Institutional tier is aimed at monthly reporting, multi-entity consolidation and asset valuation reporting.
Access can already be scoped per entity, so a Singapore viewer sees only the Singapore entity.
What an auditor wants for every crypto balance: the source, the movements, the entries, who posted them, who approved them, and every change since.
If you can't export that in one go, the audit will take longer than it should.
No API you trust for an exchange? A clean CSV still works.
Our import takes: external_id, occurred_on, asset_code, direction, quantity, description.
It records source facts for reconciliation. It never posts a journal on its own.
Web3 startup or fund with quarterly reporting? That's who our planned Startup tier is for.
Wallets, exchanges and custodians in one ledger, reconciled, with journals ready for Xero or QuickBooks.
https://t.co/s7fw58DWn5
Our AI assistant has one rule: reads run, writes wait.
Ask it to explain a number or open a report and it just does it. Ask it to post, match or close, and it proposes the change, then waits for you to confirm. Every write is audited.
Question for finance teams in Singapore and KL: how are you handling crypto in this year's audit?
Same auditor as your fiat books, or a digital-asset specialist? What went smoother than expected?
Close the period, then keep it closed.
In Token Ledger an owner or admin closes a date range. Posting, reversing or re-matching inside it is refused until someone reopens it, and both the close and the reopen are audited.
Live and read-only today:
Chains: Ethereum, Polygon, Solana, Bitcoin, Sui
Exchanges: Kraken, Bybit, Binance, Gate, Backpack
Custodians: BitGo, Fireblocks
If we don't recognise a token, we skip it and flag the sync. We don't guess.
Every price in your books should answer three questions:
Where did it come from?
As of when?
Is it still fresh?
We store the source and timestamp on every price and FX rate, and flag stale totals as provisional instead of hiding them.
Hot take: "observed balance" and "booked value" should never be the same number by default.
One is what the chain says right now. The other is what your books say under your policy.
Agree or disagree?
The most common crypto bookkeeping mistake: a transfer between two of your own wallets booked as income on one side and an expense on the other.
It's the same money. Match internal transfers before you categorise anything else.