Discrete Manufacturing
ERP
Manufacturing
Production Reporting Software: Capturing Output, Labor and Scrap
Last updated: October 9, 2026 · Independent buyer’s guide · We do not sell rankings or coverage.
Production reporting software records what each work order actually produced, how much labor and machine time it took and how much material was scrapped, then posts those quantities to your ERP so inventory, work in process and job costs stay accurate. For most US manufacturers, that means the completion, labor and scrap transactions in the ERP’s manufacturing module, often with an operator app on top. Your daily production report is only as good as those transactions, and the biggest design choice is what you record by hand and what the ERP backflushes from the bill of materials and routing.
Key takeaways
- A production report has three inputs: good output, labor and machine time, and scrap with a reason. Each one updates a different ledger in your ERP, so a missing entry distorts inventory or cost, not only the report.
- Backflushing posts material (and in some systems labor) at standard quantities when you report output. It saves data entry but hides scrap and overruns unless operators also report scrap.
- Business Central, SAP Business One and Acumatica let you choose manual issue or backflush per component or operation, so one order can use both. NetSuite turns on backflush for the whole work order.
- Published prices for systems with production reporting run from MRPeasy at $49 per user per month to Business Central Premium at $110 per user per month; NetSuite, Acumatica and Epicor quote individually.
- Production labor records are not automatically payroll records. Under federal wage-and-hour rules, you must keep hours worked each workday and keep time cards for at least two years.
What production reporting has to capture
Every production report, on a clipboard or an ERP screen, answers the same questions for each order and shift: good units made, units scrapped and why, time taken and material used. A reporting system turns those answers into inventory and cost transactions.
The table below shows what each type of entry typically updates in a manufacturing ERP. The exact postings vary by product and costing method, which our guide to standard cost vs actual cost explains.
| What the operator reports | ERP transaction | What it updates | If it is missing |
|---|---|---|---|
| Good quantity completed | Output, completion or production receipt | Finished goods inventory, order status, WIP relief | Stock looks short; orders look late |
| Setup and run time | Labor or capacity entry against an operation | Labor and machine cost in WIP, capacity history | Job cost repeats the routing estimate |
| Material used | Component issue or backflush | Raw material inventory, material cost in WIP | Inventory overstated until a count |
| Scrap quantity and reason | Scrap entry on the operation or a scrap transaction | Yield, scrap cost, variance accounts | Loss lands in month-end variance with no cause |
In Dynamics 365 Business Central, for example, the output journal records output quantity, setup and run time, scrap with a scrap code, and stop time with a stop code; finished goods reach inventory when the last routing operation is posted. The production journal also posts consumption (Microsoft Learn, July 15, 2026).
The daily production report: what managers actually read
The daily production report summarizes those transactions. A useful version shows, by line or work center and shift, planned versus actual good output, scrap and its top reasons, labor hours earned versus worked, downtime by reason, and orders at risk of missing their due date.
A spreadsheet template is a reasonable start, but it disagrees with the ERP as soon as someone types a number into one and not the other. If supervisors keep a separate daily sheet, compare its totals with the ERP’s posted output for the same day. The gap shows how much floor activity never reaches inventory or costing.
Standard ERP reports usually cover the cost side better than the shift view. Business Central, for example, includes a Capacity Task List, load reports and Production Order Statistics comparing actual with expected cost (Microsoft Learn, March 10, 2026). For a shift scoreboard by line, many plants use a reporting tool or operator app on top. Our article on real-time shop floor data in ERP covers the dashboard side.
Backflushing: what the ERP records for you
Backflushing means the ERP posts component consumption, and sometimes labor, from the bill of materials and routing when you report output. It removes much of the data entry, but your records then show what should have been used rather than what was used. Most major ERPs let you choose per component or operation:
- Microsoft Dynamics 365 Business Central offers Manual, Forward, Backward, Pick + Forward, Pick + Backward and Pick + Manual flushing methods. Backward flushing posts consumption when the order is set to Finished; with routing link codes it posts as each linked operation finishes, based on actual output. Microsoft notes that components whose consumed quantity can vary or that need item tracking might require manual posting of consumption (Microsoft Learn, November 6, 2025).
- Oracle NetSuite backflush is turned on with a Backflush box on the work order; it issues components at standard BOM quantities and completes the assembly at one time. A preference decides whether a completion still posts when staging bins are short, issuing what is available and noting the shortfall (Oracle NetSuite Help, no date shown).
- SAP Business One issues components by the Manual or Backflush method. With Backflush, items are issued automatically when a Receipt from Production is created; Manual items are issued with an Issue for Production document (SAP Learning, no date shown).
- Acumatica sets Backflush Labor and Backflush Materials separately on each production order operation. The MYOB Acumatica guide advises against backflushing when labor varies widely between runs, when materials are lot or serial tracked, when consumption is variable or wasteful, or when labor must reconcile with payroll or shop data collection (MYOB Acumatica help, no date shown; MYOB sells this Acumatica-based edition).
- Infor CloudSuite Industrial (SyteLine) backflushes labor and machine hours at 100% of the routing when you post completions or scrap, ignoring hours already entered. In Infor’s example, one manual hour plus five units at 0.25 hours each gives 2.25 hours (Infor documentation, November 3, 2021).
The Infor example shows a common mistake: if operators clock time on an operation that also backflushes labor, the job carries both amounts.
Where production reporting goes wrong
- Scrap is never reported. Backflush typically consumes material for the good units reported, so the scrapped material stays in the inventory record until a cycle count finds it missing.
- Double counting. Labor or material is entered manually and also backflushed on the same operation.
- End-of-shift batch entry. Supervisors key the day’s paper into the ERP the next morning. Entries are late and rounded, and they drift toward the standard.
- Reason codes nobody uses. Long reason lists end with most entries coded “other.” Keep the list short.
Scrap reporting also matters for accounting. Under US GAAP (originally SFAS 151, now in ASC 330), abnormal amounts of idle facility expense, freight, handling and wasted materials are charged to the current period rather than included in inventory cost, and fixed overhead is allocated based on normal capacity (Journal of Accountancy, February 1, 2005). Your controller needs scrap reasons that separate normal from abnormal loss.
How software handles production reporting
The broader execution layer (dispatch lists, work order status, clock-on and clock-off) is covered in our guide to shop floor control software. Here we focus on the reporting and posting side. You have three realistic routes.
1. Your ERP’s manufacturing module
Business Central puts manufacturing in the Premium plan, at $110 per user per month paid yearly, with Team Members at $8 (Microsoft, no date shown). Its journals are back-office screens, so many plants add a partner touchscreen app. NetSuite supports completions with backflush and, through its Manufacturing Mobile SuiteApp, operation reporting with setup and machine time; Oracle’s feature table does not indicate support for machine downtime (Oracle NetSuite Help, no date shown). Acumatica lists labor clock-in and clock-out, scrap reporting and shared kiosk terminals in its manufacturing data collection (Acumatica datasheet, April 4, 2023). Epicor Kinetic describes “data collection and IoT-enabled MES” as part of the product but publishes no prices (Epicor, no date shown).
2. MRP systems for smaller manufacturers
MRPeasy lists reporting via an internet kiosk in all plans, with Starter at $49, Professional at $69, Enterprise at $99 and Unlimited at $149 per user per month; its feature list includes shop floor reporting interfaces and labor reports by worker (MRPeasy, page modified October 7, 2026). Katana now offers a Free plan limited to 30 SKUs and an Advantage plan priced by custom annual contract, which includes its shop floor app (Katana, page modified October 7, 2026). Odoo includes all apps, Manufacturing among them, in its Standard plan (Odoo, no date shown). In Odoo 19, the Shop Floor interface shows each work order step as a card with a Start button, and a quality control point linked to an operation adds an inspection prompt to that card (Cybrosys, July 16, 2026).
3. Operator apps and no-code platforms
Tulip lets you build operator apps for tablets and touchscreens. Essentials costs $100 and Professional $250 per interface per month billed annually, with a 10-interface minimum; Professional adds HTTP and SQL connectors and edge connectivity for machine signals (Tulip, no date shown). It suits plants whose ERP has the right transactions but a poor operator interface.
Report-writing and BI tools can build the shift view from posted data, but they capture nothing, so they cannot fix missing or late entries.
Comparison: production reporting options
| Product | How output, labor and scrap are reported | Backflush options (documented) | Published US price |
|---|---|---|---|
| Business Central | Output and production journals: setup, run, scrap and stop codes | Manual, Forward, Backward, Pick variants, per component | Premium $110/user/month, paid yearly |
| NetSuite | Work order completions; Manufacturing Mobile by operation | Backflush at standard BOM quantity on completion | Not published |
| SAP Business One | Issue for Production and Receipt from Production | Manual or Backflush per component | Not published on the page cited |
| Acumatica | Move and labor transactions, kiosks, scrap reporting | Backflush labor and materials set per operation | Not published |
| MRPeasy | Kiosk and shop floor interfaces | Not covered on the pricing page | $49 to $149/user/month |
| Katana | Shop floor app on Advantage | Not covered on the pricing page | Free (30 SKUs); Advantage custom quote |
| Odoo | Shop Floor work order cards with quality checks | Not covered in the page cited | Standard plan from US$31.10/user/month (see below) |
| Tulip | Custom operator apps; posts to ERP through connectors | Depends on the ERP it feeds | $100 or $250/interface/month, 10 minimum |
What production reporting software costs
Prices above were checked on October 9, 2026 and exclude implementation. Odoo’s pricing page showed US$31.10 and US$38.90 per user per month for the Standard plan, with a note that the discount applies for 12 months to initial users (Odoo, no date shown). NetSuite, Acumatica and Epicor quote privately, so ask for a written quote naming the manufacturing modules and any mobile or data collection add-ons.
Budget separately for tablets, kiosks, scanners and label printers, for any partner operator app, and for integration from an operator app into the ERP. With many hourly operators, ask whether a lower-cost operator or kiosk license exists and confirm it can post the transactions you need.
Worked example: what backflush without scrap reporting does
Illustration only. These figures are invented to show the mechanics and do not come from any vendor or customer.
A plastics molder runs an order for 1,000 housings. The BOM calls for 2 kg of resin per unit at $3.00 per kg, and the routing allows 0.05 labor hours per unit at $30 per hour. Resin and labor are both set to backflush at completion.
- What the ERP records: 1,000 good units, 2,000 kg of resin ($6,000) and 50 labor hours ($1,500). Total $7,500, or $7.50 per unit. The daily report shows 100% yield.
- What actually happened: the press made 1,040 parts and 40 were scrapped after a mold temperature problem, so the plant used 2,080 kg of resin ($6,240). Operators worked 58 hours ($1,740). Total $7,980, or $7.98 per good unit.
- The consequences: the job is understated by $480 (6.4%). The resin record shows 80 kg more than the shelf holds, and the loss surfaces weeks later as a cycle count adjustment with no order, shift or reason attached.
Had the operator reported 40 scrapped units with a reason code, the loss would appear on that day’s report. Whether scrap entry also corrects backflushed material depends on your ERP and settings, so test it in the demo.
Our independent take
Start with the transactions your ERP already has. In most plants we would expect the larger problems to be unreported scrap, labor entered twice and paper keyed in a day late, and new software fixes none of those on its own. Backflush stable, low-value components and labor on short, repetitive operations, and record actuals where cost or yield varies.
In demos, ask each vendor to run one order end to end: a partial completion, scrap with a reason, a labor entry and the backflush, then show the inventory, WIP and variance entries and the same order on the daily production report. The report and the ledger should agree.
Three buyer scenarios
A 70-person food packager on Business Central Premium. Backward flush packaging, keep lot-tracked ingredients on manual issue, since Microsoft notes tracked items might require manual consumption posting, and give line leads a simple screen for output and scrap codes.
A 30-person assembler on QuickBooks with paper travelers. You have no work orders to post against, so reporting tools alone will not help. Look at MRPeasy, Katana or Odoo, which add manufacturing orders and operator reporting together, and confirm how each passes costs to your accounting system.
A 300-person metal fabricator on NetSuite. Backflush at standard BOM quantity will hide sheet utilization losses. Report scrap on cutting operations, keep sheet stock on manual issue, and use Manufacturing Mobile or an operator app for operation-level reporting.
When you do not need dedicated production reporting software
If you make a small range of standard products on short, single-step runs with stable yields, backflushing material and labor at completion and reviewing variances monthly may be accurate enough. Pull systems that run on kanban signals also need less transaction detail; our guide to MRP and kanban covers when pull fits better.
You also do not need a new product if your ERP already supports these transactions and your team is not using them. Clean up routings and BOMs, shorten reason codes and have supervisors close each shift’s entries before they leave.
How we researched this
On October 9, 2026, we read the vendor documentation and pricing pages for each product named, the federal recordkeeping rules in 29 CFR Part 516 and the published guidance on SFAS 151. We also reviewed the pages ranking for “production reporting software,” mostly templates and BI vendor articles that skip ERP posting, backflushing and scrap accounting. We did not test products hands-on, and no vendor paid for inclusion.
Related guides
- Routing in Manufacturing: Operations, Work Centers, Costing
- Scrap and Yield Tracking: A Process Guide for Plants
- Material Usage Variance: Formula, Causes and ERP Tracking
Frequently asked questions
Should I backflush materials or issue them manually?
Backflush components with stable consumption and low value, where data entry costs more than the error. Issue manually when consumption varies, when materials are lot or serial tracked, or when scrap is significant. Most ERPs let you set this per component, so one order can use both.
What should a daily production report include?
At minimum it should show planned and actual good output, scrap quantity with reasons, labor hours worked versus earned, and downtime by reason, broken out by line or work center and shift. Build it from posted ERP transactions so it matches inventory and cost.
Can production labor reporting replace our time clock?
Not automatically. Federal rules require you to keep each employee’s hours worked each workday and each workweek, and to keep time cards for at least two years (29 CFR 516.2; 29 CFR 516.6). Confirm with payroll before you retire a separate time system.
Why does my ERP inventory not match the shelf after production?
The usual cause is backflushing at standard quantities while scrap or overconsumption goes unreported. Material posted both manually and by backflush, and outdated BOM quantities, are the next suspects.
How much does production reporting software cost?
Published prices checked on October 9, 2026 run from MRPeasy at $49 to Business Central Premium at $110 per user per month. NetSuite, Acumatica and Epicor do not publish prices, and implementation and hardware are extra.
Sources
- Microsoft Learn: Post output and run times (July 15, 2026)
- Microsoft Learn: Flush components according to operation output (November 6, 2025)
- Microsoft Learn: Production reports and analytics in Business Central (March 10, 2026)
- Microsoft: Business Central pricing (no date shown, checked October 9, 2026)
- Oracle NetSuite Help: Backflush logic (no date shown)
- Oracle NetSuite Help: Manufacturing order types and features (no date shown)
- SAP Learning: Running the production process in SAP Business One (no date shown)
- MYOB Acumatica help: Production with backflushing (no date shown; MYOB sells this product)
- Acumatica: Manufacturing data collection datasheet (April 4, 2023)
- Infor CloudSuite Industrial: About backflushing labor and machine hours (November 3, 2021)
- Epicor: Kinetic (no date shown)
- MRPeasy: Pricing (page modified October 7, 2026)
- Katana: Pricing (page modified October 7, 2026)
- Odoo: Pricing (no date shown, checked October 9, 2026)
- Cybrosys: How to set up quality checks on work orders in Odoo 19 (July 16, 2026)
- Tulip: Plans (no date shown)
- eCFR: 29 CFR 516.2, records employers must keep (up to date as of October 7, 2026)
- eCFR: 29 CFR 516.6, Records to be preserved 2 years (up to date as of October 7, 2026)
- Journal of Accountancy: Accounting news, February 2005 (SFAS 151) (February 1, 2005)
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
