KB: Logging sub-contractors' work - Revision history

Dina at 12:39, 8 July 2020

2020-07-08T12:39:32Z

← Older revision		Revision as of 12:39, 8 July 2020
Line 1:		Line 1:
	=Problem Description=		=Problem Description=
	Working with subcontractors in ~~CommitCRM~~ is best achieved by defining subcontractors as restricted employees and letting them access via ~~CommitCRM~~ Web Interface. In some cases users may consider working with subcontractors by letting them access the system as customers via the Customers Web portal. This alternative is limited and requires more manual management on your side; however, you may find it useful for your needs. [[KB:_Managing_your_Sub-Contractors’_Work\|Click to read more about managing subcontractors]].		Working with subcontractors in RangerMSP is best achieved by defining subcontractors as restricted employees and letting them access via RangerMSP Web Interface. In some cases users may consider working with subcontractors by letting them access the system as customers via the Customers Web portal. This alternative is limited and requires more manual management on your side; however, you may find it useful for your needs. [[KB:_Managing_your_Sub-Contractors’_Work\|Click to read more about managing subcontractors]].
	<br><br>		<br><br>
	When working with subcontractors as customer users, subcontractors enter their work History Notes in ~~CommitCRM~~. You can then convert the History Notes into Charges. Since these Charges are actually entered using your own user, you may need a way to identify charge to know to which subcontractor it belongs.		When working with subcontractors as customer users, subcontractors enter their work History Notes in RangerMSP. You can then convert the History Notes into Charges. Since these Charges are actually entered using your own user, you may need a way to identify charge to know to which subcontractor it belongs.
	<br><br>		<br><br>
	If you need to be able to find out how much time was spent by each subcontractor, you need to keep this information in the Charge or Tickets so you can easily find it later on.		If you need to be able to find out how much time was spent by each subcontractor, you need to keep this information in the Charge or Tickets so you can easily find it later on.

Robert at 10:39, 1 September 2013

2013-09-01T10:39:22Z

← Older revision		Revision as of 10:39, 1 September 2013
Line 1:		Line 1:
	=Problem Description=		=Problem Description=
	Working with subcontractors in CommitCRM is best achieved by defining subcontractors as restricted employees and letting them access via ~~Commit~~ Web Interface. In some cases users may consider working with subcontractors by letting them access the system as customers via the Customers Web portal. This alternative is limited and requires more manual management on your side; however, you may find it useful for your needs. [[KB:_Managing_your_Sub-Contractors’_Work\|Click to read more about managing subcontractors]].		Working with subcontractors in CommitCRM is best achieved by defining subcontractors as restricted employees and letting them access via CommitCRM Web Interface. In some cases users may consider working with subcontractors by letting them access the system as customers via the Customers Web portal. This alternative is limited and requires more manual management on your side; however, you may find it useful for your needs. [[KB:_Managing_your_Sub-Contractors’_Work\|Click to read more about managing subcontractors]].
	<br><br>		<br><br>
	When working with subcontractors as customer users, subcontractors enter their work History Notes in CommitCRM. You can then convert the History Notes into Charges. Since these Charges are actually entered using your own user, you may need a way to identify charge to know to which subcontractor it belongs.		When working with subcontractors as customer users, subcontractors enter their work History Notes in CommitCRM. You can then convert the History Notes into Charges. Since these Charges are actually entered using your own user, you may need a way to identify charge to know to which subcontractor it belongs.

Sheli at 09:47, 7 July 2010

2010-07-07T09:47:57Z

