Sub-ledgers transaction, typically for PO and FT invoice gets transferred as per batch rule defined in GL parameter. There we define whether the sub-ledger transfer will be synchronous or asynchronous.
If the batch transfer rule is asynchronous, then you need to post the sub-ledger entry using a batch job called post sub-ledger entry which is available is periodic section of GL module.
You need to run the batch process to update sub-ledger entries financially. This can be scheduled also.
I don’t know why sub-ledgers entries options transfer is now a de-coupled process, but i can say that this is done to enhance the optimization.
If the batch transfer rule is asynchronous then the performance of AX will be enhanced. We can transfer sub-ledger entries at a time when load is low. This is particularly useful for industries like retail where the volume of transactions are very high.
What about AR invoice, is it related to any batch (even hidden one) that transfers it to the subledger?
We’re getting some accounts not transferred, as Issue and Consumption accounts.