Recent Posts:

1.37 Release Notes

  • 6 minute read

Hi All This is a fairly major release that we are quite excited about.  I will therefore be putting in a bit more detail about some of the larger features in this release.  The most important aspects are:

  • Support for multiple legal entities and brands - This is a very powerful feature which has now been added. You can now set up a single division in harmony to contain multiple legal entities and multiple brands within each legal entity. See more detail here.
  • Auto-Refresh checkbox on ticket list - An extremely useful piece of functionality which means you can keep support screens open on team boards to see various queues over time
  • Improved customer branding for login page - Add your own logo, twitter feed, headers and footers
  • Ticket communications between Harmony instances - If you have different instances of harmony within your group, tickets can be passed from one system to the other with a reference kept between the two
  • Ticket closed reason list - You can now set up a list of reasons why a ticket is closed and make this mandatory by ticket type
  • Delivery manager schedule initialisation list - The delivery manager for an order now gets his own list of schedule lines which are awaiting intitialisation. He can mark these as ready to start billing which informs finance to start the schedule
  • Ability to generate proposals from Harmony - You can add additional formatted information to your product list and have Harmony auto generate a full proposal document when creating quotes for clients
  • Many other small improvements such as improved full text search, quick create links etc.
RefNumber Type Name
#20131014.1 Bug Incorrect value on invoice line when partial release by value
#20130925.36 Feature Ability to parse external ref out of email content
#20130923.16 Bug Next Numeric Value setting is incorrect
#20130918.26 Bug Missing EndCustomer
#20130918.18 Feature Auto refresh checkbox on ticket list
#20130918.11 Feature New 'Today' date range for date filters
#20130917.33 Feature Add opportunities to the full text search
#20130916.19 Bug An entity of type 'TicketType' with Id missing
#20130916.7 Bug Add addtional stop words to lucene
#20130912.3 Bug /PaymentObligation/ViewPaymentObligation - Object reference not set to an instance of an object.
#20130911.1 Bug /ResponsibilitiesTransaction/PermanentlyAssignAll - String or binary data would be truncated.
#20130910.13 Feature Cross account movement report
#20130910.11 Bug Mobile: Create Ticket Save Button allows multiple clicks
#20130909.11 Bug Mobile: Second blue button titled True
#20130909.10 Bug Resources > Employees > Responsibilities > Follow Up doesn't show resposibilities for complete tasks
#20130906.11 Bug Error saving addresses for companies and users
#20130904.9 Feature Add specific functional operation for terminating schedules
#20130903.6 Feature Ticket Grid: Updated By Column
#20130903.2 Bug /BusinessData/GetTaskDetails - The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.
#20130830.10 Bug Times on Email History
#20131008.2 Feature Indexation on schedules
#20130828.9 Bug Contact Title issue with Upload
#20131004.23 Feature Ability for delivery manager to tell finance when a schedule can start being billed
#20130828.7 Feature Mandatory contacts on ticket
#20131003.21 Feature Quick Create dropdown in header
#20130809.2 Bug Support Manager ticket emails
#20130731.15 Feature Schedules: Add Estimated time to Tickets grid
#20130926.5 Bug Ability to archive account codes
#20130717.9 Bug Removing lines from a credit note
#20130925.39 Feature Checkbox on ticket type for Default Visible To Customer
#20130711.9 Feature Automatically set the status on a ticket after first public comment
#20130925.38 Feature Swap team and assigned to on ticket
#20130705.6 Feature Date list on contract renewal screen not right
#20130628.7 Feature Multi-entity division
#20130924.10 Bug Removing Users
#20130613.4 Feature Please remove option to delete private comments
#20130923.26 Feature Copy asset reference over when cloning tickets
#20130923.20 Feature Ability to have a Closed Reason list
#20130515.9 Feature Change how time budgets are created and used for fixed price ps
#20130923.18 Bug Attribute tree on asset lookup should only be showing branches where a leaf exists
#20130416.4 Bug Assigned to field on Notes
Read More

Supporting diverse organisational structures across the IT industry

  • 2 minute read
Ours is an industry where mergers and acquisitions are a common-place growth mechanism, the result is a plethora of different organisational structures, each with their specific requirements in terms of systems, data management, branding and accounting.

In this post I take a broad-based look at the common organisational structures within the IT industry. Looking at the advantages and disadvantages of each and explaining how we have developed HarmonyPSA, business automation software, to support IT businesses of every configuration.

Multi-divisional organisational structure

Multi-divisional means that there is one parent company, and that parent company owns smaller companies that use its brand and name. The whole organization is ultimately controlled by central management, but many decisions are left to autonomous divisions.

A multi-divisional instance of Harmony can support transfer pricing arrangements and separate base accounting currencies for each division. However, under this system there can be no cross division of projects, users must work in a single division.

Multiple legal entities within one division

Often resulting from acquisition, many IT businesses have a structure that includes a number of separate legal entities, these would normally be marketed under distinct branding and may require separate account journal exporting for financial reporting.

Harmony can now support multiple legal entity operations from a common instance.  This gives the flexibility to manage a single customer account across subsidiaries, increasing opportunities to cross-sell and allowing projects to be delivered across the division, taking advantage of efficiencies where possible whilst retaining the separate brand identities and fulfilling financial reporting requirements.

CTO Steve Powell says “We have included this feature in response to a number of customers who operate in this way.  Operating multiple legal entity businesses with a single organisation and management team is tough with conventional solutions that tend to split the world down legal entity lines.  Harmony allows users to define product lines that are tied to their operating entities but cross-sell and cross-deliver projects with ease.  This addresses a core problem in an industry that is built on acquisition”

Multi-brand structure

Multiple branding is commonly used to differentiate products produced by the same company. Multiple brands can be supported by Harmony.  All documentation and outbound customer communication produced by the system can be set up to reflect the company brand name through which the respective products or services were purchased.

We think we have got it covered but it is always great to receive feedback so please share your thoughts and questions or get in touch via

Read More


Recent posts

Subscribe to our blog