Plunet 6.2 to 6.3 to 7.0

Share with
Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Buffer this pageEmail this to someone
Richard Sikes
Multilingual January/February 2017
Product Reviews

Plunet’s long history in standalone translation business management software is an advantage and a disadvantage. The product has reached a state of robustness and maturity that is unrivaled within the segment, and the company has benefited from customer input extending over years. On the other hand, aspects of Plunet’s user interface (UI) have been a source of criticism even among long-time proponents of the software. Newer entrants to the market have had the advantage of learning from Plunet’s design. This has allowed them to create intuitively compelling user interfaces. But, let’s not fall into the trap of judging a book only by its cover....

Since Plunet’s early versions, subsuppliers such as freelancers could use their portal access to create their invoices directly using project data. From the perspective of project data consistency, this practice is useful. But it rests on an assumption that isn’t necessarily real-world, which is that the external providers work exclusively for one company. Many, if not most, such providers have multiple customers. Therefore, they can’t conveniently use Plunet as their central invoicing system, especially in taxation environments that strictly enforce numerical consistency for invoices. The 7.0 release gives suppliers freedom to use Plunet to upload invoices generated by other applications (Figure 2). This freedom keeps invoicing information, even from an external application, together with the underlying project data, so it’s easier all around for resources in the payment chain. The new right also allows providers to delete invoices that they have created. Previously, if an invoice was created by a provider within Plunet, they had no ability to delete it, for example, if they made a mistake. A project manager had to do so.

The 7.0 release includes a new template that simplifies cumulative invoices. This functionality is helpful to LSPs that invoice once per month for multiple orders. It’s accomplished by new flags that enable invoicing templates to accumulate order totals onto a single invoice without the corresponding line item detail. Previously, only experienced template builders could create this functionality, and it was quite kludgy, to say the least. The new, consolidated invoicing format greatly reduces invoice page counts. The old format remains available if more detailed invoices are required....


Share with
Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Buffer this pageEmail this to someone