Documentation  /  {{BRAND}} Demo
{{BRAND}}

{{BRAND}}™ — The Operating System of Business

 Document done by Rajeesh Ambadi · Co-Founder & Chief ERP Architect  ·  Rashid Abdul Kareem · Co-Founder & Solution Architect
The operating system of business Updated 18-Jul-2026 Product document
Product Document · 2026

{{BRAND}}™
The operating system
of business.

One AI-native, keyboard-first ERP — from a one-person shop to a 10,000-user enterprise, on a single codebase, with zero consultants.

Developed and marketed by{{COMPANY}}
5 years of research behind the final design Since 2022 in active development
“Configuration is our competitor. Conversation is our product.”
▶  See a live business flow Read the thesis
0data models shipped
0API endpoints live
0lifecycle stages — 14 sales + 14 purchase
0levels of GL-mapping fallback

The Mission

Enterprise-grade accounting has been priced, scoped and staffed for enterprises. We think a five-person shop deserves the same ledger as a five-hundred-person company — and should not need a consultant, a project plan or a budget round to get it.

Put enterprise-quality accounting within reach of the smallest business that needs it, and let it grow to ten thousand users without ever being re-implemented.

What stands in the way today

The capabilities that make an ERP trustworthy — GR/IR clearing, multi-book accounting, conditional account determination, approvals, an audit trail that holds up — exist in the large suites and essentially nowhere below them. The reason is not that small companies do not need them. It is what it costs to get to them.

Cost assumes a finance department Licence plus implementation is budgeted by organisations that already employ the people to run it. For a shop or a midsize firm, the entry price alone ends the conversation — long before anyone asks whether the product fits.
Time is measured in quarters Blueprinting, configuration, data migration, testing, training, go-live. A business that needs working books this quarter cannot wait for a programme, and cannot carry the risk of one that slips.
A consultant sits between you and your own ledger Account determination, posting rules, approval policy — all of it configured by someone else, re-engaged for every change. The dependency does not end at go-live; it is the operating model.
So the product is built to remove all three
Depth without the entry priceThe enterprise mechanisms are in the kernel for every edition, not sold as a tier. A Shop-edition trader posts through the same double-entry engine, the same validation and the same audit trail as an enterprise.
Live the same week, not the same yearGuided setup, chart-of-accounts presets and a migration engine that imports from Tally and other systems — with a dry run and a reconciliation report before anything is committed.
Configuration you ownPosting rules, approval policy and account determination are data, written in plain language and testable with simulation and what-if before they touch the ledger. No implementation partner required to change your own rules.
Growth without re-implementationOne user to ten thousand on one codebase and one dataset. Editions are feature flags; an upgrade is not a migration and never a second product.
The honest version. The large suites are not bad software — they are correctly built for organisations that can absorb their cost and their timeline. Our claim is narrower and, we think, more useful: the same rigour can be delivered without the implementation project, and the market that has been priced out of it is far larger than the market inside it.

Vision & Thesis

One ERP for the globe — run entirely through plain language, with zero technical or functional consultants. The ERP grows like a ledger, not like an implementation project: complexity appears only when business events demand it.

The problem. Legacy enterprise suites need consultants and months of configuration. Desktop accounting tools have keyboard speed but limited cloud controls, approvals, and AI. Entry-level cloud accounting is friendly but shallow — no GR/IR clearing, no multi-book accounting, no conditional account determination. Nobody ships one ledger that grows with you.

How the core was arrived at

The core modules — the accounting kernel and financials, and with them the item master, inventory, business partners, and the sales and purchase lifecycles — are the product of five years of research before the final design was settled. Development has been under way since 2022.

5 yearsof research and design iteration before the final draft
2022development begins on the settled architecture
Core firstledger, financials, inventory and the document lifecycles — before any skin
Why that matters more than a feature count. An ERP is bought on whether its core was thought through, because the core is the part a customer can never replace later. Posting rules, the double-entry kernel, how a document moves through its stages and how accounts are determined were settled first and built second — which is why account determination is configuration here rather than a customization, and why the same ledger serves a one-person shop and a 10,000-user enterprise without a fork.

The architecture in one picture

UI SKINSSwitchable experience modes — presentation only, never logic
AI ORCHESTRATORParses, drafts, explains — never posts
POLICY LAYERBusiness rules as data, not code — natural language compiled to deterministic checks
KERNELTiny, universal double-entry engine · immutable event log · inventory · parties · documents

