## Theme
This Engager Live session focuses on providing comprehensive updates regarding Engager's ongoing development, including new integrations, system improvements, and upcoming features. It also serves as an interactive Q&A forum, addressing user queries on various functionalities, best practices for using Engager, and insights into the future of ID verification and AML compliance.
## Key Points
* **Imminent Major Releases:** Engager is preparing for a busy 6-8 week period of significant releases, including the Adfin and Xenon integrations, and a new Proposals feature.
* **Zama Integration Enhancements:** Crucial fixes are being rolled out for the Zama integration to drastically reduce notification spam and improve the handling of varied address formats.
* **Companies House ID Verification:** Engager is planning to implement a dedicated, functional field for Companies House director codes, including verification capabilities, contingent on Companies House finalising their API.
* **Efficient Communication Management:** The importance of utilising Engager's dedicated CRM communication section for logging all client interactions, meetings, and calls is highlighted for robust record-keeping and accountability.
* **AML Compliance Strategy:** A dual-system approach is recommended for AML, leveraging Xama for client-facing ID checks and the TaxCalc AML Center for internal firm policies, risk assessments, and staff training logs.
## Highlights
* ` "In this age, we shouldn't be handling those kind of documents. You shouldn't be asking the client to come in and show you their passport or proof of ID. Because without electronically verifying those documents, are you qualified to tell me that's a genuine passport or driving license? I know I'm not."-- Johann `
## Chapters & Topics
1. **Adfin Integration and System Updates**
> The Adfin integration and the fixes for the Zama connection, including the pop-up issue, are being released together. The delay is to ensure thorough testing is completed to avoid user frustration.
* The Adfin integration is slightly delayed due to a 'horrible loop' in how client phone numbers are stored and updated between Adfin, QuickBooks, Xero, and FreeAgent.
* When the Adfin integration is released, it will include a series of improvements for the Zama connection.
* The update will fix an issue where a single address change for an individual linked to multiple entities (e.g., 26 different companies) generates multiple notifications. After the update, only one notification will be sent.
* New programming rules have been added to help correct address formats for Zama, addressing issues with variations in how 'United Kingdom' is entered (e.g., UK, England, Scotland, Ireland, different capitalisations), noting that Northern Ireland is not accepted.
* An example was cited where one client's house move created 26 different notifications because they are related to 26 different entities.
* The constant Zama pop-up issue will be resolved with this same update.
* A future plan is to replace the free-text country field with a drop-down menu to prevent formatting issues, but this is a larger project for a later date.
2. **TaxCalc Integration Update**
> Significant progress is being made on the TaxCalc integration. An interim bulk-import solution will be available shortly to help users get started, with full integration features expected to be tested and released over the summer.
* An interim solution has been created to allow users to bulk export data from TaxCalc and import it into Engager.
* This involves a spreadsheet that can be imported into TaxCalc's PM reporting tool to collect the necessary information in the correct column order.
* Users can then copy and paste this data into the Engager import sheet.
* The full integration with TaxCalc is making 'very good progress'.
* Testing of the 'Zenon' component is planned for the following week within the speaker's firm.
* A general public release is anticipated a 'couple of weeks' after testing begins, specifically between seven and 21 days.
* Testing for proposals is also expected within the 'next couple of weeks'.
3. **Saving Custom Report Views**
> Currently, it is not possible to save custom job views or report settings; the filters must be set up each time. The ability to save views is on the long-term plan but is not yet implemented.
* A user asked if it's possible to save the settings for a custom report, for example, the number of self-assessment returns completed since 2006.
* The current method to get this information is to go to the 'Jobs' section, filter by work type and set a future deadline date (e.g., 31st January 2027).
* The system shows future jobs because when a job is completed, the next recurring job is generated.
4. **Storing Companies House Director Codes**
> A dedicated and functional field for Companies House director codes will be built once Companies House confirms its API. This is dependent on their timeline, which could be 18-24 months.
* A user asked about adding a field in Engager to capture the new Companies House codes for directors.
* The plan is to add a new field in the 'Tax References' section for a client, but this is contingent on Companies House finalising their API.
* The new functionality is intended to not only store the ID but also verify it with Companies House, similar to the existing VAT number verification.
* The development from Companies House is expected to take place over the next 18 to 24 months, and their plans are currently 'quite fluid'.
* Companies House is also considering requiring accountants to perform ID verification by reading the NFC tag in passports or driving licenses, which adds complexity and would require a phone app.
5. **Adding Specific Job Roles**
> This feature is on the ideas list and is likely to be implemented to bring functionality in line with TaxCalc. The speaker hopes it will be addressed at some point this year, but there have been no further discussions on it at the moment.
* A user asked if it's possible to add more specific job roles, such as 'Tax Manager' or 'Payroll Manager', beyond the current 'Director' and 'Manager' options.
6. **Finding Comments on Completed Jobs**
> To view comments from a completed recurring job, you must open the next occurrence of that job. The previous comments will be displayed there, forming a timeline.
* A user asked how to find comments on a job that has been completed.
* Comments where users are tagged are carried forward to the next occurrence of that recurring job.
* When viewing the new job, the comments from the previous job appear at the bottom, creating a historical timeline.
* An example showed comments related to a 2025 deadline appearing on the newly generated job for the 2026 deadline.
* These comments are specific to the job and do not appear on the main client summary page.
7. **Accessing Webinar Recordings**
> All webinar recordings since January 10th, 2024, are available in the Engager Help Centre under 'Weekly Q&A session recordings'.
* A user asked where to find the recordings for the Engager Live webinars.
* The recordings from last week and this week will be uploaded tomorrow.
8. **Upcoming Engager Team Events**
* A list of upcoming events where the Engager team will be present is available on the Engager website under 'upcoming events'.
* TaxCalc Roadshow in Birmingham: July 17th (tomorrow), a free event.
* AccountX Manchester: Attended by Johann and Marcus.
* TAG Conference: In October, attended by Marcus or Johann.
* 2020 Innovation Conference: October 23rd in Birmingham, attended by Marcus.
* ICB Annual Conference: In London, attended by Johann and Marcus.
* FAB 2026: In March, attended by Johann, Marcus, and potentially Andy T.
* DAS 2026: Confirmed for October 26, attended by Johann, Marcus, and probably Andy T.
9. **Managing Communication Notes in Engager**
> Using the dedicated communication section provides a robust log for all client interactions, which can be used to verify meeting attendance and commitments.
* Meeting notes and communication records should be stored in the 'Communication' section of the CRM in Engager, not in job comments.
* This section can log emails, text messages, meetings, and calls.
* When logging a meeting, you can record the date, duration, location (e.g., Johan's Zoom meeting), and attendees (both staff and clients).
* The system allows tracking attendance details, such as who was late, who didn't show up, and the reason for absence.
* Summaries and transcriptions from AI recording tools (like Teams, Zoom, Fixer, AI, Claude, Firefly, Otter) can be pasted into the meeting description.
* Relevant documents can be linked or uploaded to the meeting record.
* Ad hoc tasks can be created from a meeting, and their status is visible within the meeting log.
* It is not possible to link a service to a meeting, only ad hoc tasks. This is because services roll over, which would break the links, whereas tasks are one-off.
10. **AML and Training Log Management**
> While Xama is excellent for client ID verification, the TaxCalc AML Center offers more robust features for managing a firm's internal AML policies, procedures, and training records.
* A user, Callie, uses the meetings feature to record training webinars and AML training.
* Johann suggests using the dedicated training log within the TaxCalc AML centre for proper CPD logging and generating reports for governing bodies.
* For firm-wide AML management, Johann's firm uses a dual-system approach:
* Xama is used for client-facing ID checks and client risk assessments due to its excellent customer journey.
* TaxCalc AML Center is used for managing the firm's internal policies, firm-wide risk assessments, and staff training logs, as it provides a better audit trail of reviews and updates.
11. **Managing Custom Fields for Tax Reminders**
> To effectively manage tax payment reminders via email, it is best to maintain two years of data in custom fields and recycle the oldest fields annually, rather than creating new ones each year or deleting past data.
* A user, Miriam, asked whether to create new custom fields for 2025 tax reminders or overwrite the 2024 data.
* Johann advised against deleting the 2024 data.
* He suggested maintaining two years' worth of data at any time by having separate fields for each payment period (e.g., '24 January', '24 July', '25 January', '25 July').
* The oldest fields can be recycled for the next year (e.g., in February, rename the '24 fields to '26 fields) while keeping the current year's data.
* Historical data, if needed, can be found on the SA302 or tax calculation documents.
12. **ID Checks and The Future of Verification**
* TaxCalc is developing new ID check features that will have a customer journey similar to Xama, including NFC passport checking required by Companies House.
* Other providers like Inform Direct are also reportedly looking to partner with firms for ID checks.
* The speaker praised Xama's efficient customer journey, which sends a link to the client to upload their documents directly.
* Manually handling sensitive documents is discouraged due to the difficulty in verifying authenticity without electronic tools and the associated security risks.
* Companies that provide ID verification services are highly advanced, serving banking, solicitors, insolvency practitioners, and other sectors with stringent AML requirements.
13. **TaxCalc's 'What-If Planner'**
> The 'What-If Planner' is a fantastic, low-cost value-add that enhances client service by providing proactive tax estimations.
* The 'What-If Planner' is a feature in TaxCalc for self-assessments that costs around £80 a year.
* It uses the current year's income to estimate the next year's tax bill based on the upcoming year's tax brackets.
* This provides a proactive service to clients, who will either appreciate the estimate or be prompted to discuss changes in their circumstances.
* Discussions about changing circumstances can be monetised as a separate tax consultation.
14. **Upcoming Product Releases and Roadmap**
> A busy 6-8 week period of significant releases is planned, including new integrations with Adfin and Xenon, improvements to the Xama integration, and a new Proposals feature.
* There will be a series of major releases over the next six to eight weeks.
* Adfin Integration: Release is imminent, slightly delayed by a phone number formatting issue that is being resolved.
* Xama Integration Fixes: Will be released alongside the Adfin integration. This will reduce the number of notifications and resolve issues with UK location data.
* Zenon Integration: Testing is expected to begin next week, with a public release projected for 7 to 21 days after testing starts.
* Proposals Feature: Coming shortly after the Zenon integration. The accountant-facing side is complete, and work is being finalised on the client portal.
* Integrations are the most complex features to build due to the lack of data standardisation across different platforms (e.g., Xero and QuickBooks store telephone numbers differently, requiring different formats for country code, area code, and number).
* Engager's central role in numerous integrations means new integrations must consider impacts on existing ones.
## Suggestions
* For now, it is suggested to store the new Companies House codes in a custom field or within the 'Software Credentials' section.
* To access the recordings, click on your name in the app and select 'Get Help', or navigate directly to help.engager.app. The recordings from last week and this week will be uploaded tomorrow.
* Use the communication log to back up conversations with clients, especially regarding meeting attendance, as it provides a verifiable timeline of interactions.
* Create tasks for team members directly from a meeting to ensure they read the notes or complete follow-up actions, and track their completion status within the meeting log.
* Consider using TaxCalc's 'What-If Planner' for self-assessments as a proactive value-add service for clients.
Comments
0 comments
Article is closed for comments.