The use case: how Komplai deploys Truto
Komplai, an AI-powered accounting firm, uses Truto's unified accounting API to read and write accounting data in ERPNext and QuickBooks Online through one set of endpoints, so its product needs no code changes per accounting system.
More reported results
Figures published in Truto’s case study. They are not independently measured by usedby.
Truto delivered 12 of its requests in under 4 hours, and update support for QuickBooks journal entries, expenses, payments and transfers in August and September 2026.
In the customer’s words
Also the MCP is super useful! Makes it so easy to work with the integration.Other companies using Truto
Customers across industries, with public evidence.
See all Truto customers
Go straight to the source
Based on Truto’s published case study. We check the public evidence; the results are reported by the vendor.
truto.one- Source published
- Oct 15, 2026
- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 5 daysChecked
Printed word for word on the page, near the name of Komplai.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Komplai.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Komplai uses TrutoChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Komplai built on ERPNext first, then asked for QuickBooks Online behind the same calls. Truto matched QuickBooks to ERPNext: the same account type filter, the same type parameter on invoices, the same four date and last-modified filters, and matching response fields wherever QuickBooks has the same data.