Skip to content

Advance Payment#

21.12.102726.0 - 2023-10-09#

Hotfix

  • VAT Product Posting Group not transferred from Advance Plan to Deposit Lines (#7170, AZ-115)
    When creating an Advance Plan with deposits and deviating VAT Product Posting Groups assigned in the Advance Plan itself the creation of the Advance Invoice will ignore the VAT Product Posting Group for the deposit lines. Hence all deposit invoice lines will not contain the assigned VAT Product Posting Group.
  • Wrong Credit Amount (Cent difference) (#7173, AZ-117)
    In the case of advance credit memos, cent differences could occur when distributing the remaining amount to the lines. Now this difference is balanced with the last line.

21.10.91555.0 - 2023-08-08#

Hotfix

  • No Update for Deposit in advance payment plan (#5772, AZ-74)
    If the deposit amounts are changed in Advance Payment Document, the changes are now written back to the Advance Planning Entry when posting.
  • Currency exchange to down payment invoice (#5814, AZ-76)
    To avoid differences between the advance payment invoice and the advance chain string, it is not possible to change the currency code in the advance payment invoice.
  • Update Advance Plan by Advance Credit Memo (#6025, AZ-84)
    Credited amounts are now shown in the advance plan and taken into account in the cash flow calculation.
  • Create Closing Credit Memos with different VAT Bus. Posting Group at Vendor (#6559, AZ-100)
    The order of the validates has been changed so that the correct VAT Bus. Posting Group is entered before the lines are created.
  • Cumulative Advance Invoices with Order-line-based Advance Plans (#6783, AZ-104)
    The cumulated advance invoice planning had multiple flaws when creating order lines based on Sales / Purchase Order Lines, e.g. an inadequately generated description for advance planning lines.
  • Wrong Url for Online Help at two pages (#6869, AZ-105)
    There were coded online help links though. A relanch of the website changed the URLs, so they were no longer correct. The links have been removed, instead the standard help can be used.

21.5.67288.0 - 2023-03-15#

Hotfix

  • Bug during subsequent applying advance payment invoice / several payments (#5488, AZ-66)
    If a payment and advance payment invoice apply was reversed and applied with a new advance payment invoice, too many posting were made.

21.5.66374.0 - 2023-03-09#

Hotfix

  • Correction of copy function projects (#5348, AZ-53) When copying the project, the Advance Chain was deleted in the original project, this is now prevented.
  • Error Renaming a job (#5382, AZ-55)
    Issue was solved.
  • Error message - Posting the delivery from the sales order (#5441, AZ-52)
    Advance Chains are only checked for invoice.
  • Correction Attachment Default Dimensions for Security Deposits (#5457, AZ-65)
    It is now possible to store default dimensions for table SecurityDeposit.

21.3.57805.0 - 2023-01-13#

Hotfix

  • Deletion of Advance Planning Entries leads to deletion of unrelated Advance Invoice Lines (#4858, AZ-42)
    When deleting an Advance Planning Line BC tries to automatically delete any unposted invoice lines related to this Advance Planning Line. In some cases BC identifies the wrong invoices and hence tries to falsely delete them.

Change

  • Transfer Deposit to Advance invoice based on amount (#4865, AZ-43)
    When specifying deposits for advance planning lines you can either specify a percentage or a fixed amount. Previously BC always referred to the percentage when creating the Advance Invoice. This could result in unexpected amount differences when the Advance Invoice amount differed from the planned amount, e.g. due to cumulated invoice planning.
    Now BC will save whether the percentage or the amount has been specified for a deposit and will transfer the deposit accordingly to the invoice.

21.2.55009.0 - 2022-12-20#

Hotfix

  • Error on applying Payment with Job-related Advance Invoice, unrealized VAT and regular Receivables/Payables Account (#4622, AZ-38)
    When using the same Receivables/Payables Account for Advance Documents and regular Documents and posting a job-related Advance Invoice with unrealized VAT, then application with a payment fails due to the error message: "Posting Date must have a value in Advance Job Ledger Entry".

21.2.53024.0 - 2022-12-07#

Change

  • General performance and stability improvements.

21.1.49930.0 - 2022-11-16#

Change

  • Management of Deposits (#3482, AZ-21)
    It is now possible to specify deposits for advance invoices and closing invoices. When invoices are created, negative lines for the deposits amounts are listed in the respective invoice, so that the deposit amounts are deducted from the invoice amounts.

    When invoices containing deposit amounts are posted, an additional invoice document with the respective retention amount is posted for each deposit amount.
  • Cumulative Advance Planning (#4096, AZ-32)
    With new settings in the Sales&Receivables/Purchase&Payables Setup it is now possible to enable cumulated Advance Planning. This provides additional columns in the Advance Planning Chart to specify the invoice amounts cumulated (total balance incl. previous Advance Invoices)
  • Compare Advance Plan Amount with posted Invoice (#4097, AZ-33)
    A new setting in the Sales&Receivables/Purchase&Payables Setup allows to specify whether Advance Invoices should be compared to the original Advance Planning Entry when posting the invoice. If desired the Advance Planning Entry can be automatically updated to match the posted invoice.

Hotfix

  • Custom-specific Invoice Adresses are not transferred to Advance Docs (#4305, AZ-34)
    A sales order/purchase order is given a custom-specific invoice address. Now an advance payment plan is specified at the order/purchase order and advance invoices are generated.

    The user-defined invoice address data was incorrectly not taken over to the advance invoice.
  • No creation of Order Flow Entries for Advance Documents (#4307, AZ-27)
    Advance Invoices / Credit Memos will no longer create Order Flow Entries.