Data Mart ETL - 2026-11-12
In this release:
- Customer payment write-off amount (breaking change):
writeOffAmountoncustomerPaymentsnow covers the payment's open applications only, like Visma.net ERP. - Supplier payments applied to debit adjustments (breaking change):
appliedAmountandunappliedBalancenow subtract a debit adjustment applied to an unreleased check. - Base-currency amounts on payments: new base-currency fields on
customerPaymentsandsupplierPayments.
Customer payment write-off amount (breaking change)
Breaking change. On customerPayments, writeOffAmount added up the write-offs of all applications of the payment, including applications that were already released. It now returns only the write-off of the payment's open (unreleased) applications. This is the write-off amount Visma.net ERP shows on the payment.
Payments whose write-offs are all released now return 0 where they returned an amount before. Payments without write-offs are not affected.
The write-off of every application, released or not, stays available on customerPaymentLines: each line has balanceWriteOff and released.
What you need to do:
- If your integration uses
writeOffAmountas the total written off over the payment's life, sumbalanceWriteOffover the payment'scustomerPaymentLinesinstead. Lines withreleasedset totruegive the amount already posted. - Otherwise, no action is needed.
Supplier payments applied to debit adjustments (breaking change)
Breaking change. On supplierPayments and apPayments, a debit adjustment applied to an unreleased check or void check was added to appliedAmount instead of being subtracted. appliedAmount was too high and unappliedBalance too low for these payments.
Both fields now follow Visma.net ERP. For example, a check of 900 applied to a bill of 1 000 and a debit adjustment of 100 now returns appliedAmount 900 and unappliedBalance 0 (before: 1 100 and -200).
Field names and types are unchanged. Payments without a debit adjustment among their open applications keep their value.
What you need to do:
- If your integration corrects these amounts on your side for debit adjustments, remove that correction.
- Otherwise, no action is needed.
Base-currency amounts on payments
New fields give the payment amounts in the company's base currency, at the payment's own exchange rate.
On customerPayments:
paymentAmountInBaseCurrencyappliedToDocumentsInBaseCurrencyappliedToOrdersInBaseCurrencyavailableBalanceInBaseCurrencywriteOffAmountInBaseCurrencyfinanceChargesInBaseCurrencydeductedChargesInBaseCurrency
On supplierPayments and apPayments:
unappliedBalanceInBaseCurrencyappliedAmountInBaseCurrencyfinanceChargesInBaseCurrency
For a payment in the company's base currency, each new field equals its document-currency counterpart.
Existing payments
Existing customer and supplier payments are corrected and get the new fields as part of the release. The correction updates updatedInDataMartDateTime, so an incremental fetch picks up the corrected payments. Until a payment has been corrected, the new fields are not returned for it.