Accounting API
Welcome to our official feedback forum for the Xero Developer API.
The Xero Community site is the best place to submit feedback for improving Xero Business
558 results found
-
Allow POST call on SentToContact for Credit Notes
Sent to Contact on credit notes is read only right now.
Please allow us to do a POST call to this so we can mark sent to contact true as needed
4 votes -
Allow API Access to run the Bank Reconciliation Report
In lieu of being able to interact with the Bank Feed information directly via the API - it would be useful to be able to run the Bank Reconciliation Report directly from the API.
The use case in mind is:
I would like to set up a proactive notification when there are incoming amounts that are not reconciled in Xero in order to prompt someone to go in to Xero and manually reconcile those items. This will help prevent our customers from getting automated invoice reminders when they've paid.
We're not at the point yet where someone is in Xero…
4 votes -
Invoices API: Enable/disable reminder when creating an Invoice
It would be very useful to be able to programatically enable or disable invoice reminders for a given invoice when an Invoice is created using the Invoices API.
4 votes -
UpdatedDateUTC to be updated on Contacts when a Contact Group is modified
When a contact has been added or removed from a group, or when a group is changed the UpdatedDateUTC on the contact should also be change to reflect this.
4 votes -
include cost of sales on invoices
A customer of ours need to pull Invoices via the Xero API and are particularly interested in the COGS value of sales in order to calculate a Gross Profit value.
Unfortunately, that value does not appear in the Invoices endpoint.
I ran some tests where i posted a sale, then posted a purchase with items with a higher purchase price, then edit the sale and increase the quantity.
I then checked journals and i could see a reversal jounral for the COGS that used the old COGS value, and a reposting using the new COGS value.
This implies the data…
4 votes -
Show TrackingOptionID in LineItem in Invoices API (and other endpoints)
The Invoices endpoint in particular (and many others in general), do not include the TrackingOptionID in the data set. Instead, they generally provide only the Name, Option and TrackingCategoryID.
It is really important for being able to use "joins" on the data to incl;ude the TrackingOptionID .
4 votes -
Provide the OpenDate and ClosedDate in the Projects endpoint
The Projects endpoint of the Xero Projects API does not include the OpenDate and ClosedDate as fields.
These are useful for users to report with and should be included.
4 votes -
4 votes
-
Ability to access Practice Manager staff billable rates
It would be really useful to be able to access (and ideally edit) staff billable rates via the Practice Manager API.
Many other fields can be accessed via the Staff endpoint:
https://developer.xero.com/documentation/api/practice-manager-3-1/staff
This would be a really useful addition.
4 votes -
Full Account details must be available with Invoice record
When GET invoice called using API, we get only ContactId and Contact Name. Here full contact details must be available so that if contact is not available in local database we can insert new one.
3 votes -
Show ContactNumber field next to contact name for each invoice
We make extensive use of the ContactNumber field for invoicing.
Can Invoice listing show ContactNumber field next to contact name for each invoice to help with updating/locating drafts?
Can ContactNumber be shown on contact listing instead of phone or email field for locating contacts?Original question - http://answers.xero.com/developer/question/23051/
3 votes -
In the Invoice API, include the JournalLineID under LineItem details
To enable the ability to trace the journal created by an invoice.
3 votes -
3 votes
-
Allow rules to apply to invoices coming through the API (especially Vend)- So you can automatically add account codes, analysis codes etc.
Rules to apply to invoices recived through the API - analyisis codes
3 votes -
Generate reports by using specific identifiers in the "reference field"
As a building business it would be nice to ascertain the costs of a specific build/client to ensure the company is on track with profit/loss per project.
When I started out in Xero, and when all purchases were been entered in as drafts, when a certain reference was entered, such as the client name or job number, a running total was always displayed as to how much was spent on a particular build/client.
Ironically once the purchases were approved and/or paid, upon typing the same specific reference, would no longer provide a tally or what was spent, to be paid…
3 votes -
Is it possible to have the Management Report and more budget reports available to export via API?
I use QWD and would like to see the Management Report exportable as well as more budget reports eg budget per month from budget manager.
This would allow far more flexibility in building reports and dashboards.3 votes -
have a discount field in purchases
When clients have Retail Express and applying the discount on purchases in Retail Express there is no possibility to import the original price and the discount received when doing the import. A solution would be either to have the discount per line or at least under total balance of purchase have a field of "total discount applied" to this purchase...so the original price can be still found. When checking that the imports are correct at present it causes confusion and a lot of going back and forth to find out wether bill had been imported with discount and what the…
3 votes -
Give detailed validation responses
When adding Customers response with what Name is a duplicate,
With Email Addresses give the email address that failed validation, I have a list of +-20 valid email addresses but Xero seems to believe one or all are invalid3 votes -
Add GET all or where employee_id= functionality to Paystubs
It takes a lot of requests to get paystubs for a specific employee. Having the ability to get all or get where employee_id= would reduce the number of requests significantly.
3 votes -
Wrap Paystub element in Paystubs on GET
Not having it wrapped in Paystubs seems inconsistent with the other endpoints. They are all wrapped even if they are passing an id, which indicates they are only returning one item.
3 votes
- Don't see your idea?