Limitations Of Accounting Products That Integrate With Ostendo

Limitations Of Accounting Products That Integrate With Ostendo

Occasionally Development-X is asked for comments on which accounting software would be most appropriate for an Ostendo site. Development-X cannot promote any one accounting software package, however below we have endeavoured to highlight limitations we have identified so far when specific accounting software is used with Ostendo. The selection of the most appropriate Accounting Software solution should be made on the basis of suitability for your client along with taking into account the limitations as shown below. The criteria for selecting Accounting Software is somewhat different to that of Operational Software, therefore we would advise any ‘non accounting’ Partners to source the appropriate information from a specialist in this field.


MYOB AccountRight Live
  1. Can only use Ostendo Header Tax Rounding Rules when AR Posting Style is set to Journals
  2. A problem with MYOB GST Cash Report (Summary and Detail) This MYOB report cannot handle (Does not produce results) transactions posted in MYOB without Tax Codes. NB: This is not only restricted to those transactions posted from Ostendo, but also any transactions posted in MYOB without Tax Codes.
  3. Maximum 8 character Invoice Number
  4. Credits Applied in MYOB cannot be read back by Ostendo, therefore a Match Credit To Invoice Payment needs to be processed in Ostendo to remain in sync
  5. Consolidated Tax Codes are not available to the API, therefore transactions with these Tax Codes cannot be passed through to MYOB without erroring. Therefore a workaround is required. Refer "Consolidated Tax" Knowledge Base Article

Xero
  1. Cannot Use Ostendo Rounding Of Invoice Header Tax Rules
  2. Xero API does not allow the application of AR Credits to Invoices to be read back as payments into Ostendo
  3. Must use a Bank Clearing Account and Rules in Xero if Ostendo Customer Payments or Deposits are used as Xero does not allow direct journal posting to Bank Accounts
  4. There are transactional volume limitations within Xero that should be considered. Xero is promoted as a ‘Small Business Accounting Package’, therefore not suitable for high volume transactions. In the case of high volume sites it is suggested that Posting Daily Summaries are implementation
  5. Credits Applied in Xero cannot be read back by Ostendo, therefore a Match Credit To Invoice Payment needs to be processed in Ostendo to remain in sync

MoneyWorks
  1. Cannot Use Ostendo Rounding Of Invoice Header Tax Rules
  2. Credits Applied in MoneyWorks cannot be read back by Ostendo, therefore a Match Credit To Invoice Payment needs to be processed in Ostendo to remain in sync
  3. MoneyWorks API does not accept Foreign Currency Customer Payments made through Ostendo. These payments must be processed directly through MoneyWorks thereby allowing Ostendo to read back and update the Invoice as paid. NB: This only applies to Foreign Currency Customer Payments only.

Quickbooks Online (QBO)
  1. An API issue has been identified when a Purchase Invoice contains a mixture of + and - extended value lines. The API recalculates the transaction total potentially leading to a difference between Ostendo and QBO. This requires the user to manually amend the Purchase Invoice in QBO to ensure it balances to the total entered in Ostendo. Sales Invoices with a mixture of + and - post correctly.


QuickBooks (Reckon R2 and above)
  1. No Foreign Currency Capability
  2. If GST basis is ‘Cash Immediate Sales’ (Payments Basis) you must run a combination of GST reports and settings in QB’s in order to report the correct GST Inputs and Outputs values.
  3. QB’s Supplier Name only allows 41 characters
  4. Requires a separate posting application to post financial transactions from Ostendo