Enterprise DNA

Instead of Caseware

Stop renting Caseware. Own your year-end system.

We build your version around how your practice prepares, reviews and signs accounts, bring your Caseware trial balances across and run it for you.

Caseware does not publish its prices. Its cloud licences are counted by active user and quoted through its sales team, so ask for your renewal figure before you compare.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The recurring software bill

What the Caseware licence pays for

Start with the work your team does every year-end: a trial balance, a set of workpapers, a review and a partner signature. Much of what you license is the screen around that work.

group

Active user licences

Caseware Cloud is licensed by the number of active users. Every preparer, reviewer and partner who opens a file counts.

request_quote

Prices by quote

No price list is published. Your figure comes from a sales conversation and the renewal terms you agreed.

apps

Separate apps

Financials and audit sit in separate cloud apps. A practice that only produces year-end accounts can still end up comparing several products.

description

Templates and content

Statement and workpaper templates come with the product. Your own layout still needs setting up and keeping current each year.

desktop_windows

Desktop and cloud versions

Caseware sells Working Papers on the desktop alongside its cloud apps. Check which of them your renewal covers.

lock

One client at a time

Each file is opened on its own. Seeing every late file and every open question across the practice takes extra reports or a spreadsheet.

The work in your own database

From a client's ledger to signed accounts

Trial balance

Every account mapped and balanced

Bring the closing balances in, map each account to a statement line and see the comparatives beside it.

  • check Final balances after posted journals
  • check Proposed journals kept apart until posted
  • check Unmapped accounts listed for every file
  • check A file cannot move on until it balances

Workpapers

A reason behind every movement

Each workpaper records the evidence held and the conclusion reached, and who prepared it.

  • check Movements over materiality checked against prepared workpapers
  • check Evidence reference and conclusion on every workpaper
  • check Workpapers still to prepare, by preparer
  • check Next year's index carried forward from this year

Clients

The questions you are waiting on

Track what you asked each client, when it is due and who owns the chase.

  • check Overdue client questions across every file
  • check A draft letter listing what is still needed
  • check Answers recorded against the question
  • check Files held until the questions are answered

Review and sign-off

Second review and partner sign-off you can show

The reviewer is never the preparer, and the partner signs only when the file is complete.

  • check Review points open more than a week
  • check Terms of engagement checked before sign-off
  • check NZ minimum requirement references checked for companies
  • check Signed files locked, with a workpaper and sign-off sheet

Make it yours

Design your own Caseware replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Caseware. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Caseware replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Caseware data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three real runs against a fictional practice. Ask a question and see the files, client questions and movements behind the answer.

forum

Year-End Accounts for Claude Code

Connected to your own database

What needs attention across the practice today?

Review point open over 7 days

Record
RP-101
Owner
Aroha
Due
2026-10-08

Client query overdue

Record
Q-101
Owner
Aroha
Due
2026-10-11

Accounts overdue

Record
YE26-103
Owner
Priya
Due
2026-10-14

Movement over materiality unexplained

Record
YE26-101
Owner
Aroha
Due
2026-10-29

Unmapped accounts

Record
YE26-101
Owner
Aroha
Due
2026-10-29

Ask it anything

Ten questions across every year-end file

The free version answers these questions today, across every client at once. They show how your records fit together, without claiming that a Caseware file cannot answer them one client at a time.

chat_bubble Which year-end files are past their due date and not yet issued?
chat_bubble Which trial balances do not balance after posted adjustments?
chat_bubble Which accounts are still not mapped to a statement line?
chat_bubble Which movements over materiality have no prepared workpaper?
chat_bubble Which client queries are overdue and who owns the chase?
chat_bubble Which review points have been open longer than seven days?
chat_bubble Which files are held from sign-off only by missing references?
chat_bubble What profit does each file report against last year?
chat_bubble Which preparers carry the most workpapers still to prepare?
chat_bubble Which proposed adjustments are waiting, and what do they do to profit?

Switching

How to switch from Caseware

