Banking & reconciliation
Bring your bank into your books two ways: import statements (CSV or Excel) with automatic bank detection, or connect a live feed through the RBI Account Aggregator framework. Either way, OnGravy suggests matches against your books and applies your categorisation rules — and never posts anything without you.
Importing statements
Upload a CSV or Excel statement at /dashboard/banking. The format is detected from the header signature — no template mapping to fill in for supported banks:
- 20+ Indian banks: HDFC, SBI, ICICI, Axis, Kotak, Yes Bank, IndusInd, Federal, IDFC First, Bank of Baroda, PNB, Canara, Union Bank, RBL, Bandhan, AU Small Finance, Equitas, IDBI, and more.
- 20 Nigerian banks and fintechs, detected the same way.
Amounts are stored exactly, down to the paise — no floating-point drift between the statement and your books.
Auto-matching — suggests, never posts
After import, OnGravy matches statement lines against your invoices, bills, and vouchers using a deliberately strict rule: the amount must match exactly, and the date must be within 3 days. Matches appear as suggestions for one-click confirmation.
Matching never auto-posts. A suggested match does nothing to your books until you accept it — the same review-first principle as the OCR inbox in Daily bookkeeping.
Bank rules — auto-categorisation
For recurring lines that are categorisation rather than matching — bank charges, subscription debits, UPI settlement sweeps — set up rules under Settings → Bank rules. Rules are applied automatically by a scheduled job, so imported and fed-in transactions arrive pre-categorised the way you decided once.
Account Aggregator — live bank feeds (India)
Instead of importing statements by hand, Indian businesses can connect live feeds through the RBI-regulated Account Aggregator framework at /dashboard/aa-consents:
- Start a consent: enter your VUA (virtual user address), pick the bank accounts, the date range, and the refresh frequency.
- You are redirected to your Account Aggregator app to approve the consent — the approval happens with the AA, not inside OnGravy.
- Once granted, feeds refresh automatically every 4 hours. No more downloading statements.
Managing AA consents is restricted to the owner, admin, and accountant roles.
Same-day cheque clearing flags
Under the RBI same-day cheque clearing regime (January 2026), cheques clear the day they are presented. OnGravy uses this: any cheque still uncleared after more than one business day is flagged as an anomaly — an early warning for bounces, holds, or entry errors that used to hide inside a multi-day clearing window.
Reconciliation
/dashboard/reconciliation is where you close the loop: work through unmatched statement lines and unmatched book entries until the bank balance and the ledger balance agree. Confirmed matches from auto-matching and categorisations from bank rules have already done most of the work by the time you get here.
Gotchas & good to know
- Matching is strict on purpose. Exact amount + 3-day window means fewer, safer suggestions. A payment that arrives net of charges will not auto-suggest — handle the difference explicitly.
- Nothing posts without you. Neither imports, nor matches, nor AA feed lines write to your ledger on their own; rules categorise, humans confirm postings.
- AA consent lives with your Account Aggregator. If feeds stop, check the consent status in your AA app first — expiry or revocation happens on their side.
- AA is India-only (an RBI framework), and only owners, admins, and accountants can manage consents.
- Detection is by header signature.Export the statement in your bank’s standard CSV/Excel format — heavily edited or re-saved files can lose the headers detection keys on.
- Paise-exact storage means a one-paisa difference is a real difference — trust the mismatch and find the source rather than rounding it away.