Skip to content

Advance Payment#

See also the following ChangeLogs#

26.2.1462.0 - 2025-06-20#

Change

  • Convert obsolete functions and events to new logic (#14599, AZ-258)
    MS has created the possibility to rebuild the obsolete events and functions (from BC25). This requires the minimum version BC26 CU1.
  • New Field "Check Doc. Total Amounts." in "Purchases & Payables Setup" (#14814, AZ-288)
    If the option "Check Doc. Total Amounts“ option is used in Purchasing, the ”Preassign Total Doc. Amounts" can be activated so that Advance Payment documents can continue to be posted automatically.

26.1.1441.0 - 2025-06-02#

Change

  • "Invoice Post. Buffer" Fields and Events Obsolete (#14598, AZ-295)
    When removing the “Invoice Post. Buffer”, which is set to Removed with BC27, events were discovered that had not been obsoleted. The fields in the table were also obsoleted. As the new posting logic is active in BC26, the events and fields are no longer active.

26.1.1427.0 - 2025-05-12#

Change

  • Error before posting the correction credit memo due to changed header (Other app) (#14137, AZ-253)
    The current header is now retrieved again before posting.
  • Add Advance Plan Template to Advance Chain (#14184, AZ-274)
    The last template used is displayed in the advance chain.
  • Optimization of rounding precision (#14188, AZ-248)
    The calculation of amounts and percentages in the advance payment entries has been optimized to reduce rounding differences.

26.0.1387.0 - 2025-04-09#

Hotfix

  • Correction of posting status display (#14059, AZ-283)
    For the "Advance Planning Entry" of the type “Closing Invoice”, a different way of determining the status has been implemented. The caption has also been adjusted.

26.0.1357.0 - 2025-04-01#

Hotfix

  • Overpayment Credit Memo cannot be created for Advance Invoices with negative Lines (#13999, AZ-282)
    The value of the vendor ledger entry is now reversed and can thus be transferred to the document.

Change

  • Preview: Some Events and Objects were obsolete by Microsoft (#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.
  • BC26: Preparation for BC26 (#13772, AZ-280)
    Obsolete objects, functions and fields have been removed and checked to see if changes are required by BC26.