Instead of Leapfin
Stop renting your Leapfin revenue desk. Own your revenue review system.
We build your version around how your accountant reviews revenue, bring your supported Leapfin records across and run it for you. Your policies, your evidence and your database.
Leapfin lists Premium from $1,000 a month, equivalent to $12,000 for twelve months. Its subscriptions are annual; confirm the quoted currency and scope.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
Your revenue records sit inside a paid platform
Leapfin has a broader platform than this free base. Compare the revenue review work your team needs with the package on your invoice. Standard is listed from $500 a month, Premium from $1,000, and Enterprise is quoted privately.
An annual subscription
The vendor lists monthly starting rates, but says subscriptions are annual. Premium adds up to $12,000 for twelve months at the listed starting rate.
A package of capabilities
Standard, Premium and Enterprise bundle different levels of reporting, integrations and service. Check your agreement against the functions you actually use.
Accounting records and links
Leapfin keeps contracts, line items and other financial records together with their linked history. Your replacement starts with the supported records you export.
Accounting rules
Its rules turn transaction records into accounting entries. Your owned revenue desk begins with explicit fixed-consideration allocations approved by your accountant.
Reports around the records
Leapfin offers standard and advanced reporting. Its record-search documentation says linked-record filters are not supported; those joined checks are built into this base.
Review controls and history
Period locks and audit trails are part of the product you rent. Your base keeps recognition history and blocks changes to locked months in your own database.
Your owned revenue desk
A clear path from source record to monthly review
Source evidence
Know where the number came from
Bring supported source records across, keep their original details and link them to the working obligation.
- check Import contract and line-item records with their source identities
- check Keep original fields and linked-record details as evidence
- check Find imported lines with no obligation linked to them
- check Flag changed source records before they overwrite history
Revenue schedules
See the months behind the total
Allocate fixed consideration to accountant-defined obligations and see the resulting monthly schedule.
- check Daily allocation with partial months and leap days
- check Point-in-time recognition dates backed by evidence
- check Exact allocation of every cent
- check Separate currencies and draft assessments from approved schedules
The weekly review
Join the questions your team keeps asking
Read overdue reviews, allocation gaps and pending recognition together, with an owner attached.
- check Find owners with both overdue reviews and pending revenue
- check Find customers whose contracts use different currencies
- check Identify past months containing draft obligations
- check Read notes alongside unresolved allocation gaps
Evidence and control
Leave a record the accountant can follow
Prepare the assessment, record the review and preserve the history behind it.
- check Require evidence for approval and completed-month recognition
- check Void an incorrect review with a recorded reason
- check Lock fully reviewed months against later changes
- check Produce branded contract memos, schedules and retention records
Make it yours
Design your own Leapfin replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Leapfin. 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 Leapfin 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 Revenue Schedules for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Revenue Schedules for Claude Code
Connected to your own database
Which completed months still need review?
obl1
- Ligation co
- Annual access
- Ntract cu
- Harbour annual service
- Rrency mo
- NZD
- Nth pe
- 2026-08-01
- Nding pe
- 1019.18
- Riod status
- open
obl1
- Ligation co
- Annual access
- Ntract cu
- Harbour annual service
- Rrency mo
- NZD
- Nth pe
- 2026-09-01
- Nding pe
- 986.30
- Riod status
- open
obl2
- Ligation co
- Setup handover
- Ntract cu
- Harbour setup project
- Rrency mo
- AUD
- Nth pe
- 2026-09-01
- Nding pe
- 3000.00
- Riod status
- open
obl3
- Ligation co
- Bundled access
- Ntract cu
- Coastal bundled service
- Rrency mo
- USD
- Nth pe
- 2026-09-01
- Nding pe
- 994.48
- Riod status
- open
| Source id ob | Ligation co | Ntract cu | Rrency mo | Nth pe | Nding pe | Riod status |
|---|---|---|---|---|---|---|
| obl1 | Annual access | Harbour annual service | NZD | 2026-08-01 | 1019.18 | open |
| obl1 | Annual access | Harbour annual service | NZD | 2026-09-01 | 986.30 | open |
| obl2 | Setup handover | Harbour setup project | AUD | 2026-09-01 | 3000.00 | open |
| obl3 | Bundled access | Coastal bundled service | USD | 2026-09-01 | 994.48 | open |
Ask it anything
Questions across your revenue records
These joined checks run on the fictional demo today. Leapfin documents a linked-record limit in its record-search screen; its warehouse reporting can also support custom analysis.
Switching
How to switch from Leapfin
The move usually depends less on loading records than on mapping your fields and rules, choosing how much history to bring, and reconciling schedules before cutover.
- 1
Export your records
Ask Leapfin how to export the records your account allows, usually CSV or Excel, and check the available format with them. Include contract and line-item records for the fixed-consideration schedules you use. Include historic postings and rule definitions in your migration scope if you need them, because they require separate mapping and review. Do not assume this covers every Leapfin function.
- 2
Load a sample first
Check that your export format is supported, then load a small representative batch of contract and line-item records into the database's source inbox before loading the rest. The import supports CSV exports or a JSON array using its documented record model. It can map different headings and preserves the full source payload. The material does not specify a separate test-run option.
- 3
Review import results
Check the import outcome for rows that failed and line items that have not been linked to an obligation. Changed rows fail rather than silently overwriting history. Review allocation gaps and missing links, then have your accountant enter the working obligations, reconcile the schedule, and approve the basis. Resolve issues before relying on the imported records for review.
- 4
Run both systems briefly
Keep Leapfin running while you review the same contracts and periods in both systems for a short time. Compare the imported source details, obligation links, allocations, monthly schedules, and accountant review records. Keep currencies separate when comparing totals. Ask your accountant to investigate differences and confirm the treatment and evidence before you rely on the new records.
- 5
Switch after approval
Cut over only after your accountant approves the treatment and you have reconciled the records you plan to use. Confirm that the functions you need are covered, since the free base handles fixed-consideration revenue schedules and accountant review records, not every Leapfin function. Once the replacement workflow is ready, switch off Leapfin according to your account terms and retention needs.
Where the real effort goes
The real work is usually mapping your own fields and rules, deciding how much history to bring, and reconciling imported records with the schedules your accountant approves. Historic postings and rule definitions need separate mapping and review. If you have Enterprise DNA run the replacement, that migration work is included in the agreed scope.
Not ready for a call?
Get your Leapfin switch plan by email
We will send you the step-by-step plan for moving your business off Leapfin, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Leapfin switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free, open source
- 1 Clone the repo and install its dependencies
- 2 Run npm test and npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
- 3 Export supported Leapfin records and run import leapfin with --source and --dry-run
- 4 Reconcile the import, enter approved obligations and ask /weekly-review
Built around your business
We customise it
One setup fee, then a retainer
- check Your export headings and source history mapped and reconciled
- check Your accounting policies, evidence fields and review documents
- check A finance screen or different technical foundation scoped to your team
- check Additional recognition methods and connections agreed with your accountant
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed in a database your business owns
- check Agreed access, backups and retention controls operated for you
- check Your review routines and supporting documents maintained
- check Run through Omni by Enterprise DNA with a team responsible for the system
Questions
Instead of Leapfin, answered
Does this replace everything in Leapfin? expand_more
The free base covers fixed-consideration revenue schedules and accountant review records. We scope your full replacement around the functions you use, including the required connections and additional accounting methods. Your accountant approves the treatment before a cutover.
What happens to our Leapfin history? expand_more
Supported contract and line-item exports enter a source inbox with their original details. Your accountant then links the working obligations and reconciles the schedule. Historic postings and rule definitions need a separate mapping and review, which Enterprise DNA includes in the agreed migration scope.
How do we trust the revenue numbers? expand_more
Each approved contract must allocate its full fixed consideration. Monthly schedules preserve every cent, keep currencies separate and require evidence before recognition is recorded. Locked months reject later changes. The accountant remains responsible for policy, performance evidence and the final financial statements.
What does Leapfin cost compared with our own version? expand_more
Leapfin lists Premium from $1,000 a month, or $12,000 for twelve months, and Standard from $500 a month. It says subscriptions are annual and Enterprise is quoted privately. The page uses a dollar symbol without naming the currency. The free base has no licence fee; Enterprise DNA builds and runs your version for one setup fee, then a retainer.
Can you build the screens and connections our finance team needs? expand_more
Yes. We agree the source systems, accountant workflow, access rules and finance screens before building. Your team gets the version it needs, with the records in a database you own and the review responsibilities kept clear.
Put your revenue review on your own terms
Spend 30 minutes with Sam. Bring your Leapfin bill and one monthly revenue review. We will identify the records, rules and connections your version needs, then agree the build and ongoing operation.
Revenue Schedules for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Leapfin?
Get your version built