In this article
Use weighted totals and a fixed fee scope so a rate comparison reflects the activity you actually mean to compare.
A percentage can be arithmetically correct and still answer the wrong question. Processing fees divided by card sales describe one thing; the same fees divided by sales after refunds describe another. Combining card and ACH volume in only one side of a comparison produces a third measure. Before reacting to a rate change, define both the numerator and the denominator.
Write the definition next to the result
Helcim’s statement guide defines a card brand’s effective rate using its processing fees divided by its sales amount. For your own comparisons, state which fees and which sales you included. Keep that definition constant across periods. If you also want a broader business-cost measure, calculate and label it separately rather than quietly changing the meaning of “effective rate.”
Use dollar totals to combine groups. Averaging two percentages gives each group equal weight even when one group has ten times the sales of the other. A valid arithmetic mean is not automatically a valid overall rate. The weights must match the measure you are describing.
Work a weighted example
In a fictional month, channel A processes $9,000 with $180 in fees. Its effective rate is 2%. Channel B processes $1,000 with $40 in fees. Its rate is 4%. The simple average of 2% and 4% is 3%, but the combined business processed $10,000 and incurred $220. Its weighted overall rate is 2.2%.
For a second fictional month, suppose channel A processes $5,000 with $100 in fees and channel B processes $5,000 with $200. Each channel’s assumed rate is unchanged, yet the combined result is $300 divided by $10,000, or 3%. The overall increase comes from the shift toward channel B. This does not prove that any real channel has those rates; it demonstrates a mix effect.
Now consider refunds. If the first month also includes $500 of refunded sales, dividing $220 by $9,500 gives about 2.32%. That might be a useful separately labeled measure of fees relative to net sales, but it is not the original 2.2% gross-sales calculation. The business should not compare one month’s gross denominator with another month’s net denominator and attribute the difference to pricing.
Look at ticket size as well as volume
With an invented fixed fee of $0.15, ten $100 payments incur $1.50 in fixed fees, while one hundred $10 payments incur $15. Both groups process $1,000. This isolates the fixed-fee effect without assuming anything about Helcim’s actual rates or the percentage costs. Transaction count deserves its own column because volume alone cannot explain every movement.
Helcim’s export instructions allow the reporting population to be filtered. Use consistent status, date, terminal and payment-type selections when building your comparison. Check whether a file includes attempted or declined transactions before using its row count as the count of completed sales. Preserve the unedited source file so an accidental spreadsheet change does not become the new evidence.
Make the comparison reviewable
- Name the period and currency.
- State the included fee categories and sales definition.
- Show sales, fees and completed-transaction count before showing a percentage.
- Separate channel or payment-type mix changes from changes within a group.
- Flag one-time items instead of silently deleting them.
A useful conclusion is specific: “The overall rate rose because the higher-cost group became a larger share of these fictional sales; neither group’s assumed rate changed.” For actual records, you may need several explanations. Stop at what the evidence supports. A two-decimal percentage can look precise while its inputs remain incomplete.