Settings and activity

7 results found

1. <CurrencyCode> in invoices endpoint is ignoring lower case currency code

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accounting API » Invoices  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Peter McCarroll shared this idea  ·  Jun 7, 2015

2. integrate batch payment export into a banks payment system

   11 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Accounting API » Banking  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Peter McCarroll supported this idea  ·  Jan 6, 2015

3. Recurring Direct Debit Invoices

   12 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  New Integrations » Payment Systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   An error occurred while saving the comment
   Peter McCarroll commented  ·  Dec 18, 2014  ·  Edit…  ·  Delete…

   For those interested in processing pre-authorised Direct Debit or Credit Card transactions based on your Xero invoice due date please check out [url=http://www.ucollect.biz]uCollect[/url].

   Right now (Dec 2014) it has facilities for Direct Debits for NZ Banks (BNZ, ANZ, Westpac & ASB), Direct Debits using generic ABA file in Australia, and EziDebit. Coming soon will be Stripe, eDebit, eWAY, SEPA Direct Debits, DPS (NZ) and Authorize.net.

   Save Submitting...

4. sales tax report

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accounting API » Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Peter McCarroll supported this idea  ·  Nov 18, 2014

5. Allow third party apps to plug into the Xero interface

   34 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   7 comments  ·  Accounting API » General Requests  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   under review  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   It is certainly a nice idea in a lot of ways, and Jesse’s use case example is good one.

   On the other side, allowing 3rd party applications plug into the core Xero application present some quite major security implications. The data we hold on behalf of our customers is considered highly sensitive by us and we ensure we have bank level security across all aspects of our application.

   Second to that, we are a design lead and focused company – we want our software to be really easy to use and remain simple and intuitive, so allowing 3rd parties to introduce interface elements into Xero would be something we would need to carefully plan for.

   With this in mind, it would be quite an onerous task for us to implement a secure framework that would allow 3rd party applications to interface within Xero, in a sensible way that does not detract from the UI.

   It could still be a worthwhile project though – I’d encourage those interested to keep voting for it and also to please leave a comment about your particular use case – this will help inform our decision making.

   Ronan

   It is certainly a nice idea in a lot of ways, and Jesse’s use case example is good one.

   On the other side, allowing 3rd party applications plug into the core Xero application present some quite major security implications. The data we hold on behalf of our customers is considered highly sensitive by us and we ensure we have bank level security across all aspects of our application.

   Second to that, we are a design lead and focused company – we want our software to be really easy to use and remain simple and intuitive, so allowing 3rd parties to introduce interface elements into Xero would be something we would need to carefully plan for.

   With this in mind, it would be quite an onerous task for us to implement a secure framework that would allow 3rd party applications to interface within Xero, in a sensible way that does not… more

   Peter McCarroll supported this idea  ·  Nov 14, 2014

6. Reconcile via the API

   279 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   243 comments  ·  Accounting API » Banking  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   declined  ·  AdminKelly (Admin, Xero Developer Centre) responded

   Thank you for the continued feedback and for your patience on this long‑running request. We know that programmatic bank reconciliation and AI‑driven workflows are increasingly important to many of you, and we understand the frustration that this capability is not available via the Xero API.

   
   

   After reviewing this again with our legal, risk and banking teams, we have confirmed that we will not be adding the ability to reconcile bank statement lines via the API or to expose unreconciled bank statement data via the public API.

   
   

   There are a few key reasons for this decision:

   1. Regulatory and contractual obligations on raw bank data. Unreconciled bank statement lines are “raw” banking data – unmodified information that comes directly from banks. In markets such as Australia, this data is treated as banking data under consumer data rights regimes. Sharing it on to third parties (including via an open API) would require us to treat every consuming app as if it were a regulated data recipient, with substantial security, accreditation and liability obligations that sit on Xero as an intermediary as well as on those third parties. We have taken a policy decision not to operate as an intermediary for redistributing raw bank statement data.This ensures that the highest standards of banking security are maintained directly between the customer and their financial institution.
   2. Our data‑sharing boundary: unreconciled vs reconciled data. We draw a clear line between:

   • Unreconciled statement data, which is banking data supplied to us by banks and subject to the obligations above; and
   • Reconciled transaction data, which has been improved within Xero (for example, matched to contacts, invoices or accounts) and for which Xero is the custodian on behalf of the customer.

   1. We can expose certain reconciled/derived data through specific endpoints such as the Finance API’s Bank Statements Plus in limited, finance‑focused scenarios, but those endpoints are not designed or licensed for broad, high‑volume access to raw bank feeds or for third‑party replication of Xero’s bank reconciliation engine.
   2. Why “reconcile via the API” falls on the wrong side of that line. Supporting full reconciliation via the API would, in practice, require programmatic access to unreconciled statement lines and a way to push reconciliation decisions back into Xero. That would effectively recreate bank reconciliation workflows outside Xero while still relying on Xero to redistribute raw bank data, which is exactly the pattern our regulatory, security and contractual constraints are designed to avoid. For these reasons, this is not something we can safely or responsibly offer as an open API capability.

   
   

   We recognise that a small number of existing partner applications continue to receive limited access to certain statement data under legacy, contract-specific arrangements that pre‑date this policy. These specific arrangements are strictly managed under heightened security and compliance terms. To ensure we meet our current regulatory and risk standards, we are not extending these legacy permissions to new partners or applying them to any new use cases.

   
   

   We also hear the concern that “this is customer data and customers should be able to use it where they choose”. We agree that customers should have access to their own banking information, and open banking frameworks are designed to give customers direct access to that data from their bank or banking aggregator, without Xero sitting in the middle as a redistributor. For apps that need raw bank statements to power AI or other automation, the right pattern is to source that data directly from the bank or an accredited open‑banking provider, and then connect into Xero using the data structures we do expose.

   
   

   Our strategy for bank reconciliation is to invest in automation inside Xero, where we can manage risk, performance and user experience end‑to‑end. That includes features such as bank rules, suggested matches, cash coding, and newer improvements like statement-period bank reconciliation, enhanced bank feeds, and our AI-powered automation features, rather than exposing the underlying feeds for external reconciliation logic.

   
   

   We will continue to review our approach as regulation, banking connectivity and customer needs evolve, but we want to be clear and transparent that this specific request will remain declined under our current legal and risk framework. We genuinely appreciate the thought and passion that has gone into this thread, and we’ll keep focusing our efforts on making in‑product reconciliation as efficient and intelligent as we can, within those constraints.

   Thank you for the continued feedback and for your patience on this long‑running request. We know that programmatic bank reconciliation and AI‑driven workflows are increasingly important to many of you, and we understand the frustration that this capability is not available via the Xero API.

   
   

   After reviewing this again with our legal, risk and banking teams, we have confirmed that we will not be adding the ability to reconcile bank statement lines via the API or to expose unreconciled bank statement data via the public API.

   
   

   There are a few key reasons for this decision:

   1. Regulatory and contractual obligations on raw bank data. Unreconciled bank statement lines are “raw” banking data – unmodified information that comes directly from banks. In markets such as Australia, this data is treated as banking data under consumer data rights regimes. Sharing it on to third parties (including via an open API) would require us… more
   An error occurred while saving the comment
   Peter McCarroll commented  ·  Oct 13, 2014  ·  Edit…  ·  Delete…

   In addition, or as a substitute, we also need to be able to create payment batches through the API (groups of invoices/bills under a single Payment transaction in the bank ledger). This would alleviate a huge issue people are asking for here.

   Save Submitting...
   Peter McCarroll supported this idea  ·  Oct 13, 2014

7. Import bank statement lines via the API

   997 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   240 comments  ·  Accounting API » Banking  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   working on it  ·  AdminKelly (Admin, Xero Developer Centre) responded

   Thanks for your continued feedback and patience on this long-standing request. Our team has started to build this out, and we’re looking forward to sharing more as development and testing progresses.

   This release will support ingestion of bank statement data via the Bank Feeds API for accounts where a bank feed has not been established and allow customers to automate the current manual file upload process.

   As part of this work, we’ll be running a beta with a small group first (from mid June) so we can test the experience and gather feedback before broader availability. We’ll continue to post updates here as we reach key milestones.

   Peter McCarroll supported this idea  ·  Oct 13, 2014