Advance Payment#
See also the following ChangeLogs#
25.5.1334.0 - 2025-03-28#
Hotfix
- Wrongly updated Deposit Amounts in Purchase and Sales Documents (#13967, AZ-285)
When manually changing the amounts and quantities of a deposit line, it is set to Fixed amount.
Change
- Change Sorting for Advance Project Ledger Entries (#13891, AZ-276)
The default sorting of the Job Ledger Entries has been adopted for the KVSADVAdvanceJobLedgerEntries page (“Job No.”, “Posting Date”). - Dimensions behave analogously to standard (#13893, AZ-278)
The behavior of the advance chain and the lines has been adapted to the standard behavior of the dimensions. - Advance Chain at document line level in the purchase order (#13930, AZ-238)
The check of existing lines when setting the option "Plan Advance Payment on Document-Line-Level" has been improved. If no advance chain are defined, not invoiced and no prepayment, the option can now be changed even though lines exist. - Transfer Qty. to Adv. Invoices with Unit of Measure (#13931, AZ-277)
When the quantities are transferred, the unit of measure code is transferred to the advance payment invoice.
25.5.1304.0 - 2025-03-12#
Hotfix
- Deposit Amounts are reduced to Zero on Releasing of Documents (#13857, AZ-281)
The field "KVSADVDeposit Fixed Amount" is set to true so that the lines are handled as before.
25.5.1295.0 - 2025-03-10#
Hotfix
- Document layouts advance payment invoices (#13770, AZ-271)
Advance payments invoices have been added to the document layouts. This means that customer-specific e-mail addresses can be stored for sending e-mails.
Change
- Some Events and Objects were obsolete by Microsoft with BC26 (#13769, AZ-264)
The “Adjust Exchange Rates” report can no longer be used with an Advance Payment. The function extension “Extensible exchange rate adjustment” must be activated. Reason: Activation of the function extension with BC26 and validation of the app by MS against BC26 with BC25.5 and the removal of the report in BC26.
25.4.1260.0 - 2025-02-27#
Hotfix
- Problems Update Deposits (#13698, AZ-272)
Problems with dependent apps and approval workflows have been fixed.
Change
- Missing field information in posted deposit invoices (#13705, AZ-237)
If a deposit is posted from a sales/purchase invoice, your reference and purchaser or salesperson code are now transferred to the posted deposit invoices.
25.4.1252.0 - 2025-02-21#
Change
- Fields OptimizeForTextSearch (#13037, AZ-256) Selected fields have been added for the optimized text search feature.
- Message: Activate the "Extensible Exchange Rate Adjustment" feature (#13667, AZ-270)
When using the Adjust Exchange Rates report in a session for the first time, a message appears informing me that the Extensible Exchange Rate Adjustment feature must be activated with BC25.5 at the latest. Reason: activation of the feature with BC26 and validation of the app by MS against BC26 with BC25.5.
25.4.1239.0 - 2025-02-14#
Hotfix
- Correction Generate Reconciliation Entries (#13562, AZ-263)
For entry types 07 and 08, the account type (customer/vendor) is now filtered. - Correction Print Recon. Entries (#13568, AZ-265)
The assignment of fields without foreign currency has been changed. In addition, when searching for G/L entries and VAT entries, the Advance Chain No. is also taken into account in addition to the transaction number.
Change
- Refresh deposit lines when total amount changes (#13559, AZ-93)
It is now recognized in the document lines whether they are fixed or variable deposits. This means that variable deposits can be recalculated when the document is released. Automatic calculation is no longer possible as soon as the document is partially invoiced.
25.3.1196.0 - 2025-01-28#
Change
- Adjustment “Indirect permission” Job Integration (#13421, AZ-260)
Indirect permissions have been set to KVSADVAdvanceChain and KVSADVAdvance Planning Entry in the KVSADVJobIntegrationSales codeunit. This means that indirect permissions can be used for the user permissions.
25.2.1167.0 - 2025-01-20#
Change
- Renaming of customer and vendor numbers is not possible. (#13209, AZ-245)
As with the merging of customers and vendors, unnecessary checks are now skipped when renaming customers and vendors.
25.2.1143.0 - 2024-12-16#
Change
- Function "Create Entries By Lines" only with not cumulated Advance Chains (#12740, AZ-185)
It is no longer possible to use the "Create Entries By Lines" function for cumulative advance payments. - Reconciliation list for unreal/real. advance payments - Net Amount Paid (LCY) (#12984, AZ-255)
The calculation of the “Net Amount Paid (LCY)” field has been changed.
25.1.1112.0 - 2024-11-18#
Change
- Report "Print Recon. Entries" - Foreign currency (#12618, AZ-249)
A few improvements for Report "Print Recon. Entries" (Foreign currency).
25.1.1105.0 - 2024-11-13#
Change
- General performance and stability improvements.
25.1.1085.0 - 2024-11-05#
Hotfix
- Apply payment - missing / incorrect Advance Chain No. in General Ledger Entries (#12432, AZ-232)
When apply the payment, the system now searches for the correct Advance Chain No. This means that it is also correct when apply several Advance Chains with one payments. - Can not create new advance invoice in cum. Advance Chain (#12612, AZ-239)
The logic with the setting “Cum. cancels prev. Inv.” has been revised.
Change
- Improve Setup Experience after installing App from AppSource (#12304, AZ-240)
- Show global dimensions in Advance payment ledger entries (#12384, AZ-241)
"Global Dimension 1 Code" and "Global Dimension 2 Code" were displayed in the pages "Cust.Advance Ledger Entries" and "Vendor Advance Ledger Entries". - Reconciliation list for unreal/real. advance payments (#12567, AZ-163) A possibility was created to analyze and reconcile individual advance payment processes.
- Reconciliation list - Figure of exchange rate differences (#12576, AZ-244) Currency differences were included in the analysis.
25.0.996.0 - 2024-10-01#
Change
- General performance and stability improvements.