Five non-negotiables

1 · No consultant, ever

If a feature requires documentation, training, or an implementation partner to use, it is wrong. Our decision heuristic: “Would this force a one-person company to hire a consultant? If yes, find another way.”

2 · Deterministic core, probabilistic edge

AI parses, suggests, drafts and explains. AI never posts. Only kernel-validated, human-confirmable transactions reach the ledger — each traceable to an immutable event.

3 · Single-window flows

One window for the full purchase flow, one for the full sales flow — stages as tabs, never fragmented screens. The user moves a document through its life; they never “navigate a module”.

4 · UI is a skin, business logic is not

All flows run on one headless API. Four experience modes — Classic, Rapid, Flow and Forms — switch live without losing context or data.

5 · Any size without migration

Day one is a notepad and a stream. Approval chains, dimensions, multi-entity and warehouses appear on demand. Growing never requires reimplementation.

Industries {{BRAND}} Serves

One kernel, every vertical. Industry needs are profiles — feature flags, workflow presets, GL presets and document types — never schema forks. The same product runs a food truck and a hospital group.

Retail & POS
Wholesale & Distribution
Manufacturing
Construction & Contracting
Hotels & Hospitality
Restaurants & Food Delivery
Rental & Leasing
Healthcare & Pharma
Education
Logistics & Transport
E-commerce & D2C
Professional Services
Real Estate & Property
Agriculture
Accounting & Audit Firms
Why it matters: the product is not built for one vertical — it is built for every business that keeps books. Industry profiles mean a new vertical is a content pack, not an engineering project.

Item Master

One item record carries everything the business knows about a product or service — and feeds the GL engine, POS, web store and AI copilot from a single source.

Rich classificationItem types, categories, groups, brands and custom attributes (size, colour, rental-asset flags…) — every one a GL-mapping dimension.
Units of measureMultiple UoMs with conversions (PCS ↔ BOX ↔ CTN), bilingual names out of the box.
Batch & expiryBatch tracking with FEFO picking and expiry alerts — pharma and food ready.
Bill of materialsBOM headers and lines for manufacturing and assembly.
Pricing engine hooksPrice lists, customer-specific prices, quantity and promotional pricing, tax-inclusive or exclusive.
Vendor & media linksPreferred vendors per item, product images, documents and attachments.
Live stock per itemPer-warehouse, per-bin stock with oversell blocking at POS (“stock short”).
AI contextEvery item exposes an AI-context endpoint — the copilot answers “why is this item’s margin falling?” with real data.
Tax intelligenceHSN/SAC codes per item drive automatic CGST/SGST/IGST determination.

Business Partner Master

Customers, suppliers, or both — one deep partner record (~50 API endpoints) that replaces the scattered “customer card / vendor card” of legacy ERPs.

Roles, not duplicatesOne partner can be customer, supplier, transporter or agent — roles attach to a single master record.
Full identityGroups, categories, entity types, multiple addresses, contact persons and communication preferences.
Financial profileBank accounts, tax registrations (GSTIN/VAT), and a credit profile that feeds credit-limit approval gates.
Compliance readyKYC documents, relationships between partners, block/unblock with full audit.
GL control linksAccounting links map partner groups to control accounts — the GL engine resolves receivable/payable ledgers automatically.
Custom attributesDynamic attributes extend partners without code — channel, region, VIP flags — all usable in rules.

Purchase Flow — Procure-to-Pay

A 14-stage lifecycle in one workspace: Purchase Request → Requisition → RFQ → Vendor Quotation → Comparison → Purchase Order → Approval → Goods Receipt → Quality Inspection → A/P Invoice → Vendor Payment → Debit Note → Return → Closure.

Below is a real cycle executed through the production API — 100 routers from Nexus Distributors, ₹17,70,000 with GST. Click each stage to see what the GL engine posted.

Notice what’s missing: data entry. The warehouse clerk confirms a receipt; GR/IR clearing, input-tax splits and vendor control postings happen inside one atomic, audited transaction. Quotations and orders post nothing — commitments aren’t accounting.

Sales Flow — Order-to-Cash

The mirror image, also 14 stages: Lead → Opportunity → Quotation → Sales Order → Approval → Fulfillment → Delivery → Shipment → Invoice → Payment → Returns → Credit Note → Collections → Closure.

