Xero Transaction Rate Limits



Please note that Xero has certain transaction limits. This link explains the current Xero Limits:

 

https://developer.xero.com/documentation/oauth2/limits



Essentially the following limits at a Tenant (Xero Organisation) level are managed by Ostendo as follows:


  • Concurrent Limits: 5 calls in progress at one time: This is managed automatically by the design of Ostendo's integration script as Ostendo will only make one call at a time during the posting process. (ie: no concurrent calls are made)
  • Minute Limit: 60 call per minute: This is managed automatically by Ostendo's integration script which will delay the processing of a batch during the posting process by one minute if this limit is breached.
  • Daily Limit: 5000 calls per day: Each Batch posting records the number of API calls along with the number of daily calls remaining. If this limit is breached, Ostendo will stop processing the batch. Users will then be required to wait 24 hours (for a reset of this limit) before the batch can be re-posted.



We have also done the following to minimise the chances of exceeding these limits:

 

To reduce the number of calls we make to Xero when exporting customer and supplier records, we bundle 100 records at a time. However each request cannot exceed 3.5MB (size limit per call). 


The 5000 API calls limit is a “rolling 24 hour period”. So if API calls are spread out evenly then it would be less of an issue. We have provided in Systems Settings the function to set the frequency of posting. If you have high transaction volumes, you may need to set a more regular posting frequency (perhaps hourly or every 30 mins).



The Total number of API calls per batch, along with the Daily Limit Remaining are displayed for each batch in the Journal Posting screen(File-> General-> Inquiries-> Inquiry Journal Posting)  and also included in each batches Debug file.




Should your organisation be consistently breaching the Xero Daily API Limit, it is suggested you consider summarisation of journals from Ostendo. This will substantially reduce the volume of traffic through the Xero API. 



You should also be familiar with Xero’s  SYSTEM LIMITS as described in the link above:


  1. Xero is designed for volumes of up to 1,000 Sales invoices (Accounts Receivables) and 1,000 Purchases bills (Accounts Payables) per month, dependent also on the frequency of invoicing during the month, variability of amounts and the frequency of sales tax reporting requirements. 
  2. Using Xero to handle Inventory of more than 1000 items may cause performance issues, therefore using Ostendo to handle inventory will minimise the transactions problems. 
  3. Storing more than 5000 Contacts (suppliers + customers + employees) in Xero could also cause performance issues. 



There are also Pricing Plan limits – which determines the number of Invoices that can be processed by Xero in a month.


Your Ostendo Consulting Partner will guide you through the most appropriate method to adopt.