| Account | Description | Amount | Issue |
|---|---|---|---|
| Motor Vehicle | Car insurance — FY25 | (4,200) | Vehicle |
| Director Fees | Director remuneration | (24,000) | Withholding Tax |
| Entertainment | Client meals — FY25 | (3,800) | Entertainment |
| Renovation | Office partition works | (8,500) | Renovation |
Each tool targets a specific piece of the tax workflow that's tedious, error-prone, or simply overdue for automation — built after hours, one idea turned real at a time.
Enter the Armoury →Drop a GL export — Xero, MYOB, or most Excel formats — and get back a tax-ready workpaper in seconds, with the items that need attention flagged for review.
Open tool →Paste your income statement and answer a few guided questions — a draft ECI computation, return calculations and key follow-up points land in your inbox.
Open tool →Turn a rough idea into a precise AI brief — Context, Role, Audience, Format, Task, Exclusions, Documentation — and get back a clean, copy-ready prompt. Six prompt builders in one, all in your browser.
Open tool → New to AI? Start with the 2-min lesson →The Instant computation’s full-fledged sibling — the complete Singapore corporate tax file: staged classifications, capital allowances, FRS 116, foreign income, Statements A–D and the Form C / C-S summary, issued as a formatted Excel working paper. In closed beta with a small group of practitioners.
Request access →The personal return prepared the way a corporate file is — the IR8A built line by line, the Appendix 8A benefits-in-kind schedule, share plans totalled, reliefs claimed with the S$80,000 cap shown rather than silently applied, and the whole computation read as a statement. In closed beta with a small group of practitioners.
Request access →The computation for a fund exempt under sections 13D, 13O, 13OA or 13U — holdings confirmed as designated investments, each income line linked to the holding behind it, the four specified-income exclusions asked only where they bite, and common expenses apportioned on a schedule that ties back to the accounts. In closed beta with a small group of practitioners.
Request access →Load two Excel files side by side, laid out the way Excel shows them, and see every difference highlighted — changed rows pair up by colour even when reordered, and deleted or new rows read like a code diff.
Open tool →Test whether unutilised capital allowances, trade losses, and donations survive the >50% common-shareholder continuity requirement between relevant dates.
Open tool →Drop Singapore bank statement PDFs — DBS Corporate format supported — and extract structured transactions, consolidated into a single export.
Open tool →A keyboard-first calculator mapped to the left half of the keyboard, so your right hand never leaves the mouse. Audit-trail history, save/load, QuickCast.
Open tool →New tools are always in the works. Step into the Armoury to see the full rack — and what's coming next.
Enter the Armoury →Short, practical lessons on getting more out of the tools — and out of AI generally. Built like everything else here: no fluff, straight to what works.
Enter the Arcanum →Russolutions is built by Russell Sim — an SCTP Accredited Tax Advisor and ISCA Chartered Accountant, with a career spanning Big 4 tax advisory, commercial in-house roles, and co-founding Taxpedited, an SFFS-approved tax software that files corporate returns directly with IRAS.
Every rule in these tools comes from repetitive work I've done the manual way. The belief behind them is simple: humans shouldn't spend time on what computers do better. If it repeats, it's worth automating — and the time freed goes back to the human parts of the work, and of life.
What I enjoy most is building my own automation with Claude Code. Accounting automation belongs in custom-built, tested tools, not free-form AI generation — though there's real room for AI to draft first-pass judgements for a human to review. My strength is knowing the difference: what AI can and can't do, what it's better and worse at, and when to use which.
There's no sales pitch here — tools get built because something repetitive annoyed me enough. If something in your workflow deserves the same treatment, I'm genuinely interested to hear about it. It might become the next tool, or it might not — no promises, no timelines. That's the luxury of building on my own clock.
What I can tell you is that if I do take it on, I'll solve it the way I think it should be solved. That might not be the way you expect. It'll probably be more thorough than necessary, and a little over-the-top. That's just how I roll.
I'll read it, and if it's interesting, I'll reply. Write to me at russell@russolutions.sg — or find me on LinkedIn.
Read this. It's short and it matters.
The outputs are computational results from your input data and built-in rules — not tax advice, and no advisory or client relationship is created. These tools are designed for professionals capable of reviewing and validating computational output; if you use one to prepare a filing, that filing is your responsibility. For advice, speak to a qualified tax professional — preferably an SCTP-accredited ATA or ATP.
The rules engine is built around common Singapore tax scenarios and applies working assumptions where an item doesn't map cleanly — rare edge cases may be wrong, and rules may lag the latest IRAS guidance. Outputs are also only as good as your inputs: clean inputs produce clean outputs, and ambiguous items get flagged for review. You are responsible for spotting and overriding these cases — the tool flags what it's uncertain about precisely for this reason.
These tools are free — nothing is bought, no engagement is created, and everything is provided as-is. To the fullest extent Singapore law allows, I accept no liability for the outputs or how they're used: verification is the professional's job, and a filing you prepare is yours, as it always was. The data you upload is your responsibility too — be authorised to process it; the tools hold nothing either way.
No financial data stored. No profiling. No mining. Here's how it works.
Your financial data is never written to any database or storage layer. When a job is done, the data is gone. Where a tool asks you to verify your email with a one-time code, that email is the only thing retained — used purely to keep bots out and see which tools get used. Never for marketing.
There is no dashboard showing me what you upload — data passes through in memory and I'm not watching it. No ad networks, no data brokers, no aggregates passed to third parties. I don't sell your data, and that won't change even if some tools become paid down the line — your data is never the product.
Most tools run entirely in your browser. Where server-side processing is needed, data is sent via HTTPS to an isolated serverless function, processed in memory, and returned to you. Nothing is retained.
Drop it in and see what the analyser finds — in seconds.