5.7.3.9

CRM.COM release 5.7.3.9 includes the following features, enhancements & bug fixes:

Issue key	Summary	Description	Issue Type	Components
V5-6720	Enhancements when setting up Tax Regions and Rates	Enhancements for setting up Tax Regions and Rates: Automatic creation of a default Tax Region during Business sign-up Name: Default Model: Tax inclusive Countries: The business’s base country Easier set up and management of Taxes per country within the region.	Improvement	ACCOUNTS
V5-6718	Invoice of an Order gets rejected due to CRM.COM Wallet balance	Upfront order's invoice is rejected at the time of order placement due to insufficient wallet balance, even though the account has a credit limit sufficient to cover the invoice amount.	Bug	ACCOUNTS
V5-6848	Automatically update shared products when B2B Merchant makes a change	Enable automatic updates to shared products when the B2B Merchant makes changes, including: a) Product name and description updates b) Product price adjustments This ensures consistency and alignment across B2B peer product catalogues.	Improvement	BUSINESS NETWORK
V5-6595	Ability for a Businesses signing up to CRM.COM platform to accept Terms & Conditions	Terms & Conditions acceptance Enable businesses to review and accept CRM.COM’s Terms & Conditions during the sign-up process. When CRM.COM updates its Terms & Conditions, businesses must reaccept the revised terms to maintain uninterrupted access to the platform.	New Feature	CONTACTS
V5-6771	Ability to notify multiple users of the fulfilling organisation using their email address	Enhance Automations to explicitly specify a number of email addresses to notify fulfilling organisation users that an order has been placed.	Improvement	ORDERS
V5-6857	Issue when updating a Service Request entity	An error occurs when attempting to update a Service Request assignable entity using an API key, where the specified user cannot be found.	Bug	SERVICE REQUESTS
V5-6872	Payment driven topup does not extend the termed period	Payment driven topup does not extend the termed period	Bug	SUBSCRIPTIONS
V5-6871	Usage not billed	A post-bill subscription that has never been billed has pending usage records. When the bill subscription API is called to bill the service in advance (with a price of 0) and its consumed usage, no invoice is generated and the subscription terms remain unchanged.	Bug	SUBSCRIPTIONS
V5-6855	Issue when billing a service with no applicable prices	Issue when billing a service with no applicable prices. The service is to be billed but service delivery does not identify a price applicable for the service product. In such cases the service is considered as invalid to be billed and should be deactivated (since invoicing will fail).	Bug	SUBSCRIPTIONS
V5-6850	Customer billed twice for the same billing cycle	Customer billed twice (2 different invoices) for the same services and billing cycle. So two payments were also posted.	Bug	SUBSCRIPTIONS
V5-6847	Top-up with commerce pool does not trigger payment driven flow	Top-up with commerce pool does not trigger payment driven flow. Commerce pocket is credited but the service is not added to the subscription. There are no product dependencies, the contact already has a cancelled subscription that used to include the same service.	Bug	SUBSCRIPTIONS
V5-6844	Issue when applying event-based charges during trial	Event-based charges are applied when a service is initiated. The service is added as a trial on a subscription BUT then gets upgraded/downgraded to another service during the trial period. This results in removing the fee. The process should be enhanced so as to check whether to keep the fee or not for the new service i.e. if the service is removed due to a change AND the new service to be added is also applicable for the same fee, then keep the fee (if the fee is related to the initiation event).	Bug	SUBSCRIPTIONS
V5-6804	Automatic grace period automation issue	Subscribers repeatedly receive a grace period because the automation is triggered each time a deactivation is attempted. Update the default automation behaviour to prevent consecutive grace periods. If a subscription exits grace and, on the same day, is flagged for deactivation due to outstanding debt, the system should proceed with deactivation instead of reapplying grace.	Bug	SUBSCRIPTIONS
V5-6795	Subscription analytics issues	Number of subscribers vs number of subscriptions do not match for a business where each contact has a single subscription with a single service.	Bug	SUBSCRIPTIONS
V5-6782	Post-billing usage issue	Billing always bills usage on a post-bill basis. Review billing of UDRs for pre-bill termed services Issue description 1st of month is the billing date and a payment intent is created intent is posted on the 8th May invoice is issued on the 8th of may (instead of first due to delayed/asynchronous payment) which is ok BUT it ALSO include all UDRs created from 1st may to 8th May expected result was to bill usage records up until the cut of date which is set on the 1st of month	Bug	SUBSCRIPTIONS
V5-6764	Issue when applying prorating rules	Issue when applying prorating rules	Bug	SUBSCRIPTIONS
V5-6741	Managing anniversary billing based on billing day	In anniversary models, when the billing day is set by user/customer then we always bill based on that date and the day is never reset: Not clear if the customer opted-in to specific day When trying to set the day e.g. 1st of month and currently the api says 1st of month, then you cannot change it. Therefore on reactivating the subscription the billing date is reset	Bug	SUBSCRIPTIONS
V5-6730	Issue in provisioning information returned by the GET device Web API	The GET Device Web API returns provisioning details for only one provider, even though the device is provisioned by two providers.	Bug	SUBSCRIPTIONS
V5-6728	Automatically activate services via Automation based on their state	Automatically activate services via Automation based on their state i.e. enforce the re-activation if the service is in Draft and/or Not Effective state.	Improvement	SUBSCRIPTIONS
V5-6856	Issue when using Web API to upload files	Issue when using Web API to upload files.	Bug	USER EXPERIENCE AND TECHNICAL
V5-6852	Issue when sending multiple IRD commands through utility	Provisioning providers utility issue. Select to send a command to all contacts having a specific service - an unhandled error is thrown. The expected behaviour was to send the command to all devices on which the specified service(s) is enabled.	Bug	USER EXPERIENCE AND TECHNICAL
V5-6824	Issue in app settings screen - cannot request to publish	Issue in app settings screen - cannot request to publish, unhandled error thrown.	Bug	USER EXPERIENCE AND TECHNICAL
V5-6777	Enhanced SMPP Integration setup	Enhancements in SMPP parameters so as to allow multiple TON and NPI	Improvement	USER EXPERIENCE AND TECHNICAL
V5-5985	Issue with base Country after business sign up	A default country is specified on business sign up. During the onboarding process, the business owner is requested to specify the base country of operations. Change base country does not work as expected because the user must first enable another country and then switch from the initially set base country.	Improvement	USER EXPERIENCE AND TECHNICAL
V5-6734	Ability for a POS user to initiate an OTP for a spend to be sent to a contact	Subject to integration, a POS user can initiate an OTP for a spend to be sent to a contact. Applicable in cases where contacts do not have access to request an OTP to spend.	Improvement	WALLET
V5-6784	Introduce new 'Restricted visibility' option for product	Introduce a new option to mark products as 'restricted visibility' when they are not intended for general use or are not fully defined. Products marked this way: Are excluded from ordering flows Do not appear in best-selling product lists Are excluded from recommendation results Despite these restrictions, such products remain eligible for use in reward offers.	Improvement	PRODUCT CATALOGUE