AMPS 2.17 Release

Handling of Account Service Credits as prepayments on invoices are incorrect (WFAMPS-2291)

This application fix resolves an issue where invoices that are fully paid using service credits are not correctly reflected in the ERP process. The zero-value invoice happens when the new charges are completely offset by previous service credits, for example when downgrading a product to a lesser value. When handling the zero-value invoice, the new charges will be recognized as paid, and the credits should be reversed like a credit note.

Unable to distinguish between split addresses (WFAMPS-2942)

This application fix resolves an issue where, when “split delivery” addresses in AMPS events were configured to be combined in a single event rather than individual events, too many address changes was included in the event. This issue has now been resolved and only the split addresses that are part of the update of delivery addresses are included in the event. Future address changes are NOT included.

Remove dunning notification on Mobile Pay (MBP) (WFAMPS-3126)

This application fix resolves an issue where dunning notifications was sent for subscriptions on Mobilepay payment terms. This issue has now been resolved, and dunning notifications are no longer sent for this payment term.

Farpay Paymentfile: Processing of value in the Tag "PaymentReference" (WFAMPS-3204)

This application fix resolves an issue where the processing of payments from FARPAY lost the payment reference provided in the file. This issue has now been resolved and the payment reference is solved for later use.

“Retrieve Product [ProdRetrieveProduct]” is not returning correct data in field 'productAccessDays' (WFAMPS-3226)

This application fix resolves an issue where planAccessDays in the response was not built correctly. This has now been resolved. Also the integration specification has been updated so that the attribute is correctly referenced as “planAccessDays”. For DIGITAL only products, the days will be returned as “XXXXXXX”

AMPS to allow card type to be set in AcctManagePayMethod (WFAMPS-3259)

This application fix resolves an issue where the API “Manage Payment Method [AcctManagePayMethod]” incorrectly set card type in ARIA. It was always set to VISA irrespective of the card type used. This issue has been resolved by allowing the caller to set the card type in the API call, if one is available. For some ARIA managed payment gateway ARIA will automatically pick up the card type and other key information.

InvoiceTaxSpecification not set correctly when no taxes apply (WFAMPS-3273)

This application fix resolves an issue in the “Financial Document” XML where tax base amount for non-taxable services was set incorrectly. This has now been resolved.

PriceModelChecker causes a prorated invoice to be created (WFAMPS-3319)

This application fix resolves an issue were updating the custom rates on a subscription due to a specific price model being used (PRICE-ADJUST or PRICE-PERIOD) caused prorated charges and credits to be generated, rather than just setting the new rates and use them at the next invoice. This issue has now been resolved so that no prorated charges or credits are generated at the time of update. The invoicing_option was updated to resolve this issue.

DocmProduceAMPSXML does not handle service credits on tax credits (WFAMPS-3320)

This application fix resolves an issue where the process caused an exception when processing invoice line items referencing the tax service. If the invoice lines referencing a line type 3 (tax) and the service number is 10004, then the invoice line is a tax line, and should not be included in tax calculations.

Credit and Reissue of invoice does not credit the full amount and Billing dates does not adjusting correctly (WFAMPS-3505)

This application fix resolves an issue where tax lines on the original invoice was not processed correctly when creating the credit associated memo. Also the new billing dates for future invoices was not set correctly. This issue has now been resolved

Stampen ERP - File generated for "restart day" is missing payments (WFAMPS-3506)

This application fix resolves an issue where payment applications were incorrectly applied and caused additional postings to be created. This issue has now been resolved and all entries for unapplied payments are now processed.

Autogiro payment response file processing rejects file with failed payments (WFAMPS-3507)

This application fix resolves an issue where payments are processed even though the overall file has formatting or other logical errors. To resolve the issue, if the file received passes the format checks and validation and that the totals match, then the file should be loaded into AMPS per standard. Individual payments may still be rejected due to various errors, but these errors should be reported and corrected manually. Some transactions will also be processed as unmatched payments.

Cancellation failing due to exceeding credit amount (WFAMPS-3508)

This application fix resolves an issue where surcharges are not correctly processed when creating a credit memo on the original invoice. This issue has now been resolved.

Stampen: PRICE-PERIOD does NOT work as expected (WFAMPS-3524)

This application fix resolves an issue were updating the custom rates on a subscription due to a specific price model being used (PRICE-ADJUST or PRICE-PERIOD) caused prorated charges and credits to be generated, rather than just setting the new rates and use them at the next invoice. This issue has now been resolved so that no prorated charges or credits are generated at the time of update. The assignment_directive was updated to resolve this issue.

Enable setting of tokenized credit card when modifying billing groups (WFAMPS-3572)

This application fix resolves an issue where it was not possible to set a new tokenized credit card as the payment method, when modifying existing billing groups. This has now been resolved in “Manage Billing Group [AcctManageBillingGroup]” API.

• Billing group can change from a normal payment option like INVOICE, FIK, BANKGIRO, etc. to credit card or another ARIA managed payment method.
• Billing group can change from credit card payment method managed by ARIA to a normal payment option like INVOICE, FIK, BANKGIRO, etc.
• Billing group can change from one standard payment option to another standard payment option, for example going from “INVOICE” to “INVOICE with SURCHARGE”

Number of units is not being passed to Dimaps in START request correctly (WFAMPS-3588)

This application fix resolves an issue where the number of units sent to DIMAPS was truncated to a single digit, resulting in for example, number of units of 10 was sent as 1. This issue has now been resolved and number of units are sent based on the number of units defined on the subscription.

“Retrieve Document [DocmRetrieveDocument] response is showing incorrect period dated for invoice (WFAMPS-3589)

This application fix resolves an issue where the incorrect billing period was shown for an invoice (or document). The issue has been resolved by ensuring the for recurring invoices the subscription dates are obtained from the invoice lines, and for campaign invoices, the dates are obtained from the campaign period.

DI file error – customerSystem and Product printed twice (WFAMPS-3672)

This application fix resolves an issue where the process to generate the DI files, caused customerSystem and Product to be included twice. This has now been resolved.