TransPost Version 3.3.3 - Release Notes

Note: All these changes have also been applied to version 3.3.3 of TransPost Plus, TransPost Premier and TransPost Express

Retry and timing changes

These changes are designed to reduce the impact of errors arising from connectivity issues:
  • Communication errors in AccountRight Live
  • ODBC locking, arising from changes to Classic AccountRight 19.13
While we are in no position to fix issues arising from MYOB AccountRight these changes should alleviate these issues and reduce the incidence of such problems.

New import fields

There are many really useful applications which output data for accounts but not in the exact mix of fields required by AccountRight. Data input to the new TransPost fields will be transformed into the appropriate form for AccountRight.
  • CompanyName and LastName

    Classic MYOB accepts Company Name and Last Name via the same CoLastName field but many systems supply two separate fields.

    TransPost will now accept CompanyName and LastName from different columns and pass both on to Classic MYOB as CoLastName where appropriate.

    For AR Live it will also continue to searching for cards on the basis that anything mapped to CoLastName could match either Company Name or LastName.

    When importing card data there is now a specific IsIndividual field where previously it was derived from the existence of data in FirstName. (This will be ignored for Classic MYOB which does not accept this input.)

  • Discounts

    Many applications record discounts as an amount rather than a percentage. The new DiscountAmount field will be used to calculate the discount percentage to be input into AccountRight.

    In some circumstances a discount is indicated by providing a non-discounted price with a discounted line total. In other situations a discrepancy might indicate an error. The new CalculateDiscount field will control how such a discrepancy will be treated. If it is 'Y' then the discrepancy will cause calculation of a discount rate. Otherwise such a discrepancy will be recorded as an error and the transaction rejected.

  • Shipping Address fields City, State,Postcode and Country

    Some systems output shipping address as Line 1. Line 2, City, State, Postcode and Country (or fields equivalent to these). When importing sales and Purchases AccountRight accepts the fields AddressLine1,AddressLine2, AddressLine3 and AddressLine4. TransPost will now convert City, State, Postcode and Country into lines so that what is then passed on to AccountRight is the expected 4 address lines.

  • Payee fields City, State, Postcode and Country

    Similarly Payee might appear as as Line 1, Line 2, City, State, Postcode and Country (or fields equivalent to these). When importing Payments AccountRight accepts the fields PayeeLine1,PayeeLine2, PayeeLine3 and PayeeLine4. TransPost will now convert the appropriately mapped Payee City, State, Postcode and Country into lines so that what is then passed on to AccountRight is the expected 4 payee lines.

Payment Refunds and Reversals

When processing receipts and payments a negative amount is taken to indicate a reversal.

For Customer Payments, the search for the invoice to apply the payment to is normally restricted to open invoices and orders, starting with the oldest invoice that matches the payment criteria.

If the payment amount is negative TransPost will open the search to include closed invoices.

Tax Codes

Within a session TransPost now only retrieves details of a Tax Code once and then remembers it. Apart from the advantage performance-wise this also pays in dealing with consolidated tax codes in AccountRight Live.

AccountRight Live & Consolidated Tax Codes

The Accountright Live API does not directly retrieve details of consolidated tax codes so input of data containing such tax codes is a problem as the UID (identifier) is not easily available. Essentially this means that if you import sales data referencing a tax code such as 'GW' (consolidated WEG & WET) the transaction will fail because the UID for 'GW' is not available.

This problem may be mitigated by using at least some Item codes which have the consolidated code as 'Tax Code when sold' as the UID is supplied with Tax Code when retrieving details of an Item. If the sale data references and Item Number which has 'GW' as is tax code when sold then the Item data contains the UID for the tax code 'GW'.

TransPost will remember the relationship between a Tax Code and its UID for the remainder of the session so that any subsequent input that refers to that tax code will then work.

Classic AR - Tax Calculations

Classic AR requires input of both Ex-tax and Inc-tax amounts. If only one of those is provided TransPost will calculate the other. This calculation in the past was only applied if the tax code was of the Tax Type "Goods & Service Tax" (which includes 'GST', 'FRE' and in NZ 'S15' & 'Z').

This calculation has now been extended to sales tax types such as 'WET' and also to derived Consolidated Tax codes such as 'GW'. This enables the processing of wholesale wine sales where only one of Inc-tax and Ex-tax amount (or price are provided).

For wholesale wine sales where the Item details recorded have the correct Tax Code and ex-tax or Inc tax price, the only data required to complete the calculations , apart from the Customer and Item Number is the quantity. The item price and tax code will be retrieved from the Item details in MYOB and everything else will be calculated appropriately.