Real cycle: Skyline Infotech orders 40 routers + a ₹2,00,000 AMC. Watch the engine split product vs service revenue and post inter-state IGST — click each stage.

The keyboard-first layer on top

Tally’s native vocabulary, on the web: Enter confirm · Esc back · Ctrl+A save · F4 Contra · F5 Payment · F6 Receipt · F7 Journal · F8 Sales · F9 Purchase · ⌘K command palette with an “Ask AI” fallback. High-volume operators never touch the mouse.

Salesmen & Commission

Sales performance is first-class data, not a spreadsheet at month-end.

Salesperson masterEvery salesperson is a managed entity with territory, targets and document assignments across quotations, orders and invoices.
Commission rulesConfigurable commission rules — by item, category, partner group or margin — versioned and effective-dated like every other engine.
Performance trackingLive performance endpoints: achievement vs target, collection efficiency, and pipeline per salesperson.
GL-mapped payoutsCommission accruals post through the same engine — a commission dimension on every sale, payable settled like any liability.
Salesperson is also a GL-mapping dimension — “post agent sales to a separate revenue ledger” is a rule, not a customization.

POS Module

A full point-of-sale inside the same ledger — not a plugin. Every checkout posts inventory, COGS, revenue, tax and cash to GL in one atomic transaction.

Register sessionsOpen a shift with a cash float, close with end-of-shift reconciliation — variance tracked per cashier, per register.
Fast billingBarcode or exact-code entry, per-line HSN and GST%, live stock / warehouse / batch display with oversell blocking (“stock short”).
Automatic tax splitCGST + SGST vs IGST determined automatically from the customer’s GST state — the cashier never thinks about tax.
Split tenderPart cash, part card, part UPI in one sale — with change calculation. Every payment type is mapped to its own GL account.
Inline customer creationRegister a new customer mid-checkout without leaving the billing screen.
Professional receiptsThermal 80mm / 58mm or A4, auto-print, Code 39 barcode, amount in words — designed in the built-in print-template designer with version history.
The POS is the GL: a ₹850 card sale instantly debits Card Clearing, credits revenue and output tax, reduces stock and posts COGS — with zero end-of-day journal work.

Order Management Module

One order pipeline for every sales channel — dine-in to delivery apps to web stores — flowing into the same stock, the same kitchen of work, and the same ledger.

Eight channels, one queue

POS
Zomato
Swiggy
UberEats
Shopify
WooCommerce
Webstore
Phone
Channel ingestion APIExternal platforms push orders into a single ingest endpoint — validated, priced and staged automatically.
Configurable order stagesEach channel gets its own stage flow (New → Preparing → Ready → Dispatched → Delivered) — defined as data, per business.
Barcode-scan fulfillmentScan each line as it’s picked — the order can’t advance until every line is verified.
Full order lifecycleAssignment to staff, attachments, event timeline per order, and controlled cancellation with audit.
No reconciliation spreadsheets: a Swiggy order and a walk-in POS sale hit the same inventory, the same tax engine and the same trial balance — in real time.

Approvals & Workflow Engine

Every forward transition in every document passes one policy gate. Rules are data — written in plain language, drafted by AI, enforced deterministically.

The gate every document must pass

AAUTONo rule matched — the stage advances instantly. Zero rules means safe auto, never a bypass.
·
BBLOCKA hard rule failed — e.g. PO unit price up >5% vs last purchase. The document cannot move.
·
CPENDINGRoute to a human — an approval request lands in the right person’s Action Center.
Multi-level approval flowsSequential chains — manager → CFO → CEO. Approving level n creates level n+1; rejection at any level rejects all.
Rich conditionsOn value, quantity, cost center, project, counterparty, item category, document sub-type — combined with AND/OR trees.
Work routingRouting rules decide who acts next — by user, role, creator or document owner — with SLA hours and priority. A fulfillment clerk logs in and sees “10 orders to process today”.
Claim soft-locksRole queues let one clerk claim a work item — two people never process the same order.
Action CenterOne bell for everything: Needs you · My work · My requests · Activity.
Zero-setup for small teamsSelf-approval switches on automatically for single-user companies — the engine appears only when the team does.

Approvals that ship out of the box

