Share
Report
10Hi everyone,
We are new to business central, been using it for a few months now. A key point in the various sets of books we manage is that our particular clients use Journal entries and NOT invoicing. Each client is batched a monthly levy run and that is that.
All customers are set to Apply to Oldest, but this seems to be hit and miss. If it misses it affects the aging and in turn any automated processes that sends out payment reminders etc.
The problem we are experiencing is the Balance Due issue when we try to grab the Aging via power automate.
In the example below, you will notice that Entry number 158112 has been applied, instead of the entry before it 157136. This causes the Aging to show that a small amount is outstanding i.e 30days+.
Our payment terms have been set to calculate the Due date as CD (I believe that that would bake the due date the same as the posting date)
We also have an external automated bank reconciliation process that is centralized since we have 70 companies that work exactly the same. (The normal thinking of doing things in 1 company does not apply here, since they need to be replicated over many more companies)
I need to figure out how to fix the /Apply to/ so that it does not skip over older posting dates. Or I need to find a way to grab the Balance at the end of each period (not Balance Due, since the Balance Due relies on the Open items to be applied correctly). With each period I mean that I want to obtain and use the Running balance on the last day of each period (for 6 periods [months]) with an API or power automate to use externally on a regular basis.
Categories:
All responses (
Answers (
