Default Xero monthly profit and loss - months are not in correct order

[vaughn66]

The default Xero monthly profit and loss dashboard card does not display the months in the correct order.

The default Xero profit and loss report tab does the same thing.

The reason is that the reports seem to be treating a Financial Year in the same way as a calander year.  This is not the case.

The report orders like this: Mar-FY2016, Jan-FY2017, Feb-FY2017, Apr-FY2017, May-FY2017, Jun-FY2017, Jul-FY2017, Aug-FY2017, Sep-FY2017, Oct-FY2017, Nov-FY2017, Dec-FY2017

It should read Mar-FY2016, Apr-FY2017, May-FY2017, Jun-FY2017, Jul-FY2017, Aug-FY2017, Sep-FY2017, Oct-FY2017, Nov-FY2017, Dec-FY2017, Jan-FY2017, Feb-FY2017

The calendar years for this data are: Mar-2016, Apr-2016, May-2016, Jun-2016, Jul-2016, Aug-2016, Sep-2016, Oct-2016, Nov-2016, Dec-2016, Jan-2017, Feb-2017

Sorting needs to be by calendar year but labels by financial year.

-------------

The reason why Jan-FY2017 and Feb-FY2017 should be the last two ones is due to most Financial Years not ending in December.

Our Financial Year ends in March.  Therefore the FY2017 starts in Apr 2016 and ends in Mar 2017.

If your financial year ended in June, FY2017 would start in July 2016 and go through to June 2017.

For us, Jan-FY2017 equals calendar year Jan 2017

Apr-FY2017 equals calendar year Apr 2016

If Jan-FY2017 and Feb-FY2017 come before Apr-FY2017 then they are out of chronological order.

If the report were converted to calendar years, it would then read Mar2016, Jan2017, Feb2017, Apr2016, May2016 etc.  This is not correct.

Hope this helps your understanding v-haibl-msft

[v-haibl-msft]

@vaughn66

I’m a little confused about the expected order. Why Jan-FY2017 and Feb-FY2017 should be the last two ones?

It should read Mar-FY2016, Apr-FY2017, May-FY2017, Jun-FY2017, Jul-FY2017, Aug-FY2017, Sep-FY2017, Oct-FY2017, Nov-FY2017, Dec-FY2017, Jan-FY2017, Feb-FY2017

Best Regards,

Herbert

[vaughn66]

The reason why Jan-FY2017 and Feb-FY2017 should be the last two ones is due to most Financial Years not ending in December.

Our Financial Year ends in March.  Therefore the FY2017 starts in Apr 2016 and ends in Mar 2017.

If your financial year ended in June, FY2017 would start in July 2016 and go through to June 2017.

For us, Jan-FY2017 equals calendar year Jan 2017

Apr-FY2017 equals calendar year Apr 2016

If Jan-FY2017 and Feb-FY2017 come before Apr-FY2017 then they are out of chronological order.

If the report were converted to calendar years, it would then read Mar2016, Jan2017, Feb2017, Apr2016, May2016 etc.  This is not correct.

Hope this helps your understanding v-haibl-msft

[v-haibl-msft]

@vaughn66

Is the order correct in reports displayed in xero.com? If the order is correct in xero.com but not correct in Power BI Dashboard, could you please post two screenshots for them?

Best Regards,

Herbert

[vaughn66]

This chart is the one from Power BI.

As you can see it starts with Mar-FY2016 = Mar 2016 and then shows Jan-FY2017 and Feb-FY2017 that equates to Jan 2017 and Feb 2017 respectively.  Then the report shows Apr-FY2017 etc.  These dates have to represent Apr 2016 on as Apr 2017 has not happened yet.

This is a report from Xero.  It is not exactly the same but it does show the correct order of months.

Don't get confused by Mar being at the end in this report.  I took the snap shot today and we have had one day of March 2017.  If I was to refresh the Power BI report now the Mar-FY2016 would now be gone and the report would then read Jan-FY2017, Feb-FY2017, Mar-FY2017, Apr-FY2017, May-FY201, ...

This report would confuse people as Apr 2017, May 2017 etc would look like they are in the correct order, but they are not because they have not happened yet.

[tailoredaccount]

Has this issue been escalated or sorted yet? I had same issue here with conflicted months in P&L report & chart. Somehow PowerBI is using different moth order comparing with XERO

[vaughn66]

No this issue hasn't been sorted yet.

I don't know how to escalate the problem in this forum.

[v-haibl-msft]

@vaughn66 @tailoredaccount

I’ve reported it internally to Power BI Team: CRI 34077561
I’ll post here once I get any update about it.

Best Regards,
Herbert

[v-haibl-msft]

@vaughn66 @tailoredaccount

I've got response from the Product Team. Now we can wait for the next content pack update to correct this behavior.

Thanks for the feedback. This is a feature request that we'll incorporate at the first coming update that Xero choose to make to the content pack. Right now, no update is planned soon and i have no ETA on when will Xero choose to update their content pack.

Best Regards,
Herbert