Or does it? Today's post is the first #TipTuesday of 2019 and a little bit of an obscure one at that. The short version is if using the write-off feature while applying payments or credit notes in Dynamics GP Receivables Management, the results display rather oddly on the RM Historical Aged Trial Balance (HATB). In fact, at first glance, it seems like the report is wrong, but it's not, and here's why.

Example

Here's a transaction example that I worked with. I have a hypothetical invoice for $10,000. The invoice has gone unpaid for over a year. A payment arrangement has been worked out with the client where for every $90 they pay, $100 will be applied to the invoice (instead of giving them a $1,000 credit up front).

What this means is for each payment of $90, there is a $100 reduction in A/R, which means applying a payment and adding in a $10 write-off at the time of application. Here's what the inquiry window looks like for this (I didn't get a screenshot of the actual apply window, unfortunately).

Apply to Debits window showing a write-off on a Receivables invoice.

The problem

"The problem" isn't a problem, but it sure does look weird. Here is what the RM HATB looks like when I have a write-off during an apply.

Receivables HATB report

The payment amount on the PMT lines is $90 representing the amount of actual cash received, but where is the write-off? In my example, I've recorded 2 payments of $90, and the invoice balance is $9,800. The Grand Total is correct, it shows $9,800 but what isn't super obvious is the heading on the Over 90 column shows the invoice amount is $9,980, not $10,000. That's where the write-off amounts accumulate so users don't see the detail of $10 per payment like they might expect.

So, in the end, the report is correct, but what users are not seeing is date-by-date detail on the write-off amounts. The detail would be completely visible in something like Smartlist if someone needed to see it by date though.

That's it for this post. It's something that came up at work, when one of our A/R team was concerned that the report was wrong, not showing the correct amounts. I figured she might not have been the only one who ran into this!