Every part earns its place
Kelekto is built around six questions. Does a feature help capture billable work, build the right invoice, send it, confirm payment, decide whether to chase, or manage the commercial relationship? If not, it is not here.
Clients
Just enough CRM to bill correctly.
- Billing and registered addresses, VAT and company numbers
- Multiple contacts with billing and contract roles
- Client-level defaults for currency, payment terms and tax
- Full activity history — every invoice, payment and change
Contracts
The commercial agreement is a first-class record, not a note.
- Start and end dates, renewal type and notice period
- Contract value, with invoiced and unbilled consumption tracked against it
- PO requirements enforced before an invoice can be sent
- Signed documents, SOWs and amendments in private storage
Rates
Rates live on the contract and are versioned by date.
- Day, hour, fixed, monthly or unit billing types
- Valid-from and valid-until windows, so mid-year uplifts just work
- Per-rate tax treatment overriding the contract default
- Historical invoices keep the rate they were actually raised on
Work
Time tracking is optional, never mandatory.
- Log a day, a half day, or hours against a contract rate
- Or simply enter “12.5 days” while building the invoice
- Billable and non-billable entries kept distinct
- Unbilled work value surfaced on the dashboard and the contract
Expenses
Policy decides what the client can be charged.
- Categories: mileage, travel, hotel, food, equipment and your own
- Expense policies per contract: at cost, fixed rate, marked up, or not billable
- Original currency, exchange rate and base currency all retained
- Mileage recorded with origin, destination and distance, priced from policy
Invoices
Assembled from real records, then frozen.
- Draft, ready, sent, part-paid, paid, overdue and void states
- Server-side transactional numbering — no gaps, no duplicates
- Seller, customer, contract and rate snapshots on finalisation
- PDF plus an optional tokenised customer view with supporting evidence
Payments
Know exactly what has landed.
- Manual payment recording with method, date and reference
- Partial payments and overpayments handled properly
- Balances always derived from confirmed payment records
- Bank import and Open Banking matching designed for, not bolted on later
Collections
Chasing that respects the relationship.
- Collection policies at contract, client or organisation level
- Grace periods and a first / second / final reminder ladder
- Snooze an invoice with a reason when you know payment is coming
- Recommendations informed by that client's own payment history
Historical integrity
An invoice from last year still says what it said last year
Change a client's address, renegotiate a day rate, update your VAT number — none of it rewrites history. Finalised invoices snapshot the seller, the customer, the contract terms and every line, so what you sent is what you can always reproduce.
Acme Ltd
Software Consultancy 2026/27 · PO 44120
Billing period
1 – 31 Aug 2026
Senior Development
12.5 days @ £650.00
Train — London
Receipt attached
Taxi — client site
Receipt attached
Hotel — 2 nights
Receipt attached
- Subtotal
- £8,429.40
- VAT @ 20%
- £1,685.88
- Total
- £10,115.28
Due 30 Sep 2026 · 30 day terms
Send invoiceDeliberately out of scope
What Kelekto is not
It is a billing and collections assistant, not an accounting system. Keeping it focused is what keeps it fast and easy to trust.
Accounting integrations are planned, so the numbers Kelekto produces can flow into the system your accountant already uses.