Enterprise DNA

Instead of Diligent Entities

Stop renting Diligent Entities. Own your company records.

We build your version around how your firm runs company secretarial work, bring your Diligent Entities records across, and run it for you. The statutory records stay yours.

Diligent publishes no price for Entities: you request a quote for a package sized to your organisation. Ours has no per-entity or per-seat charge.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription charges for

A quoted package to keep a list of companies and their dates

The records are plain: who the directors are, who holds the shares, what was filed and when. The deadlines come straight from the Companies Act and the Corporations Act. Most of what you pay for is the screen around them.

📞

A quote, not a price

Diligent's pricing page is a form. You find out what Entities costs in a call with a sales specialist, sized to your organisation.

🏢

A package sized to your company

Diligent describes its pricing as tiered and tailored to your size and stage of growth. The bill follows how big you are, not how hard the work is.

🌍

A hundred jurisdictions you may not need

Entities is built to track obligations across more than 100 jurisdictions. A New Zealand and Australian group pays for that reach and uses two.

🗂️

Reports with the columns they chose

Quick Reports export what the vendor built. Questions like who ultimately owns a company through a chain of holding companies mean another spreadsheet.

📊

Structure charts as a feature

Drawn ownership charts and dashboards are part of the package. The ownership itself is a short list of who holds which shares.

🔐

Your statutory records in their system

The registers the law asks you to keep live inside the vendor's platform. Leaving means exporting reports and rebuilding the history somewhere else.

Your version

Company secretarial work, run from a database you own

DEADLINES

Every date the law sets, worked out for you

No calendar to keep by hand. Each deadline comes from the rule and the date something happened.

  • check Director changes notified within 20 working days in New Zealand, counted around public holidays and the Christmas break
  • check Australian appointments, resignations and share changes within 28 days
  • check Annual returns in each company's filing month and annual meetings within six months of balance date
  • check ASIC review fees, statement checks and solvency resolutions from each company's review date

RECORDS

Registers that keep themselves straight

The share register is every issue and transfer added up, so it cannot drift.

  • check Current and former directors and secretaries for every company
  • check Shareholdings worked out from issues, transfers and buy-backs, never typed in
  • check A transfer of more shares than someone holds is refused on the spot
  • check Branded registers of directors and shareholders for every company, ready to print

OWNERSHIP

Who really owns what

The question a bank, a buyer or a lawyer asks, answered across your whole book.

  • check Look through every holding company in a chain to the people and trusts at the top
  • check Every company one person is a director or shareholder of, in one list
  • check A client group's ownership laid out from the top company down
  • check Each answer shows the chain the share runs through

NZ AND AU RULES

The checks a trans-Tasman group needs

Built for the two Acts your clients actually live under.

  • check A New Zealand company with no director living in New Zealand or directing an Australian company
  • check An Australian company with no Australian-resident director
  • check Australian directors with no director ID on file
  • check New Zealand directors with no signed consent, and board minutes not written up within a month

Make it yours

Design your own Diligent Entities replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Diligent Entities 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 Diligent Entities data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Entity Management for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Entity Management for Claude Code

Connected to your own database

What do we need to sort out this week across our companies?

breached

Entity
Kauri Trading Pty Ltd
Item
Tom Kauri (director since 2020-08-22)
Finding
no director ID on file
Rule
AU-DIRECTOR-ID

breached

Entity
Pohutukawa Dental Limited
Item
Sam Okoro (director since 2022-07-01)
Finding
no signed consent on file
Rule
NZ-DIRECTOR-CONSENT

breached

Entity
Kauri Orchards Limited
Item
annual return 2026
Finding
due 2026-09-30 (-11 days)
Rule
NZ-ANNUAL-RETURN

breached

Entity
Pohutukawa Dental Limited
Item
annual meeting balance date 2026-03-31
Finding
due 2026-09-30 (-11 days)
Rule
NZ-ANNUAL-MEETING

breached

Entity
Rimu Freight Australia Pty Ltd
Item
Board meeting: Melbourne depot lease on 2026-09-01
Finding
minutes not recorded, due 2026-10-01
Rule
AU-MINUTES

breached

Entity
Rimu Freight Australia Pty Ltd
Item
Priya Nair ceased as director on 2026-09-06
Finding
notice due 2026-10-04 (-7 days)
Rule
AU-OFFICEHOLDER-NOTICE

breached

Entity
Rimu Freight Limited
Item
Hemi Rawiri appointed director on 2026-09-07
Finding
notice due 2026-10-05 (-6 days)
Rule
NZ-DIRECTOR-NOTICE

breached

Entity
Kauri Trading Pty Ltd
Item
directors: Mere Kauri (NZ), Tom Kauri (NZ)
Finding
no director ordinarily resides in Australia
Rule
AU-RESIDENT-DIRECTOR

due

Entity
Rimu Freight Australia Pty Ltd
Item
Board meeting: Priya Nair's resignation on 2026-09-21
Finding
minutes not recorded, due 2026-10-21
Rule
AU-MINUTES

due

Entity
Rimu Freight Limited
Item
1500 ORD to Hemi Rawiri on 2026-10-07
Finding
notice due 2026-10-21 (10 days)
Rule
NZ-SHARE-ISSUE-NOTICE

