Articles

The Invoices Are Fine, the Costs Are Gone: Job Costing in QuickBooks for Light Manufacturers.

8 min read

The Invoices Are Fine, the Costs Are Gone: Job Costing for Light Manufacturers on QuickBooks.

Here is a conversation we have with light manufacturers more often than any other. The owner says the books are clean. The accountant agrees. Invoices go out on time, the bank reconciles, the tax return is filed. Then someone asks what last month's biggest job actually cost, and the room goes quiet.

The invoices are fine. The costs are gone. Not wrong, gone, and the reason is not QuickBooks. It is that a job's cost is made of three things that happen in three places QuickBooks never sees, and nobody built the path from those places to the ledger. This post is about that path, and about why searching for manufacturing accounting software is usually the wrong first move.

What a job cost is made of.

A job cost, for a company that makes things to order or in small batches, is material plus labour plus a share of overhead. Each one has a home, and none of the homes is the accounting system.

Material cost is what was actually consumed on the job: which parts, how many, at what cost, including the scrap and the substitution the floor made when the specified part was out. That fact is born on the floor and, if you are lucky, recorded on a work order or a traveller. QuickBooks knows what you bought from the supplier. It does not know which job used it.

Labour cost is the hours actually spent on the job, by whom, at what loaded rate, including the setup and the rework. That fact is born on the floor too, on a time clock or a job ticket or a whiteboard. QuickBooks knows the payroll total. It does not know which job the hours went to.

Overhead is rent, power, equipment, supervision and everything else that keeps the floor running, shared across the jobs by some rule: machine hours, labour hours, a percentage of material. QuickBooks knows the overhead total, because it pays the bills. It does not know the rule, because nobody wrote it down.

So QuickBooks holds the purchases, the payroll and the overhead as totals and holds the invoice per job. It has the top line by job and the cost as a lump. The margin by job is not wrong. It does not exist.

What it costs not to know.

  • Quotes built from last time. With no cost by job, the next quote for a similar job is the last price plus a feeling. Some of those quotes lose money, and nobody finds out, because the loss disappears into the lump.

  • Products that subsidise other products. Every mixed-product manufacturer has a line that loses money and a line that carries it. Without cost by job, the two are one number, and the decision to drop, reprice or redesign the losing line never gets made.

  • A month-end that explains nothing. The accountant produces a gross margin for the company. It moved three points. Nobody can say which jobs moved it, so the response is a general instruction to watch costs.

  • Pricing conversations lost. A customer pushes back on a price. Without the cost, the only answer is to hold or to fold, and folding is easier.

Why a manufacturing accounting package is usually the wrong answer.

The search that follows the quiet room is for manufacturing accounting software, and the results are two kinds of product. One is a manufacturing-specific accounting package that replaces QuickBooks. The other is an ERP with a manufacturing module that replaces QuickBooks and several other things.

Both can do job costing. Both will do it only if material consumption, labour hours and the overhead rule are captured and fed to them, which is the exact thing that is not happening today. Replacing the ledger does not create the feeds. It creates a bigger ledger with the same three gaps, plus a migration. We wrote about the general version of this mistake in do you need an ERP, or do you need your systems to talk to each other, and job costing is the clearest case of it.

There is a day when the answer is an ERP, and we say which day at the end. For most light manufacturers on QuickBooks with a few dozen products and a floor of ten to sixty people, that day has not come, and what is missing is two feeds and a rule.

The two feeds and the rule.

Feed one: material consumption by job.

The work order has to record what was actually pulled for the job, at the cost it was bought for. If your work orders live in a spreadsheet, a small work order application replaces the spreadsheet; if they live in an inventory system, the inventory system already knows the pull and the cost and the feed is a join. Either way, the feed posts material cost to the job in the accounting system as it is consumed, not as it is bought. We have written separately about what a manufacturer's inventory system has to do, and the material feed is the part of that work that pays for itself first.

Feed two: labour hours by job.

Hours have to be captured against the job, not against the week. A time clock that asks for the job number, or a job ticket that is closed with hours, or a tablet on the floor. The feed posts the hours at the loaded rate to the job. This is the feed that meets the most resistance, because it changes what the floor does every day, and it is the one that most often turns a losing product into a visible one.

The rule: overhead by a denominator you can defend.

Pick a rule, write it down, apply it every month. Machine hours if the floor is machine-bound, labour hours if it is people-bound, a percentage of material if neither dominates. The rule does not have to be perfect. It has to be consistent, because a consistent rule makes jobs comparable to each other, which is the point.

With the two feeds and the rule, QuickBooks can carry cost by job in its own job costing, or Zoho Books can, and the accountant's month-end margin becomes a list of jobs rather than a lump. Nothing was replaced. Two things were connected and one was written down.

