When I enter a Funeral fact and a Burial fact for the same date, I think it would be nice if they defaulted so that the Funeral fact appears before the Burial fact on the Edit Person screen. Yes, I fixed this manually using the Sort Date field immediately after I took this screenshot, but it feels like extra work.
I’m sure there are occasions when the funeral happens after the burial, but I think typically that is not the case.
Burial comes before Funeral since B is before F in alphabet 
Well that does make sense. Even if I don’t love the outcome I do appreciate a logical reason why it happens. Thanks.
You control the sequence of events on the same date using “-1” etc on the “Sort Date” field.
See the bottom of this Help Topic
Good thing there’s sort dates involved. Can you imagine Burial and then Death. 
This issue is not specific to Funeral before Burial. RM does not support any kind of default ordering for events which happen on the same date. For example, sometimes a Birth and Death can occur on the same day and they can end up in RM with the Death before the Birth.
The RM solution is always to use sort dates. Be it a pain or not, that is the solution.
There have been noted cases where people thought to be dead were buried (usually not discovered until after they really died.
@kevync1985 I know, and it’s horrifying … thus the .
Good thing that he never had a “Cremation” Fact. 
That would come before death also.
I found that RM treats them as to the order you enter them. In those instances Birth entered first followed by Death results in Death then Birth.
Yes you can enter the sort date OR reverse the order of entry (Death then Birth) and they are correct. Just interesting.
I agree that RM goes by the order you enter them when facts have the same date. I don’t think it has anything to do with alphabetic order of the names of the facts. It always comes down to using sort dates to place events into the correct order when they occur on the same date.
In sort date on the entry on the bottom - pick a later date
That works, but I usually set the sort dates “the same” except for a suffix. For example, if somebody died and was buried on 17 July 1904, then I would make the sort date for Death to be 17 Jul 1904-1 and the sort date for Burial to be 17 Jul 1904-2.
You can set the sort date to be 17 Jul 1904 for the Death and the sort date to be 18 Jul 1904 for the Burial. It works and the correct dates show in reports rather than the sort dates that are curiously “incorrect”. But I still prefer the -1 and -2 suffixes. There is no practical limit on how high the suffix numbers can go. And since they are sort dates rather than actual dates, they don’t print in reports.
Lets put the FUN back in funeral I say lol
As an IT professional a date field that isn’t a date field gives me eye twitches, lol.
Well, not always. If I update the death with other information (not changing the dates), RM will put the death before the birth, or burial if you have one (generally Jewish burials occur on the same date as the death). I use the sort date field adding -1, -2 etch as needed to the date.