Skip to content
Zenocta Solutions

Mobile App Development10 Jun 2026 · 8 min read

How We Built TracAny: A Shared Ledger for Construction Partners

The build story of TracAny, our Android and web shared expense ledger: modelling partner shares, agreements and settle-up, and what to know before building a ledger for a project team.

ZEBy , Editorial Team

TracAny app social image from Zenocta, showing the app icon with the Zenocta Solutions logo

Anyone who has built a house or run a small project with partners knows how the money record starts: a notebook at the site, a chat group full of payment screenshots and a spreadsheet one person updates when they remember. It works until someone asks who actually owes whom. This is how we built TracAny, our shared expense and project ledger for Android and web, and what the build taught us about modelling money between people. It describes software for recording and reporting, not financial or legal advice.

What problem was TracAny built to solve?

The TracAny case study describes the problem in the construction industry: businesses split expenses and profit shares across multiple partners and contractors, using spreadsheets or manual notes. That makes it difficult to track who owes what, to reconcile project costs and to produce timely financial reports. The case study also names the business consequence: disputes and delays caused by inconsistent, manual tracking of shared project costs.

The word that matters is shared. Tracking your own spending is a bookkeeping problem. Tracking money that several people put in, take out and are owed is a trust problem, because every number is also a claim on somebody. The Play listing says it plainly: spreadsheets get messy and chat groups lose numbers. TracAny keeps every partner on the same page, with one ledger per project, a full history of every edit, and balances that always add up.

We cover the everyday side of this in construction expense tracking for multi-partner projects. This article is about the build.

Who is TracAny for?

The case study is aimed at the construction industry: site owners, contractors and partners. Its FAQ says the expense and partner-share model adapts to any business that splits costs and profits across a project team, and the Play listing describes it as a shared ledger for partners, teams and organisations. That is the same idea at two scales: construction was the starting point, and the structure underneath is general.

One detail from the case study shaped the interface more than any other: the users are often not accountants. The user experience challenge is stated as presenting financial data clearly enough for non-accountant users, such as site owners and contractors, to review and act on quickly. Every screen had to pass the test of whether a site owner could read it standing on the site.

The approach and decisions behind the build

Model the sharing, not just the spending

The first technical challenge in the case study is modelling flexible partner-share and expense-splitting logic that can adapt to different project and partnership structures. That is the hard part. Partners do not always share equally. Some put in money up front, some lend, some are repaid in instalments. We read the case study as a decision to treat the arrangement between partners as data that the ledger understands, not as a note someone remembers.

One ledger per project, with a full history

The listing describes organisations and projects, each with its own income, expenses and balance. Entries carry a category, partners, notes and a receipt photo. They can be edited, duplicated, deleted and restored, and every change is recorded: who changed what, and when. For a shared ledger, the history is a feature, not a log. It is what lets a partner accept a number they did not enter.

Agreements and settling up

The listing describes agreements between partners, such as loans, advances and instalments with a progress bar, and a settle-up view that shows exactly who owes whom with the fewest payments. Here is a short example with made-up numbers, in whatever currency you like. Three partners share a project cost of 90 equally, so each share is 30. Partner A paid 60, partner B paid 30 and partner C paid nothing. A is owed 30, B is square, and C owes 30. One payment settles everything: C pays A 30. A good settle-up screen finds that result for you instead of leaving three people to argue over it.

Flutter, Firebase and partner systems

TracAny is built with Flutter and Firebase (Authentication, Firestore and Cloud Storage), with real-time reporting dashboards and REST API integration for partner and contractor systems. Real time matters for a shared ledger: when one partner records a payment, another should see it, not wait for a spreadsheet to be emailed. Our general approach to that choice is in Flutter vs native app development.

Keep currencies honest

The listing says each entry keeps its own currency and totals are never mixed between currencies, with 150+ currencies and 200+ countries supported. This is one of those quiet decisions that prevents loud errors. Adding amounts in two currencies together gives a number that means nothing.

How do the features fit together?

150+currencies supported
200+countries supported
LayerWhat the listing describes
LedgerOrganisations, projects, income and expenses, category, partners, notes, receipt photo, edit history, duplicate detection
Partner arrangementsAgreements for loans, advances and instalments, and a settle-up view
DashboardsIncome vs expenses by month, cash flow, category mix, project profit and loss, partner balances, top expenses and trends, each chart with a table, filters by project, dates, category and currency
Smart insightsForecast of the next months with a confidence range, unusual spending alerts, runway, budgets with alerts, recurring entries
AI assistant (Premium)Type an expense in plain words and review it before saving, scan a receipt, ask questions, monthly summary
ExportChoose data and fields, then download as CSV, Excel, PDF, Word or JSON