Ask it anything

Questions for your company secretarial book

Each one runs against the fictional demo practice today. On your version, it runs against your own companies, directors and shareholders.

chat_bubble Which changes has the Companies Office or ASIC not heard about yet, and what is the last day for each?
chat_bubble Which New Zealand annual returns are due this month, and which has already slipped past its month?
chat_bubble Which Australian companies still need a solvency resolution before the two months run out?
chat_bubble Which companies have no director who meets the residence rule in their country?
chat_bubble Which directors of our Australian companies have no director ID on file?
chat_bubble Every company Grace Liu is a director or shareholder of, including through other companies?
chat_bubble Who ultimately owns Harbour Developments once you look through every company in the chain?
chat_bubble Which board meetings have no minutes written up within a month?
chat_bubble Which client group has the most late items, and who looks after it?
chat_bubble What does each person in the practice have due in the next 30 days?

Switching

How to switch from Diligent Entities

In practice, the move involves exporting your records, testing and checking the import, then running both systems side by side briefly before you stop using Diligent Entities.

  1. 1

    Export three Quick Reports

    Run Diligent Entities' three standard Quick Reports: All Entities, Appointments and Shareholders. Save each report as a spreadsheet file, using CSV as described in the import guide. These reports provide the entity, appointment and shareholder records the import expects. If you cannot find these reports or your account offers a different export format, check with Diligent Entities before you proceed.

  2. 2

    Test, then load your records

    Start with the import's test option before bringing anything into the database. It shows the entities, people, appointments and shareholdings it would create, without saving them. Once the test looks right, run the import to bring those records across. Directors, secretaries, residence and director IDs, and each shareholding are included in one step.

  3. 3

    Review skipped rows and records

    Read the test results carefully. Review every record the test says it would skip and the reason given. Check the entities, people, appointments and holdings it would create against your Diligent Entities records, with particular attention to names, ownership and officer details. Resolve gaps before the live import, then repeat the test until you understand what will come across and what will not.

  4. 4

    Run both systems side by side

    Keep Diligent Entities available for a short period while you check the imported records against the originals. Compare the information your team relies on, including officers, shareholdings and upcoming items. Confirm that your team can find what it needs in the new setup. Remember that Entity Management records and reminds, but you or your team still file with the registry.

  5. 5

    Switch off Diligent Entities

    Once you are satisfied that the records you need have come across and your team is comfortable using the new setup, stop using Diligent Entities. Keep in mind that the standard import covers entities, appointments and shareholdings. The full share transaction history is brought across for you when Enterprise DNA runs the move.

construction

Where the real effort goes

Most of the work is usually mapping your own fields and rules, then deciding how much history to bring across. The standard reports cover entities, appointments and shareholders, while the full share transaction history needs separate attention. If you have Enterprise DNA run the move, they handle the mapping and bring that full share history across.

Not ready for a call?

Get your Diligent Entities switch plan by email

We will send you the step-by-step plan for moving your business off Diligent Entities, 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 run it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /attention and /notices on the demo practice
  4. 4 Test your Diligent Entities exports with import diligent --dry-run
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your companies, trusts and client groups set up, with each filing month and review date checked
  • check Your Diligent Entities records brought across, with the share history if you need it
  • check A drawn ownership chart, a client portal or other countries' rules if you want them
  • check Registers, resolutions and client reminders in your firm's brand
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and run inside Omni by Enterprise DNA
  • check Every deadline watched, with reminders drafted to clients before they fall due
  • check Resolutions, consents and registers drafted for signing
  • check A Monday summary of what is late, what is due and who is on it
Book a call

Questions

Instead of Diligent Entities, answered

Can we bring our Diligent Entities records across? expand_more

Yes. Run three of Diligent's standard reports (entities, appointments and shareholders), save them as spreadsheet files, and do a test run that lists everything that would come across and every row that would be skipped, with the reason. Then bring it in. Directors, secretaries, residence and director IDs, and each shareholding arrive in one step. The full share transaction history is something we bring across for you.

Does it file with the Companies Office or ASIC? expand_more

No. It tells you what is due and by when, drafts the resolutions, consents and client reminders, and records what you lodged with its reference. You or your team still file with the registry. When we run it for you, we watch the dates and prepare everything for lodging.

How do you know the deadlines are right? expand_more

Each rule is written down with the section of the Companies Act 1993 or the Corporations Act 2001 it comes from, and the system checks your records against those rules every time you ask. New Zealand deadlines count working days around public holidays and the Christmas break. When a rule changes, the rule and the check change together.

We look after hundreds of client companies. Does it still work? expand_more

Yes. There is no charge per company or per user, so adding clients does not change the bill. Each company sits in a client group with the person who looks after it, so you can see what each group and each staff member has due.

What does Enterprise DNA charge? expand_more

One setup fee to build your version and bring your records across, then a retainer for ongoing work. There is no per-entity band. If you would rather run it yourself, the free version is yours to keep.

Bring your entity list to a 30-minute call with Sam

Bring the list of companies you look after, a Diligent Entities report and the deadline that last caught you out. We will map the version your firm needs and what it takes to bring your records across.

Entity Management for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Diligent Entities?

Get your version built