Case Study: BOM, Labor Hours, and Double-Entry Books in One Core Business System

For a manufacturer, product cost is never a single number on a spreadsheet. It is the sum of materials consumed, hours worked, scrap written off, and the ledger entries that describe each of those actions. When those pieces live in different systems, the cost on the income statement is a guess dressed up as a fact. This case study follows one type of company, a textile-machinery maker in Osaka with roughly 150 staff, as it brought the shop floor and the general ledger into one core business system.

A Real-World Scenario

The firm designs and assembles loom components, sourcing steel, bearings, and electronic controllers from a network of regional suppliers. About 150 people work across engineering, assembly, quality, sales, and a lean back office.

For years the company ran operations on three loosely connected tools. An engineer maintained the bill of materials (BOM) in one application, tracking each sub-assembly down to the screw. Supervisors captured labor hours on paper timesheets, then handed them to accounting a week later. The accounting team posted journal entries in a separate double-entry ledger, often rekeying material and labor figures by hand.

The result was predictable. The cost of a finished machine on the books bore little resemblance to what it actually cost to build. Material price changes from suppliers arrived in the ledger a month late. Labor hours for overtime shifts were rounded or dropped. Scrap was written down as a vague adjustment at month end. When leadership asked for the true margin on a flagship product, the answer took two weeks and still came with a footnote.

The turning point came after a lost bid on a large export order. The sales team had priced aggressively, assuming the existing cost figure was accurate. A post-mortem revealed the real cost had been understated by nearly nine percent, almost entirely because supplier price increases and recent overtime had never reached the ledger in time. The board approved a search for a single core business system that could tie manufacturing to accounting.

The Problem Behind It

The root cause was never the people. The accounting team was disciplined, the supervisors were meticulous, and the engineers kept accurate component lists. The problem was architecture: three separate sources of truth, each updated on its own clock, reconciled by hand under deadline pressure.

Three failures recurred.

First, the bill of materials drifted from reality. Engineering changed a bearing supplier, but purchasing still ordered against the old specification, and accounting costed the assembly at the old price. Multi-level BOMs amplified the error, because a small change on a sub-assembly propagated silently into every finished machine.

Second, labor hours arrived too late to matter. A timesheet filled on Friday was entered into the cost system the following Wednesday, and reached the general ledger during the next monthly close. By then the period was closed and the variance became an unsolvable mystery.

Third, the journal entries never tied back to the physical events. A consumption of raw steel, a scrap write-off of castings, and an overtime premium each landed in the ledger as a manual line, detached from the inventory movement or the manufacturing order that caused it. When auditors asked for the trail behind a cost figure, the answer was a stack of printouts.

This is the quiet crisis of the divided system. Each individual tool works. The connection between them does not. For a manufacturer, the connection is where the truth lives.

What Changes

The company moved to a single core business system where the bill of materials, manufacturing orders, labor hours, and double-entry books all live together as one source of truth, replacing the three spreadsheets that used to hold them apart. The shift did not auto-connect everything. It put everything in one place and changed four things.

The bill of materials became a live structure rather than a static document. Multi-level BOMs are defined once, and each manufacturing order draws materials against them, deducting raw materials automatically on completion. When engineering changes a component, the change is visible to purchasing, inventory, and costing in the same motion. Inventory movements, including consumption and scrap, are recorded as typed operations that live alongside the books in one system, so the full picture is in one place. Scrap is no longer a vague month-end adjustment but a distinct stock-out operation that is captured as it happens. Tying that scrap to a specific general-ledger account is a manual journal entry, confirmed with your accountant.

Labor hours became part of the cost record from the day they were worked. Timesheet and attendance entries capture hours against each job or project, so the data sits alongside the manufacturing order and the double-entry books in one system rather than on a separate paper trail. The system captures the hours; it does not automatically push a labor cost onto a manufacturing order or into the ledger. The true product cost is assembled by combining the materials the manufacturing order already consumed, the labor the timesheet already captured, and a manual journal entry that connects the labor to the right cost account, confirmed with the accountant. Overtime hours, previously invisible until close, are visible in the same period the work was done.

