--- title: Komplai uses one Truto API for ERPNext and QuickBooks slug: case-studies/komplai-truto description: Komplai calls the same Truto endpoints for ERPNext and QuickBooks Online. Truto had the ERPNext integration working for Komplai about 5 days after kickoff. canonical: https://truto.one/case-studies/komplai-truto/ --- # Komplai uses one Truto API for ERPNext and QuickBooks Truto had ERPNext working for Komplai about 5 days after kickoff. Komplai is an AI-powered accounting firm, and Truto gives its product the same endpoints for ERPNext and QuickBooks Online, with matching filters wherever QuickBooks has the same data. - **2** accounting systems behind one set of endpoints - **~5** days to ERPNext working on Truto - **12** requests delivered in under 4 hours > Also the MCP is super useful! Makes it so easy to work with the integration. > > — Anirudh Varma, Komplai (August 2026) ## Komplai at a glance - **Customer:** [Komplai](https://letskomplai.com/) - **What they do:** An AI-powered accounting firm: software that automates bookkeeping, an assistant that answers questions in real time, and a team that handles review, compliance and filings - **Truto products used:** The [unified accounting API](https://truto.one/unified-apis/accounting/), field mappings Komplai's engineers edit themselves, the Proxy API, the Link SDK and Truto's Platform MCP Server - **Accounting systems:** [ERPNext](https://truto.one/integrations/detail/erpnext/) and [QuickBooks Online](https://truto.one/integrations/detail/quickbooks/) - **Kickoff:** Dec 12, 2025 - **ERPNext working:** About 5 days after kickoff (Dec 17, 2025) - **QuickBooks Online:** Switched on Mar 9, 2026, then matched to ERPNext's filters and response fields where QuickBooks has them - **Requests in under 4 hours:** 12, from missing fields and filters to update support for QuickBooks journal entries and transfers ## How Truto worked with Komplai ### The challenge Komplai's product reads and writes accounting data: accounts, invoices, payments, journal entries and transactions. It started on ERPNext and wanted QuickBooks Online behind the same calls, so its own code would need no changes for a second accounting system. ### What Truto did Truto built the ERPNext integration for Komplai, then matched QuickBooks to it: the same account type filter, invoice type parameter and date filters, with matching response fields wherever QuickBooks has the same data. Komplai's engineers edit their own field mappings too, and ask for the rest in a shared Slack channel. ### The result Komplai calls one set of unified accounting endpoints for both systems. 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. ## From ERPNext to QuickBooks Timeline, Dec 2025 to Sep 2026. - **Dec 12, 2025:** Kickoff: Truto starts building the ERPNext integration for Komplai. - **Dec 17, 2025:** The ERPNext integration is working for Komplai. The same day, Truto confirms QuickBooks is on the same unified accounting API. (About 5 days in) - **Jan 5–23:** Truto adds the fields, filters and companies list Komplai asks for, and creates submitted ERPNext payments in one call. Komplai starts editing its own mappings. - **Mar 9, 2026:** QuickBooks Online is switched on for Komplai. - **Mar 13–17:** Truto matches QuickBooks to ERPNext on accounts, invoices and payments: the same filters and parameter names, with matching response fields wherever QuickBooks has the same data. - **Jul 10, 2026:** ERPNext's four date and last-modified filters arrive on QuickBooks invoices, expenses, payments and journal entries. - **Aug 25, 2026:** Updates to QuickBooks journal entries arrive about an hour after Komplai asks. Komplai starts using Truto's Platform MCP Server to work on its integration. - **Aug 27–Sep 3:** Updates to QuickBooks expenses, payments and transfers arrive, and one payment can be split across several invoices or bills. ## How fast Truto delivered Komplai's requests - **About 1 hour:** A sandbox option when connecting QuickBooks - **About 1 hour:** Update QuickBooks journal entries - **About 1 hour:** The same account type filter on QuickBooks as on ERPNext, so Komplai syncs its chart of accounts and bank accounts the same way for both - **Under 1 day:** ERPNext's four date and last-modified filters on QuickBooks invoices, expenses, payments and journal entries > we use the same api to use quickbooks as well > > — Ankur Prabhu, Komplai (July 2026, on ERPNext's filters for QuickBooks) ## Under the hood APIs, matching filters, writes and setup ### Unified accounting API - Accounts, invoices and bills, payments, journal entries, transactions, expenses and companies, for ERPNext and QuickBooks Online - Accounts filtered by `type` (`general_ledger` or `bank_account`) on both, with `current_balance` for ERPNext read from its `get_account_balances` method - `accounting/transaction-journals`: the debit and credit lines behind a QuickBooks invoice, bill or payment ### The same calls for both systems - `date_start`, `date_end`, `modified_at_start` and `modified_at_end` on QuickBooks invoices, expenses, payments and journal entries, as on ERPNext - `type` on invoices for both systems, contact names and credit and debit accounts in the response, and line items always returned as an array - Unified mapping overrides in Komplai's own environments, which Komplai's engineers edit themselves ### Writes - ERPNext records created as Submitted in one call, with `status: "Submitted"` - Updates for QuickBooks journal entries, expenses, payments and transfers, passing QuickBooks' `sync_token` where it asks for one - One payment allocated across several invoices or bills ### Setup - Truto's Link SDK, opened straight to ERPNext with `integration: 'erpnext'` - A sandbox option offered when connecting QuickBooks, for testing - ERPNext's timezone from System Settings through the Proxy API - Changes reach Komplai's development environment first, then its other environments once Komplai confirms - Truto's Platform MCP Server, which Komplai uses to work on its integration ## Questions about Komplai and Truto ### What does Komplai use Truto for? Komplai, an AI-powered accounting firm, uses Truto's unified accounting API to read and write accounting data in ERPNext and QuickBooks Online: accounts, invoices, payments, journal entries, transactions and expenses. Truto keeps the endpoints the same for both, with matching filters and response fields wherever QuickBooks has the same data, so Komplai's product calls the same endpoints for either system. ### How long did ERPNext take for Komplai? About 5 days. Truto kicked off the ERPNext integration for Komplai on Dec 12, 2025 and had it working for Komplai on Dec 17. In the weeks after, Truto added the fields and filters Komplai asked for, a companies list, and one-call creation of submitted ERPNext payments, many within hours. ### How does Komplai use one API for ERPNext and QuickBooks? 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. As Ankur Prabhu of Komplai put it, they use the same API for QuickBooks as well. ### Can Komplai change its unified mappings itself? Yes. When Komplai asked in January 2026 whether it could edit the unified mappings, Truto said it could at any time and walked the team through it on a call. Komplai's engineers edit the mappings in their own environments, and ask Truto in a shared Slack channel for anything bigger, such as a new endpoint. ## More customer stories - [Naq: Microsoft Intune in 5 days, and a new AWS API built from its brief](https://truto.one/case-studies/naq-truto/): Builds its compliance-evidence reads of users, devices and cloud accounts on Truto’s unified APIs, with Microsoft Intune live for its customers. - [Evergrowth: 6 CRMs live within a month of signing](https://truto.one/case-studies/evergrowth-truto/): Dynamics 365, HubSpot, Salesforce, Zoho CRM, Pipedrive and Attio through a single API, with each customer’s custom fields mapped both ways. - [Workweek: Salesforce Events in 16 hours, HubSpot diagnosed in 90 minutes](https://truto.one/case-studies/workweek-truto/): Is building CRM reporting for its B2B newsletter ad network on Truto’s unified CRM API, for Salesforce and HubSpot. - [15Five: 21 integrations live, the first three within a month](https://truto.one/case-studies/15five-truto/): Slack, Jira, Google Calendar and more feed 15Five’s AI features for managers, with a public launch about 3 months after kickoff.