AWRA OpsHub Search

The Cost That Was Never Work in Progress

Plenty of stock systems expense material the moment it leaves the store for a job, and bring the finished output back onto the books as a debt to nobody. This one keeps part-finished work on the balance sheet and credits a receipt from where the stock came from — and what is left is more interesting than either: the ledger will tell you what a job consumed and what its output was valued at, and it will not pretend those two numbers agree.

Manufacturing & Agribusiness Washingtone Aura 13 min read

This is the article for whoever prepares your accounts. The operational picture — what production looks like in the system — is the easy half. The accounting underneath it is where a stock system built for retail goes wrong for a manufacturer, in two specific ways a manufacturer meets in their first month. It is worth knowing both, because they are the two entries to check in any system you evaluate, ours included.

What AWRA does about them is not a manufacturing accounting module. It is narrower and more honest than that: the ledger keeps part-finished work on the balance sheet where it belongs, and it refuses to hide the difference between what a job consumed and what its output was valued at. That difference is the subject of the second half of this article.

Material issued to a job is work in progress, not an expense

The retail entry on an approved stock issue is expenses debited, inventory assets credited, with no exception. For a retailer that is broadly right. For a manufacturer it is wrong in a specific way: the material has not been consumed in the sense the accounts claim. It has been transformed, and it is sitting on the factory floor as part-finished goods you still own.

AWRA has a Work in Progress account, and an issue charged to a job debits it instead of expenses. When output is received back into stock against that same job, the receipt credits Work in Progress. Material moves from raw inventory into WIP, stays an asset while it is being worked on, and leaves WIP as finished stock — which is what a manufacturing system is supposed to do.

The job is the trigger, and nothing else is

An issue only becomes work in progress if it is charged to a project. Issue the same material with no job on it and it debits expenses — because a write-off, a breakage, a sample and internal consumption really are consumption, and treating them as WIP would be the same error running backwards. Bills of materials and assembly orders are in the product too, but an assembly order completes in one step — components out, finished item in, cost rolled up — so it never sits in work in progress; for a run that spans days, the project is still the unit of work in progress. If your team does not code issues to jobs, none of this engages, and that is the one thing to check in week one.

One production run in three postings: material issued to a job debits Work in Progress and credits Inventory Assets at the cost stamped when the stock left; Work in Progress holds the value while the job runs; output received against the same job debits Inventory Assets and credits Work in Progress at the finished item's standing price. A residual is marked where the two valuations differ, labelled as the variance to explain rather than an error.
Material moves into work in progress and leaves it as finished stock. What does not net off is the difference between what the job consumed and what its output was received at — and that is the number worth looking at.

Why it matters at month-end: where issues are expensed, part-finished production is worth nothing on paper, so closing the books mid-run — and a mill or a bakery is always mid-run — understates profit by the full cost of everything on the floor and understates total assets by the same amount. The worst books belong to the busiest month, which is the least convenient time to be reading your own numbers wrong.

Expensing on issue is a distortion that scales with how busy you are. A factory with nothing in progress has accurate books; a factory running flat out has the worst ones.

Your own output does not arrive as a debt

A system that treats every receipt as a purchase posts finished goods back onto stock as inventory assets debited, accounts payable credited. The debit is right — the goods are an asset. The credit is not: accounts payable is money owed to a supplier, and there is no supplier. You made the goods. It creates a payable to nobody that grows with every production receipt, and because it sits inside the same balance as real supplier debt it is invisible — the creditors listing simply stops agreeing with the invoices you actually hold, by the cumulative value of everything you have ever manufactured.

In AWRA the credit is derived from where the stock actually came from. A delivery against a purchase order or a procurement request still credits accounts payable, because somebody genuinely is owed. Output received against a job credits Work in Progress, which is the entry that relieves the job. A receipt with neither — found stock, an opening balance, a customer return — credits a separate Inventory Received Clearing account, so the value is visible as its own balance you can journal out rather than buried in what you owe your suppliers.

Note the ordering, because it is deliberate: a supplier document beats a job. Material bought for a job is still a purchase, and it only becomes work in progress later, when somebody issues it from the store.

What is left: the two figures do not agree, and you can see it

