Hi all, we use the % complete override on a projec...
# accounting
d
Hi all, we use the % complete override on a project for booking our revenue. One particular project, we split out the revenue evenly July 2021 through June 2022 (100% complete in June 2022). No problems there and that all worked as intended. However, now when we are looking at our profitability and revenue reports, it is booking a negative revenue for July 2022 when there shouldn't be any revenue at all. As far as I can tell, there is no difference on this project & it's revenue settings compared to every other project. We have never seen this before and have exhausted hours trying to find what is causing this. Any ideas what is going on?
c
Did the total amount of revenue change in July 22? f.ex if it's linked to an SO line did it get edited or closed? Did something else get added to the same arrangement + you're using FV allocation? Both of these scenarios could cause the revenue to change even if nothing changes on the project itself.
d
no - this was a set it and forget it Sales Order. Set up in June 2021 with a 12 month billing schedule, set the % complete and the only time we touched the SO was to create each monthly invoice. No line items were adjusted or closed.
c
Are you on ARM?
If so, does the revenue plan have versions?
d
yes and yes! It appears as though the status was re-opened at the end of July. Is there a way to see why it went back to in progress? It should have stayed closed after reaching the 100% in June.
c
Can you screenshot: 1. The previous revenue plan 2. The revenue arrangement header 3. The revenue arrangement version subtab 4. The revenue arrangement message subtab?
It reopened because something changed, that caused the revenue amount of the plan to change...question is what?
d
looks like the previous version also had a negative entry.
albeit a different amount
c
If you go to the revenue element and look at its system notes, does it show changes in any of Sales Amount, Discounted Sales Amount, or Revenue Amount?
d
not since originally opening the SO last June
l
@Dawn just want to butt in because I think we had the same issue before. Were there actual and approved time entries recorded in July 2022?
d
Hey Luis - appreciate the butting in! Yes to the time entries, in both July and now August as well. However, this is pretty typical for us to have time entries outside of the months we book revenue and we haven't seen this before. I wonder if we screwed up on some settings that is factoring in time now?
l
And if that happens you don't include those periods in the Percent Complete Override subtab and put 100% as cumulative percent completion?
Maybe those previous scenarios still resulted in 100% completion based on time entries (if they are not in the Percent Complete Override subtab)
What's the percentage of completion based on time entries as of July 2022 in the example above?
Is it less than 100%?
Like 90.76% to arrive at that negative adjustment?
d
correct. we exclusively use the % complete override. The actual hours and their billable rates are less than the total fee we billed to the client. This is also common and has not created an issue in the past.
We had some employee's billable rates change during the past year and I haven't been able to figure out exactly what the difference is due to that but it doesn't seem to be as much as the revenue is adjusting for
l
I was asking because in our experience and in the documentation, if there's an approved and actual time entry posted in a period that is not included in the Percent Complete Override, NS will use the percentage of completion based on time entries. For example, your actual hours as of July 2022 are 91 but your planned hours are 100, then that's just 91%, so NS will make a negative adjustment assuming there's a time entry in that period and the period isn't in the Percent Complete Override. Just to be clear, the billable rates don't matter. It's just actual hours divided by the planned hours (or whatever the formula is).
I was thinking earlier that maybe the reason why it wasn't happening in other cases is because the actual entries divided by planned hours is still at least 100%, so there will be no adjustment even if the period isn't in the Percent Complete Override.
d
gotcha. I'm seeing what you mean now. We don't use the planning tasks, and it defaults to just 10 hours for one department. We are well over that on actuals
message has been deleted
well, i figured a workaround for this particular project by adding an additional 100% complete to July 2022 (keeping June 100% as well). However, I've tried recreating this and I simply cannot figure out why that is required. I have several other jobs with the exact same situation and it functions just fine. Another NS mystery!
l
Yeah. That's what I'm going to suggest too. 'Cause that's what we do and that's what's in the documentation in case there are time entries beyond the original last period. My hunch is your actual work divided by the calculated work as of July 31, 2022 (not what you see right now 'cause that's as of today) is less than 100%. Other than that, I have no clue.
c
I think Luis is on to something. I was discounting the actual time because you are using % Complete Override, but you have to shut a project down properly. If Actual Time entries are made in a period not covered by your % Complete Override, then NS is going to recalc for that month.
d
What steps might I be missing from shutting down the project properly that could affect this?
c
IMO part of project shut down is confirming no further time entries will be made, & that the %complete override covers all periods.
d
gotcha. Agreed we will definitely make this a part of things going forward. It makes sense for sure but I cannot seem to replicate it & it's making me crazy! I have other projects that have time outside of the % complete (both over and under the NS calculated % work complete) and they did not have this issue.
thanks to you both! Definitely helped me have a larger understanding of things and where to start looking
Just an FYI - I went ahead and removed the 2nd 100% complete in July and recalculated (so everything was the way it was previously). It did not make the negative revenue come back. Starting to think this was just a fluke. Might submit a help ticket and see if they have anything to say about it. Will let y'all know if anything comes from it.
c
Dawn, I was wondering if someone entered time dated in July and then removed/unapproved/edited date to June etc
d
No, all the time entries are still the same.