Business Entity Profile: The Quiet Foundation of Every Indian Finance Stack

23 Oct 2026 · @RAMA

Status: Research stage. Baseline is under development. This post shares our design thinking, not a shipped product.

The Hook / Executive Summary

A Business Entity Profile is the one record that tells your finance software who your business legally is. Legal name. PAN. Every GSTIN. Registered address. Legal structure. Base currency.

Lowkey boring. Also the most load-bearing record in your entire finance stack.

Here’s why. Every invoice, ledger entry, GST return and compliance deadline points back to it. Get it right once, and everything downstream inherits clean data. Get it wrong, and every error quietly multiplies.

In India, the stakes are higher. A GSTIN is not just a number. It encodes your state and your PAN. Your state, compared with the buyer’s, decides whether tax splits into CGST and SGST or lands as IGST. And with purchase credits now matched against data your vendors file, a mismatched identity gets caught fast.

TL;DR

• What it is: The foundational record for legal identity, tax registrations and business structure.
• Why it matters now: Indian compliance runs on machine-matched data. Identity errors surface early, and they cost more the later you fix them.
• What follows: The pain points, the cost of ignoring it, our design blueprint, and an honest look at how Tally Prime, SAP and Oracle handle it.

The Hidden Friction (Why Do We Need It?)

Most teams treat entity setup as a one-time form. It is actually a set of decisions every later transaction depends on. Here is where the friction hides.

One PAN, many GSTINs. GST registration is PAN-based and state-specific. A business with branches in several states needs a separate registration in each. Inside one state, branches usually sit under a single registration as additional places of business. Separate business verticals can take their own. So “the business” is really one legal entity wearing several tax identities.

The GSTIN carries hidden data. Its first two digits are the state code. The next ten are your PAN. The last digit is a checksum. Good software reads all of that. It does not store the number as plain text.

State drives tax. Place-of-supply logic compares states to decide between CGST plus SGST and IGST. That logic needs a trustworthy home state on day one.

Legal structure changes the rulebook. A proprietorship, an LLP and a company face different statutory formats and filing calendars. Companies, for example, deal with MCA filings such as AOC-4 and MGT-7A.

Details change. CBIC guidance expects a taxpayer to apply for an amendment within 15 days when the legal name or place of business changes. So the profile cannot be a frozen form. It needs history.

Everything reads from it. Ledgers, invoices, returns, deadlines. When each tool holds its own version of your name and address, that mess turns into reconciliation work later.

The Cost of Inaction (What Happens When You Don’t Use It?)

Skip a proper profile, or scatter it across tools, and the damage shows up later. Quietly at first. Then all at once.

• Wrong tax splits. If the home state is wrong, the intra-state versus inter-state logic flips. Every invoice built on it carries the error.
• Bad GSTINs slip in. Tally’s own setup guide warns that a wrong GSTIN can cause mismatches and rejections at filing.
• Registrations blur together. Each GST registration behaves like a separate taxpayer for invoicing, credits and branch transfers. Merge two GSTINs into one “company” record and returns and credits land in the wrong place.
• Retrofits are expensive. TallyPrime only added multiple GST registrations in one company in Release 3.0 (June 2023). Teams that had kept one company per GSTIN needed a merge procedure to export and re-import their data. Plot twist: the fix is rarely small.
• Deadlines go missing. Without a structured legal type on record, nothing can generate the right compliance calendar automatically.
• Client data bleeds. For CA firms, a weak boundary between one client’s books and another’s is a trust problem, not just a bug.

Illustrative scenario (hypothetical). A Pune manufacturer opens a depot in Gujarat. Its books still treat everything as one Maharashtra GSTIN. Gujarat invoices carry the wrong number and the wrong tax split. At filing time, nothing reconciles, and someone spends a weekend untangling it.

The Strategic Advantage (What Happens When You Do Use It?)

A solid profile makes everything built on top of it simpler. These are our design goals. We have no live customer numbers yet, and we will publish real results once pilots exist.

• Validate once, trust everywhere. A GSTIN’s structure is checkable: state code, embedded PAN, entity number, checksum. One whose embedded PAN does not match the entity’s PAN is structurally invalid. Catch that at entry, not at filing.
• Tax logic with a reliable anchor. The home state comes straight from the GSTIN, so place-of-supply rules start from verified data.
• Multi-state from day one. One entity, many GSTINs. Add a state later without migrating anything.
• Compliance that schedules itself. Legal type and registrations can generate GST, TDS and MCA deadlines automatically.
• A hard tenant boundary. Each business gets its own tenant ID. A CA firm can run dozens of clients without crossing wires.
• Room to grow. Base currency is INR-only for v1, but it lives in a field from the start. Multi-currency later does not need a data migration.
• Clean fuel for the layers above. Forecasting and advisory features will read from the accounting layer as their source of truth. Clean identity at the base means cleaner everything above it.