The remaining problem is not a defect so much as the consequence of running production as a job rather than a build: on a job, the cost going in and the value coming out are computed independently. (An assembly order does not have this problem — it values the finished item from the actual cost of the components it consumed — but it consumes the bill's quantities in one step, which suits a fixed recipe rather than a variable-yield run.) The issue is valued at the unit cost stamped on the line when the stock left the store — the same figure the job costing report uses, so the ledger and the job report agree about the cost of the same movement. The receipt, though, is valued at whatever unit cost is typed on its check-in line — and left blank, at the finished item's current average cost, a figure built from earlier receipts that has nothing to do with this run.

So the two numbers differ, and the difference stays behind in Work in Progress after the job's output has been received. That residual is not an error and it is not netted away. It is the variance between what a job consumed and what its output was priced at, and the honest thing to do with it is show it: there is a Work in Progress by Job report that lists what each job has taken in, what has come back out, and what is still sitting there — with a view for exactly the jobs whose output has arrived and which still did not clear.

The residual can be negative, and a negative one is the more informative case. It means the output was valued above what the job consumed, and the usual reason is labour: the figure the output came in at — a running cost from earlier receipts, or one typed from a costing that counts time — includes work the ledger never capitalised, because time costed to a job still sits in payroll expenses and nothing carries it into inventory value.

One milling run, as the books record it

Maize and packaging issued to the job — Dr Work in Progress, Cr Inventory Assets KES 167,700
Labour on the job, from time entries — posts nowhere KES 24,000
True cost of the run, if labour were capitalised KES 191,700
Output received against the job, unit cost left blank: 2,760 kg at the item's current cost of 70.00 KES 193,200
Posted as — Dr Inventory Assets, Cr Work in Progress KES 193,200
Work in Progress left carrying, after output KES 25,500 credit

Read that residual rather than clearing it. It is negative — the job was relieved of 25,500 more than it was ever charged — and the explanation is almost entirely the 24,000 of labour, which is in the 70.00 but never entered the ledger as inventory value because time costed to a job stays in payroll expenses. The remaining 1,500 is drift in the item's running cost. Type 60.76 on the check-in line — the 167,700 of material the job was actually charged, over 2,760 kg — and the job clears to nothing; type 69.46, the cost with labour, and the residual is exactly the 24,000 the ledger never capitalised. There is no payable to nobody and no material stranded in expenses; what is left is one number, attributable to one job, that tells you which figure the output was received at.

How far from correct is this, honestly

Manufacturing accounting, by layer

Handled properly in the product Entirely your accountant's manual work

True landed cost of imported inputs

Freight, duty and clearing allocated across a receipt by value or quantity, written onto the batch and carried into weighted average cost. Genuinely strong, and the hardest of these to do by hand.

Raw material valuation

Stock by warehouse and bin, batch identity, weighted average cost, blind counts with valued variance. Reliable.

Cost attribution to a job

Material, labour and purchases all code to a job, so what a run consumed is recoverable from source records. The attribution works; the accounting treatment of it does not.

Work in progress

Its own asset account, debited by an issue charged to a job and credited by output received against that job, with a per-job report of what is still carried. Engages only where issues are coded to jobs.

The credit side of a production receipt

Derived from where the stock came from: a payable for a purchase, work in progress for a job's output, a named clearing account for anything else. No standing journal needed.

Finished goods valuation

Built on an assembly order, the finished item absorbs the actual material cost consumed. Received against a job, it arrives at the unit cost typed on the check-in, or the item's current cost when that is blank — the run's cost only when somebody works it out and types it. Either way the ledger carries no labour content.

Overhead and cost variance

No absorption, no standard costing, no purchase-price or usage or labour variance. The WIP residual is the only variance figure and it is a by-product, not a costing system.

The shape of that scale is the honest summary of this cluster: attributing cost to a run is solid, the ledger keeps part-finished work on the balance sheet, and an assembly order values a fixed-recipe output from the material it consumed. What remains manual is the rest of valuing the output — labour, overhead and a standard to measure against.

The routine that is left

The standing correcting journals a manufacturer usually keeps for these two postings are not needed, because the postings are right at source. What is left is short, and it is review rather than correction.

  1. Make sure issues are coded to jobs

    This is the whole mechanism. An issue with no job on it is expensed, and no amount of month-end work recovers that as work in progress after the fact. If your storekeeper is issuing against a reason but not a project, fix that before anything else on this list.

  2. Read the WIP by Job report at close, and ask about the residuals

    Jobs still carrying value are legitimately in progress. Jobs whose output has been received and which still did not clear are the interesting ones — the report has a view for exactly those. A large negative residual usually means the cost the output came in at includes labour the ledger never capitalised; a large positive one usually means scrap, or output received at a price set years ago.

  3. Type the run's cost on the check-in

    Work out the job's cost over its good output and type it on the check-in line before approving it; leave it blank and the output falls back to the item's current cost. That receipt cost blends into the moving-average cost, which feeds margin on every subsequent sale, so getting it right at the receipt is the difference between one correct number and a quarter of wrong margin reporting.

A WIP balance you cannot decompose is worse than none

That is why the account comes with a per-job report. A production receipt crediting payables is dangerous precisely because a wrong figure hides inside a correct-looking total. An unexplained Work in Progress balance would repeat that mistake under a new name, so the balance is readable per job, per movement.

One thing not to do: do not try to fix the finished-goods valuation by receiving at whatever cost the item happens to carry and correcting it in a journal. The receipt's cost blends into the moving average, which feeds your margins on every subsequent sale of that item, and a journal does not move it. Get it right on the check-in line, or your gross margin reporting is wrong for reasons that have nothing to do with this.

Manufacturing accounting — the straight answer

What AWRA OpsHub does today

  • True landed cost allocated across a receipt by value or quantity, written onto the batch and carried into weighted average cost.
  • A moving-average cost per item, blended on every receipt at that receipt's own cost.
  • A cost typed on a receipt — the check-in line takes the run's unit cost, the receipt posts at it and relieves work in progress by that amount, and it blends into the item's moving-average cost.
  • Double-entry journals posted automatically from every approved stock movement, with the source adjustment referenced on the entry.
  • The account pair stamped onto the movement when it is raised, from the organization's chart — so a later change to the chart does not restate entries already posted.
  • A selectable inventory account on a receipt, so different classes of stock can hit different asset accounts.
  • Material, labour and purchases all attributable to a job, from source records.
  • A full chart of accounts you can extend, on top of the system accounts.
  • Adjustment reporting by reason and period.
  • A work-in-progress account, debited when material is issued to a job and credited when output is received against that job, so part-finished work stays on the balance sheet as an asset.
  • Issues valued at the cost stamped when the stock left the store, which is the same figure the job costing report uses — so the ledger and the job agree about the cost of a movement.
  • The credit on a receipt derived from where the stock came from: a payable for a purchase, work in progress for a job's output, a named clearing account for found stock, opening balances and returns.
  • Assembly orders valued from what they consume — completing a build against a bill of materials takes the components out and the finished item's moving-average cost absorbs their actual cost; value moving between different inventory accounts is journalled, and within one account it nets to nothing.
  • A work-in-progress report per job, showing what each job has taken in, what has come back out, and what is still carried — including a view for jobs whose output arrived and which still did not clear.

More we can add to your workspace

  • Work in progress only engages where an issue is charged to a job. An issue with no project on it is expensed, and nothing warns you that it might have wanted to be a job.
  • A cost of goods sold account in the default chart — stock issues debit a general expenses account.
  • A job's cost carried onto its output by itself, so a receipt against a job takes the material the job was charged, divided by good output, without anybody doing the division and typing it in. An assembly order already carries its components' cost.
  • A work-in-progress stage on an assembly order, so a build that spans days is carried as part-finished work. Completion is instant today.
  • Labour capitalised into inventory value. Time costed to a job sits in payroll expenses today, and nothing carries it into the finished good.
  • Overhead absorption of any kind.
  • Standard costing and therefore no cost variance — purchase price variance, usage variance or labour variance.
  • A scrap or write-off accounting distinct from an ordinary issue beyond the reason you choose.
  • A selectable account pair per issue. It comes from the organization defaults at the moment the movement is raised today, so a per-run treatment is the build.

The two entries this article opens with — a production receipt crediting payables, and material issued to a job going straight to expense — are what the ledger gets right at source. What remains is the honest scope of a system that does inventory, job costing and material roll-up on a bill of materials well, and leaves the rest of manufacturing costing to a build: labour and overhead absorption, which put time and the factory in the number; and a standard, which is what makes variance analysis worth the name. The first bullet is the one to act on, because it is the only one where your own process decides whether the mechanism works at all.

More we can add to your workspace

Anything above that you need, we can build for you

Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.

The operational work, which is what most commissions actually are

An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.

The module-shaped additions, which are the ones readers ask for most often

A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.

The report, document or pack nothing currently produces

The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.

Systems, rails and hardware you already run

The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.

How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.

Tell us what your operation needs

Our take

Show this article to whoever closes your books before you buy — the two entries it opens with are posted correctly, and the remaining boundary is easier to plan around when it is read early rather than discovered at year end. The practical test is one question to your storekeeper, not your accountant: are material issues coded to jobs? If they are, part-finished work is on the balance sheet and the residual per job is readable. If they are not, none of this engages and issues go straight to expense.

Bring your accountant to the demo

Ask to see the journal entries a stock issue and a production receipt actually post — the entries, not a report of them — and ask what happens when the same issue is raised without a job on it. It is a five-minute test and it tells you more than any feature list.

See AWRA for manufacturing

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center