Airline Revenue Accounting Software: Build, Buy, or Build the Matching Layer and Rent the Rest
One question decides this, and it is not fleet size. How much revenue did you lose last year to interline rejections that timed out during the correspondence window?
On this page
One question decides this, and it is not fleet size. How much revenue did you lose last year to interline rejections that timed out during the correspondence window? If you can produce that number and it is small, buy Accelya Revera or Hitit Crane Revenue Accounting and put the money elsewhere. If the answer is a shrug, the loss is real, it recurs annually, and a first release covering the coupon level document model and matching runs $110,000 to $220,000 over 16 to 22 weeks. Carriers with no interline partners and no codeshares should buy without further analysis; carriers where interline is a material share of revenue mostly land on the build side, and usually on a hybrid rather than a replacement.
When is off the shelf genuinely the right call here?
If you fly point to point, have no interline partners and no codeshares, and sell mostly through your own channels, do not build. Accelya Revera and Hitit Crane Revenue Accounting will process that cleanly, and a custom project would cost more in discovery alone than the licence costs in years. That is not a hedge, it is the answer for a large share of the carriers who ask us.
The buy case extends further than most people expect. If your interline arrangements are conventional and your proration is standard, buy. Both products are built by people who understand this domain properly, and the validated scenario set behind a mature revenue accounting engine is worth more than it looks. Reissues, exchanges, residual value, refunds against exchanged documents and multilateral proration are all cases somebody has already got wrong once and fixed, and rebuilding that history is a poor use of capital.
Buy as well if you are a young carrier still deciding your commercial model. Building a revenue accounting system around interline arrangements, codeshare terms and a channel mix you have not settled on produces a model you will pay to change, and the change tends to land in the part that is hardest to migrate.
The gaps in the packaged products are narrower than a sales conversation suggests, and worth naming precisely. They appear around bilateral commercial arrangements that end up handled as manual adjustments, around ancillary and codeshare revenue where each carrier has its own accounting policy, and around rejection triage, where the constraint is analyst capacity rather than product capability.
When does a custom build actually pay off?
Three conditions carry the case, and any two of them together usually flip the arithmetic.
Interline is a material share of revenue, so the matching and settlement cycle produces a number your finance director cannot fully explain and an unmatched pile that gets cleared annually by a journal entry describing it as unidentified differences. Your bilateral special prorate agreements are being handled as adjustments on top of a default engine, which means you are prorating against yourself in markets nobody has checked, and getting it wrong against yourself produces silence rather than a rejection. Or you need revenue recognised at coupon level rather than at ticket level, so liability releases when the sector is actually flown, which changes the shape of your unflown liability and the accuracy of route profitability.
What we would push back on is building the whole function. In this category the unexplained write offs live in matching, not in proration. A coupon level document model with tiered matching and reason coded exceptions can be built and proven while proration and interline settlement stay on your incumbent, and that first number is defensible on its own results. Bringing settlement into the same release roughly doubles the scope and pushes the parallel run from two reporting periods to several, because you are then cutting over a function with external deadlines attached and no room to be approximately right.
How do they compare on the things that matter in this industry?
The document model. The unit of work is a coupon on a document, not an invoice with lines. A single document can be partly flown, partly refunded and partly exchanged into another document carrying residual value. Ask any product, packaged or custom, to represent that chain and then refund the second document correctly while keeping the link to the original sale. Everything downstream depends on that answer.
Matching near misses. Flown data and sales data disagree on document numbers, dates and carrier codes more often than anyone admits, so exact key matching leaves a residue nobody can explain. What separates systems is tiered matching with confidence scoring, and more importantly reason coding on every exception, because reason codes turn a monthly clearing exercise into a list of causes you can fix at the channel or the feed.
Agreement versioning. A proration challenged eighteen months later has to be reproducible exactly as computed under the terms in force at the time. That requires bilateral agreements held as versioned objects with effective dates and market scope, not as editable parameters on a partner record. Configuration ceilings here are the single most common reason a bilateral deal migrates into a spreadsheet.
Deadline orientation. Interline billing runs on industry settlement periods, and a missed window is generally lost rather than late. A system that presents what arrived today rather than what expires this period will lose money quietly and consistently, whoever built it.
Taxes, fees and charges. These are collected on behalf of other parties, remitted on different schedules and refunded under rules that differ from the fare. Any product that folds them into a single fare amount creates untangling work that takes years to reverse, and separating them costs almost nothing at design time.
What does total cost of ownership look like at your scale?
A first release covering the coupon level document model, sales and flown ingestion, tiered matching with an exception workflow and unflown liability ageing runs $110,000 to $220,000 and ships in 16 to 22 weeks in Digital Heroes delivery experience. A full platform adding proration with bilateral agreements, interline billing and rejection handling against settlement periods, ancillary and miscellaneous document revenue, tax remittance reporting and analytics runs $320,000 to $750,000 phased across 10 to 16 months.
Passenger volume is a poor predictor of the number. Partner count and the number of special prorate agreements move it far more, because each agreement is a rule set with market scope, effective dates and its own arithmetic that has to stay reproducible for years.
Two lines dominate the running cost and neither is engineering. Channel and partner maintenance recurs indefinitely, since sales channels change formats, partners are added and removed, and agreements are renegotiated into new versions that must not disturb prior computations. Exception handling is a staff cost, correctly budgeted as an analyst allocation whose size falls as reason codes drive root cause fixes. Compute and storage matter more here than in most categories, because you hold coupon level history for years and query across it, though it stays small against staff cost. Plan on 15 to 20 percent of build cost annually all in, weighted to the upper end if you add partners or channels regularly.
Migration and parallel running are the lines most often cut and most often regretted. This function produces a line in your audited accounts, so several reporting periods of dual output with a reconciliation report explaining every difference is a budget item rather than a contingency.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. Here that means keeping your incumbent for proration and interline settlement, where a validated engine and an industry calendar are genuinely worth renting, and building the coupon level document model and the matching engine, where the write offs live.
The matching engine typically sits at $40,000 to $55,000 inside a first release, and it is both the largest single line and the fastest to repay. The return is not in the exact matches you were already getting. It is in what the third matching tier resolves automatically and in the reason codes that let you fix recurring causes at source instead of clearing the same symptom every month.
The hybrid also buys you a smaller migration. Bring open documents across with their full event history, because a reissue chain that loses its link to the original sale cannot be refunded correctly or audited at all, and bring closed, fully flown, fully settled documents across at summary. That one decision commonly removes a large share of the migration effort with no operational loss.
If you later bring proration in house, sequence it after matching rather than alongside. Proration computed on unreliable coupon data produces confident wrong answers, and confident wrong answers cost more than obvious ones because nobody goes looking for them.
Which should you choose, by operator size and stage?
Point to point, no interline, mostly direct channels. Buy. Accelya Revera or Hitit Crane, configured once, and put the money into commercial work.
Conventional interline, standard proration, no bilateral deals. Buy, and run the comparison on the adjustment line rather than the licence line. If your interesting arrangements have already migrated into spreadsheets, that is the number that will eventually change the answer.
Material interline with a handful of bilateral agreements. Build the first release at $110,000 to $220,000 and keep settlement where it is. This is the shape we recommend most often, because it produces a result a finance director will sign inside two reporting periods.
Interline heavy carrier with many special agreements and a large unexamined write off pile. The full platform at $320,000 to $750,000 is defensible, phased across 10 to 16 months, with proration at $90,000 to $190,000 and interline billing and rejection handling at $80,000 to $180,000 as separate phases rather than one release.
Any carrier that cannot answer the timed out rejection question. Start with the first release whatever your size, because you are currently making a commercial decision without the number that decides it.
Young carrier still setting its commercial model. Buy, and revisit once your partner mix and channel strategy have stopped moving.
If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
Frequently asked questions
Is Accelya Revera or Hitit Crane enough for a mid sized carrier?
For a carrier with conventional interline arrangements and standard proration, yes, and buying is the sensible choice. Both handle the core cycle competently and rebuilding a validated scenario set is not a good use of capital.
The gaps appear around bilateral commercial arrangements handled as manual adjustments, ancillary and codeshare revenue where each carrier has its own policy, and rejection triage where the limit is analyst capacity rather than the product. Those are the areas carriers extend with custom work rather than replace wholesale.
What does it cost to switch off our current revenue accounting platform?
The licence is the small part. The real switching cost is migration and parallel running, which in this category typically dominates the project. Open documents have to come across with their complete event history, and closed documents can come across at summary, so the scoping decision matters more than the tooling.
Then budget several reporting periods where both systems produce output and a line by line reconciliation explains every difference. You cannot cut over a function that produces a number in your audited accounts on a single date and hope.
What happens if our vendor changes its pricing at renewal?
Your position depends on whether you can reproduce your own numbers outside the platform. A carrier whose coupon level history, matching logic and agreement versions all live inside a vendor product has very little room, because the alternative is a migration measured in reporting periods rather than weeks.
Building the document model and matching layer changes that materially, and it does so before any renewal conversation rather than during one. It also gives you a reconciliation of the vendor's output against your own, which is a useful thing to hold in a negotiation.
How long before a revenue accounting build produces a usable number?
Sixteen to 22 weeks to a first release covering the document model, ingestion, matching and liability, then further phases for proration, interline billing and analytics.
The schedule risk sits in migration and parallel running rather than in development. Expect the first genuinely useful output to be the composition of your unmatched pile broken down by cause, which most carriers currently cannot produce at all, and which is what makes the rest of the programme fundable.
Can we build only the matching engine and leave proration where it is?
Yes, and it is the shape we recommend most often. Matching is where the unexplained write offs sit, it can be built and proven without touching settlement, and it does not put an externally deadlined function at risk during cutover.
Tiered matching with confidence scoring and a reason coded exception queue typically sits at $40,000 to $55,000 inside a first release. Sequence proration afterwards if you bring it in house at all, because proration on unreliable coupon data produces confident wrong answers.
Why is migration harder than the build in this category?
Because a document is not a row. It can be partly flown, partly refunded and partly exchanged into another document carrying residual value, and the chain between them has to survive migration intact or the new system cannot refund or audit correctly.
The saving is in scope rather than technique. Migrate open documents with full event history and closed, fully settled documents at summary, which commonly removes a large share of the effort with no operational loss.
Does coupon level revenue recognition cost more to build?
Almost nothing extra if you design for it from the start, because it is a property of the document model rather than a feature added later. Coupon status and value are carried independently, so liability releases when a sector is flown rather than on a ticket wide assumption.
Retrofitting it is expensive. If coupon level recognition is anywhere on your roadmap, specify it in release one whether you build or buy, and make any vendor demonstrate it rather than describe it.
What is the single diagnostic that tells us to build?
Ask your revenue accounting team three numbers: last year's unmatched coupon write off, the interline billings that missed the settlement window, and the rejections that timed out during the correspondence period without a counter billing.
If nobody can produce those three figures, that is itself the finding, and it is the strongest argument for a first release. If they can produce them and the total is small against a $110,000 build, stay on the packaged product and revisit when your partner mix changes.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
Should the first version of my accounting software be an MVP?
Yes, but scope it around one complete workflow rather than a thin slice of everything. A strong first release fully owns, say, invoicing and receivables while QuickBooks keeps running the general ledger, letting you validate the software with real money movement in 10 to 14 weeks. In Digital Heroes projects, one-workflow MVPs reach a stable full system faster than big-bang replacements almost every time.
How long until custom accounting software pays for itself?
Typical payback in Digital Heroes accounting projects is 18 to 36 months, driven by recovered labor hours and fewer billing errors rather than saved subscriptions. A business spending 30 hours a week on manual reconciliation and rebilling can justify a $75,000 build inside two years at ordinary bookkeeper rates. If your projected payback stretches past five years, extend your current tools instead.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Who owns the code when an agency builds my accounting software?
You should, outright, and the contract must say so with an explicit IP assignment clause rather than a usage license. Insist that the code lives in a repository you control from day one, so nothing, including the ledger schema and migration scripts, can be held back at the final invoice. Third-party libraries and any framework the agency reuses stay under their own licenses, and a clean contract lists exactly which those are.
Should I hire a freelancer or an agency to build my accounting software?
A strong freelancer is fine for a reporting dashboard or one integration; anything that holds your books needs a team. Ledger software requires backend, frontend, QA, and accounting domain knowledge, and one person rarely covers all four while staying available for the 5 to 10 year life of the system. The most common rescue job Digital Heroes takes on is a solo-built ledger with no tests and no documentation after the freelancer moved on.
What does it cost to maintain custom accounting software each year?
Budget 15 to 20 percent of the build cost annually, so a $100,000 system needs $15,000 to $20,000 a year for hosting, security patches, dependency updates, and small fixes. Accounting software carries one extra obligation most software does not: keeping tax rates, filing formats, and bank feed connections current as banks and tax authorities change their systems. Skipping maintenance for two years usually costs more to repair than the maintenance would have cost.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Tara.
React Native Lead · Delhi · 5 posts on the site
Published · Last updated .
