Flag crypto assets in Bitwave that may need impairment review this period
Every Monday, WebRun opens Bitwave, reads the current market value and carrying cost of every digital asset across your connected wallets, flags any asset trading below its cost basis, and posts a prioritized impairment review list to Slack ranked by the size of the potential write-down so your accounting team can assess GAAP or IFRS impairment requirements before the period closes.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically flag digital assets in Bitwave that may need impairment review?
WebRun opens Bitwave every Monday, compares the current market value of every held digital asset against its carrying cost, and posts a prioritized impairment review list to Slack ranked by potential write-down. Your accounting team can assess whether a write-down is required under your reporting standard and enter any adjustment in Bitwave before the period closes.
- Potential impairment candidates surfaced every Monday before period close
- Highest write-down risks reviewed first with ranked priority
- No material impairment missed because of manual oversight
Built for crypto controllers · Web3 CFOs · digital asset accountants · crypto audit teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.bitwave.ioin a real browser with your saved login - no setup, no API keys. -
1
Bitwave - compare market value against carrying cost for every asset
bitwave.io How to Automate Bitwave
WebRun opens Bitwave to compare market value against carrying cost for every asset. - Open Bitwave and navigate to the asset balance or portfolio view
- For each held asset, read the current quantity, carrying cost per unit, and current market price
- Calculate the difference between carrying cost and market price for each asset
- Flag every asset where market price is below carrying cost
- Rank the flagged assets by the total potential write-down amount (quantity times the price-to-cost gap)
Done when All assets below carrying cost are ranked by potential write-down and ready to report.
-
2
Slack - post prioritized impairment review list
slack.com How to Automate Slack
WebRun opens Slack to post prioritized impairment review list. - Post the prioritized impairment review list to your accounting Slack channel
- List each flagged asset with: ticker, quantity, carrying cost, current price, and potential write-down
- Note the total potential write-down across all flagged assets
- Flag any item where the potential write-down exceeds your materiality threshold
Done when Your accounting team has this week's impairment review list in Slack before the reporting deadline.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it record an impairment write-down in Bitwave automatically?
No. Recording an impairment is an accounting judgement that requires controller approval. WebRun flags the candidates and posts the list so your team can make the decision and enter the adjustment in Bitwave themselves.
Does it follow ASC 350 or IFRS rules for crypto impairment?
WebRun compares current market price to carrying cost as a starting signal. The specific accounting standard applied (ASC 350, IFRS 9, or another) is your team's decision based on your entity's reporting framework.
What if an asset recovers in price before the period closes?
WebRun reruns the check every Monday, so a recovered asset will drop off the list the following week. Under most standards, previously recognized impairments cannot be reversed, so your team should note the date of the original flag.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.