← Older revision		Revision as of 09:47, 7 July 2010
Line 1:		Line 1:
	=Description=		=Problem Description=
	This is ~~an article regarding~~ the ~~logging of work preformed~~ by a subcontractor, ~~and~~ the ~~payment for such work~~.		Working with subcontractors in CommitCRM is best achieved by defining subcontractors as restricted employees and letting them access via Commit Web Interface. In some cases users may consider working with subcontractors by letting them access the system as customers via the Customers Web portal. This alternative is limited and requires more manual management on your side; however, you may find it useful for your needs. [[KB:_Managing_your_Sub-Contractors’_Work\|Click to read more about managing subcontractors]].
			<br><br>
			When working with subcontractors as customer users, subcontractors enter their work History Notes in CommitCRM. You can then convert the History Notes into Charges. Since these Charges are actually entered using your own user, you may need a way to identify charge to know to which subcontractor it belongs.
			<br><br>
			If you need to be able to find out how much time was spent by each subcontractor, you need to keep this information in the Charge or Tickets so you can easily find it later on.
			<br><br>
			This article discusses how to mark Charges or Tickets entered by subcontractors when working with subcontractors as customer Web Users.

	:The Quickbooks link cannot relay subcontractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store subcontractor information and later have a report printed which lists all the tickets, worked on by a certain subcontractor, and if you have paid him for such ticket.

	=Resolution=		=Resolution=
	'''Option 1 - Referencing on the ~~ticket~~ level:'''		'''Option 1 - Referencing on the Ticket level:'''

	~~Since you pay your~~ subcontractor ~~by the~~ '~~''ticket''', we’re going to do this on~~ the ~~'''ticket''' level~~. ~~The second idea is good if~~ you ~~want to pay~~ by the ~~'''charge'''~~.		You can keep the information about the subcontractor's work in the Ticket. This way you can easily track Tickets worked on by a specific subcontractor, and keep for each Ticket details about the work, such as how much time was spent, and whether you already paid the subcontractor for this job.

			To keep this information, you should add or rename some fields in the Ticket, to reference these details.

	~~First we~~ need to ~~Add/~~rename ~~some~~ fields~~. This is done by~~ right-~~clicking a~~ field ~~and choosing '''~~Field Settings~~'''~~. ~~I’d suggest using the Details tab, and renaming fields 1 2 and 3 (providing you’re not using them~~ for ~~something else)~~.		In the example below, three fields (Field 1 – Field 3) are being renamed to reflect the information you need to keep per Ticket. To rename the fields: right-click the field label > Field Settings. See screenshot for example.

	~~Here’s the new~~ fields~~: (please see screenshot)~~		Once these fields have been renamed, you can use them when filtering Ticket lists and report.

	~~::*Field 1 – Subcontractor~~		Note that if you want to actually keep the time spent as a numeric field, so you can sub it up in reports, you may consider adding a new tab to the Ticket (e.g. subcontractor-work), and in this tab add a new numeric-field. [[Field_Customization\|Click to read more about adding new tabs and fields].

	~~::*Field 2 – Time Spent~~

	~~::*Field3 – Paid Yes/No~~

	~~Once these fields have been created, you can use them to filter ticket lists, or to create a printable report, which you can use to log your subcontractor’s pending payments.~~
	----		----
	[[File:subcontractor1.png]]		[[File:subcontractor1.png]]
	----		----
	<br>		<br>
	'''Option 2 – Referencing on the ~~charge~~ level:'''		'''Option 2 – Referencing on the Charge level:'''

			You can keep the information about the subcontractor's work using Charges. This way you can easily track Charges which were performed by a specific subcontractor.

			To keep this information, you should rename a field in the Charge, to reflect this information.

	~~All that needs~~ to ~~be done here is just~~ to rename a field ~~inside~~ the ~~charge creation window~~.		In the example below, the Charge's Field 1 is renamed to reflect the subcontractor information you need to keep per Ticket. To rename the field: right-click the field label > '''Field Settings'''. See screenshot for example.

	~~If you rename field1 inside~~ the ~~charge creation window~~, ~~you’ll be able to link a '''Labor Charge/Expense~~ Charge~~''' to the subcontractor of your choice~~.		Once the field has been renamed, you can use it when filtering Charge lists and report.

	This also will allow you to filter the charges list to only show the charges credited to your subcontractor, or even print a report that you can later use for payment to that contractor. (Please see screenshot)
	<br>		<br>
	<br>		<br>

Sheli: /* See Also */

2010-06-27T08:30:34Z

Reno at 22:11, 20 January 2010

2010-01-20T22:11:58Z

← Older revision	Revision as of 22:11, 20 January 2010
Line 1:	Line 1:
		=Description=
		This is an article regarding the logging of work preformed by a subcontractor, and the payment for such work.

		:The Quickbooks link cannot relay subcontractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store subcontractor information and later have a report printed which lists all the tickets, worked on by a certain subcontractor, and if you have paid him for such ticket.

		=Resolution=
		'''Option 1 - Referencing on the ticket level:'''

		Since you pay your subcontractor by the '''ticket''', we’re going to do this on the '''ticket''' level. The second idea is good if you want to pay by the '''charge'''.



		First we need to Add/rename some fields. This is done by right-clicking a field and choosing '''Field Settings'''. I’d suggest using the Details tab, and renaming fields 1 2 and 3 (providing you’re not using them for something else).

		Here’s the new fields: (please see screenshot)

		::*Field 1 – Subcontractor

		::*Field 2 – Time Spent

		::*Field3 – Paid Yes/No

		Once these fields have been created, you can use them to filter ticket lists, or to create a printable report, which you can use to log your subcontractor’s pending payments.
		----
		[[File:subcontractor1.png]]
		----
		<br>
		'''Option 2 – Referencing on the charge level:'''

		All that needs to be done here is just to rename a field inside the charge creation window.

		If you rename field1 inside the charge creation window, you’ll be able to link a '''Labor Charge/Expense Charge''' to the subcontractor of your choice.

		This also will allow you to filter the charges list to only show the charges credited to your subcontractor, or even print a report that you can later use for payment to that contractor. (Please see screenshot)
		<br>
		<br>
		----
		[[File:subcontractor2.png]]

		[[Category:KB\|SubContractors]]

		<br>
		=See Also=
		[[KB:_Managing_your_Subcontractors’_Work\|Managing your Subcontractors Work]]

Reno: Blanked the page

2010-01-20T22:06:50Z

Blanked the page

← Older revision		Revision as of 22:06, 20 January 2010
Line 1:		Line 1:
	~~=Description=~~
	~~This is an article regarding the logging of work preformed by a subcontractor, and the payment for such work.~~

	:The Quickbooks link cannot relay subcontractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store subcontractor information and later have a report printed which lists all the tickets, worked on by a certain subcontractor, and if you have paid him for such ticket.

	~~=Resolution=~~
	~~'''Option 1 - Referencing on the ticket level:'''~~

	~~Since you pay your subcontractor by the '''ticket''', we’re going to do this on the '''ticket''' level. The second idea is good if you want to pay by the '''charge'''.~~



	First we need to Add/rename some fields. This is done by right-clicking a field and choosing '''Field Settings'''. I’d suggest using the Details tab, and renaming fields 1 2 and 3 (providing you’re not using them for something else).

	~~Here’s the new fields: (please see screenshot)~~

	~~::*Field 1 – Subcontractor~~

	~~::*Field 2 – Time Spent~~

	~~::*Field3 – Paid Yes/No~~

	~~Once these fields have been created, you can use them to filter ticket lists, or to create a printable report, which you can use to log your subcontractor’s pending payments.~~
	~~----~~
	~~[[File:subcontractor1.png]]~~
	~~----~~
	~~<br>~~
	~~'''Option 2 – Referencing on the charge level:'''~~

	~~All that needs to be done here is just to rename a field inside the charge creation window.~~

	~~If you rename field1 inside the charge creation window, you’ll be able to link a '''Labor Charge/Expense Charge''' to the subcontractor of your choice.~~

	This also will allow you to filter the charges list to only show the charges credited to your subcontractor, or even print a report that you can later use for payment to that contractor. (Please see screenshot)
	~~<br>~~
	~~<br>~~
	~~----~~
	~~[[File:subcontractor2.png]]~~

	~~[[Category:KB\|SubContractors]]~~

Reno at 22:02, 20 January 2010

2010-01-20T22:02:06Z

← Older revision		Revision as of 22:02, 20 January 2010
Line 1:		Line 1:
	=Description=		=Description=
	This is an article regarding the logging of work preformed by a ~~sub-contractor~~, and the payment for such work.		This is an article regarding the logging of work preformed by a subcontractor, and the payment for such work.

	:The Quickbooks link cannot relay ~~sub-contractor~~ information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store ~~sub-contractor~~ information and later have a report printed which lists all the tickets, worked on by a certain ~~sub-contractor~~, and if you have paid him for such ticket.		:The Quickbooks link cannot relay subcontractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store subcontractor information and later have a report printed which lists all the tickets, worked on by a certain subcontractor, and if you have paid him for such ticket.

	=Resolution=		=Resolution=
	'''Option 1 - Referencing on the ticket level:'''		'''Option 1 - Referencing on the ticket level:'''

	Since you pay your ~~sub-contractor~~ by the '''ticket''', we’re going to do this on the '''ticket''' level. The second idea is good if you want to pay by the '''charge'''.		Since you pay your subcontractor by the '''ticket''', we’re going to do this on the '''ticket''' level. The second idea is good if you want to pay by the '''charge'''.


Line 15:		Line 15:
	Here’s the new fields: (please see screenshot)		Here’s the new fields: (please see screenshot)

	::*Field 1 – ~~Sub-Contractor~~		::*Field 1 – Subcontractor

	::*Field 2 – Time Spent		::*Field 2 – Time Spent
Line 21:		Line 21:
	::*Field3 – Paid Yes/No		::*Field3 – Paid Yes/No

	Once these fields have been created, you can use them to filter ticket lists, or to create a printable report, which you can use to log your ~~sub-contractor’s~~ pending payments.		Once these fields have been created, you can use them to filter ticket lists, or to create a printable report, which you can use to log your subcontractor’s pending payments.
	----		----
	[[File:subcontractor1.png]]		[[File:subcontractor1.png]]
Line 30:		Line 30:
	All that needs to be done here is just to rename a field inside the charge creation window.		All that needs to be done here is just to rename a field inside the charge creation window.

	If you rename field1 inside the charge creation window, you’ll be able to link a '''Labor Charge/Expense Charge''' to the ~~sub-contractor~~ of your choice.		If you rename field1 inside the charge creation window, you’ll be able to link a '''Labor Charge/Expense Charge''' to the subcontractor of your choice.

	This also will allow you to filter the charges list to only show the charges credited to your ~~sub-contractor~~, or even print a report that you can later use for payment to that contractor. (Please see screenshot)		This also will allow you to filter the charges list to only show the charges credited to your subcontractor, or even print a report that you can later use for payment to that contractor. (Please see screenshot)
	<br>		<br>
	<br>		<br>
Line 38:		Line 38:
	[[File:subcontractor2.png]]		[[File:subcontractor2.png]]

	[[Category:KB\|~~Sub-Contractors~~]]		[[Category:KB\|SubContractors]]

Reno at 15:57, 29 September 2009

2009-09-29T15:57:21Z

← Older revision		Revision as of 15:57, 29 September 2009
Line 1:		Line 1:
			=Description=
	This is an article regarding the logging of work preformed by a sub-contractor, and the payment for such work.		This is an article regarding the logging of work preformed by a sub-contractor, and the payment for such work.
	~~<br>~~
	~~----<br>~~
	The Quickbooks link cannot relay sub-contractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store sub-contractor information and later have a report printed which lists all the tickets, worked on by a certain sub-contractor, and if you have paid him for such ticket.

			:The Quickbooks link cannot relay sub-contractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store sub-contractor information and later have a report printed which lists all the tickets, worked on by a certain sub-contractor, and if you have paid him for such ticket.

			=Resolution=
	'''Option 1 - Referencing on the ticket level:'''		'''Option 1 - Referencing on the ticket level:'''

Reno at 19:02, 9 September 2009

2009-09-09T19:02:54Z

← Older revision		Revision as of 19:02, 9 September 2009
Line 1:		Line 1:
	This is an article regarding the logging of work preformed by a sub-contractor, and the payment for such work.		This is an article regarding the logging of work preformed by a sub-contractor, and the payment for such work.
	~~<br>~~
	<br>		<br>
	----<br>		----<br>
	~~<br>~~
	The Quickbooks link cannot relay sub-contractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store sub-contractor information and later have a report printed which lists all the tickets, worked on by a certain sub-contractor, and if you have paid him for such ticket.		The Quickbooks link cannot relay sub-contractor information when creating charge invoices. So I suggest that we customize the CommitCRM system a bit so that we can store sub-contractor information and later have a report printed which lists all the tickets, worked on by a certain sub-contractor, and if you have paid him for such ticket.

Reno at 19:00, 9 September 2009

2009-09-09T19:00:33Z

← Older revision		Revision as of 19:00, 9 September 2009
Line 40:		Line 40:
	----		----
	[[File:subcontractor2.png]]		[[File:subcontractor2.png]]

			[[Category:KB\|Sub-Contractors]]

← Older revision		Revision as of 08:30, 27 June 2010
Line 42:		Line 42:
	<br>		<br>
	=See Also=		=See Also=
	[[KB:~~_Managing_your_Subcontractors’_Work~~\|Managing your Subcontractors Work]]		[[KB:_Managing_your_Sub-Contractors’_Work\|Managing your Subcontractors Work]]