Source: https://velofy.co/research/india-ledger/

Published: 2026-08-23T00:00:00.000Z
Updated: 2026-08-23T00:00:00.000Z

[RESEARCH](https://velofy.co/research/) / ARCHIVE

# An accounting operating layer for India

A field dossier on Last Accounting Company and an India adaptation: own the ledger, tie entries to evidence, win on GSTR-2B input-tax-credit mismatch detection.

Velofy · 23 Aug 2026

From the archive. This page preserves the original publication; product plans and capabilities may have changed. See [current open source work](https://velofy.co/open-source/).

This is a field dossier: our internal working notes, not a shipped-product announcement. The primary source is Last Accounting Company's own news post from July 2026.

Last Accounting Company (LAC) is YC S26, out of Finland, co-founded by Sami Laakkonen. Dozens of Finnish companies run on it and more than $80M of transaction value has moved through the system. Its founding claim: **“interfaceability” is a property of the whole system, not a feature.** LAC built its own general ledger rather than layering on Procountor or Netvisor. Outbound is stable read interfaces plus limited, typed write actions.

Firm and software are one product; review happens inside the same system that generates the work.

## Five lessons we take from the teardown

Five principles survive contact with our own market:

1.  **L1: Own the ledger.** Never build on Tally or Zoho internals; integrate read-only. The ledger is the product; everything else is a connector.
2.  **L2: Make the evidence chain the data model.** Every entry links to its source document and its history.
3.  **L3: Publish the trust boundary from day one.** LAC runs three tiers: reads (books, VAT position, statements, invoices); limited writes (document upload, invoice drafts, filing review requests); and portal-only, never API (payroll approval, settings, user access, keys).
4.  **L4: Name the agent, name the signer.** LAC's agent Björn is messageable from inside any workflow, and humans sign off on filings.
5.  **L5: Expose an MCP/API surface.** Claude, ChatGPT and custom agents operate the books through it, and other tools build on top.

## Where India bends the model

Finland's VAT and payroll cycles find their counterpart in the GST stack (GSTR-1, 3B and the annual GSTR-9) plus TDS, e-invoicing with IRN above turnover thresholds, advance tax schedules and MCA filings. Monthly plus annual cadence, rigid deadlines throughout.

Indian SMBs live inside Tally or Zoho Books and their accountants resist replacement.

*   **Wedge segment:** D2C and ecommerce SMBs (Shopify brands, Amazon sellers, Flipkart sellers).
*   **Connector priority:** bank first, through the Account Aggregator framework plus direct bank feeds; then Razorpay and Stripe settlements; then marketplace payout reports from Amazon and Flipkart; the email inbox as the purchase-invoice trap; and a Tally XML export path for switchers.

### GSTR-2B mismatch: the feature LAC cannot follow us through

The killer feature is regulatory: **input tax credit (ITC) mismatch detection against suppliers' GSTR-2B filings.** Indian businesses lose credit every month when a supplier fails to file. Automated vendor-chasing turns it into an instant ROI story: _“we found ₹X of credit you were about to lose.”_

## MVP architecture

*   **Ledger core:** a double-entry store with append-only entries; every entry carries an `evidence_id` pointing at its document (PDF or email extract) and an immutable audit log records every touch.
*   **Ingestion agents:** a classifier (document type, entity, GST fields), an extractor, and a reconciler matching transaction ↔ document ↔ ledger entry with confidence scores. Anything under threshold queues for human review instead of guessing.
*   **Filing engine:** GSTR-1 and 3B builders derived from ledger state. Validation rules are versioned code, never prompts.
*   **Human layer:** a chartered accountant's dashboard showing only the exception queue and a monthly sign-off checklist, with digital signature on filing packets.
*   **Client surface:** a WhatsApp or Telegram bot (_“where is my ITC this month?”_) plus a web dashboard.

## Risks

*   **R1: Trust.** Accounting firms are sticky and risk-averse. Counter: a free quarterly audit with published accuracy metrics, and a CA signature on every filing from day one.
*   **R2: Regulatory liability.** We partner with a licensed firm initially rather than hiring chartered accountants in-house immediately.
*   **R3: LAC-style players entering India.** Counter with speed and GST depth; 2B matching alone requires years of India-specific rule accumulation.

### The short version

Enter through D2C sellers and win on the GSTR-2B mismatch check. Pricing follows volume tiers with filing included, benchmarked against the accountant fee plus software subscription the client already pays.

This dossier applies the accounting case derived in [three markets, one thesis](https://velofy.co/research/first-principles/); the product it informs is scoped and being built in [the Numera lab note](https://velofy.co/labs/numera/).

[← Three markets, one thesis](https://velofy.co/research/first-principles/)[Where to host an MVP, and what it really costs →](https://velofy.co/research/mvp-hosting/)
