Commission disputes often begin before the final accounting step, when a patient's original source is left out of the record. If agency or partner attribution is scattered across conversations, messages, and separate sheets, a dependable period-end list cannot be produced. Zoho CRM can make the attribution relationship visible through a lookup field, but it does not calculate the commission itself. The underlying problem is not the arithmetic but the missing timely record.
A sound model separates three elements: the partner linked to the patient, the numeric base used for commission, and the agreement's interpretation of entitlement. In supported editions, Zoho CRM can provide record and reporting structure for the first two. You define commercial decisions such as attribution duration, repeat visits, cancellations, and refunds. Period-end discussion can then rely on an established, reviewable record chain instead of circling around ambiguous names.
The dispute starts before period end
At month end, two lists sit side by side: the agency's spreadsheet and the clinic's record screen. Several names appear in both, but some are written differently in one. The discussion circles around those names while the omission remains. Because the patient's source was not recorded in a shared structure at first contact, later interpretation cannot establish attribution, and matching names cannot resolve the disagreement.
The date when a disagreement becomes visible is therefore not the date when it began. The finance team can compare available records, but retrospectively interpreting missing attribution creates no new evidence. The aim is not to prepare a more elaborate period-end spreadsheet, but to preserve the source as distinct, consistent information when the event occurs. The commission list is a periodic view of that chain.
Create a record for each partner
Keeping each partner as a separate record instead of repeatedly typing free text into patient records reduces spelling variations and ties the relationship to one identity. A partner code can be marked unique, with case-insensitive matching. Uniqueness applies only to Text, Email, Phone, Integer, Long Integer, and URL fields. The limit is two fields in most modules and three in Leads, Contacts, Products, and custom modules.
A lookup field establishes the link between patient and partner. It cannot be added to Tasks, Meetings, or Calls, and one criterion can use no more than five lookup fields. If the partner occupies a separate custom module, Free offers no such module. Custom and team modules consume the same allowance: Standard has 10, Professional 25, Enterprise 200, and Ultimate 500.
When attribution is recorded
The partner relationship belongs in the record when the patient's source becomes known. An assignment rule is not a mechanism for filling the partner field. It runs only for records created through import, web form, or API and does not trigger for manually created records. It can choose the owner, optionally create a follow-up task, and send an unassigned record to the default user. Assignment Rules & Threshold profile permission is required.
A patient first arrives through a partner's referral, then returns independently months later for a second procedure. Commission is requested for the second visit too, but the record contains no marker distinguishing it. A lookup preserves the relationship between patient and partner; it does not determine the visit or context to which that relationship applies. That distinction depends on commercial rules and record discipline.
A commission base is not a calculation
A rollup summary field in Zoho can produce a record count or calculate the Sum, Average, Maximum, or Minimum of numeric values from a related list. It is read-only, and its value appears after the record is saved. Enterprise allows 10 rollup summary fields per module and Ultimate allows 15; lower editions have none. The result can show a commission base, but it is not the commission calculation, and the total cannot be presented as the amount payable.
A workflow field update writes a fixed value or an empty value to the selected field; it does not multiply rates, perform date arithmetic, or increment counters. Such calculations can use a read-only formula field or a custom function attached to a workflow. Formula fields require Professional or above, while custom functions require Enterprise or above. Because a formula's ability to read a rollup summary is unknown, no commission calculation can be promised on that combination; the base and calculation remain separate design decisions.
The currency trap
When a clinic works with overseas partners, the same commission base can appear inconsistent because of different exchange-rate expectations. In a multi-currency account, reports, analytics, and forecasts use the rate written on the record, not today's rate. A later rate change does not mean the rate used on existing records has changed. Reconciliation therefore needs to examine the recorded rate together with each amount; otherwise, the parties may read the same records using assumptions from different dates.
The direction of the Exchange_Rate field can feel counterintuitive: its value shows how many units of the record currency equal one unit of the home currency. Converting an amount into the home currency requires dividing it by that rate. Multi-currency is unavailable in Free. Because its threshold in other editions is conflicting, it must be verified in Setup; an unknown boundary cannot be presented as a definite package feature. This check avoids tying reconciliation to an incorrect edition assumption.
Build the period-end list in advance
A reconciliation report combines only modules that are already related. A parent module connects through a lookup field, while a child connects through a related list, and one report can include at most five parent modules. A joined report places no more than three reports created from the same primary module alongside one another. Zoho reporting does not create a missing partner relationship at period end; the list begins with established record relationships. Report design is therefore not merely a formatting task left until month end.
When primary and related modules appear together in analytics, Count of measures rows rather than records; Count of Unique is needed for the true record count. On-screen reports, scheduled reports, and formatted exports have a 2,000-record ceiling. Detailed export is limited to 50,000 rows, and the organization total is 50,000 records per day. With Schedule report profile permission, scheduled reports run daily, weekly, monthly, or yearly and arrive as XLS attachments. Reconciliation frequency and output format should account for these ceilings.
What belongs in the agreement
A record structure cannot decide which event creates commission entitlement. The attribution window, the credited partner when two partners refer the same patient, whether a repeat visit creates another entitlement, and the treatment of cancellations and refunds are commercial questions for the agreement. Fields established before those decisions are written may provide orderly data, but they cannot create the correct reconciliation criterion or supply a missing contractual interpretation. Technical structure cannot replace a commercial meaning that the parties have not settled.
The inability of workflow field updates to calculate does not alter this boundary. Reports and exports can present records for review under rules defined in the agreement; they cannot replace a commercial term. Referral chain is one of the patterns in the Eksenium Clinic CRM Pattern Library (referral-chain).
Edition threshold boundaries
Zoho CRM limits need to be considered together. Free has no custom modules; Standard allows 10, Professional 25, Enterprise 200, and Ultimate 500, with custom and team modules consuming the same allowance. Rollup summaries are limited to 10 in Enterprise and 15 in Ultimate and are absent below Enterprise. Formula fields require Professional or above, while custom functions require Enterprise or above. Lookup filters and multi-select lookups require Enterprise or above. These thresholds prevent assuming that one record model can be built identically in every edition.
Standard lookup relationships and reporting across related modules are edition-independent. A module can contain no more than two multi-select lookup fields, and bringing additional fields from the lookup module requires Enterprise or above. Multi-currency is absent from Free, while its threshold in other packages must be verified in Setup. In a lower edition without rollup summaries, the commission base can be read from a report and calculated outside CRM. Attribution and commission calculation therefore stay separate, without promising an unsupported calculation.
