By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
Batch manufacturer accounting tracks the full cost of each production run, including materials, labor, setup and overhead, and carries unfinished batches as work in process until they become finished goods. An ERP supports it when production records post to the ledger finance closes, so month-end inventory valuation ties to the balance sheet.
This guide covers how batch costing works, how NetSuite records it, what tends to go wrong after go-live and how to make the case for a system to your leadership team.
What is batch manufacturer accounting and finance?
Batch manufacturers produce groups of identical products that move through production stages together before the next batch starts. A craft brewery brews, ferments, filters and packages one recipe before cleaning the tanks for the next. Continuous flow manufacturing, such as a refinery, runs around the clock without a start and finish for each lot. That difference sets the accounting job: a batch has a beginning and an end, so its cost can be collected and compared with the next batch of the same product.
Accounting for it means assigning materials, labor, setup time and overhead to each run, valuing the batch while it is still in progress and releasing the cost to cost of goods sold when the product ships. “Batch processing” also describes posting groups of transactions together in accounting software. This guide is about the manufacturing meaning.
What is a batch manufacturing system?
A batch manufacturing system is software that manages recipes or bills of materials, schedules production in discrete runs, tracks lots, and costs each run. In an ERP those functions share records with finance, so an item received, a batch produced and a unit shipped each update the same inventory and ledger accounts. Three capabilities carry most of the weight for accounting:
- Lot and batch tracking, so each run has an identifier that follows it through inventory and shipment.
- Work in process records, so the cost of a partly finished batch sits on the balance sheet at a defined value.
- Costing that matches the way the plant works, so a batch’s cost reflects what was consumed and what the item’s costing method says it is worth.
How do batch cycles change the books?
Four features of batch production create decisions for the accounting team, and each one is better settled before go-live than after.
- Setup and changeover costs. Cleaning, reconfiguring and testing equipment between recipes costs money and produces nothing. Decide whether those costs sit in overhead or attach to the batch that follows, because the choice changes product profitability.
- Idle time. Machines and people waiting during a changeover raise the same question: overhead or a specific batch.
- Quality testing. Tests at several points in a run protect customers and add cost that has to be assigned to the batch.
- Lot traceability. Each batch needs a unique identifier that follows it through production, inventory and distribution, which supports quality control and recalls.
Spreading fixed setup costs over a larger batch lowers the setup cost per unit, which is one reason plants run larger batches. The accounting question is whether the system shows the true cost of a small batch next to the cost of a large one.
How does NetSuite account for work in process in batch production?
Oracle’s Manufacturing WIP documentation describes three records that track a work order through production:
- Work order issue: moves raw materials to an assembly area.
- Work order completion: assembles the materials and stocks the finished goods.
- Work order close: reconciles variances.
To use them you enable the WIP feature, set up items as WIP assemblies, set default WIP accounts and identify a WIP location, which has to match across the three transactions. A two-stage product shows how this works: ingredients combined into a batch create an intermediate with its own work in process value, and a second assembly consumes that intermediate with packaging to make the finished good. Each stage that creates an intermediate is a stage to map before work orders are built. Our guide to why NetSuite for manufacturers walks through the day-to-day use of these records.
Which costing method fits batch production?
NetSuite supports several inventory costing methods, and Oracle’s Costing Methods documentation describes them. Average is the default.
| Method | How Oracle describes it | What batch manufacturers weigh |
|---|---|---|
| Average | A moving average of cost across the units available | Simple to run, and a batch’s cost blends with earlier stock |
| FIFO | The first goods purchased are the first sold, so ending inventory holds the most recent purchases | Fits products where the oldest lot ships first |
| Standard | Tracks standard costs for items and the variances between expected and actual cost | Fits stable recipes where batch-level variance reporting matters |
| Lot numbered | Tracks the purchase, stock and sale of a group of items under a lot number | Fits cases where cost has to follow the lot |
The first two columns come from Oracle. The third column is Nuage’s practical view, and your accountant should confirm which method fits your reporting and tax position. Oracle also states that you cannot change the costing method after you save it on the item record, so the choice belongs in the design phase.
A plant with more than one sourcing model feels this first. Finished goods bought from a supplier and finished goods assembled from purchased materials plus a co-packer’s tolling fee are different transactions, and each needs a deliberate choice of item type and costing method before the item records are saved.
What goes wrong in batch accounting after go-live?
The examples below come from setup decisions that were not made, or were made and not carried through to every transaction.
Transactions that hit inventory accounts without an item
A food manufacturer’s finance lead needed a month-end inventory figure for packaging and ingredients that matched the balance sheet, and the inventory valuation report did not. Our team built a report of every transaction that hit an inventory account with no item attached. It surfaced bills coded straight to inventory accounts, freight that had been expensed instead of added to item cost, vendor prepayments booked to inventory, and a vendor return posted to the wrong account. Correcting the freight properly needs a landed cost process, so the next step was defining one with the client’s operations team.
Oracle’s Landed Cost overview describes the feature that handles this: it tracks expenses such as freight and duty fees incurred when purchasing inventory and adds them to the asset value of the items, allocating them by weight, quantity or value.
Units of measure
Two clients traced inventory errors to how units of measure were set up. At a home goods distributor, items bought in case packs were being received as single units, which multiplied quantities on receipt, drove recurring inventory adjustments and was affecting item costs, so we walked through the purchasing process with the buyers to correct it. At an environmental products manufacturer, a “box” unit had been set up as equal to one each when a box holds 50, so the cost on one fulfillment came out about ten times higher than expected; our team added the correct 50-per-box unit, and the receipt and bill were re-entered in that unit.
Costing decisions that cannot be reversed
Because the costing method is fixed per item once it is saved, a plant that adds a second sourcing model after go-live may need new items to change how cost is calculated. Settle the method for each sourcing model during design.
How do you justify a batch manufacturing system to the C-suite?
Leadership usually asks two questions: what does the business get, and how soon. The controller gets a month-end inventory figure that ties to the balance sheet. Operations sees each batch’s cost next to the plan, and quality can follow a lot from receipt to shipment.
The second answer depends on the plant, and no platform is fastest for every manufacturer. Time to first value depends on the number of costing models in use, the quality of item and bill of materials data, and how many design decisions need sign-off from operations. Manufacturing, bill of materials and production planning made up 129 of the 3,241 client tickets we classified. Of the 51 that had closed when we measured, the median took 59.6 calendar days, against 26.8 days for all closed tickets. The base of 51 is small, but the pattern is why we scope this work with checkpoints from the start.
Ask each platform vendor the same questions:
- Which costing methods does the system support, and which can be changed after items are saved?
- How are work in process and variances recorded and posted to the ledger?
- How does the system track lots from receipt through shipment?
- Which design decisions must be settled before the first work order, and who signs them off?
- What do customers with our production model do in the first close after go-live?
How Nuage approaches batch manufacturer accounting
In recent projects and assessments, our team has taken or recommended these steps. The order changes with each account.
- Map the production stages. We agree which stages create intermediates with their own work in process before anyone builds a work order.
- Settle costing models before items are saved. Where a plant has more than one sourcing model, we design each separately and choose the costing method before the item records exist.
- Check units of measure on the way in. We confirm how each item is bought, received and sold, so quantities and costs convert correctly.
- Report on transactions that bypass items. We build a report of postings to inventory accounts with no item, and review it with finance at each month end.
- Define landed cost with operations. Freight and duty need a process that finance and operations both follow.
Nuage’s NetSuite experts do this work as part of NetSuite optimization and managed services. For software selection, see also our guide to ERP software for batch manufacturing, the NetSuite advanced manufacturing guide and our guide to ERP for food manufacturing.
Frequently asked questions
What does batch accounting mean?
In manufacturing, batch accounting collects the cost of each production run, values the run while it is in progress and releases that cost to cost of goods sold when the product ships. The phrase also appears in accounting software, where it means posting a group of transactions together. This guide covers the manufacturing meaning.
What costing methods does NetSuite support, and can I change one later?
Oracle documents average (the default), FIFO, LIFO, standard and lot-numbered costing. The method is set on the item record, and Oracle states that you cannot change it after you save the record. Choose the method before items are created, and have your accountant confirm it fits your reporting needs.
How do batch manufacturers value work in process?
In NetSuite, a work order issue moves materials into production, a work order completion stocks the finished goods, and a work order close reconciles variances. The value of a partly finished batch sits in the WIP account set up for the assembly item. Plants with several stages map each stage that creates an intermediate before building work orders.
What metrics should a batch manufacturer’s finance team track?
Track cost of goods manufactured, cost of goods sold, batch-level variances between standard and actual cost, and inventory turns. Add the share of month-end inventory that ties to the balance sheet without adjustment, since a gap there points to postings that bypass items or to unit of measure errors.
How does batch manufacturing differ from continuous flow?
Batch manufacturing runs in distinct cycles with a clear start and finish, and the equipment is cleaned and reset between recipes. Continuous flow runs around the clock on one product. The difference matters to accounting because a batch has its own cost, setup time and lot identifier, while continuous flow costs are usually collected by period.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work in this article is our team’s.