Discount approvalCredit-limit approvalDelivery approvalInvoice-hold approval Purchase-request approvalRFQ approvalPO approvalBudget validation Vendor onboarding approvalEscalation & SLA rules
Configured in plain language: “Purchases over ₹50,000 on project Skyline need manager then CFO” → AI drafts the rule → a human enables it → the engine enforces it deterministically. Every decision is audited.

Inventory & Warehouse

Multi-warehouse, multi-bin stock that stays tied to the general ledger — every movement posts value, not just quantity.

Warehouses & binsUnlimited warehouses with bin/rack-level locations; per-item, per-warehouse, per-bin stock visibility.
Batch & expiry controlBatch tracking with FEFO picking and proactive alerts — “3 batches expiring within 30 days”.
Reservations & ATPSales orders commit stock (available-to-promise) so the same unit is never promised twice.
Landed costFreight, customs and insurance allocated into item cost on import purchases — true margins, not guesses.
ValuationMoving-average costing proven in the live test cycle — delivery posted COGS of exactly 40 × ₹15,000.
Negative-stock guardOversell blocking at POS and order level, with Insights flags if any record ever goes negative.

Projects & Job Costing

A project is a cost object with its own budget, commitments, progress and revenue — not a tag on an invoice. Contractors, agencies and R&D teams get percentage-of-completion accounting on the same kernel that runs the shop floor.

Project master & typesCode, status, dates, contract value, project currency, manager and counterparty. Project types are configurable archetypes — construction, service, R&D, internal — so a vertical is a preset, not a fork.
Unlimited WBSWork breakdown to any depth, each element flagged posting or summary and billable or not, with planned vs actual start and finish, a responsible person and a linked cost centre.
Commitments from POsA purchase order against a project raises a commitment — so spend is visible when it is promised, not when it is invoiced. That is the difference between cost control and cost reporting.
Progress & revenue recognitionPhysical or cost-based percentage of completion drives revenue recognition over time, posted through the GL engine like any other event.
Settlement rules & runsPercentage distribution to target cost objects, executed as runs with an audit record — every settlement answerable after the fact.
Project GL rolesWIP, accrued revenue and unbilled receivable are mapping roles, so project postings resolve through the same 13-level fallback as everything else. Retention on project billing is handled, not worked around.
Why this is hard elsewhere: most SMB systems bolt job costing on as a reporting layer, so committed spend, recognised revenue and the ledger disagree at period end. Here the project is a dimension the accounting kernel already understands — profitability is a query, not a reconciliation.

See all 22 Project & Job Costing features, individually listed

Tax & Compliance

Tax is determined, split and posted by the engine — configured as data, correct by construction.

Indian GST, built inStates, HSN/SAC code masters with import, rate tables, and a compute endpoint that prices tax per line.
Automatic CGST / SGST / IGSTIntra-state splits into CGST + SGST (TAX_HALF basis); inter-state posts IGST — decided by the customer’s state, not the user.
Multi-country by designTax category and tax code are GL-mapping dimensions — “Dubai branch + VAT 5% → UAE Output VAT” is a rule, not code.
Compliance packsCountry compliance, tax and e-invoicing ship as pluggable packs — never branches in the kernel.

Reports & Analytics

Every report reads from posted ledger entries — indexed, decimal-safe, and drillable to the source document.

Live today

Trial BalanceProfit & LossBalance SheetGeneral Ledger Day BookCash FlowTax Summary

On the engine, next

Sales RegisterPurchase RegisterReceivables & AgeingPayables & Ageing Cash / Bank BookStock SummaryInventory Valuation
Drill-anywhere: click any number and a drill card opens — ledger → voucher → source document. Golden-arrow drill-down with deep links is a platform primitive, not a report feature.

GL Mapping Engine

No hardcoded ledgers. Accountants write conditional rules against any field on the document or its lines, combined with AND/OR across 10 operators; the engine resolves accounts through a 13-level priority fallback — with simulation and what-if preview before anything is saved.

Rules an accountant actually writes

  • Item group = Electronics + warehouse = Main → inventory posts to GL 130100
  • Customer group = Export → revenue posts to Export Sales
  • Branch = Dubai + tax = VAT 5% → UAE Output VAT
  • Payment method = Card → Card Clearing Account
  • Transaction currency ≠ company currency → exchange gain/loss posts automatically

Multi-book accounting

IFRS leadingLOCALTAXMGMT

Every posting renders per book — statutory, tax and management views from one event.