The efficiency gain is simple to describe. Less re-keying. Fewer reconciliation surprises. More time on decisions instead of data repair.

Under the Hood (How Does It Work in Real Life?)

This is our design blueprint, seen from the user’s seat. Picture a business owner or their CA onboarding a new client.

1. Create the entity. Enter the legal name, PAN and legal structure: proprietorship, LLP, company and so on. The system generates a unique tenant ID. Every record that follows carries it.
2. Add the GSTINs. Enter one or more. Baseline checks the format, reads the state code, matches the embedded PAN against the entity’s PAN and verifies the checksum. Bad numbers bounce at the door.
3. Add the registered address. It becomes the legal address on record.
4. Confirm the base currency. INR only for v1. It is stored as a field from day one, so adding currencies later is not a migration.
5. Build on top. User roles, the fiscal year and period structure, and the chart of accounts all attach to this entity. Invoices pick the right GSTIN. Compliance deadlines follow from the legal structure.

What the record holds

• Legal name: the name exactly as registered.
• PAN: the anchor identity.
• GSTINs: a list, one per state registration.
• Registered address: the legal address.
• Legal structure: drives formats and deadlines downstream.
• Tenant ID: the isolation key for every record.
• Base currency: INR for now, a field from the start.

Two things are not in the record yet: per-GSTIN details such as registration type, and a change history. Both show up in our open questions below.

The Competitive Landscape (How the Giants Do It)

Tally Prime, SAP and Oracle all solve this problem. They solve it for different eras and different buyers. Credit where it’s due.

Get Pranavkamble’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Tally Prime

• Strengths: Setup is fast and familiar. You create a company with a name, address, financial year start, books-beginning date and base currency, then switch on GST. The GST screen captures state, GSTIN, registration type (Regular, Composition or Regular-SEZ), return periodicity and e-invoice applicability. Since Release 3.0, one company can hold several GST registrations, each with its own voucher series. A registration can be deactivated on suspension or surrender.
• Friction: The unit is a company data set. Running several businesses means several companies, with a Group Company for consolidated reports. Multi-GSTIN support arrived only in 2023, so older setups often need a merge. The GSTIN is entered by hand, and features are switched on by the user.

SAP

• Strengths: The company code is the smallest unit for which a complete, self-contained set of accounts can be created. SAP documentation says at least one must exist before Financial Accounting is implemented. It is a strong legal and reporting backbone for groups running many companies in one system.
• Friction: It is defined in Customizing, which is typically implementation-project territory. For India GST, the GSTIN sits on a business place, and SAP’s own knowledge base notes that GST invoices for plants under different GSTINs must be created separately. That is power with complexity. It is not a self-serve first step for a small business.

Oracle

• Strengths: A rich model of ledgers, legal entities and business units. A business unit posts to a single primary ledger yet can process transactions for many legal entities. India GST is handled through Oracle Fusion Tax, with documented setup.
• Friction: Several linked objects need designing before the first transaction: legal entities, tax profiles, legal reporting units, ledgers and a chart of accounts. Practitioners on Oracle’s community forums ask how to map legal reporting units to locations and invoice lines.

The gap we see. These platforms grew up around the desktop accountant or the enterprise implementation team. In our reading of their public documentation, none treats a validated, GSTIN-aware, multi-tenant entity profile as a quick, self-serve first step for a growing Indian business. That is the lane we are designing for.

Conclusion & Call to Action

Entity setup looks boring. It is also where accurate books begin. Treat it as a first-class module, and every ledger, invoice and return built on top starts from verified facts.

Here is a five-minute audit for your current stack:

• Does every tool show the same legal name and address?
• Can you list every GSTIN you hold, with its state, in one place?
• Could you add a new state tomorrow without re-keying anything?

Three “no” answers mean your finance stack is built on sand. Lowkey fixable, but better fixed early.

We are building Baseline in public. Read this, reply, and poke holes in it. If you are a CA, finance head or founder, tell us where this breaks in your world.

Open Questions: help us pressure-test this

• Per-GSTIN details. Should each GSTIN carry its own address and registration type (Regular, Composition, SEZ)? How often do you use additional places of business within a state?
• Change history. When a legal name or address is amended, how should the profile keep history so past invoices and returns stay untouched?
• Groups. Should a holding company with several PANs be several tenants with a consolidation layer, or one tenant with several entities?
• Validation depth. Are format, PAN-match and checksum checks at entry enough, or would you want a live lookup against the GST portal?