AKC — Contracts, HR & Accounting ERP

Overview

Individual, company, association and chalet contracts with offers and payments; journal entries and chart of accounts; vehicle fleet with faults and fuel; payroll, loans, penalties and leave.

01The challenge

The client sells the same service four different ways, each with its own rules: individual contracts priced per visit, company contracts per building, association contracts per unit with a recurring split invoice, and chalets seasonally. Forcing them into a single contracts table would have produced a table half of whose columns are always empty.

On top of that, every fault report runs a chain — intake, technician assignment, site visit, spare parts, customer rating — and each step creates a financial obligation that must reach both the ledger and the technician’s monthly statement.

02What we built

We split each contract type into its own table, screens and pricing logic, with a shared layer for payments, notes and price offers. Fields stayed meaningful, and no type had to work around another type’s constraints.

The finance side runs on a real chart of accounts and journal entries, with an account-mapping layer that decides which account receives which movement — so invoices, extracts, salaries and fuel all post their entries automatically. Balance sheet, profit and loss, customer/supplier/employee statements and trial balance are all derived from there.

Because technicians work on site, they got their own API: today’s jobs, photo and invoice upload from the field, notes, and live location tracking — with real-time push over WebSockets and Firebase.

03The outcome

The four contract types are now run from one system without any of them being forced into another’s mould, and recurring association invoices are issued and split across units automatically instead of being recalculated by hand every month.

The financial side closes: every field cost — a spare part, fuel, a loan, a penalty — has its entry and its account, so any customer, employee or supplier statement is ready on demand instead of being assembled from scattered files.