Chapter 13: Finance Integrates Naturally |
13.1 The Two Languages of the Factory |
Every factory speaks two languages. The first is the language of operations: parts, machines, hours, kilograms, meters, shipments, and defects. The second is the language of finance: dollars, euros, yen, assets, liabilities, revenue, expenses, and profit. These two languages describe the same reality, but they use different words and different grammar. In many factories, the two languages are spoken by different departments that rarely talk to each other. The operations team manages production. The finance team manages the books. Each has its own data, its own systems, and its own version of the truth. |
This separation is expensive. When operations and finance do not share data, decisions are made with incomplete information. The plant manager might decide to increase production of a popular product, not realizing that the product's margins have eroded because raw material prices have risen. The finance manager might cut the maintenance budget to improve this quarter's profit, not realizing that the deferred maintenance will cause a breakdown that costs ten times the savings. The CFO might report a healthy profit, not realizing that the inventory on the balance sheet includes obsolete parts that will never be sold. |
An ERP system integrates finance with operations naturally. It does not force finance to learn operations, or operations to learn finance. It provides a common data model where a single transaction - a material issue, a labor hour, a shipment - creates the operational record and the financial record simultaneously. The two languages become one. This chapter explores how this integration works, why it is essential, and how it transforms both operational and financial management in a mechanical factory. |
|
13.2 The General Ledger - The Final Destination |
All financial transactions in an ERP system eventually flow to the general ledger. The general ledger is the master record of the company's financial position. It contains accounts for assets, liabilities, equity, revenue, and expenses. Every financial transaction is recorded as a journal entry that debits one account and credits another. |
In a non-integrated factory, the general ledger is updated manually. The accounting department receives paper documents - purchase orders, receiving reports, work order completions, shipping documents - and enters journal entries based on them. The process is slow, error-prone, and always behind. By the time the financial statements are produced, the data is weeks old. |
In an integrated ERP system, the general ledger is updated automatically. When a purchase order is created, no financial entry is made - the order is a commitment, not a transaction. But when the goods are received, the ERP creates a journal entry: debit inventory, credit accrued liabilities. When the supplier's invoice is matched, the ERP creates another entry: debit accrued liabilities, credit accounts payable. When the invoice is paid, the ERP creates a third entry: debit accounts payable, credit cash. Each of these entries is created automatically, based on the operational transactions recorded by the receiving clerk, the buyer, and the accounts payable clerk. |
Similarly, when a work order is completed, the ERP creates journal entries to move costs from work-in-progress inventory to finished goods inventory. When a shipment is made to a customer, the ERP creates entries to reduce finished goods inventory and to record revenue and cost of goods sold. When a machine breakdown triggers an emergency repair, the ERP creates an entry to record the maintenance expense. |
The result is that the general ledger is always current. At any moment, the CFO can see the company's financial position as of the last transaction. Month-end closing, which used to take two weeks, now takes two days. The time saved is not just clerical. It is time that finance can spend on analysis, planning, and decision support. |
|
13.3 The Automatic Journal Entry - Every Transaction Counts |
The heart of financial integration is the automatic journal entry. Every operational transaction in the ERP is configured to generate one or more journal entries. The configuration is done once, when the ERP is implemented. After that, the entries happen automatically, without human intervention. |
Consider a simple operational transaction: a worker issues raw steel to a work order. The worker scans the material lot number and the work order number. The ERP records that the material is no longer in raw material inventory; it is now part of work-in-progress. But the ERP also generates a journal entry. It debits the work-in-progress inventory account for the cost of the steel. It credits the raw material inventory account for the same amount. The total assets of the company do not change. The composition of assets changes. Steel that was sitting in a bin is now steel that is being machined. |
Now consider a more complex transaction: a worker completes a work order and moves the finished product to finished goods inventory. The ERP calculates the total cost of the work order: the sum of all material issues, all labor hours, and all allocated overhead. It then generates two journal entries. The first moves the cost from work-in-progress to finished goods: debit finished goods inventory, credit work-in-progress inventory. The second records any variances if standard costing is used: debit or credit variance accounts, with offsetting credits or debits to the inventory accounts. |
Now consider a shipment to a customer. The ERP records the reduction in finished goods inventory. It also records the revenue from the sale. The journal entry is: debit cost of goods sold, credit finished goods inventory for the cost of the product; and debit accounts receivable, credit revenue for the selling price. The difference between the selling price and the cost is the gross profit on that sale. |
Each of these journal entries is created automatically, in real time, from the operational data. No accountant touches them unless there is an error. The ERP does not eliminate the need for accountants. It eliminates the need for data entry. The accountants focus on analysis, control, and planning. |
|
13.4 Cost of Goods Sold - The Bridge Between Operations and Profit |
Cost of goods sold (COGS) is perhaps the most important financial metric for a manufacturing company. It is the direct cost of producing the products that were sold during a period. Revenue minus COGS equals gross profit. Gross profit minus operating expenses equals net profit. COGS is the bridge between operations and profitability. |
In a non-integrated factory, COGS is calculated after the fact, using estimates and allocations. The finance team might take the total cost of production for the month, add the beginning finished goods inventory, subtract the ending finished goods inventory, and assume that the difference is the cost of goods sold. This method is crude. It does not reflect the actual cost of the specific products sold. |
In an integrated ERP, COGS is calculated per shipment. When a shipment is recorded, the ERP knows exactly which finished products were shipped. It knows the cost of each product, either from standard costing or from actual costing. It multiplies the quantity shipped by the cost per unit and records that amount as COGS. The result is a COGS number that is precise, timely, and traceable to specific shipments. |
This precision is valuable for several reasons. First, it enables accurate profitability analysis by customer, by product, by order. The CFO can see which customers are most profitable, which products have the highest margins, and which orders lost money. Second, it enables accurate inventory valuation. The finished goods inventory balance is the sum of the costs of the products still on hand. Third, it enables accurate variance analysis. If COGS is higher than expected, the ERP can trace the increase to specific shipments and specific products. |
The precision of COGS depends on the accuracy of the underlying product costs. If the product costs are wrong, COGS will be wrong. This is why costing - Chapter 11 - is so important. Finance integration does not fix costing errors. It exposes them. |
|
13.5 Inventory Valuation - The Balance Sheet Asset |
Inventory appears on the balance sheet as a current asset. For a mechanical manufacturer, inventory is often the largest current asset. It includes raw materials, work-in-progress, finished goods, and spare parts. Getting inventory valuation right is essential for accurate financial reporting. |
In a non-integrated factory, inventory valuation is done periodically, usually at month end. The finance team takes the beginning inventory, adds purchases and production costs, subtracts shipments and material issues, and arrives at an ending inventory. This method is called periodic inventory. It is simple, but it provides no visibility during the month. |
In an integrated ERP, inventory valuation is perpetual. Every receipt, every issue, every completion, every shipment updates the inventory balances in real time. The ERP knows, at any moment, the quantity and value of every item in every location. The inventory balance on the balance sheet is the sum of these values. |
Perpetual inventory has several advantages. First, it enables real-time financial reporting. The CFO can produce a balance sheet at any time, not just at month end. Second, it enables better control. If inventory disappears, the ERP shows the loss immediately, not weeks later. Third, it enables more accurate costing. The ERP knows the cost of each item when it is used, not just an average over the period. |
The accuracy of perpetual inventory depends on the accuracy of the underlying transactions. If a worker issues material without recording the issue, the ERP will still show the material in inventory, and the inventory balance will be overstated. If a worker records an issue for the wrong material, the ERP will show the wrong item out of stock. Perpetual inventory does not replace physical inventory counts. It makes them more efficient, because discrepancies are identified and corrected promptly. |
|
13.6 Accounts Payable - The Three-Way Match Revisited |
We introduced the three-way match in Chapter 10. It is worth revisiting here because it is a critical financial control. The three-way match ensures that the factory pays only for goods that were ordered, received, and invoiced correctly. |
In a non-integrated factory, the three-way match is a manual process. The accounts payable clerk receives the supplier's invoice, finds the corresponding purchase order and receiving report, and compares them. The process is slow, and errors are common. The factory may pay for goods it never received, or pay a higher price than agreed. |
In an integrated ERP, the three-way match is automatic. When the receiving clerk scans the goods, the ERP creates an electronic receiving record. When the accounts payable clerk receives the supplier's invoice, they enter it into the ERP. The system compares the invoice to the purchase order and the receiving record. If all three match - same item, same quantity, same price - the system approves the invoice for payment. If there is a mismatch, the system flags the invoice for review. The accounts payable clerk investigates the discrepancy, contacts the supplier if needed, and then manually approves or rejects the invoice. |
The automatic three-way match is a powerful control. It prevents overpayment, duplicate payment, and payment for goods not received. It also speeds the payment process. Invoices that match automatically can be paid immediately. Only exceptions require human intervention. |
|
13.7 Accounts Receivable - From Shipment to Cash |
Accounts receivable is the mirror image of accounts payable. When the factory ships goods to a customer, it creates an invoice. The customer owes the factory money. That owed money is an asset - accounts receivable. When the customer pays, the cash is received, and the receivable is reduced. |
In a non-integrated factory, the accounts receivable process is often disconnected from shipping. The shipping department sends the goods. The billing department creates the invoice, often days later. The accounts receivable department applies payments to invoices, often with errors. The result is slow cash collection and high administrative cost. |
In an integrated ERP, the accounts receivable process is automated. When the shipping clerk records a shipment, the ERP automatically creates an invoice. The invoice is sent to the customer electronically. The ERP updates the customer's account balance. When the customer's payment arrives, the accounts receivable clerk enters the payment, and the ERP matches it to the open invoices. If the customer pays exactly the amount due, the match is automatic. If there is a discrepancy - a short payment, a disputed charge, a prompt payment discount - the system flags it for review. |
The integration between shipping and invoicing eliminates delays. The invoice is created at the moment of shipment, not days later. The customer receives the invoice sooner, and pays sooner. The factory's cash flow improves. The integration also reduces errors. The invoice is based on the same data as the shipment - the same quantities, the same part numbers, the same prices. There is no re-keying, and no opportunity for transcription errors. |
|
13.8 Fixed Assets - The Machines That Make the Parts |
Mechanical manufacturing requires expensive machines: lathes, mills, grinders, presses, furnaces, and measuring equipment. These machines are fixed assets. They appear on the balance sheet at their purchase cost, minus accumulated depreciation. Depreciation is the systematic allocation of the machine's cost over its useful life. |
In a non-integrated factory, fixed asset management is often a separate spreadsheet. The finance team tracks the purchase date, cost, useful life, and depreciation of each machine. When a machine is sold or scrapped, the spreadsheet is updated manually. The spreadsheet is rarely reconciled to the physical machines on the shop floor. |
In an integrated ERP, fixed assets are managed in the same system as inventory, purchasing, and maintenance. When the factory buys a new CNC machine, the purchasing module creates a purchase order. When the machine is received, the receiving module records it. The finance module creates a fixed asset record, with the purchase cost, useful life, and depreciation method. Each month, the ERP automatically calculates depreciation and creates the journal entry: debit depreciation expense, credit accumulated depreciation. |
When the maintenance module tracks repairs and overhauls, the ERP can determine whether the cost should be expensed as maintenance or capitalized as an improvement to the fixed asset. A major overhaul that extends the machine's life by five years should be capitalized. A minor repair that just keeps the machine running should be expensed. The ERP applies the factory's capitalization policy automatically, based on the dollar amount and the type of work. |
When a machine is sold or scrapped, the ERP calculates the gain or loss. The sale proceeds are compared to the net book value (cost minus accumulated depreciation). The difference is a gain or loss on disposal. The ERP creates the journal entry: debit cash for the proceeds, debit accumulated depreciation for the total depreciation taken, credit the fixed asset for the original cost, and credit or debit the gain or loss account. |
Fixed asset integration ensures that the balance sheet reflects the reality of the shop floor. The CFO can see, at any time, the net book value of every machine. The maintenance manager can see the depreciation history. The tax accountant can calculate depreciation for tax purposes separately from book depreciation. The system handles the complexity, leaving the people to focus on the decisions. |
|
13.9 Month-End Closing - From Two Weeks to Two Days |
Month-end closing is the process of finalizing the financial records for a period. In a non-integrated factory, closing is a mad rush. The operations team provides production data. The purchasing team provides receiving data. The inventory team provides count adjustments. The finance team reconciles everything, makes adjusting entries, and produces financial statements. The process can take two weeks or more. During that time, the financial data is frozen, and decisions are made based on old information. |
In an integrated ERP, month-end closing is fast and painless. The operational data is already in the system, and the financial entries are already made. The finance team's job is to review, not to enter. They run reports to check for unusual transactions. They investigate and correct any errors. They make a few adjusting entries for items that are not captured operationally, such as prepaid expenses or accrued interest. Then they close the period. The entire process takes two days, not two weeks. |
The speed of closing has several benefits. First, it frees finance staff for higher-value work: analysis, planning, and decision support. Second, it provides management with timely information. Decisions are made based on data that is weeks fresher. Third, it reduces the risk of errors. The fewer manual entries, the fewer opportunities for mistakes. |
The key to fast closing is integration. If the operational data is already in the ERP, and the financial entries are already made, closing is just a matter of review. If the finance team is still re-entering data from paper, closing will always be slow. |
|
13.10 Real-World Example: The Valve Manufacturer's Financial Transformation |
Consider a manufacturer of industrial valves. The company had grown rapidly, acquiring several smaller competitors. Each acquired company had its own systems - different ERPs, different spreadsheets, different processes. The corporate finance team struggled to consolidate financial results. Month-end closing took four weeks. The CFO never had a clear picture of the company's profitability by product line or by customer. |
The company implemented a single, integrated ERP across all locations. The implementation was painful. Data had to be cleaned and standardized. Processes had to be re-engineered. Employees had to be trained. But the results were worth the pain. |
For the first time, the finance team could see the company's financial position in real time. When a shipment was made in one factory, the corporate balance sheet updated instantly. When a purchase order was received in another factory, the accounts payable accrual updated automatically. Month-end closing dropped from four weeks to three days. |
The real transformation was in management reporting. The CFO could now produce a profitability report by product line, showing revenue, cost of goods sold, and gross margin for each valve type. The report revealed that the company's highest-volume product line was actually its lowest-margin, because the production process was inefficient. The company invested in new equipment for that product line, and margins improved. |
The CFO could also produce a profitability report by customer. The report showed that one large customer, who received volume discounts, was actually unprofitable because of high return rates and demanding delivery requirements. The company renegotiated the contract, and the customer accepted higher prices in exchange for better service. The account became profitable. |
The CFO could also produce a working capital report, showing inventory days, accounts receivable days, and accounts payable days. The report revealed that the company was holding excessive inventory of slow-moving parts. The operations team reduced the inventory, freeing up cash. |
The finance team's role changed. They were no longer bookkeepers, entering data and reconciling accounts. They became business partners, providing analysis and insights to operations. The ERP did not replace the finance team. It elevated them. |
|
13.11 The Human Factor - Finance as a Partner, Not a Police |
In many factories, the finance department is seen as a police force. They enforce rules, question expenses, and slow down decisions. This perception is often deserved. When finance is disconnected from operations, they have no choice but to be reactive and controlling. |
In an integrated ERP, finance can become a partner. They have the same data as operations. They can see the same realities. They can ask questions that are informed, not suspicious. When a production manager requests a capital expenditure for a new machine, the finance manager can see the machine's expected return on investment, the impact on working capital, and the tax implications. They can have a productive conversation, not an adversarial one. |
The shift from police to partner requires a change in mindset. Finance must see their role as enabling the business, not controlling it. Operations must see finance as a resource, not an obstacle. The ERP provides the common platform. The people must provide the trust. |
|
13.12 Summary: One Reality, One System, One Truth |
Finance and operations describe the same reality. The parts on the shop floor are the same parts on the balance sheet. The labor hours recorded by the machinist are the same labor hours that drive payroll expense. The shipment to the customer is the same transaction that creates revenue and accounts receivable. |
When finance and operations are separate, reality is described twice, in two different languages, with two different sets of numbers. Reconciliation is a constant struggle. Trust is low. Decisions are made with incomplete information. |
When finance and operations are integrated in a single ERP, reality is described once. The operational transaction creates the financial entry. The general ledger is always current. The balance sheet reflects the shop floor. The income statement reflects the shipments. The cash flow reflects the receipts and payments. There is one reality, one system, one truth. |
Integration does not eliminate the need for financial expertise. It amplifies it. The finance team is freed from data entry and reconciliation. They can focus on analysis, planning, and decision support. They can be partners to operations, not police. They can help the factory make more money, not just count it. |
In the next chapter, we will explore how the ERP manages the human resources of the factory - the skills, training, and schedules of the people who make everything possible. Labor is not just a cost to be allocated. It is a resource to be developed. And the ERP has powerful tools for that development. |
|
Key takeaways from Chapter 13 (expanded without formulas or tables): |
1. Finance and operations speak two different languages describing the same reality - integration aligns them into one truth. |
2. The general ledger is the final destination for all financial transactions - in an integrated ERP, it is updated automatically from operational transactions. |
3. Automatic journal entries are created from every operational transaction - material issues, work order completions, shipments, receipts. |
4. Cost of goods sold (COGS) is calculated per shipment, enabling precise profitability analysis by customer, product, and order. |
5. Inventory valuation is perpetual - every receipt and issue updates the balance sheet in real time. |
6. Accounts payable uses automatic three-way matching (purchase order, receiving record, invoice) to prevent overpayment and errors. |
7. Accounts receivable is integrated with shipping - invoices are created automatically at the moment of shipment. |
8. Fixed assets are managed in the same system - depreciation is calculated automatically, and disposals are recorded with gain or loss calculation. |
9. Month-end closing drops from weeks to days - the finance team reviews rather than enters data. |
10. Real-world examples show that integration transforms finance from bookkeeping to business partnership. |
11. The human factor is critical - finance must shift from a policing mindset to a partnering mindset, enabled by shared data and trust. |
cs@easiersoft.com