Comments
We saw this behavior with a client recently. It was a pain point but we have a work around in the interim. Basically we have them Post the Fee as a Customer Charge (Miscellaneous Charge)ConfigurationCreate a dedicated Charge Code Accounts receivable → Charges → Charge codesExample: Code: CC_FEECharge category: Fixed or PercentMain account: Payment Fee RevenueSales tax group: As applicableDo NOT use AR Payment Fee setup for customer-paid fees Leave AR Payment Fees only for company-paid merchant feesTransaction FlowCustomer Payment Journal Apply payment to the invoice onlyBank reflects actual deposit receivedApply Charge to Customer Use: Customer → Transactions → Maintain charges or Add charge directly to the invoice before settlementResulting Posting Debit: CustomerCredit: Payment Fee RevenueNo bank impactNo manual settlement required
It will be very useful if we can use financial tags in Management report. It will open new possibilities for solution across system and reduce the requirements of custom fields, and it can become source for many financial reports like cash flow, fund flow, auditing etc.Regards,CA Neeraj Kumar
In the Event Planning Module, the current design allows the same Contact to register for an event multiple times.Can we have a feature that only allows each Contact to register once for each event?This makes sense, as registering the same person twice does not have any meaning. In the registration form, if we detect that the same Contact has already registered, it should return a warning or message on the front end to notify the user that they have already registered for this event.
The event registration process does not consider multiple submissions as duplicates because the platform allows a single contact to have multiple registrations for the same event. This design supports scenarios where attendees may register for different sessions or ticket types under the same event.To address your concern about preventing duplicate registrations for the same contact within the same event, the feature that should be implemented is a duplicate check at the Event Registration level. This enhancement would:Validate whether an existing registration already exists for the same contact and event combination.Block or prompt the user before creating a new registration for the same event.Provide flexibility to configure exceptions (e.g., allow multiple registrations for multi-session events if required).This functionality is not currently available out-of-the-box, as matching rules apply only to Contacts and not to Event Registrations. Implementing this feature would require either:A custom plugin for synchronous validation during registration, orA Power Automate flow with logic to check existing registrations before creating a new one.