What's New in Kharchai: API Access, Webhooks, and Receipt Scanning

We have spent the past few weeks building the parts of Kharchai that most expense tools skip: the plumbing that lets it fit into how your business already works. Four things shipped, and each one solves a specific complaint we kept hearing from early users.

Plans that match how you actually grow

Kharchai now has three tiers: Free, Pro, and Custom. Free covers one branch and up to five active submitters, which is enough for a single office finding its feet. Pro removes the submitter limit, adds up to five branches, and unlocks the features below. Custom is for organizations that need unlimited branches and entitlements shaped around how they specifically operate. Every tier keeps the same core: submission, approvals, payments on a double entry ledger, budgets, and a full audit trail. Pricing is still being finalized before launch, which is why our pricing page shows "Rs XXX" for now. The tiers and their features are real; the numbers are the last piece.

An API, so Kharchai is not an island

If you already have a system for payroll, accounting, or internal reporting, the last thing you want is another dashboard nobody checks. Pro and Custom organizations can now generate scoped API keys and pull expenses, payments, and journal entries directly into whatever you already use. Pro gets read only access; Custom gets full read-write with higher rate limits, for teams building deeper integrations. Every key is scoped to exactly what it is allowed to touch, and every key can be revoked the moment it should not exist anymore.

Webhooks, so you find out the moment something happens

An API you have to poll is only half useful. Webhooks push events to you the moment they happen: a payment fails, an expense gets approved, a receipt finishes processing. Each webhook endpoint is signed, so you can verify a request genuinely came from Kharchai, and every delivery attempt is logged, including retries and failures, so you are never guessing whether an event actually reached you.

Receipts that read themselves

This is the one non-technical users will feel first. Instead of typing in the amount, date, and merchant off a photo, snap the receipt and Kharchai reads it for you. Every scan comes with a confidence score, and anything the system is not sure about gets flagged for a human to check before it is trusted. It will not replace judgment on a blurry, half torn bill, but for the ordinary taxi receipt or lunch bill, it turns a thirty second data entry chore into a five second confirmation.

Getting your data out, cleanly

Not everything belongs inside Kharchai forever. Finance teams need to hand data to auditors, load it into Excel for a board deck, or archive a fiscal year. Expenses, journal entries, and payments can now be exported to CSV directly from the app.

Why this batch, and not something else

Every one of these four things exists because it removes a reason not to switch. "It will not talk to our other tools" is answered by the API and webhooks. "Data entry from receipts takes too long" is answered by OCR. "We cannot get our data back out" is answered by CSV exports. None of it changes how approvals or payments work, because that part was already solid. It just makes Kharchai easier to plug into a business that already exists, rather than one built from scratch around it.

We are still in early access, and pricing for these tiers is not final. If you want to be first in line when it opens up, join the waitlist.