Revision history for HowToSetupServiceBusiness


Revision [1373]

Last edited on 2009-02-03 14:08:37 by PatClay [typo fix]
Additions:
There is some criticism that entry of an order is unnecessary for a service based business. However, whilst we are required to enter an order in webERP, the invoice is only a few click exercise once the order is entered - there is no duplication of input at all. Many service based businesses agree up front on the scale of charges and the brief for the work - the order allows this to be recorded. Similarly, service based businesses often need to quote for their work before it is accepted. The same logic in webERP is therefore advantageous ... in my view!
Deletions:
There is some criticism that entry of an order is unnecessary for a service based business. However, whilst we are required to enter an order in webERP, the invoice is only a few click exercise once the order is entered - there is no duplication of input at all. Many service based businesses agree up front on the scale of charges and the brief for the work - the order allows this to be recorded. Similarly, service based businesses often need to quote for their work before it is accepted. The same logic in webERP is therefore advantages ... in my view!


Revision [1358]

Edited on 2009-01-30 11:31:53 by PhilDaintree [typo fix]
Additions:
With this option flagged to allow narrative, on each order entry line a text field will allow entry of up to 255 characters of text to describe what it is that was achieved with the service/consultancy work your business provided. The narrative entered here in the order will be shown on the invoice.
There is some criticism that entry of an order is unnecessary for a service based business. However, whilst we are required to enter an order in webERP, the invoice is only a few click exercise once the order is entered - there is no duplication of input at all. Many service based businesses agree up front on the scale of charges and the brief for the work - the order allows this to be recorded. Similarly, service based businesses often need to quote for their work before it is accepted. The same logic in webERP is therefore advantages ... in my view!
Deletions:
With this option flagged to allow narrative, on each order entry line a text field will allow entry of up to 255 characters of text to describe what it is that was acheived with the service/consultancy work your business provided.


Revision [1357]

Edited on 2009-01-30 11:26:03 by PhilDaintree [typo fix]
Additions:
You might make an item say for "Computer consultancy" and another for "webERP support" the units might be in hours or other unit you charge for consultancy in.
Pricing for a unit of the service/consultancy item is much the same as any other item - you can price in different currencies and have prices for different customers etc. See the manual on pricing.
Often when you invoice service items you need to provide a description of what the order was for and this can often be several lines - you will not wish to go through changing the item description every time - it is too short anyway and will not show correctly on old invoices that had a different description. The answer is to use the feature that allows free-form narrative against each line item ordered/invoiced. This feature is accessed from Setup -> Configuration Settings
{{image class="center" alt="Line Item Narrative" title="Line Item Narrative" url="uploads/ScreenShotUploads/LineItemNarrative.jpg" }}
With this option flagged to allow narrative, on each order entry line a text field will allow entry of up to 255 characters of text to describe what it is that was acheived with the service/consultancy work your business provided.


Revision [1356]

Edited on 2009-01-30 11:14:42 by PhilDaintree [typo fix]
Additions:
{{image class="center" alt="Set Up Service Item" title="Set Up Service Item" url="uploads/ScreenShotUploads/ServiceItemsSetup.jpg" }}


Revision [1355]

The oldest known version of this page was created on 2009-01-30 11:07:23 by PhilDaintree [typo fix]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki