Connect every source your money touches - in minutes.
Money leaves a trail across systems that never talk to each other. RakamHQ collects all of it - provider reports, bank statements, order exports, cash totals - and keeps every file as immutable evidence.
Every reconciliation starts with getting the raw truth in. RakamHQ meets each rail where it actually is - a Khalti secret key that floods in history, an eSewa report you forward to a private address, a bank statement you upload, an orders CSV mapped once. No rail is left out because it lacks a nice API.
Whatever comes in is stored exactly as received, content-addressed and immutable, before a single number is normalized. Every figure downstream can be traced back to the specific line in the specific file it came from.
What you get
- Khalti API pull - full transaction history and per-transaction fees
- eSewa reports via private email-forward address or upload
- Bank statements (CSV / XLS / PDF) with a per-bank format registry
- Orders via CSV column-mapping wizard, Google Sheet, or push API
- Cash logged as a simple daily total
- Every file kept as immutable, content-addressed evidence
Sources, in detail.
Three ways in, per source
Connect a credential and RakamHQ pulls automatically. Forward a provider's daily report to your private reports address and we parse it the moment it lands. Or upload last month's file by hand. Each source picks whatever is easiest - a Khalti key, an eSewa email-forward, a bank CSV - and the ledger never knows the difference, because every connector presents the same normalized shape.
The parser framework is the moat
A new file format is mapped once. Its headers and a few sample rows produce a proposed column mapping that a person confirms, and from then on it is deterministic forever. Every format that reached production becomes a permanent test fixture, so parsers only gain formats and never silently change old outputs. An unparseable file surfaces as an exception with the offending rows highlighted, never a quiet discard.
Evidence first, numbers second
Files land in an immutable evidence locker keyed by content hash, so re-uploading the same eSewa report is a no-op by construction. Only after a file is safely stored do parsers turn it into normalized transactions. Every transaction keeps a pointer back to its exact source line, so nothing in your ledger is ever un-provable.
Your keys, on a short leash
RakamHQ never asks for a dashboard password. It accepts a provider's API secret key only - a Khalti key that pulls history and per-transaction fees - and you can revoke it in one click. Most sources need no credential at all, working from forwarded reports or uploaded files, so the blast radius of any single key stays small.
History first, then every day after
A newly connected key first floods in the full history it can reach, then settles into a daily rhythm - each morning's report parsed on arrival, each new transaction appended. eSewa reports you forward, bank statements you upload monthly, and orders pushed in real time all converge on the same timeline, so the ledger is always as current as its slowest source.
FAQ
Sources,
explained
Common questions about sources. Want it run on your own data first? The concierge reconciliation is free.
Never. We accept provider API secret keys only, and you can revoke them in one click. Most sources work from files alone, with no credential at all.
Get your free reconciliation.
Send us last month's eSewa report, Khalti export, bank statement and orders sheet. Within 48 hours we send back a one-page close - every payment matched, every fee computed, every settlement decomposed.
Files only · private upload link · nothing to install