docs / get-paid-without-chasing-people
Get paid without chasing people
Kiipu turns collections into something that runs on its own until a decision is needed. Every payment is approved by a person before it touches the books, and every movement lands in a ledger that balances by construction.
before you start
What this guide covers.
// Kiipu is niiko's collections module. It works with bank transfers and receipts.
This guide covers issuing a debt, getting it in front of the person who owes it, chasing it without anyone having to remember, and recording the payment. It is not general accounting, and Kiipu never moves funds itself.
Card numbers never touch niiko's infrastructure, and no payment is ever applied automatically. A person approves every cent before it counts.
step one
Issue the debt, with a plan if it needs one.
// An installment's state is a projection of the ledger, never an editable column.
An invoice can carry an installment plan. The state of each installment — paid, pending, overdue — is derived from the ledger rather than stored as a field somebody edits. That distinction is the reason the numbers can always be audited against their own detail: nothing can be marked paid without a movement that says so.
step two
Send a link the debtor can actually open.
// One link per debt, no account needed, revocable.
- Public by link — the person opens it without creating an account
- One link per debt, so revoking one never affects another
- Revocable when you need it
step three
Let the reminders go out on their own.
// Deduplicated, and held outside quiet hours.
Reminders send themselves over WhatsApp and email on schedule. Two things matter more than the schedule itself: they are deduplicated, so a person never gets the same nudge twice from two paths, and they are held outside quiet hours — a debt collector that messages at 3am costs you the relationship, not just the payment.
Reminders go out once a day on a single schedule. Choosing the send times per workspace is not built yet.
step four
Let AI read the receipt, and a person confirm it.
// It suggests. It never applies a payment on its own.
The debtor uploads a photo of their transfer receipt. The system reads it and suggests the amount, the date and the reference; a person approves before anything is applied. That boundary is deliberate and it is not a setting: an AI reading a blurry photo of a bank transfer is useful, and it is not something that should be able to close a debt by itself.
how it adds up
Every movement lands in a ledger that balances.
// Double-entry by construction, not by discipline.
Money never moves in niiko without a double-entry record. It is why the state of an installment can be derived instead of stored, and why a number on a screen can always be traced to the movements that produced it.
What this guide doesn’t cover
Running in production: payment links, automatic reminders, AI-read receipts, the approval step and the ledger. What is not built yet:
- Per-workspace send times for reminders. They go out once a day on a single schedule.
- It is not general accounting, and it never moves funds — it works with bank transfers and receipts.
Last updated: 2026-09-02.