Skip to main content
Solved

Multiple Sales and COGS GL Accounts one Inventory Item

jaymarzian
Varsity I
Forum|alt.badge.img

Hey folks,
Got a question:

Let’s say a customer is selling a stock item in 2-3 different contexts:
     a. Over-the-counter item sold at the store (has it’s own account for COGS and Sales).

     b. Same item sold in the context of a service call to a customer  (has it’s own account for COGS and Sales).    

     c.  Item provided as a warranty item or according to a contract (has it’s own account for COGS and Sales).

As far as revenue and cogs go, how does the system know where to allocate those two transactions for the same part in inventory in different scenarios?  Can you have just a single inventory item that can be used in different contexts without having to manually change the GL entries each time?

Best answer by lbarker

You can use Reason codes.  The sales account can come from the reason code.  

Maybe have multiple sales order types too maybe to help identify reason codes.  There is a customisation on Github to make a default by type

https://github.com/Acumatica/SalesOrderTypeDefaultReasonCode

OR

Perhaps consider using e customer location.  You can have locations on every customer for WARRANTY / COUNTER / SERVICE which you can auto add using a business event when a customer is added, but this is for all items sold on the sales order.  Just depends on if its related to the item or the entire order

 

Is subaccounts not rather a solution than using different GL codes?  They can report on the subaccount or even branches which could be warranty / counter /service rather

 

View original
- John
Did this topic help you find an answer to your question?

lbarker
Varsity III
Forum|alt.badge.img+1
  • lbarker
  • Varsity III
  • January 12, 2024

You can use Reason codes.  The sales account can come from the reason code.  

Maybe have multiple sales order types too maybe to help identify reason codes.  There is a customisation on Github to make a default by type

https://github.com/Acumatica/SalesOrderTypeDefaultReasonCode

OR

Perhaps consider using e customer location.  You can have locations on every customer for WARRANTY / COUNTER / SERVICE which you can auto add using a business event when a customer is added, but this is for all items sold on the sales order.  Just depends on if its related to the item or the entire order

 

Is subaccounts not rather a solution than using different GL codes?  They can report on the subaccount or even branches which could be warranty / counter /service rather

 

meganfriesen37
jaymarzian
2 people like this
  • meganfriesen37
    meganfriesen37
  • jaymarzian
    jaymarzian
jaymarzian
Varsity I
Forum|alt.badge.img

@lbarker Wanted to say thank you for your response.  I was able to implement a solution using Reason Codes for Sales Accounts for my customer.   I would love for them to utilize subaccounts for both sales and cogs, but they do not want to do that.   Anyway, they were pleased with the Sales account solution.  Thanks again!

- John
lbarker
Chris Hackett
2 people like this
  • lbarker
    lbarker
  • Chris Hackett
    Chris Hackett

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved