Billing Lifecycle

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Revision as of 09:11, 3 August 2009 by Yarden (talk | contribs) (Created page with 'The following is a common work flow which may be used in your business when working with Commit: '''I: Log a problem'''<br>When a customer reports a problem, open a Ticket in C…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The following is a common work flow which may be used in your business when working with Commit:


I: Log a problem
When a customer reports a problem, open a Ticket in Commit

->

II: Solve the problem
Handle the Ticket remotely (e.g. by the phone or remote control) or by dispatching a technician for an onsite visit

->

III: Log the work done (Charging)
Log Charge records for the time spent, work performed or parts used in order to solve the problem (resolve the Ticket)

->

IV: Billing
Bill the customer for the relevant Charges recorded (unless covered by a contract)


The work flow explained in this document focuses on the Charging phase (III) and the Billing phase (IV).

Alternative Work Flows

The flow above assumes you will be working with Tickets in order to report on a customer issue.


Alternatively, it is possible to add Charges for an Account (customer) directly in the Account or Contract (see Using Contracts). This can be helpful in certain cases, such as, when a customer visits your office/repair shop and purchases products or parts, or where you offer consulting services and need to track the time spent on consulting.

Alternative Work Flows

Alternative Work Flows

Alternative Work Flows

Alternative Work Flows