I have implemented the automatic settlement feature for our customer IFRC (International Federation of Red Cross). We have setup recurrences with the Process automation feature in General Ledger, to settle "suspense accounts" that are debited and credited, hopefully with the same amount, by different transactions posted by different custom processes we have developed. An example of such custom process is illustrated below:

1) A process is creating in AR subledger a transaction that debits the customer account (e.g. 1000 USD = 950 CHF) and credits a suspense account 254510 by 1000 USD / 950 CHF

2) Same process is also creating in the Project Accounting menu a Project Fee journal that credits revenue account for 1000 USD / 950 CHF and debits the suspense account 25410 by 1000 USD / 950 CHF

Note that transactions posted in steps 1 and 2 use the notion of Financial Tag. We defined a financial Tag called "Pledge Id", that is a very important notion for an NPO like Red Cross. Therefore, debit and credit posted on the suspense account will both be posted with Financial Tag Id "Pledge Id" = M2501001 for example, when transactions in AR and Project module were created for this Pledge id.

3) every night, we want the suspense account 254510 to be automatically settled in GL as the 2 transactions above should match and lead to generate a total amount = 0,00 in the suspense account, if everynthing went well.

We have 2 issues with the current feature in D365:

1) Our client will generate postings like shown above, with posting date in December 2024, at least until end of February. We may have thousands of transactions posted in just one day, with posting date (i.e. accounting date) = 31/12/2024 for example, whereas they were created with system date = 20/02/2025. The current automation process will ignore all these transactions, when it is run on Feb 25th, as the automation process will only try to settle transactions with accouting date in 2025. Doing manual settlement of such suspense account for transactions posted between Jan 1st 2025 and Feb 28th 2025, which have an accounting date in December 2024 is a nightmare, and a loss of time.

2) In standard, we can use the Financial Tag Id as a matching criteria to force the system to settle a transaction of +1000 USD with another one of -1000 USD, as long as they both have the same value for the financial tag. However, FO considerd "blank" value as an eligible value to settle denit and credit togethers. At IFRC, we would need to define in the setup, that we want to use Financial Tag as a matching criteria, but would like the system to ignore transactions that do not have the financial tag fed. A setup rule should allow to say "Settle only transactions if Financial tag is not = blank". For IFRC, any transaction with blank financial tag must be reviewed first, then updated to feed the financial tag valuen before it can be settled.

We tried on our project to develop customizations to solve our 2 issues above, but code is frozen, and we cannot even develop what we need.