Pull the customer and items from records you already have, send a GST invoice with a payment link, and watch the ledger reconcile itself. Built for Indian businesses, in development now.
The customer is in your CRM. The items and prices are in your Catalog. So the invoice mostly fills itself — you confirm, you don't transcribe.
The bill-to comes from the CRM contact; every line item, its price and its tax rate come from Catalog. Change a price once in Catalog and every future invoice is correct — no stale rate hiding in a Word template from last year.
Pick the contact; name, address, GSTIN and payment history come with it. No re-keying a customer you already know.
Line items, prices and tax rates are referenced, not typed — so the invoice and your price list never disagree.
When SK Voice or SK Chat closes a sale, the draft invoice is the next step in the same flow — not a separate chore for later.
Send a quote, get a yes, convert it in one click — the numbers carry over untouched.
Retainers and subscriptions bill themselves on schedule, with the same payment link and reminder flow.
Invoice in ₹, $ or € — the customer sees their currency, your books stay consistent.
Every invoice carries a Razorpay payment link, and a reminder sequence runs until it's paid. You stop being the collections department.
Day zero: the invoice goes out with a one-tap payment link. Day three: a gentle WhatsApp nudge. Day five: an SMS. Day seven: a task lands on someone's desk. Every step runs through SK Notifications with fallbacks — and the moment the customer pays, the chase stops and the invoice marks itself paid.
UPI, cards, netbanking — one tap on the invoice. Money lands in your account, not in a follow-up call.
WhatsApp → SMS → email, on your schedule, until paid. Polite, automatic, relentless.
The payment webhook flips the invoice to paid and posts to the ledger — no manual matching.
Advance, balance, instalments — tracked cleanly, the running balance always correct.
Past due dates escalate automatically; you see who's late at a glance, not after a spreadsheet hunt.
Paid invoices send a receipt on the customer's channel — no extra step from you.
Every invoice, payment, credit and refund posts to an append-only internal ledger as it happens. Your books reconcile by construction.
Accounts receivable, tax collected and cash movement aren't things you maintain — they're derived from the posting log. Nothing is back-dated; corrections post forward. The number is always defensible because you can always see how it got there.
Every event posts once and stays. No silent edits, no overwrites — a history you can defend to any auditor.
Who owes what is computed from the log, not maintained by hand. It can't drift out of sync.
GST collected is a derived figure, ready for filing — not a quarter-end reconstruction.
Mistakes are fixed with a new dated entry, never by rewriting the past. The trail stays intact.
Handled as first-class postings, so your AR and cash always reflect reality.
Clean, structured data your accountant can actually use — not a PDF pile to re-enter.
Tax rates, HSN/SAC codes, registration details and compliant numbering are first-class — designed for the rules Indian SMBs actually file under.
Each line carries its tax treatment; the invoice computes CGST/SGST/IGST correctly; document numbering follows the rules; registration details sit where they belong. It's built for India first, not retrofitted from a US template.
Intra- and inter-state tax computed correctly per line, automatically — not a manual lookup.
Stored on catalog items, printed on invoices, ready for your returns.
Sequential, gap-free invoice numbering that holds up to scrutiny.
Yours and your customer's, where the format requires them.
Designed to plug into IRN/e-invoicing as thresholds bring more businesses in scope.
Tax data structured for GSTR filing rather than reconstructed at quarter-end.
Draft → sent → partially paid → paid → overdue is a guarded lifecycle. An invoice can't silently flip states, and every transition is on the timeline.
Status changes are guarded transitions with an actor and a timestamp. You can always answer who sent it, who edited it, when it was paid — because the invoice carries its own audit trail, and the customer's timeline shows it too.
States change in legal order only — no invoice mysteriously 'paid' without a payment behind it.
Who, what, when — on every invoice and on the customer's timeline. Disputes end quickly.
Billing history sits beside calls, tickets and bookings — one view of the whole relationship.
Cancellations void with a reason and stay visible. History never disappears.
Who can send, who can void, who can only view — controlled, audited, clear.
invoice.sent, payment.recorded, invoice.overdue — your systems hear it the moment it happens.
SK Billing lives on the same customer record, the same events and the same rails as the rest of the suite.
Start free See the developer surface →