What the billing partner sees.
A full batch comes back split. Every line is sorted into in-scope, out-of-scope, or advisory, each bucket tallied with its rationale.
Run the review in your browser.
A faithful recreation of the review workflow, on sample data. Keyboard-operable, and nothing leaves your browser.
Select a line to review it
Six of 300 sample lines shown · 3 carry exceptions
Select a line, or press Run review, and the exceptions surface here with their rationale, the way a billing partner sees them.
Hourly billing pays a firm less for the same work.
AI is taking hours out of tax and accounting work, and a fee that tracks hours shrinks with them. Fixed-fee billing needs the WIP sorted by scope first, and today a partner does that sort by hand.
lines in the sample WIP batch above, the kind a billing partner hand-reads today before any of it becomes an invoice.
buckets every WIP line falls into: in-scope, out-of-scope, advisory.
of the billing tools we have evaluated sort the WIP before the invoice. They start at the invoice; the sort still happens upstream, by hand.
For the billing partner
- The split is done for you: in-scope, out-of-scope, advisory.
- Every line carries rationale you can read in one sentence.
- Approve, modify, write off, or revert. Every decision stays yours.
- Friday afternoons stop costing you a Friday afternoon.
For the firm
- The compliant-vs-out-of-scope split a fixed-fee model needs, ready on day one.
- Out-of-scope and advisory work captured for billing instead of lost in the scrub.
- Per-firm taxonomy built on your service codes and your scope definitions.
- Compliant hours still tallied, so firms on billable hours lose nothing.
What firms ask first.
Does Billswarm replace CCH Axcess Practice?
No. Billswarm sits upstream of your billing tool rather than in place of it. We read the WIP export Axcess already produces, split it into in-scope, out-of-scope, and advisory work, and hand the breakdown back to whoever generates the invoice, whether that's TaxDome, Karbon, Aiwyn, or Axcess itself.
Does Billswarm integrate with CCH Axcess?
There is no integration to install. You upload the WIP export CCH Axcess already produces, one PDF, and get back a master XLSX with every line's bucket and rationale, reviewable line by line in the dashboard. No API keys and no schema mapping.
How is our client data handled?
The application is deployed into your firm's own environment, so your data never shares infrastructure with another firm, and everything is encrypted at rest and in transit. The application logs every decision on a flag with who made it and when, in an append-only record that can't be edited after the fact. The rationale for each flag stays on the line itself, in the dashboard and the XLSX. The Security page has the full posture.
Is our client data sent to an AI vendor?
Not to a public model API. Inference runs on Amazon Bedrock, called from your firm's own AWS account under your firm's IAM and billing, and the application has no model route outside your own tenant. The pipeline replaces client names and tax IDs with tokens before any line reaches the model. Under AWS's published Bedrock terms, prompts and outputs are not used to train models and are not shared with the model provider.
How does Billswarm split the WIP?
Every line is sorted into one of three buckets: in-scope (the core engagement), out-of-scope (work beyond the engagement letter), and advisory (consulting work outside the signed tax-prep scope). Each bucket is tallied, and every line carries a one-sentence rationale.
Can we override or move a line to a different bucket?
Yes, and overriding is the whole point. Billswarm proposes the bucket; the billing partner decides where each line belongs, and every decision is logged. Your overrides land in the audit trail, and we use them to tune your firm's taxonomy with you.
How long does deployment take?
Deployment is a scripted run into your firm's cloud account, done with your IT contact, followed by a working session with your billing partner to set up your service codes and scope definitions. The one step we cannot script is your firm's cloud-account provisioning, so the calendar depends on your IT.
What does Billswarm cost?
A one-time deployment into your firm's own environment, which you own, plus a per-page usage rate as you run it. Consulting for updates and support is optional and hourly, with discounted packages if you buy hours ahead. Cloud costs bill to your own account. No per-seat fees and no required subscription; a firm that would rather maintain it in-house can. Email for a quote.
See your WIP split for fixed-fee billing in a 20-minute demo.
We’ll run the console on a sample batch. When you’re ready, we run a month of your own WIP or a redacted sample, under NDA, in a deployment inside your firm’s own cloud and network.