When the answer is an ERP.

The two-feeds answer runs out on a definable day. It is the day the manufacturer needs material requirements planning, meaning the system has to decide what to buy and when from the demand and the BOM rather than a person deciding it; or the day there are several sites with stock moving between them; or the day the product has enough revisions and variants that the BOM itself needs a system to hold it. On that day the accounting system is one module of something larger, and the comparison between Zoho Books and QuickBooks becomes a comparison between suites, which is a different decision with a different cost.

Most light manufacturers reach that day, if they reach it at all, two or three years after they first ask what a job cost. Building the two feeds now does not waste that time. It produces the numbers that tell you when the day has come, and the feeds carry across into whatever the ERP turns out to be.

How we approach it.

We start with a no-risk discovery: a few days to see how work orders, hours and overhead are actually recorded today, to pick the three or four biggest jobs of last quarter and cost them by hand, and to show the owner the margin by job that the company has never seen. That number is usually enough to decide. You get a written plan and a guaranteed estimate for the two feeds and the rule, built in the order that the material feed comes first, the labour feed second, and the rule is agreed before either.

The short version.

Your invoices are fine because QuickBooks is good at invoices. Your job costs are gone because material, labour and overhead by job are created on the floor and nobody carries them to the ledger. Manufacturing accounting software replaces the ledger and leaves the gaps. Build the two feeds, write the overhead rule down, and cost by job appears in the accounting you already have. The ERP day comes later, and the feeds tell you when.

Find out where your orders, inventory and invoices stop agreeing.

In a no-risk discovery we follow an order from sale to shipment to invoice across your systems and show where it breaks and what one connected system would change. You pay only if you proceed. Or see how we approach it.

Book the no-risk discovery

More on the same problem:

Frequently asked questions.

What does manufacturing accounting software do that a general ledger does not?

It carries cost by job or by product, not only in total. That means recording which materials were consumed on which job, which hours were spent on it, and a share of overhead by a fixed rule, then rolling the three into a margin per job. A general ledger holds purchases, payroll and overhead as totals. The difference is the feeds, and a manufacturing package only delivers job costing if those feeds exist.

How do you calculate job cost for a small manufacturer?

Add three numbers. Material actually consumed on the job at the price it was bought for, including scrap and substitutions. Labor hours charged to the job at a loaded rate, including setup and rework. And overhead allocated by a consistent rule, such as machine hours, labor hours or a percentage of material. Subtract the total from the invoice for the job. The rule does not have to be perfect, but it has to be applied the same way every month.

Can QuickBooks do job costing for a manufacturer?

It can carry cost by job once the inputs reach it. The gap is not the ledger but the capture: QuickBooks knows what was bought from suppliers and what payroll totals were, not which job used the parts or the hours. A work order system or inventory system that records consumption by job, a time capture that asks for the job number, and a written overhead rule put cost by job into the accounting system you already run.

When should a manufacturer move from job costing feeds to an ERP?

On a definable day. When the system has to plan what to buy and when from demand and a bill of materials, rather than a person deciding. When stock moves between several sites. Or when products have enough revisions and variants that the bill of materials itself needs a system to hold it. Most light manufacturers reach that day, if at all, two or three years after first asking what a job cost, and the feeds built earlier carry across.

Why is overhead allocation important for job costing?

Because overhead is often the largest cost after material, and without a rule it stays a lump that no job carries. Rent, power, equipment and supervision have to be shared across jobs somehow. A consistent denominator makes jobs comparable to each other, which is the point: it shows which products subsidise which, and which quotes lose money. The rule is written down once and applied every month, and changing it changes every margin.

What does it cost a manufacturer not to know job costs?

Quotes built from the last price plus a feeling, some of which lose money without anyone noticing. Product lines that lose money and are carried by others, with no decision ever made to fix or drop them. A month-end gross margin that moves and cannot be explained. And pricing conversations lost because, without the cost, the only options are to hold or to fold. None of those costs appear on a report, which is why they persist.

Where we're not the right answer

We'll tell you if we're a fit. If we're not, we'll tell you that too.

  • Your current stack works and nobody wants to change it
  • You want licences resold at a discount and nothing else
  • Your internal team owns the operating model and is not handing it over
  • You want hours of configuration work and nothing run for you: that is on our services pages, and it is not a managed solution
How we start

Most of our best clients come to us with a feeling, not a plan.

"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.

Talk to us

Have a question about this?

Say who you are and ask. A person replies within one business day.

The rest of the form follows your answer.

A new client, or thinking about becoming one

Never shared. Never sold.

A solution, a service, or not sure yet.

Platforms you run today

Pick every one that applies. Choosing one is an answer too.