Instead of iBAIS
Leave iBAIS behind. Own your broking records.
Enterprise DNA builds your version around how your office quotes, renews and handles claims, maps your iBAIS reports across, and runs it for you. Trust accounting stays in a system built and audited for it.
BAIS publishes no price or licence model for iBAIS. The core system and add-on modules such as Premium Funding, the Rating Engine and the Customer Self Service Portal are quoted privately.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the BAIS quote covers
One private quote, a long feature list, and add-ons on top
BAIS sells iBAIS to brokers, underwriting agencies and claims managers as one system running from quote and policy through to the ledger. The clients and policies inside it came from your office. A large part of the quote pays for the way you reach them.
No figure until you call
The iBAIS page has no pricing section and no licence model. The way in is the contact form or the Australian support line.
Modules sold as extras
Financial Services, the Customer Self Service Portal, Premium Funding, the Rating Engine and Time-costing are listed as add-on modules, each outside the core.
Reports through a report writer
Custom reports are built in the eXpress Report Writer. A question the standard reports do not cover becomes a report someone has to design.
Talking to their screens
Voice-controlled queries and build-your-own dashboards work inside iBAIS's own reports and screens, not on the records directly.
Conversion that runs one way
BAIS advertises a full conversion service into iBAIS, from a team with hundreds of conversions behind it. Its pages say nothing about converting out.
Years of book in their engine
Policies, claims and invoices sit in the Universe database engine iBAIS runs on. Its reports export to XLS, CSV and html.
What you get instead
Your brokerage's book, answered in plain English
Clients
Each client and every cover they hold, in one read
A client is one record with all their policies and sections beneath it, so a business's property, liability and fleet covers read as one programme rather than separate searches.
- check Every client on cover who has not heard from you in six months, biggest premium first
- check Which broker looks after which clients, and what changes hands if someone resigns
- check Endorsements stored with the day they took effect
- check A name that matches two clients lists both and asks, rather than guessing
Renewals
A renewal pipeline, not a list of expiry dates
Every renewal carries its stage, from not started through in market to bound, so Monday begins with what has slipped.
- check The sixty day outlook, ordered by premium where nobody has rung the client
- check Policies past expiry that still show as in force, flagged at the top
- check Renewals in market longer than the underwriter promised terms
- check Which insurer takes longest to come back with terms, class by class
Claims and compliance
Claims and advice files checked against the Code
Each claim event and advice record is its own entry, and a check lists every file short of the rules your brokerage operates under.
- check Open claims ordered by how long since the client was last updated
- check Placements from the past year with no advice record on file
- check Every rule quotes the clause it comes from, such as the Insurance Brokers Code of Practice
- check Claim progress letters drafted from the record for a broker to read and send
Ownership
Plain records, changed by describing the change
Your book sits in a database any tool can read, and a new field, stage or report arrives when you ask for it.
- check Brokerage earned by month and insurer, and what was booked but never received
- check Schedules and claim letters in your own colours and logo
- check A new question answered the day you think of it, with no report writer
- check Open source, with nobody to ask permission
Make it yours
Design your own iBAIS replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from iBAIS. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your iBAIS data across and run it for you.
Switching
How to switch from iBAIS
A move involves exporting the records iBAIS makes available, mapping them into the new database, checking the import, then running both systems together before you stop using iBAIS.
- 1
Export your records
Start with iBAIS reports for clients, policies, claims and contacts, which can export to XLS or CSV. Ask BAIS in writing for a full extract well before your agreement ends, since its published conversion service covers moves into iBAIS, not out of it. Check with BAIS what your account allows and which records and history you can export.
- 2
Map and load the records
The iBAIS report columns do not match the new system's import format, so map the fields before loading anything. Start with the records you need in the new system, and decide how much history to bring across. Run the offered test import first. It shows every row before anything is written, giving you a chance to check the mapping and correct problems.
- 3
Review the import flags
Go through the test results row by row. Check which records loaded, which were flagged, and whether key details such as client contacts, policy periods, claims and brokerage are in the right place. Resolve the flagged rows before loading the full set. If a field or rule in iBAIS has no clear match, decide how you want it represented rather than leaving it out without review.
- 4
Run both systems together
Keep iBAIS available while you work from the new database as well. Compare client, policy, renewal and claims records between the two systems, and check that your team can find the history it needs. Use this period to catch missing records or mapping issues and agree which system staff should update for each task. Do not treat the new records as complete until those checks are done.
- 5
Switch off iBAIS
When the records and working process have been checked, agree a cutover point with your team. Make sure staff know where to record new work and where to find older history. Keep any systems you still rely on for work the free version does not cover. End or switch off iBAIS only after you have confirmed what must remain available and how you will handle it.
Where the real effort goes
The main work is usually mapping your own fields and rules, then choosing how much history to bring across. The iBAIS exports need mapping before they fit the new import, and the test run helps expose gaps before records are written. If Enterprise DNA runs the move for you, it handles that mapping. If iBAIS holds your trust account or ledger, plan that separately because the free version does not hold client money or a ledger.
Not ready for a call?
Get your iBAIS switch plan by email
We will send you the step-by-step plan for moving your business off iBAIS, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your iBAIS switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Try the free version, or have Enterprise DNA build and run yours
Open source
Run it yourself
Free
- 1 Download the free version from GitHub
- 2 Load the demo brokerage and open it in Claude Code
- 3 Ask what renews in the next fortnight with no client contact
- 4 Export your iBAIS reports to CSV and ask Claude Code to map them in
Omni by Enterprise DNA
Have Enterprise DNA build it for you
One setup fee, then a monthly retainer
- check We map your iBAIS clients, policies, claims and contacts across and check every count against what you had
- check We connect it to the accounting and trust account system that keeps your ledger
- check We set up the renewal stages, broker reports and compliance checks your office runs on
- check It runs inside Omni, our managed Command Center, alongside the rest of your business
Questions
Instead of iBAIS, answered
iBAIS runs our trust account and general ledger. Where does that go? expand_more
Not into the free version. It never holds client money, a trust account or a ledger, on purpose: that work belongs in an accounting system built and audited for it. Enterprise DNA scopes that move with you and your auditor first, then connects your version so premiums and brokerage line up with each policy. If the ledger is the part you would miss most, say so on the call.
How do we get our data out of iBAIS? expand_more
BAIS's pages describe its conversion service into iBAIS, not out of it. iBAIS reports export to XLS and CSV, so start there for clients, policies, claims and contacts, and ask BAIS in writing for a full extract well before your agreement ends. Those columns are not the free version's import format, so they are mapped on the way in. Enterprise DNA does that mapping, with a test run showing every row before anything is written.
We trade through Sunrise and the Steadfast platform. Do we lose that? expand_more
The free version does not connect to Sunrise, the Steadfast Client Trading Platform or premium funders: you record what was quoted, bound and funded. If those links carry a large share of your placements, they are scoped into the version Enterprise DNA builds, or kept running alongside while the rest moves.
iBAIS already lets us ask questions by voice. Why change? expand_more
Because the question still runs inside BAIS's system, against their reports, on their terms. Here the records sit in a database your brokerage owns, any question gets an answer from them directly, and adding a field or a rule is a sentence, not a request to the vendor.
We are an underwriting agency. Does this cover bordereaux and sub agents? expand_more
Not in the free version: it is built around a broking office's clients, renewals, claims and advice files. Bordereau reporting, sub agent nets and claims floats are agency work that Enterprise DNA would scope and build into your own version, so talk it through on the call before you plan a move.
Own your book, not a BAIS licence
30 minutes with Sam. We look at what your office pays for iBAIS and its modules, which parts your team uses every week, where the trust account would live, and what your own version would look like. If it fits, we build it and run it. If it does not, take the free version and run it yourself.
Broking for Claude Code is free and open source, published by Enterprise DNA.
Done paying for iBAIS?
Get your version built