For workflow software that ends in a payment
Every job, case, booking or lease in your software ends with someone owing someone money. CitaLedger adds the invoice, the follow-up, the payment, the supplier bill and the statement to the product your customers already use, with books that always balance.
Field service · property management · clinics · law and accounting practices · agencies · trades · memberships
Why you need it
Your platform is where the work happens: the job is scheduled, the case is opened, the appointment is booked, the task is marked done. Then the money leaves the building. The invoice is made somewhere else. The payment lands in a bank portal. Someone chases the late ones by email. Suppliers are paid from memory. At month end, the accountant types it all in again.
The result is three versions of the same money that never quite agree, and simple questions nobody can answer on the spot.
"Has this customer paid?"
Today: open the bank, search the inbox, ask a colleague. With CitaLedger: the answer sits on the job itself.
"Who is late, and did we remind them?"
Today: a spreadsheet someone updates on Fridays. With CitaLedger: the list is always current, and the follow-up is part of the workflow.
"Whose money is this?"
Deposits, retainers and client funds all land in the same account. With CitaLedger: money held for others is kept apart from the first dollar.
In plain terms, CitaLedger turns money from a side job into part of the product your customers already pay for.
How it works
Three systems, three jobs. Your platform keeps the people and the work. CitaLedger keeps the money. The accountant keeps their own software. Nothing is replaced, and nobody re-types anything.
CitaLedger never holds anyone's money. Payments are made by licensed providers straight into the business's own bank account, or into a trust account when the money belongs to someone else. CitaLedger asks for payments and records them, which keeps it a software product and keeps funds where the law expects them.
The same steps a business already follows, with CitaLedger writing the books at every one of them.
AI in CitaLedger
The slow parts of money work are reading, matching and following up: a supplier's invoice, a bank transfer with a cryptic note, a polite reminder that has to go out again. CitaLedger's AI handles those. Anything that moves money, or changes the books, waits for a person to approve it.
Turns a PDF or an emailed bill into a draft entry, matched to the job or order, with anything unusual pointed out.
An e-Transfer that says "inv 1042 thx" gets matched to the right customer and suggested for a one-click confirmation.
Drafts a reminder in the business's own tone, picks the right moment, and knows when to stop because the money has arrived.
A duplicate invoice, a bill much higher than the quote, a payment that doesn't match anything: flagged before it becomes a problem.
A draft is always labelled a draft. AI suggestions appear clearly marked until a named person approves them. The books themselves are written by rules that never change, so an AI mistake can be caught and reversed, never silently absorbed.
The ledger and statements are available today. Collection, reminders, supplier payments and the AI helpers follow on our roadmap.
Built for Canada
Most money software is built elsewhere and adapted later. CitaLedger starts from how business money actually moves here.
Deposits, retainers, client funds and holdbacks are kept apart from the business's own money, with the reconciliations that provincial regulators ask for. Rules differ by province and profession, so they are settings, not rewrites.
Pre-authorized debit for recurring amounts, Interac e-Transfer for everything else, cards where it makes sense, and electronic transfers to suppliers, with fees kept low on a typical small payment.
Canada's payment systems are moving to one international standard for payment messages. CitaLedger's records already use it, so nothing is lost when money moves or when a bank statement is matched.
Built to be hosted in Canada, with the privacy rules that apply to customer and client information designed in rather than bolted on.
How it compares
| What matters | General accounting software | A payment processor's dashboard | Building it yourself | CitaLedger |
|---|---|---|---|---|
| Lives inside your platform | No, a separate login | Partly, their branding and their rules | Yes | Yes, through one connection |
| Keeps proper books, not just a list of payments | Yes | No, it only sees its own transactions | If you get the accounting right | Yes, books that always balance |
| Keeps money held for others separate | Only with manual workarounds | No | Months of specialist work | Yes, by design |
| Collects, follows up and pays suppliers | Partly, often US-centric | Collects, with their fees; no follow-up or bills | A year of work and licensing questions | Through licensed Canadian providers, at cost |
| Works with the accountant's own software | It is the accountant's software | Exports, usually re-typed | Another integration to build | Clean monthly entries, no re-typing |
| Time to offer money features | Never, it stays separate | Weeks, for payments only | A year or more | Weeks, for the whole money flow |
Get started
Your developers can start today: the full technical reference is public.
Thirty minutes, your questions, no slides. Tell us your name and the platform you build, and we will reply within a business day.
Email hello@citaledger.comPrefer to start with the practice copy? Ask for a sandbox key in the same email.