The 13-level fallback — click to explore

    Select a level to see how resolution cascades from the most specific rule to a global default.

    See all 16 GL Mapping features, individually listed

    AI, Everywhere — but it never posts

    Deterministic core, probabilistic edge. AI is on every surface; the kernel alone decides what reaches the ledger.

    In-app copilotBring-your-own-LLM (OpenRouter / Gemini / OpenAI), per-user AES-256-GCM-encrypted keys, monthly token budgets, usage metering. RAG over ERP knowledge via LlamaIndex + pgvector.
    ⌘K “Ask AI” everywhereThe command palette falls back to an AI answer grounded in the current screen. “Ask your books”: any number traceable to its events.
    MCP server for AI agentsA standards-compliant Model Context Protocol server — a category first. Customers’ own AI agents read and operate the books under scoped, expiring, revocable grants.
    Insights Command CenterDeterministic findings — “trial balance out by X”, “3 batches expiring”, “2 tenders unmapped” — each with a one-click Fix link or “Fix with AI”.
    1AI proposes“Draft a receipt for Skyline’s NEFT of ₹14,16,000”
    →
    2Human confirmsPosting slip with inferred values highlighted
    →
    3Kernel validatesAccess → period lock → Dr = Cr → atomic commit → audit log
    Natural-language policy: “Purchases over ₹50,000 on project Skyline need manager then CFO” becomes a versioned, testable approval rule — data, not code. That is how configuration dies.

    See all 19 AI features, individually listed

    Integration & Custom Work

    Nobody replaces every system at once. An ERP that cannot talk to what a business already runs — the storefront, the bank, the marketplace, the old ledger — is a second silo, not a solution.

    Versioned REST across every moduleToken-authenticated, with tenant, organization and company scoping enforced on every call, a consistent response envelope and idempotency keys on important writes — so a retry after a timeout cannot double-post.
    Third-party writes obey the kernelThe rule that makes integration safe: an external system cannot bypass accounting validation. Anything written through the API passes the same checks, and lands in the same audit trail, as something typed by a person.
    Headless commerce contractA storefront API contract with cache-invalidation webhooks, so a custom front end stays consistent with stock and pricing without polling.
    Your AI agents, scoped and auditedAn MCP interface lets a customer's own AI agents operate the ERP under admin-issued grants — scoped permissions, read-only where you say so, every AI write recorded in the audit trail as an AI actor.
    Migration as an integrationThe migration engine reads Tally today and is built so a new source ERP implements only discovery, extraction, parsing and normalization — never its own posting logic. Imports run through the ERP's own services, never a direct database write.
    Custom work, without a forkIndustry needs are profiles — feature flags, workflow presets, GL presets, document types — and posting rules are configuration. Most of what would be a customization elsewhere is a rule here, which is what keeps one codebase serving every customer.
    On the roadmap, stated plainly: hashed, scoped, rotatable and rate-limited public API keys; HMAC-SHA256-signed outbound webhooks with retry; OAuth applications for partner integrations; a published API documentation portal; and bulk import/export utilities for masters. They are designed and specified, not shipped — and this document marks them that way everywhere it mentions them.

    See all 14 integration features, individually listed

    All Modules at a Glance

    The complete module map of {{BRAND}} — what’s live today and what’s next. Green is shipped, amber is on the roadmap.

    Financials

    Accounting & Vouchers

    Double-entry vouchers, reversals, FX adjustments, period locks.

    GL Mapping Engine

    13-level fallback, determination trace, simulate & what-if.

    Multi-Book Accounting

    IFRS · LOCAL · TAX · MGMT books from one event.

    Tax & Compliance

    GST engine, HSN/SAC, auto CGST/SGST/IGST, country packs.

    Multi-Currency

    Per-line exchange rates, automatic FX gain/loss posting.

    Financial Reports

    TB, P&L, Balance Sheet, GL, Day Book, Cash Flow, Tax Summary.

    Dimensions

    Cost centers, profit centers, projects, segments.

    Revenue Recognition

    Schedules and recognition runs on the GL engine.

    Projects & Job Costing

    WBS, commitments from POs, percentage-of-completion, settlement runs.

    Operations

    Item Master

    Types, categories, brands, UoMs, BOM, attributes, media.

    Inventory & Warehouse

    Bins, batches, FEFO, ATP reservations, landed cost.

    Business Partners

    Roles, credit profiles, KYC, bank & tax records, GL links.

    Sales Workspace

    14-stage order-to-cash document chain.

    Purchase Workspace

    14-stage procure-to-pay document chain.

    POS

    Registers, split tender, thermal receipts, offline-fast billing.

    Order Management

    8 channels, ingest API, scan fulfillment.

    Salesmen & Commission

    Targets, commission rules, performance tracking.

    Billing Schedules

    Milestone, progressive and subscription invoicing, retention.

    Control

    Users & RBAC

    Roles, permissions, invites, per-company access.

    Approvals & Workflow

    Multi-level flows, condition trees, policy gate.

    Work Routing

    Queues, claim soft-locks, SLAs, Action Center.

    Audit Trail

    Immutable who/when/old/new/IP on every sensitive action.

    Intelligence

    AI Copilot

    BYO-LLM, encrypted keys, token budgets, RAG.

    MCP Server

    Scoped, audited access for customers’ own AI agents.

    Insights Center

    Deterministic findings with one-click Fix / Fix-with-AI.

    ⌘K Command Palette

    Fuzzy actions, recents, Ask-AI fallback.

    Help Center

    F1 per-screen help, field tips, full user guide.

    Platform

    Public API

    Versioned REST across every module, token auth, tenant-scoped, idempotency keys.

    Webhooks

    Storefront cache-invalidation live; HMAC-signed outbound with retry on the roadmap.

    Print Designer

    HTML/CSS templates, A4 + thermal, version history.

    English / العربية

    Full RTL, bilingual masters and printed invoices.

    Coming next

    Payroll

    Salaries, statutory deductions, GL-linked pay runs.

    Advanced Manufacturing

    BOM costing, work orders, subcontracting depth.

    OAuth Marketplace

    Third-party apps on scoped OAuth 2.0.

    Industry Packs

    Vertical presets — flags and templates, not forks.

    E-Invoicing Certs

    Per-country clearance integrations.

    Complete Feature List

    Every capability of the platform, enumerated individually and marked either available today or on the delivery roadmap — documented to field level so nothing is left to assumption on either side.

    Enterprise Platform

    True multi-tenancyTenant → Organization → Company → Branch/Warehouse scoping on every table and query. Accounting firms run multi-client workspaces natively.
    Immutable audit trailAppend-only event log: who, when, old value, new value, IP, reason. Corrections are new events — never edits.
    One atomic posting transactionAccess → period lock → Dr = Cr → voucher → ledger entries → tax → stock → audit. Any failure rolls everything back.
    Decimal-safe moneyAll amounts numeric(18,4), exchange rates (18,8). No floating point anywhere near accounting.
    Public APIVersioned REST across every module, token-authenticated and tenant-scoped on every call, with idempotency keys on important writes. Third-party writes cannot bypass accounting validation. Hashed rotatable keys and HMAC-signed outbound webhooks are on the roadmap.
    POS & omnichannelRegisters with split tender and thermal receipts; orders ingested from Zomato, Swiggy, Shopify, WooCommerce; barcode-scan fulfillment.
    Bilingual from day oneEnglish + Arabic RTL across UI, masters and printed invoices.
    Reports live todayTrial Balance, P&L, Balance Sheet, General Ledger, Day Book, Cash Flow, Tax Summary — from indexed ledger entries.

    Competition

    We do not win by claiming the incumbents are weak — anyone evaluating us has used them. SAP and Oracle are deep, correct systems. We win on who can reach that depth, how long it takes, and who owns the rules afterwards.

    ✓ Available ◐ Partial, edition- or partner-dependent ⧗ On our roadmap — not shipped ✕ Not available
    Capability{{BRAND}}SAP S/4HANA Oracle Fusion / NetSuiteTallyDynamics 365 BC
    Depth — where the incumbents are strong, and we match them
    Enterprise accounting depth (GR/IR, multi-book, landed cost, retention) ✓✓✓✕◐
    Conditional account determination ✓ 13-level✓✓✕◐ posting groups
    Multi-book accounting — IFRS · LOCAL · TAX · MGMT ✓✓✓✕◐
    Immutable audit trail on every posting ✓✓✓◐ edit log✓
    Access — who can actually get to that depth
    Configure posting rules without a consultant or partner ✓✕✕◐ limited scope✕ partner-led
    Natural-language policy compiled to testable rules ✓✕✕✕✕
    Pre-posting simulation & what-if on mapping rules ✓ built in◐ custom dev◐ custom dev✕✕
    One product, 1 user → 10,000+, no re-implementation ✓✕ tiered products✕ tiered products✕ ceilings✕ upgrade to F&O
    Keyboard-first transaction speed ✓ entry & focus advance✕✕✓✕
    Cloud-native multi-tenant SaaS ✓◐ cloud editions✓✕ desktop-first✓
    AI — where the category is still being defined
    AI assistant grounded in your own ERP data ✓✓ Joule✓✕✓ Copilot
    AI architecturally barred from posting to the ledger ✓ hard rule◐ not stated◐ not stated✕◐ not stated
    Audited MCP access for the customer’s own AI agents ✓ category first✕✕✕✕
    Every AI write recorded in the audit trail as an AI actor ✓◐ not stated◐ not stated✕◐ not stated
    Getting on — and getting off
    Built-in migration engine from Tally ◐ local Tally reads live; scope expanding◐ partner tools◐ partner toolsn/a◐ partner tools
    Migration imports through the accounting kernel, never direct DB writes ⧗ architectural rule, not yet shipped◐ varies◐ varies✕◐ varies
    Switchable UI modes on one dataset ⧗ Classic ships; Rapid, Flow, Forms designed✕✕✕✕

    How to read this. Rows are chosen where the differences are real and checkable, and the incumbents are marked honestly — SAP and Oracle carry ✓ on every depth row because they earn it. Our own roadmap items carry ⧗ rather than ✓, including in the row where that costs us the comparison. Capabilities vary by edition, module and licence, and vendors ship continuously; this reflects generally available positioning as of this document’s date and is our reading, not the vendors’.

    The one-line version. Against SAP and Oracle we are not claiming more depth — we are claiming the same depth without the implementation programme, and owned by the customer afterwards. Against Tally and Business Central we are claiming the depth outright. No competitor is currently offering audited, scoped access for a customer’s own AI agents, which is the row we expect to matter most three years out.

    Editions & Go-to-Market

    One product, four editions. Upgrades are flags, not migrations.

    Shop1–5 users

    POS + simple books. Engines hidden; a solo trader is “everyone” — zero setup.

    Standard5–50 users

    Basic engines, simple approvals, full accounting and inventory.

    Professional50–500 users

    Full GL-mapping, workflow and pricing engines; serial/batch & landed cost.

    Enterprise500–10,000+

    Unlimited multi-company & country, custom dimensions, OAuth apps.

    Roadmap

    Kernel first. Engines second. Skins last.

    P0 — Foundation Shipped
    Everything shipped in P0
    • Multi-tenant model — Tenant → Organization → Company → Branch / Warehouse
    • Auth — JWT login, refresh tokens, change password, sessions
    • Users & RBAC — invites, role assignment, permission engine
    • Accounting masters — chart-of-accounts presets & import, groups, ledgers, balances
    • Voucher posting engine — one atomic transaction: access → period lock → Dr = Cr → voucher → ledger entries → tax → stock → audit; reversal entries; FX gain/loss adjustments
    • Item, warehouse (with bins) and business-partner masters
    • Classic UI shell — dashboard, window manager, drill-down cards, context menus
    • Immutable audit trail on every sensitive action
    P1–P3 — Engines & workspaces Shipped

    Sales workspace — all 14 stages shipped:

    Lead→Opportunity→Quotation→Sales Order→Approval→Fulfillment→Delivery→Shipment→Invoice→Payment→Returns→Credit Note→Collections→Closure

    Purchase workspace — all 14 stages shipped:

    Purchase Request→Requisition→RFQ→Vendor Quotation→Vendor Comparison→Purchase Order→Approval→Goods Receipt→Quality Inspection→A/P Invoice→Vendor Payment→Debit Note→Purchase Return→Closure
    GL Mapping Engine — shipped
    • Multi-book accounting — IFRS / LOCAL / TAX / MGMT with leading-book flag
    • Account roles, posting templates, stage postings
    • Priority-based conditional mapping rules over any document or line field
    • Simulate, simulate-document and what-if previews before saving
    • Validation rules with BLOCK / WARN severity
    • Financial periods — generate, lock, unlock
    • Revenue recognition schedules + recognition runs
    • Config versions with diff and one-click restore
    Workflow, routing & approvals — shipped
    • Policy rules — AUTO / BLOCK / route-to-human on every forward transition
    • Multi-level approval flows with USER/ROLE approvers and condition trees
    • Routing rules → work items with claim soft-lock, claim / done
    • Action Center — Needs you · My work · My requests · Activity
    POS, omnichannel & documents — shipped
    • POS — register sessions with float & reconciliation, split tender, thermal/A4 receipts, amount in words, barcode
    • Omnichannel orders — POS · Zomato · Swiggy · UberEats · Shopify · WooCommerce · Webstore · Phone, with barcode-scan fulfillment
    • Process documents — pre-posting simulation, journey view, raise-purchase (back-to-back), billing milestones, retention, landed cost, flow templates
    AI, MCP & Insights — shipped
    • AI copilot — per-user provider/model/key (AES-256-GCM), token budgets, usage logs
    • MCP server — scoped, expiring, revocable AI access grants; writes through the posting engine
    • Insights Command Center — deterministic findings with one-click Fix / “Fix with AI”
    • ⌘K command palette with Ask-AI fallback · F1 Help Center
    Experience modes In progress

    Design-token framework + Rapid (Tally) mode with full keyboard engine; Flow (Fiori) mode next.

    P4 — Depth

    Payroll, advanced manufacturing (BOM costing), partitioning & read replicas, Forms (Oracle) mode.

    P5 — Ecosystem

    Public OAuth marketplace, subscription billing, industry profile packs, per-country e-invoicing certifications.

    Proof, Not Promises

    A full Procure-to-Pay + Order-to-Cash cycle ran through the production API on an isolated company. Every journal was posted automatically by the GL engine — no manual entries.

    Resulting control accounts

    Inventory on hand (60 units)₹ 9,00,000 Dr
    Cost of goods sold (40 units)₹ 6,00,000 Dr
    GR/IR clearing₹ 0 — nets to zero
    Vendor control (Nexus)₹ 0 — nets to zero
    Customer control (Skyline)₹ 0 — nets to zero
    ICICI Bank (net)₹ 3,54,000 Cr

    Trial Balance

    ₹ 17,70,000 = ₹ 17,70,000

    Balanced to the rupee. Intra-state GST auto-split into CGST/SGST; inter-state posted as IGST; product vs service revenue routed by line type; COGS at moving-average cost.

    0API controllers
    0test suites over the kernel
    0accounting books — IFRS/LOCAL/TAX/MGMT
    0industry verticals on one kernel

    Talk to us

    Two different conversations, so they get two different starting points — tell us which one you are and we will not waste your time on the other.

    For businesses

    See your own books run on {{BRAND}}

    We walk your team through a live company end to end — procure, sell, post, report — then hand you the keyboard. Bring your own chart of accounts and a month of real documents; the migration engine imports Tally and multi-ERP sources, so the demo runs on your data, not ours.

    • Live walkthrough on your own ledger
    • Migration assessment from your current system
    • Straight answer on what is available today vs on the roadmap
    Request a live walkthrough
    For investors

    The numbers behind the claims

    Every figure in this document is counted out of the repository at build time rather than typed — data models, API endpoints, controllers, lifecycle stages and test suites. The complete feature list enumerates all 764 capabilities individually, each marked available today or on the roadmap, so due diligence starts from a claim you can check rather than a pitch.

    • Architecture and engineering walkthrough
    • Product and go-to-market detail under NDA
    • Feature-by-feature delivery status, in writing
    Start an investor conversation

    Figures shown are from the product’s own live test ledger. Feature counts and code metrics are generated from the source at build time.
    {{COMPANY}} · sales@virtux.in

    The people behind {{BRAND}}

    RA
    Rajeesh Ambadi Co-Founder · Chief ERP Architect · Techno-Functional ERP Specialist
    • ERP Architecture, Core Engine & Financial Ledger Design
    • Product Vision, System Architecture & Platform Engineering
    • Business Process Transformation & Enterprise Solution Design
    • Bridging Business, Finance, and Technology to build next-generation ERP platforms
    RK
    Rashid Abdul Kareem Co-Founder · Project Engineer · Solution Architect · Business Transformation Consultant
    • Enterprise Solution Design & Business Process Engineering
    • Project Planning, Implementation & Delivery
    • Digital Transformation Strategy & Operational Excellence
    • Business Analysis & Customer Success