Category: 

What is Backflush Costing?

Article Details
  • Written By: Malcolm Tatum
  • Edited By: Bronwyn Harris
  • Last Modified Date: 18 September 2016
  • Copyright Protected:
    2003-2016
    Conjecture Corporation
  • Print this Article
Free Widgets for your Site/Blog
In late 19th-century London, mail was delivered to residential addresses up to twelve times each day.   more...

September 28 ,  1924 :  Two US military planes complete the first flights around the world.  more...

Backflush costing is a strategy that involves delaying the costing process until the production of goods or services is completed. Once the production cycle is finished, the costs are then applied to the operation, making it possible to determine the costs associated with manufacturing the products and to set the sale price accordingly. One of the benefits of this strategy is that there is no need to closely track costs as they occur, thus simplifying the accounting process while the production process is in progress. While this approach is relatively easy, the lack of detail can sometimes create issues at a later date.

The concept of backflush costing is often associated with a just-in-time or JIT operation. With this approach, one of the goals is to keep the inventory of raw materials as low as possible. Thus, orders for raw materials are scheduled so that the goods arrive just before the production commences. By the time the invoicing for the materials is received, the goods are produced, costs are calculated, and the products are sold at a rate that covers the expenses. All relevant postings in the company’s accounting books are made at that point, thus keeping the books balanced and factual, but without the need to make multiple postings all through the production process.

Ad

One of the drawbacks of backflush costing is that the strategy is not widely considered to be in compliance with generally accepted accounting principles. This is because the inventory is likely to be undervalued during the course of production, since the actual cost for recently arrived inventory is not posted until the production is finished. This situation is sometimes structured to allow the posting of a standard cost for the raw materials when they are purchased. There are also some objections to not recognizing the finished goods until the point of sale, rather than accounting for them in a finished goods inventory, as is the case with other accounting methods.

While backflush costing does work well with a just-in-time inventory approach, the lack of detail can sometimes create issues during an audit of the company’s financial records. This can lead to situations where it becomes necessary to use existing documentation to reconstruct the chain of events involved in the production process, rather than simply following the sequence of events as recorded in the accounting records. For this reason, the use of backflush costing may generate more work than would have been necessary by following a more traditional accounting approach.

Ad

You might also Like

Recommended

Discuss this Article

starrynight
Post 2

@sunnySkys - While backflush costing sort of sounds like it makes sense, I think it's probably more trouble than it's worth.

As the article said, it makes it difficult if you need to do an audit. We all know audits are important if you run a business. Why create a problem for yourself down the road?

sunnySkys
Post 1

I think backflush costing makes sense. It seems like it saves time, at least. If you wait until production is completed before figuring your costs, you'll have all the relevant information in one place.

Plus, it seems like doing costing during production just creates more work. Wouldn't you just have to do it again after production was completed? Also, sometimes unforeseen events happen. If you wait until the end you can factor those events in to the final cost of the item.

Post your comments

exception 'Exception' with message 'error writing captcha: Duplicate entry '2147483647' for key 'PRIMARY'' in /ssd/www/wisegeek/public_html/_core/classes/public/Captcha.php:44
Stack trace:
#0 /ssd/www/wisegeek/public_html/_core/controls/public/ControlDiscussionPostBox.php(324): Captcha->createCaptcha()
#1 /ssd/www/wisegeek/public_html/framework/classes/Control.php(104): ControlDiscussionPostBox->preRender(false)
#2 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): Control->render()
#3 /ssd/www/wisegeek/public_html/tpl/default-nocustom-lu/pages/public/article/article.htm(526): Control->__toString()
#4 /ssd/www/wisegeek/public_html/framework/classes/Control.php(300): require('/ssd/www/wisege...')
#5 /ssd/www/wisegeek/public_html/framework/classes/Control.php(309): Control->requireTpl('pages/public/ar...', Object(PageArticleCom), true)
#6 /ssd/www/wisegeek/public_html/framework/classes/Control.php(131): Control->renderTpl('pages/public/ar...', Object(PageArticleCom))
#7 /ssd/www/wisegeek/public_html/framework/classes/FormDataControl.php(87): Control->renderTemplate()
#8 /ssd/www/wisegeek/public_html/framework/classes/Control.php(109): FormDataControl->renderTemplate()
#9 /ssd/www/wisegeek/public_html/framework/classes/ScriptPage.php(50): Control->render(false)
#10 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): ScriptPage->render()
#11 /ssd/www/wisegeek/public_html/framework/classes/Page.php(97): Control->__toString()
#12 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(443): Page->processRequest()
#13 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(7): PublicFrontController->renderPage()
#14 /ssd/www/wisegeek/public_html/index.php(11): PublicFrontController::run()
#15 {main}