The finance team that runs itself.
Connect your marketplaces. CosmOS finds what they kept, files the claim, and books the entry. Your books close themselves.
GST-native · immutable ledger · money never floats
Overview
Where the money went this period.
Gross sales
₹42,58,120
12 settlements
Marketplace fees
₹6,31,004
14.8% of gross
Leakage found
₹1,52,340
222 open findings
Net deposited
₹27,59,500
reached the bank
Gross to net
Reads directly from
Every leaked rupee, found and claimed.
Every settlement line checked against the orders behind it. When a fee is wrong, you get the number and the evidence.
- Commission overcharges, flagged per line
- Shipping fees and weight-slab disputes
- Returns and RTO checked against stock
- Refund commission never credited back
- Referral fee overchargeS-1042 · rate card 15.5%, charged 18%₹12,480Claim filed
- Return not reimbursed58 units · received, never credited₹48,930Investigating
- Refund commission not returned43 orders · commission retained₹26,340Claim filed
- Payout mismatchS-1039 · report vs bank deposit₹8,930Recovered
Books that close themselves.
Every settlement, fee, return and recovery posts as a journal entry. The trial balance is always current, so month-end stops being an event.
- A voucher for every transaction, fully traceable
- Reports from the ledger, not marketplace exports
- Maker-checker where judgement is needed
- Periods that refuse to close over a known gap
- Amazon settlement AMZ-IN-2026-12Dr Bank · Dr Fees · Cr Sales₹2,54,228Posted
- TCS withheld u/s 52matched to the settlement report₹1,271Posted
- Returns provisiondrafted · maker-checker₹34,750Awaiting review
- Weighted-average COGScosted at the running average₹1,66,291Posted
GST, TDS and TCS, ready before the deadline.
Withholding is tracked the moment a settlement lands, not rebuilt from reports the week the return is due.
- TCS u/s 52 and TDS u/s 194-O, per settlement
- Matched to what the marketplace actually deducted
- A filing calendar built from your own postings
- Output GST and GSTR-2B credit recovery in build
- TCS u/s 520.5% of ₹42,58,120 taxable value₹21,291Posted
- TDS u/s 194-O0.1% of ₹42,58,120 gross sales₹4,258Posted
- Matched to the settlement reportboth figures agree with Amazon✓Posted
- GSTR-1due 11 Oct · summarised from the ledger11 OctAwaiting review
Your books. Not a feed into someone else's.
Reconciliation tools push a summary into Tally and stop. CosmOS is the book of record, and still exports clean entries to your ERP.
- Native double-entry, append-only by construction
- A chart of accounts you configure
- Nine integrity checks, on demand
- CSV export to Tally, Zoho, Busy, QuickBooks
- Trial balance balancesdebits equal credits✓Posted
- Every voucher balancesenforced by the database✓Posted
- Journal is append-onlyUPDATE revoked at role level✓Posted
- Inventory ties to the subledgerledger vs stock✓Posted
Nobody hands you a login and wishes you luck.
Every customer gets an engagement sized to their business. We map your fee schedules, connect your marketplaces and set up your books before you run a single report.
Your rate cards, mapped
Every fee schedule you have negotiated, encoded rule by rule, so the reconciliation knows what correct looks like for you rather than for an average seller.
Your channels, connected
Seller accounts, bank feeds and GST credentials wired up and tested against a real settlement of yours, not a sample file.
Your chart of accounts, not ours
Configured to match how your CA already books, so the export lands in your ERP without a cleanup pass at the other end.
Your first close, together
We run the first reconciliation and the first month-end alongside your team, so the handover is a working process rather than a document.
What we learn setting you up becomes part of the product. The next business we onboard takes less time because of yours, and the one after that less again.
Ask your books anything.
Plain questions about fees, margin, tax, stock and payouts. The model picks the question. The ledger supplies the number.
When it cannot answer, it says so
- Not recognised · it cannot compute that
- Not permitted · your role cannot see those accounts
- Not licensed · your plan excludes that module
- No data · nothing posted for that period
- Out of scope · it reaches beyond your books
Five refusals, not one shrug. An assistant that guesses once is an assistant nobody trusts twice.
What did Amazon actually keep last month?
Amazon deducted ₹6,31,004 on ₹42,58,120 of gross sales, or 14.8%.
- Referral fees₹2,78,140
- Fulfilment fees₹2,18,732
- Advertising₹94,132
- Storage and other₹40,000
From 12 settlements · ledger, August 2026
From marketplace mess to closed books.
Every source feeds one immutable event log. The loop runs continuously, and everything it concludes lands as a journal entry.
Sources
Amazon
SP-API settlements
Flipkart · Meesho
seller APIs
Shopify · ONDC
orders and payouts
Banks
statements
GSTN
GSTR · e-invoice
The loop
Step four is a journal entry, not a summary handed to another system
Outputs
Trial balance
always current
P&L · Balance sheet
from the ledger
GST & TDS
per settlement
Audit trail
every action replayable
ERP export
Tally · Zoho · Busy
One line, all the way down.
A settlement line as Amazon sent it, the rule that caught the overcharge, and the entry it produced. Move an account and watch the books stay balanced.
What Amazon sent
What the rules found
Tolerance is half a point. At 7.5% this rule stays quiet.
What posted
Rule key · your account
clearing.amazon₹10,980fee.commission₹1,020revenue.marketplace4010 Marketplace Sales₹12,000Rules speak in keys. Your chart decides where a key lands, and that map is data your CA edits, not code we deploy.
The entry records what happened. The claim records what should have. Software that quietly posted the ₹840 you were owed would balance too, and your books would be a work of fiction.
Trust is a feature. It ships in the schema.
Every figure is provable. The audit trail is not a report you run, it is the system itself.
The AI cannot invent a number
The model reads and classifies. A deterministic kernel posts, and the database refuses an unbalanced voucher.
The journal is append-only
UPDATE is revoked at the database role level. A correction is a reversing entry, never a rewrite.
Money never floats
Integer paise, end to end. No figure in your books is the result of a floating-point multiplication.
One tenant cannot see another
Row-level security under a non-owner role, so a forgotten WHERE clause cannot leak another business.
A closed period stays closed
Postings into a closed period are rejected, and closing is blocked while any posting is known to have failed.
Every figure traces to an event
The ledger is event-sourced. Any balance walks back to the settlement line that caused it.
The questions your CA will ask.
Does this replace Tally or Zoho?
No. CosmOS is the book of record for your marketplace business, and exports clean journal entries to whatever your CA already runs.
How is this different from a reconciliation tool?
A reconciliation tool finds a discrepancy and hands you a spreadsheet. CosmOS quantifies it, then posts the journal entry.
Is this software or a consulting engagement?
Software. The engagement exists to get your fee structures, channels and books into it, and what we learn doing that goes back into the product rather than into a playbook we resell.
Can the AI change my numbers?
No. It routes questions and reads documents. Posting is deterministic, and an unbalanced entry is refused by the database.
Which marketplaces work today?
Amazon, over SP-API. Flipkart, Meesho, Shopify and ONDC are next, along with bank statements and GSTN.
Where does GST stand?
TCS u/s 52 and TDS u/s 194-O are tracked per settlement today. Output GST and GSTR-2B credit recovery are in build.
Is my data separate from other businesses?
Yes, enforced by Postgres row-level security under a non-owner role, and checked by an integrity test that fails on a cross-tenant line.
See what your marketplaces kept.
Thirty minutes. We walk the ledger, the reconciliation and the journal entries end to end, on demo data or on a settlement of yours.