Product Costing and Variance Analysis

The problem: you know the total variance, not what caused it

SAP Business One will tell you that a Production Order finished with a difference between the value of the components issued plus resource time booked, and the value of the finished goods received. What it will not tell you, in any structured way, is how much of that difference came from paying more for a raw material, how much from using more of it than the Bill of Materials said, how much from an operation taking longer than its routing standard, and how much from an overhead rate that no longer reflects reality.

So the month-end conversation goes in circles. The cost accountant exports Production Orders to a spreadsheet, joins them against item costs and a hand-maintained rate table, and rebuilds the analysis every period. The standard cost itself lives partly in the Item Master, partly in a workbook, and partly in someone's head. Overhead is applied as a flat percentage, if it is applied at all, because SAP B1 has no absorption engine and Resources carry a single cost rate rather than a rate structure separating labour from machine from burden.

Multi-level Bills of Materials make it worse. A cost change on a purchased component three levels down should ripple up through every parent, but a manual roll-up means it does so late, incompletely, or never.

What ECOSIRE builds

ECOSIRE builds a product costing and variance analysis add-on for your SAP Business One installation. It is built to order against your BOM structure, your cost element definitions and your overhead pools, not downloaded from a shelf. We scope it, quote a fixed price, build it, and install it into your test company database and then production.

Multi-level standard cost roll-up

A roll-up engine walks your Bill of Materials structures from the lowest level upward, resolving phantom and subassembly levels, and produces a standard cost per item broken into cost elements: purchased material, direct labour, machine time, subcontracting, and absorbed overhead. Roll-ups run against a named cost version, so you can hold last year's frozen standard, this year's live standard, and a simulation version side by side. Results are stored in User Defined Tables keyed by item, version and cost element, with User Defined Fields on the Item Master exposing the current standard for quick reference.

Cost versions and simulation

Before you commit a new standard, you can copy the current version, apply changes at the leaf level, whether that is a supplier price increase, a new labour rate or a revised overhead rate, and re-roll. A comparison view shows every item whose cost moved, the element that moved it, and the value of on-hand inventory affected. Committing a version writes the new standard cost to the items you nominate and records who changed what, when.

Overhead absorption

Overhead pools are defined with a basis you choose: machine hours, labour hours, material value, or units produced. Rates are held per pool per cost version and applied during roll-up and again during work order settlement, so absorbed overhead appears as its own cost element rather than being buried in a resource rate. Under- and over-absorption is calculated per period against the actual pool spend you enter or derive from the general ledger, which is the number that reconciles your product costing back to your Profit and Loss.

Work order variance analysis

For each Production Order, the add-on decomposes total variance into named components: material price variance from the difference between standard and actual purchase cost, material usage variance from the difference between BOM quantity and issued quantity, labour and machine rate variance, labour and machine efficiency variance against routing standard times, overhead absorption variance, scrap variance, and yield variance. Each figure is traceable back to the underlying Goods Issue, Receipt from Production and Resource booking lines, so an accountant can click from a number to the transaction that created it.

Journal posting and reconciliation

Where you want variances posted rather than only reported, the add-on creates Journal Entries at work order settlement against the variance accounts you nominate, using the SAP Business One Service Layer. Postings can be routed through a standard approval procedure before they hit the ledger. A reconciliation view ties the sum of posted variances back to the Production Order value difference so nothing goes missing between the shop floor and the general ledger.

Reporting

Crystal Reports layouts cover the standard cost sheet per item showing every element and every level, the work order variance report with the full decomposition, period variance summaries by product family or work centre, and the cost version comparison. Data is also exposed through User Defined Objects so it is queryable from SAP B1 query tools and available to your existing reporting stack.

Built on supported SAP B1 extensibility

The add-on posts through the Service Layer REST API and the DI API, extends master data with User Defined Fields on Items, Bills of Materials, Resources and Production Orders, and holds its own data in User Defined Tables and User Defined Objects so it inherits SAP Business One authorisations and can participate in approval procedures. No direct SQL writes to SAP tables, which keeps the installation supportable across upgrades.

Who this is for

Manufacturers on SAP Business One who maintain Bills of Materials and routings, carry meaningful overhead, and need a defensible product cost. It is aimed at businesses where the cost accountant currently rebuilds the analysis in Excel every month, where multi-level BOMs make manual roll-up impractical, and where management asks why margin moved and expects an answer with a cause attached.

How delivery works

Scoping call. We review your BOM depth and structure, your routings and resource rates, how you currently define standard cost, which overhead pools exist and on what basis they should absorb, which variance categories your finance team reports, and whether you want variances posted to the ledger or reported only. We confirm your chart of accounts treatment for variance accounts.

Fixed quote. You receive a written scope and a fixed price covering the roll-up engine, the cost element and version model, the overhead pools in scope, the variance decomposition, any journal posting, and the report set. Work outside that scope is quoted before it is built.

Build. ECOSIRE develops against your SAP Business One version and database platform. Typical lead time is two to four weeks from confirmed scope.

Install in test. We install into your test company database, load your cost versions and overhead rates, and run a parallel period against your existing spreadsheet so finance can reconcile line by line before trusting the system. You sign off in test.

Install in production. We install into the live company database in a scheduled window and set the opening cost version.

Support. A support window from go-live covers defects and configuration questions, with the first period close supported directly. Extended support and enhancements are quoted separately.