Unfortunately, I do not have a NAV 2013 R2 environment handy and I'm not able to recreate the error in NAV 2017.
The only thing I can think of is that someone may have set a hard filter on the General Ledger Entries page (Object ID: Page 20, from the NAV Development environment). If you, or someone from your team have access to the Development Environment, Design that page, and look at the Page Properties to see if the SourceTableView property has any TableFilters set. By default, the SourceTableView property should have a value like:
SORTING(G/L Account No.,Posting Date) ORDER(Descending)
If it has something like what you see in the bold part below, then you know there is a filter that was set by your partner or developer that needs to be corrected, and this is causing the issue:
SORTING(G/L Account No.,Posting Date) ORDER(Descending) WHERE(Document Type=FILTER(' '|Payment))
It is also possible that the filter may be set in C/AL code, which you may or may not be able to see depending on whether you have access to a NAV development license.
If you are comfortable with the NAV debugger, you could also go that route, and it should help pinpoint where the issue is arising from.
As a last resort, I advise you to take a look at the list of released cumulative updates for NAV 2013 R2, or open a support case with Microsoft.
On this page, you can scroll all the way to the bottom to look at overview of released platform and application hotfixes (two separate links, one for platform, one for application).
Depending on whether you are a Microsoft Partner or an End-Customer, you'd click on the links under PartnerSource or CustomerSource respectively.
I hope this helps. If my response has answered your question, please take a moment to verify by clicking Yes next to "Did this answer your question?"