Read from top to bottom and you see the layers build on each other. Clean ledger entries make settle-up possible, and settled balances feed the dashboards. The insights only mean something when the ledger beneath them is trustworthy. That is why we build the ledger layer first and add insight layers on top.

On AI in a money app

The listing is careful: numbers always come from your ledger, the AI can make mistakes, and you review an entry before you save it. We think that is the right posture. In a finance tool, AI should propose and the person should confirm.

How has the product grown since the case study?

The case study lists future scope: bank and UPI integration for automatic expense import, budget-versus-actual forecasting per project and a multi-project portfolio dashboard. The current listing already describes budgets with alerts, forecasts and project-level profit and loss, and it supports multiple projects within an organisation. We treat the case study and the listing as separate documents, so check the Play page for exactly what is available today.

Where do shared-cost disputes usually start?

The case study talks about disputes and delays, and in our experience they rarely begin with bad faith. They begin with small, understandable gaps in the record. An expense paid in cash with no receipt. A partner who paid a supplier directly and forgot to tell the others. A loan between two partners that nobody wrote down, so two people remember it differently. An entry made twice because two people paid half each.

Software cannot make people agree, but it can remove the gaps. A receipt photo on every entry, a warning before a duplicate is saved, an agreement recorded with its instalments, and a history that shows who changed what are all aimed at those exact moments. When the record is complete and visible to everyone, a disagreement becomes a question about the numbers on screen, not about whose memory is right.

What would we tell someone building a shared-ledger app?

These are lessons that follow from the decisions above. They are advice, not results.

  • Record the agreement, not only the payment. Loans, advances and instalments need their own structure.
  • Keep a visible history. When many people share a ledger, "who changed this and when" must be answerable.
  • Warn about duplicates. The same payment entered by two partners is the most common shared-ledger error.
  • Never mix currencies in a total. Keep each entry in its own currency and report them separately.
  • Design for non-accountants. Pair every chart with a table and label things in plain words.
  • Make AI propose, not decide. Show the draft entry and let a person confirm.

A rollout path for a shared project ledger

  1. Agree who the partners are. Names, shares and any loans or advances between them.
  2. Set up the project. One ledger, with categories everyone recognises.
  3. Enter the first week together. Use receipt photos and check that everyone sees the same totals.
  4. Use settle-up regularly. Settle on a rhythm, not at the end of the project.
  5. Turn on budgets and alerts. Once a month of data exists.
  6. Export for your records. Download what your accountant or partners ask for.

What is live today?

TracAny is on Google Play and the listing says it works on phone, tablet and web, so Android and web. For plans, we can only repeat the listing: free to start, with ads on phones; Value and Premium plans unlock the full toolset, Premium removes ads, and plans cover your whole organisation. The AI assistant is marked as Premium. See the TracAny app page and the rest of our apps. For a broader view of what contractors need beyond money tracking, read construction project management software features for contractors.

How do you get a similar product built?

If you run projects where partners, contractors or clients share costs, we can build a ledger around your structure: your partner shares, your categories, your reports. We start with how money moves between people today, agree a first release, and send a scoped, fixed-price proposal before any work begins. To keep the first version focused, see how to build an MVP without wasting your budget. When you are ready, contact Zenocta and describe your partners and projects.

Try it live

Open the real thing: demos run in a new tab with sample data, apps link to their own page.

Frequently asked questions

  • 01Can Zenocta build a finance app like TracAny for my project business?

    Yes. Zenocta builds custom financial tracking and reporting apps for construction and project-based businesses. We start with how money moves between your partners today, then send a scoped, fixed-price proposal before any work begins.

  • 02What technology is TracAny built with?

    TracAny is built with Flutter and Firebase, including Authentication, Firestore and Cloud Storage, with real-time reporting dashboards and REST API integration for partner and contractor systems.

  • 03Can the same model work for businesses other than construction?

    The case study says the expense and partner-share model adapts to any business that splits costs and profits across a project team. The partner shares, categories and reports are shaped to your business, with scope agreed in the proposal.

  • 04How does TracAny handle multiple currencies?

    The Play listing says each entry keeps its own currency and totals are never mixed between currencies, with 150+ currencies and 200+ countries supported. Number and money formats follow the country chosen in settings.

  • 05Which platforms and plans does TracAny have?

    TracAny is on Google Play for Android, and the listing says it works on phone, tablet and web. Zenocta apps are Android and web only. Per the listing it is free to start with ads on phones, with Value and Premium plans.

0% read ·

Get new guides in your inbox

Practical notes on billing, payroll, apps and AI for growing businesses, written from what we build. No spam.

We email occasional guides. Unsubscribe any time: reply to any email or write to contact@zenocta.com.

Ready to build something real?

Website and app development from ₹8,888. Book a free consultation and get a scoped, fixed-price proposal within 24 hours.