This week, we want to explore the difference between what the products do and what real-world workflows actually require in the Zoho community. From payment timing in Books to task visibility in CRM Blueprints, even to Forms feature gaps, teams are consistently running into the edges of platform capability — and the workarounds range from clever to painful.
Zoho Books: International Finance Workflows Are Straining at the Seams
Two separate Books threads this week expose the same underlying problem: the accounting data model doesn’t fully match how international businesses actually transact. One user discovered that GoCardless recurring invoices collect payment immediately on generation, with no option to delay collection to the invoice due date — forcing an awkward workaround of backdating the invoice generation cycle. A second thread makes an even sharper case: recording a payment in a different currency than the invoice currency requires journal entries, undeposited funds accounts, and manual reconciliation — even with Advanced Multi-Currency enabled. Both situations reflect real-world transactions that happen constantly in global businesses. If your team invoices internationally or uses Direct Debit, audit your Books payment workflows now against these specific scenarios before they cause reconciliation headaches at month-end.
Zoho CRM: Automation Reliability Concerns Surface
A new thread reporting that Blueprint transition tasks silently fail to create or display is worth watching closely — this type of issue is particularly dangerous because the process appears to complete successfully while the resulting task actually never appears. Meanwhile, the long-standing Last Name required field problem on CRM web forms resurfaced again this week, with a community member confirming that hiding the field via CSS or Zoho Forms doesn’t resolve it — the data simply fails to save correctly. Both issues point to the same risk: automations and data capture that appear to work but silently don’t. Teams relying on Blueprints for task assignment should add a verification step or scheduled report to confirm tasks are actually being created post-transition.
Zoho Forms: A Single Power User Is Exposing a Deep Feature Backlog
A remarkable pattern this week: one community member filed at least eight separate feature requests against Zoho Forms in a single day, covering sub-form fields as report filters, text concatenation in formula fields, richer date formula functions (specifically, getting month names rather than just numeric values), sub-form padding in CSV exports, and reassigning partially saved entries between users. The Zoho Forms team acknowledged most of these months ago and has not shipped them; several responses this week were explicit that they cannot be prioritized currently. Forms is increasingly being used as a serious data collection layer for field operations and multi-step workflows, and the formula/sub-form gaps make it difficult to use as a standalone solution without exporting to a spreadsheet. We recommend teams building complex Forms solutions to plan for a post-processing step on CSV exports and consider whether Zoho Creator might better serve advanced logic requirements.
Zoho Creator: AI-Assisted App Building Moves to Early Access
The Build Agent feature in Zoho Creator — which lets developers modify existing applications using natural language prompts — has entered early access for all paid plans. The agent generates a Change Summary preview before applying any modifications, using whichever AI provider is configured in Zia, and works in both edit and live mode. This is a meaningful shift for Creator developers who spend time on repetitive configuration work; the preview-before-apply model is a sensible guardrail for a production app context. Teams actively building on Creator should request early access and test it on lower-risk application components to understand where the natural language interpretation holds up and where it requires correction.
Zoho Desk: Reporting Gaps Around Resolution Timing
A Desk thread this week highlighted a practical analytics gap: there is no native field to measure elapsed business hours between ticket open and resolution entry — distinct from ticket close, which defaults to 48 hours after resolution and skews SLA metrics. Zoho’s response pointed toward custom functions via API rather than a native field, which means this requires developer involvement to solve. Separately, a user struggled to track their own open Zoho support tickets in the community portal — a sign that even Zoho’s own help infrastructure has usability friction. If your team measures technician performance through Desk, verify that your current resolution-time metric is actually capturing resolution entry and not auto-close time.
Next week, let’s see if Zoho responds to the multi-currency payment recording thread in Books with any roadmap signal, and keep an eye on whether the Creator Build Agent documentation expands as early access usage picks up.