Georgiana Campeanu Financial ERP Consultant

When an invoice needs to be settled with a payment journal, the financial dimensions inherited in the payment voucher should be the ones contained in the related invoice and not the ones found in the customer/vendor profiles. This would help avoid any mismatch in the accounting settlement. This also implies that, if the invoice contains multiple lines with different financial dimensions, the same should occur also in the payment voucher. For example, if you have 5 invoices (with different financial dimension combinations) that you need to liquidate with one single payment, the payment voucher should be divided according to the financial dimension combinations contained in the invoices. This additional functionality should be activated by a general ledger parameter. At the moment, this doesn’t happen meaning that the payment voucher doesn’t contain all the necessary information related to the financial dimensions.

The RiBa functionality is covered in AX with the use of the “Bill of Exchange” setup and functionality. When an invoice becomes part of a RiBa portfolio, AX automatically closes the original invoice. Every further step in the RiBa process (RiBa remittance, settlement and eventually protest) behaves in the same way: no reference to the initial invoice/s gets carried through the process; the date is always the one when the RiBa process step is booked (might be weeks/months later than the original invoice for which the RiBa was created). The standard does not foresee a logic connection between invoices and related payments (BOE). In the Transaction form it would be useful to insert the invoice voucher detail in every single BOE transaction (drawn, remittance, honored, protest and remitted).