Skip to main content

Engineer-to-Order Manufacturing Projects and Percentage of Completion Accounting

  • October 17, 2025
  • 3 replies
  • 104 views

PaulMainard55
Captain II
Forum|alt.badge.img+3

Hi Community,

Many of our manufacturing clients are ETO shops who are incorporating Project Accounting (or Professional Services) with Manufacturing.  Do to the nature of the ETO manufacturing, the client is often required to recognize revenue using the Percentage of Completion method, per their CPAs.

We love that manufacturing and (formally) project accounting are integrated, but from an accounting perspective it feels as though cost accounting for manufacturing and project accounting couldn’t be further apart, and I’m struggling as to the best way to leverage the best of each feature set to achieve the client’s accounting goals.  

To illustrate, in manufacturing (and in a full-absorbtion cost accounting paradigm) the costs of each production order are capitalized to WIP Inventory on the balance sheet until the production order is complete.  Upon completion the accumulated manufacturing costs are placed in FG Inventory until the goods are “sold” and “shipped” to the customer.  Therefore no COGS are recognized until shipment.

Accounting for Long Term Projects requiring percentage of completion accounting, as is typical in construction, all direct costs are expensed immediately thoughout the project.  The costs do not go into WIP on the balance sheet, but go directly to the P&L.  At the end of each reporting period (i.e., EOM), the Project Managers review the project costs against the budget, determine whether the project is on track to remain on budget, or if the projected costs at completion should be adjusted.  After the analysis is completed and the projected costs have been adjusted, most clients would run their WIP report to determine their corresponding “Billings in Excess of Costs” (Liability) and “Costs in Excess of Billings” (Asset) amounts and book an accrual to these accounts to adjust their revenue recognition. (Note - this assumes that all progress billings are booked to revenue, and not customer deposits).  

My question to the community to those that are working in this space is, how do you square the circle?  On one hand, your executing production orders and accumulting costs there.  On the other, you may (or should have) project costs, and progress or milestone billing, that you’re accumulating. 

As best as I can tell, Acumatica’s Project WIP report only compares project “Expense” balances to Projected Costs at Completion to measure earned revenue.  Given this limitation, how are others configuring the system to put manufacturing costs directly to COGS?  Are you mapping WIP to COGS in your Order Types, for example?  If so, what challenges do you face upon closing out the production order?

Given the matching principle requirements, it seems that booking manufacturing costs directly to COGS (as opposed to WIP) is correct from an accounting perspective.  With that said, it feels like given the accounting mechanics of labor, and overhead absorbtion, along with the transfer of costs from WIP to Inventory, the accounting can get a bit messy and convoluted (just like this post).  

I’d be very curious as how partners and other end-users are solving this.  My sense is that many are leaving some of the system’s features and functionality on the table, and are using work-arounds, or are calculating revenue outside of the system.  

If you’ve made it this far, I would love to connect and get your thoughts on this conundrum.  

Tagging ​@Chris Hackett and ​@angierowley75 in hopes you can help track down other product managers, SMEs and/or users who have faced similar challenges.  

Thanks for your indulgence.

3 replies

Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • November 4, 2025

Anyone have input for ​@PaulMainard55? 😀


PaulMainard55
Captain II
Forum|alt.badge.img+3
  • Author
  • Captain II
  • November 5, 2025

Thanks ​@Chris Hackett.  ​@angierowley75 suggested that we reach out to ​@joelhoffman as this issue seems to be more aligned with clients in this space (MFG and Project).  ​@joelhoffman - if you want to slide into my DMs I would love to discuss this with you further.  I think I have some solutions that will get me part of the way home, but would love to get your perspective on this.  


PaulMainard55
Captain II
Forum|alt.badge.img+3
  • Author
  • Captain II
  • January 20, 2026

Hi Community,

I figured this one out on my own. I decided to use a combination of Allocation Rules, Account Groups, Contra-Asset accounts, and Expense Accrual accounts in the solution.  

First Principles…

  • Maintain integrity of WIP and Finished Goods inventory.  These are control accounts which should be reconciled monthly.  This means no direct recognition of Project-based costs intended for manufacturing, including the consumption of Direct Materials, Applied Direct Labor, and Applied Manufacturing Overhead.  Those costs, whether added to WIP, or transferred to FGs inventory must remain until the production order is complete, or when finished goods are shipped to the customer.
  • Strict Adherence to the Matching Principle.  Direct costs, or COGS, must be matched against the revenue being recognized.  In percentage-of-completion based revenue recognition, direct costs (when used - as opposed to actual Direct Labor hours) are compared to projected cost to complete in order to estimate the recognizable revenue for a project, as an objective way of arriving at percent complete.

These two concepts are contradictory to one another as project-based manufacturing generates project-related costs, while also traditionally considered to be an asset, which is booked to a natural control account.  In the meantime, the WIP costs being incurred should also support, not only the calculation of revenue, but also recognized as an expense to meet the matching principle of accounting.  So - the question is, how can we have our cake, and eat it too (from an accounting perspective)?

Here’s what we did.

First, we established separate accounts for “Manufactured Finished Goods Inventory” along with the required WIP inventory accounts.  Each of these accounts were assigned to specific Account Groups so they could be included in our project accounting model.  

Second - We created two new accounts, each with its own account group:

  • MFG WIP Applied to COGS (Contra Inventory Asset Account)
  • Accrued COGS from Manufacturing (COGS Expense) account.

Now that we have these accounts, we created an allocation rule that finds and aggregates all project-related WIP and FG transactions (debits and credits), and records an accrual that debits Accrued COGS and credits the applied MFG WIP.  

What we like about this design is that it requires no allocation reversal.  The reason is as follows:

  • Costs allocated to WIP (Debit) by way of production orders is where the process begins.  As costs flow into WIP, the allocation rule, which should be run monthly, finds those costs and books the accrual.
  • WIP costs flowing into FGs (DR Finished Goods; CR WIP), theoretically generates a net-zero adjustment to Applied WIP and Accrued COGS.  
  • The shipment of FGs to the customer (DR COGS; CR FG), when run through the allocation, debits Applied WIP and credits Accrued COGS, effectively clearing the accrual activity, resulting in the final actual COGS resulting from the shipment of goods.  

The activities from the first two bullets allows us to recognize COGS as period costs.  Since they are hitting the project as expenses by way of allocations, they can be used in the numerator for the percentage of completion calculation in the WIP report, which in turn, will support the recognized revenue calculation.  Simultaneously, the costs are then matched with the revenue, meeting the matching principle requirement.  

@angierowley75 and ​@joelhoffman - I think this is a solid approach for meeting revenue recognition requirements for project-based manufacturers who must incorporate percentage of completion revenue recognition in accordance with ASC 606.