Konkat and ERPNext
How Konkat lives next to ERPNext on the same site: separate data, no accounting or stock postings, no sync, and what that means for your accounts team.
On this page
Many builders already run ERPNext for accounts, payroll or GST. Konkat can be installed on the same Frappe site, but it is a separate app: it keeps all its own records and does not change anything in ERPNext. This article explains what that means in practice.
Konkat does not need ERPNext#
Konkat only requires Frappe v15. It works on a bench with ERPNext or without it. Installing or removing ERPNext doesn’t change how Konkat works, and Konkat does not add fields, scripts or hooks to any ERPNext screen.
Separate data#
Everything Konkat records is stored in its own document types, all named “Konkat …” — for example Konkat Project, Konkat Task, Konkat Daily Log, Konkat Stock Entry, Konkat Purchase Order, Konkat Payment, Konkat Booking and Konkat Complaint.
| In Konkat | Effect in ERPNext |
|---|---|
| Projects and tasks | None. ERPNext’s own Project and Task are not used or changed. |
| Materials, stores, stock in / used / transfers | None. No Stock Ledger Entry, no change to ERPNext Items or Warehouses. |
| Suppliers & subcontractors | None. Konkat keeps its own list; ERPNext Suppliers are not read or created. |
| Purchase orders and deliveries | None. No ERPNext Purchase Order, Purchase Receipt or Purchase Invoice is made. |
| Payments made and received | None. No Payment Entry, no Journal Entry, no GL Entry. |
| Leads, bookings, customer payments | None. ERPNext CRM Leads, Customers and Sales Orders are not touched. |
| Complaints | None. ERPNext Issues and Warranty Claims are separate. |
There is no automatic sync in either direction.
What this means for your accounts team#
- Konkat is the site and project record — what was ordered, received, used, paid and booked, project by project, with the money summary for a quick picture.
- Your books stay where they are — keep entering supplier bills, payments, GST and customer receipts in ERPNext (or Tally, or whatever you use) as you do today. Konkat’s payments are not posted to any ledger.
- Use Konkat to check bills — compare a supplier’s bill with the Konkat purchase order and its deliveries (challan numbers) before you pass it in your accounts.
Because nothing is synced, a payment recorded in Konkat must also be entered in your accounting system, and vice versa, if you want both to be complete. Decide who records what, and where, when you start.
Users and roles#
- People you add from Konkat’s People screen get one Frappe role: Konkat User. They do not need any ERPNext role, and Konkat gives them none.
- The Konkat User role has no permissions on desk document types, except reading drawings, drawing folders and photos of their own projects. Everything else goes through Konkat’s own screens at
/konkat, where every action is checked against the person’s role on that project. - An existing ERPNext user (for example your accountant) can also use Konkat. An owner adds them in Konkat’s People screen; they keep their ERPNext roles and get the Konkat User role added.
- Even a Frappe System Manager sees Konkat records only for projects they are on the Team of. Only the built-in Administrator account sees every project.
See Security and access for the full rules.
Backups and updates#
Konkat data lives in the same site database as ERPNext, so the normal site backup covers both. Updating ERPNext within v15 doesn’t affect Konkat; update Konkat separately as described in Updating Konkat.
Common questions#
Can Konkat purchase orders create ERPNext purchase orders?#
No. There is no link between the two. Use Konkat’s Print / PDF to send orders, and enter bills in your accounts as usual.
Will Konkat stock show in ERPNext stock reports?#
No. Konkat stock is shown only in Konkat’s Stock screens.
Can I uninstall ERPNext later and keep Konkat?#
Konkat doesn’t depend on ERPNext. Treat any uninstall as a major change: take a full backup first.