The general ledger stopped being a destination for hand-typed summaries and became the natural output of some of the commercial documents that drive the books. Every sales invoice generates its own sales journal entry, every purchase bill generates its own bill entry, and every expense reimbursement generates its own entry, each with entry-type validation built in. Operational events such as a consumption of material, a scrap write-off, or a labor charge are recorded in the same system as the books, so the shop floor and the ledger describe one shared reality, but they do not automatically post to the general ledger. Connecting any operational event to a specific general-ledger account is a deliberate manual journal entry confirmed with your accountant.

Closing became disciplined rather than heroic. Closing schedules define each period, and a closing run locks a clean set of figures for that window. Invoices and bills tie to the run, so the period's sales and purchase figures reconcile without a weekend of manual work. The labor-to-cost and operational-to-ledger connections remain manual entries, but because the source figures all sit in one system, reconciling them is a matter of confirming numbers that are already in one place rather than hunting across three spreadsheets.

The qualified-invoice system, in effect since October 2023, added another reason to want one core business system. Under the revised transitional schedule set by the 2026 tax reform, the input tax credit on invoices from exempt suppliers steps down: 70 percent from October 2026 to September 2028, then 50 percent, then 30 percent, then zero from October 2031. A manufacturer that cannot match purchase bills to consumption and the right tax account faces a reconciliation headache that worsens every year. A core business system that stores each company's qualified-invoice registration number, keeps each partner's registration number, and applies the correct tax account per line turns that headache into a routine entry.

Why This Matters Now

The timing of this renewal is not accidental. Many Japanese manufacturers are revisiting their core business systems at the same moment. Windows Server 2012 R2, SQL Server 2014, and a generation of on-premise ERP platforms have reached the end of security support, creating a legacy cliff that makes standing still riskier than moving. METI has framed the 2025 legacy problem around a widely cited figure of roughly 12 trillion yen of potential economic impact, a scale that has pushed even conservative firms to act.

Two other forces compound the pressure. The labor shortage makes manual reconciliation an increasingly expensive luxury, because the people who hold the tribal knowledge of the old spreadsheets are the hardest to replace. The SME succession problem means owners planning a handover or a sale need systems an outsider, an auditor, or a buyer can trust. A divided system held together by one veteran's memory is an asset no acquirer will pay for.

For a manufacturer specifically, the cost-of-goods question is the heart of the matter. A core business system that holds BOM, manufacturing orders, timesheet labor hours, and the general ledger in one place does more than speed up the monthly close, which for many Japanese SMEs still takes one to two weeks. It changes what the close proves. Instead of a cost reconstructed after the fact from scattered spreadsheets, the close reports a cost assembled from figures that already sit in one system: materials consumed from the manufacturing order, labor captured in the timesheet, and a manual journal entry, agreed with the accountant, that connects the labor to product cost.

Budget vs actual discipline also becomes possible. With budgets set per department, usage tracking, and variance notifications routed to the right managers, a manufacturer can see in near real time when material consumption, labor spend, or scrap drifts past plan. That early signal is worth more than any after-the-fact report.

Common Objections

The board raised the usual objections before approving the move. Each deserved a direct answer.

Our spreadsheets work fine. Why rip them out?

Spreadsheets compute accurately, but they do not sit together. A bill of materials in one file, labor hours on paper, and journal entries in a separate ledger are three sources of truth that reconcile only through human effort. The Osaka maker's spreadsheets were correct in isolation and wrong in aggregate, the exact failure mode that lost the export bid. A single core business system does not replace calculation; it replaces the manual bridges between calculations, puts every figure in one place, and timestamps every change so the trail is auditable.

We cannot afford the disruption of a big ERP project.

