2 results found

1. Import bank statement lines via the API

   Be able to import bank statement lines into a bank account in Xero. This would be useful for custom bank accounts or banks that do not have a direct feed into Xero

   999 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

   241 comments  ·  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.

2. Create more granular accounting scopes (eg: Sales - Invoice only)

   Right now there is a very wide range of APIs wrapped up in the "accounting.transactions" scope, with no way to provide more granular access within these APIs (https://developer.xero.com/documentation/guides/oauth2/scopes#organisation-scopes).

   This means that it's not possible to grant access to something quite narrow without also granting access to other things that are often not needed. For example, you cannot grant permission to creating/manipulating Sales Invoices without also giving access to all Bank Transactions at the same time.

   This problem is perhaps accentuated for Custom Connections, which are designed to be used for "in house" integrations, as ALL developers with access to maintain such a sales invoice integration would effectively have access to their colleague's salaries and company bank balances and nothing can be done to mitigate against this.

   It feels like either there should be an extra layer of scopes such as "accounting.transactions.invoice" or "accounting.transactions.sales" available.

   I would also think this is quite easy to implement!

   Right now there is a very wide range of APIs wrapped up in the "accounting.transactions" scope, with no way to provide more granular access within these APIs (https://developer.xero.com/documentation/guides/oauth2/scopes#organisation-scopes).

   This means that it's not possible to grant access to something quite narrow without also granting access to other things that are often not needed. For example, you cannot grant permission to creating/manipulating Sales Invoices without also giving access to all Bank Transactions at the same time.

   This problem is perhaps accentuated for Custom Connections, which are designed to be used for "in house" integrations, as ALL developers with access… more

   59 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

   working on it  ·  12 comments  ·  Authentication  ·  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