A move usually involves exporting each trial balance, mapping your fields and rules, checking the imported records, then running both systems side by side before you stop using Caseware.

  1. 1

    Export trial balances

    Export each client's trial balance from Caseware, using the export option your account allows, usually CSV or Excel. Check with Caseware if you are unsure how to export it. Add the client and period details to each export. Workpapers, journals, sign-off history and attachments do not transfer, so keep those Caseware records available for reference.

  2. 2

    Map and load records

    Prepare the trial balance exports by adding client and period details, then map your columns and account map numbers. Run a test import first so you can review what it would bring across without saving anything. Once the mapping is right, load the records. The import brings clients, files, accounts, balances and comparatives across, and keeps the original rows.

  3. 3

    Check import results

    Review the import results before treating the new records as ready. Check any unmapped accounts, files that do not balance, and changed rows that need reconciliation. Correct the source details or mapping, then rerun and confirm the records are right. Every account must be mapped and the trial balance must balance before a file can be marked prepared.

  4. 4

    Run both systems

    For a short period, keep Caseware as your reference while you work in the new database. Compare trial balances and comparatives, check mapped accounts and balances, and make sure the team understands that workpapers, journals, sign-off history and attachments remain in Caseware. Resolve differences before relying on the new system for live year-end files.

  5. 5

    Stop using Caseware

    Once you have checked the imported records and your team is working from the new database, stop using Caseware for new year-end work. Keep the Caseware files available for historical workpapers, journals, sign-offs and attachments that were not imported. Confirm your record-retention needs and any licence arrangements with Caseware before ending access.

construction

Where the real effort goes

The import itself is only part of the work. You will usually spend more time mapping your own columns, account numbers, statement lines and rules, then deciding how much history to bring across. The import carries clients, files, accounts, balances, comparatives and mapping, not workpapers or sign-off records. If Enterprise DNA installs and runs it for you, they do this setup work with you.

Not ready for a call?

Get your Caseware switch plan by email

We will send you the step-by-step plan for moving your business off Caseware, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Use the free version or have your version built

Open source

Do it yourself

Free code

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Map your Caseware trial balance export and test the import with --dry-run.
  4. 4 Check balances against Caseware before using your own database.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your statement layout, workpaper index and sign-off rules
  • check Your Caseware trial balances and map numbers brought across
  • check A web front end or client portal if your team wants one
  • check A link to your ledger or a different technology setup if you need it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and connected through Omni by Enterprise DNA
  • check Access, backups and each year's import looked after
  • check Weekly due date and client question follow-ups kept current
  • check Statements, letters and sign-off sheets in your practice brand
Book a call with Sam

Questions

Instead of Caseware, answered

Does this replace everything Caseware does? expand_more

No. The free version covers special purpose year-end accounts for small clients: the trial balance, mapping, journals, workpapers, client questions, review and partner sign-off. It does not run audits, write general purpose disclosures or lodge returns. Enterprise DNA scopes anything else your practice needs into your version.

How do our Caseware files come across? expand_more

Export each trial balance from Caseware, add the client and period details, and map your columns and map numbers once. The free version brings clients, files, accounts, balances and comparatives across and keeps the original rows. Workpapers, journals, sign-off history and attachments stay in Caseware for your records.

Can we trust the numbers and the sign-offs? expand_more

A file cannot be marked prepared until it balances, every account is mapped and every large movement has a workpaper. The reviewer cannot be the preparer, and the partner cannot sign until review points are cleared and the terms of engagement are recorded. The system shows what your team records, so the partner still reads the file.

What does it cost to have our version built? expand_more

The code is free to run yourself, with your own hosting and running costs. Enterprise DNA charges one setup fee, then a retainer for the agreed work. Your practice keeps its database and gets its layouts, rules and screens shaped around how it works.

Are the compliance checks a professional sign-off? expand_more

No. They show files missing terms of engagement, the NZ minimum requirement references for companies, or a retention review. The partner remains responsible for the accounts. Enterprise DNA can build your own quality rules and your professional body's requirements into the checks.

Bring one client file and your Caseware renewal

Book 30 minutes with Sam. Walk through one year-end file, from the trial balance to the partner's signature. Agree what your version needs and what Enterprise DNA would build and run.

Book a 30-minute call with Sam Get the free version

Year-End Accounts for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Caseware?

Get your version built