The disruption of a divided system is already being paid, just in a less visible currency: lost margins, late supplier price updates, overtime that misses the period, and a monthly close that absorbs accounting for days. A fit-to-standard implementation, where company settings, business partners, products, BOMs, tax rates, and payment terms are configured rather than coded, keeps the project bounded. The goal is not to replicate every spreadsheet quirk but to adopt a clean standard.

Will the auditors and our tax accountant accept it?

Yes, and they usually prefer it. Double-entry bookkeeping is the foundation, and the commercial documents that do post automatically to the ledger, namely sales invoices, purchase bills, and expense reimbursements, each produce a typed journal entry with an audit trail of who changed what and when. Operational events such as material consumption, scrap, and labor hours are captured alongside the books in the same auditable system, and the link from those operational events to a general-ledger account is a deliberate manual journal entry confirmed with the accountant. Role-based access, passwordless passkey login, two-factor authentication, and the ability to restrict login to the office network give the internal control posture that J-SOX-conscious firms look for. The system structures the data cleanly for the tax accountant's final tax return, while leaving government submissions and the formal electronic-bookkeeping certification to the professionals who own them.

Frequently Asked Questions

Do we still need spreadsheets if the system holds BOM, labor hours, and the books in one place?

Spreadsheets compute accurately, but they do not sit together. A single core business system does not replace calculation, it replaces the manual bridges between calculations. Every figure sits in one place and every change is timestamped, so the trail is auditable rather than reconstructed at month-end.

Does the system automatically post labor cost into product cost?

No, and that is deliberate. The system captures labor hours in the timesheet and materials consumption in the manufacturing order, but connecting labor to a specific cost account is a manual journal entry confirmed with the accountant. That keeps the books under accounting control while removing the rekeying and the late variance.

Will auditors and our tax accountant accept this setup?

Yes, and they usually prefer it. The commercial documents that do post automatically, namely sales invoices, purchase bills, and expense reimbursements, each produce a typed journal entry with an audit trail. Operational events such as consumption, scrap, and labor are captured alongside the books in one auditable system, with role-based access and passkey login supporting internal controls.

Is this only practical for large manufacturers?

No. The Osaka maker in this case study runs about 150 staff, and the model scales down to smaller discrete manufacturers running bills of materials and manufacturing orders. You can model your own BOM and run the books end to end on Kikan System free with up to 2 users and no credit card, before committing to a full rollout.

Key Takeaway

The lesson from this Osaka manufacturer is narrow and practical. True product cost is not found by improving any one of BOM, labor hours, or bookkeeping in isolation. It emerges only when all three live in one system, in the same period, so they can be assembled into a single defensible number. Material cost flows from the manufacturing order, labor cost is captured in the timesheet, and a manual journal entry, agreed with the accountant, connects the labor to product cost. Reconciliation shrinks and month-end gets faster because every source figure already sits in one system, not because every connection is automatic. For a manufacturer facing the 2025 legacy cliff, the qualified-invoice transition, and a shrinking workforce, a single core business system is the difference between a cost figure you can defend and one you can only explain away.

Kikan System is built on exactly this foundation: double-entry bookkeeping at the core, multi-level BOMs and manufacturing orders that consume materials, timesheet-captured labor hours, typed inventory operations including scrap, all living alongside the general ledger in one system, plus configurable per-company tax settings and closing runs that lock a clean period. The labor-to-cost and operational-to-ledger links stay manual, but the figures behind them are already in one place. If you want to see how one core business system would handle your BOM, labor hours, and ledger, the fastest way is to try it.

See it for yourself

Start a free workspace on Kikan System today. Up to 2 users, no credit card required, and you can model your own bill of materials and run the books end to end.

(-> Start free)(/#get-started)

If you are still weighing cloud versus on-premise, our comparison of cloud ERP versus on-premise for SMEs and our guide to writing a core business system RFP walk through the decision.