A services business has clean accounting problems: bill the time, collect the cash, book the payroll. A manufacturer or product-based business has harder ones — inventory that has to be valued, cost of goods that has to be built from production data, vendor payment cycles that run at volume, and wholesale customers who pay what they think they owe rather than what you invoiced.
Most general accountants are trained on the services model. When they take on a product business, they see the journal entry but not the process that produced it — and that gap is where the errors, the delays, and the "we'll figure it out at year-end" habits live.
→ Why product businesses have harder accounting
Inventory and COGS. Every unit on the shelf is cash in another form, and cost of goods sold is only as accurate as the production data behind it. A P&L with a wrong COGS number isn't a small error — it distorts margin, pricing decisions, and tax.
Production data. The numbers that drive the financials — units produced, materials consumed, scrap, machine time — live in an ERP or production system, not in the accounting software. Someone has to get that data out, clean it, and tie it to the GL every month.
Vendor payment cycles. A manufacturer pays dozens of vendors on recurring cycles: raw materials, freight, tooling, MRO supplies. Volume plus repetition equals duplicate-payment risk, and most small businesses have no control against it beyond someone's memory.
Wholesale AR. Business customers short-pay. They deduct for freight, dispute a price, take an unearned discount, or pay three invoices with one check and a remittance format nobody's seen before. Untangling that consumes hours — and skipping it costs revenue you already earned.
→ What most general accountants miss
They see the output — the journal entry, the report, the balance — and treat the process upstream as someone else's job. So the same problems repeat: month-end waits on manual data exports, short payments get written off instead of investigated, and vendor payments run on trust instead of controls.
The accountant a product business needs works one level down, at the process layer, where the numbers are actually made.
→ Specific problems, and what good support looks like for each
Month-end close with production data. The close shouldn't depend on someone hand-exporting and re-formatting ERP data every month. At one manufacturing company, GL and production data prep that consumed one to three hours per month was rebuilt as an automated pipeline that runs in under a minute — and the full month-end close package, which once took a full afternoon to assemble, now comes together in 5 to 15 minutes with every close permanently archived. Good support means a reliable, repeatable data source — not a monthly scramble.
Vendor payment cycles. Volume and timing demand controls that a services firm never needs. The same company's vendor payment process — 30 to 60 minutes of manual bank-portal entry per cycle — was rebuilt to run in 2 to 5 minutes, unattended, with duplicate payments blocked by design and every payment logged. Since launch: zero duplicate payments. Good support means the control lives in the system, not in someone's head.
AR from wholesale customers. Short payments, remittance formats, price disputes. At the same manufacturer, researching short payments used to consume a full morning per review; an automated classification system now does it in minutes, identifying and explaining each discrepancy. Customer remittances — 22 customers, 22 different formats — went from constant manual monitoring to fully automatic processing. Good support means every short payment is classified and explained, not quietly written off.
→ What to look for in an accountant for your product business
Operational fluency — not just a software certification. Ask candidates whether they've worked inside a manufacturing or product operation, not just reviewed one. Ask how they'd handle a COGS number that doesn't tie to production data. Ask what controls they'd put around your payment cycle. An accountant who understands the process behind the number will have specific answers; one who doesn't will steer the conversation back to the financial statements.