Controllers running ERPNext hit the same wall every month-end: the platform records Cost Center on every GL Entry and lets you tag Project on transactions, but it stops well short of telling you whether a given project or job actually made money. Native ERPNext gives you a Profit and Loss statement filtered by one dimension at a time and a basic Project profitability view driven off Timesheets and Sales/Purchase totals. It does not model committed costs (open POs and unbilled subcontract work), it has no engine to allocate shared overhead down to the jobs that consumed it, and it cannot slice a true P&L simultaneously by cost center, project, department, and a custom dimension. So the analysis migrates into spreadsheets — GL exports pivoted by hand, overhead spread with a guessed percentage, and margins that are already stale by the time the board sees them. This is exactly where ERPNext native runs out of road.

ECOSIRE builds a proper Frappe app — a real app in your bench, not a stack of client scripts — that layers a multi-dimensional profitability engine on top of your existing General Ledger. We lean on ERPNext's own Accounting Dimension framework so every posting already carries Cost Center, Project, and any custom dimensions you define, then add DocTypes that the core lacks: an Overhead Allocation Rule (define a source cost pool, a driver — headcount, machine hours, direct labour, revenue share — and the target dimensions), an Allocation Run that executes a rule set for a period and writes auditable Allocation Entry lines, and a Project Profitability Snapshot that freezes committed, actual, and recognised figures at a point in time. Committed cost is computed by reading open Purchase Order and Subcontracting Order balances and unbilled Purchase Receipt values against each dimension, so a project manager sees the margin after everything already ordered — not just what has been invoiced.

Technically, the reporting is delivered as ERPNext Query Reports and script-report Python that query GL Entry grouped across multiple dimensions in a single pass, plus Insights/Number Card dashboards for margin-by-dimension, top and bottom jobs, and overhead-load trends. Revenue recognition and Work-in-Progress are supported through the standard ERPNext WIP and deferred-revenue accounts: the app posts and reverses WIP Journal Entry documents on a scheduler_events hook so period-end WIP and percent-complete recognition are automatic and reversible, never a manual paste. Doc events in hooks.py (on Sales Invoice, Purchase Invoice, Journal Entry, Timesheet, Stock Entry) keep snapshots and committed-cost figures live as transactions post. A whitelisted method layer exposes the profitability data over the Frappe REST API so Power BI, a data warehouse, or an external FP&A tool can pull the same numbers finance sees. Client Scripts add a "Profitability" action and a committed-vs-actual banner to the Project form; permission rules and a dedicated Role Profile keep allocation rules and margin dashboards restricted to Accounts Manager, Controller, and System Manager. Everything targets Frappe/ERPNext v15 and is forward-checked for v16.

Because this is build-to-order, nothing is downloaded and dropped onto your site blind. We start with a scoping call to map your cost-center tree, the dimensions you actually report on, and how you want overhead driven and revenue recognised. We build the app against a spec you approve, deploy and test it on a staging bench, run UAT with your finance team using your real chart of accounts, and only then install on production with a rollback plan. Typical delivery is one working week from confirmed scope depending on the number of allocation rules and dimensions, and you receive the full source in a git repository you own, plus a support window after go-live. There is no instant download — you get software built for your ledger and a team that installed it.