Note: Most mainstream review platforms (G2, TrustRadius, Gartner Peer Insights, Software Advice) primarily aggregate reviews for Vertex as a broader indirect tax platform (often “Vertex O Series” / “Vertex”) rather than a Communications Tax-specific SKU. Community discussions (Reddit) often focus on ERP integrations (e.g., NetSuite) rather than telecom-billing integrations.
- Review platforms (examples of positive feedback)
- TrustRadius (Vertex / Vertex O Series)
- A vetted review provided a favorable assessment, citing customer support and marketplace partner connectivity as positive factors; the reviewer also noted issues with reporting rollups and administrative partitioning.
- Gartner Peer Insights (Vertex O Series)
- A Gartner Peer Insights snippet noted recognition by auditors as a potential benefit during tax health-checks or reviews (full review text may require login).
- G2 (Vertex)
- G2 hosts multiple reviews for Vertex; some reviewers highlighted global tax treatments and setups beyond US sales & use tax for certain customers (though these comments often refer to the broader Vertex platform rather than Communications Tax specifically).
- Review platforms (examples of negative / cautionary feedback)
- Public review excerpts include criticisms around reporting, administration, and complexity; accessing complete low-rated reviews may require site accounts or gating.
- TrustRadius excerpts mention reporting and administration friction (e.g., rollups and environment partitioning) as recurring points of friction.
- Community/social (Reddit) — direct quotes and themes
- NetSuite-focused thread (critical):
- "I’m mentioning this because Canadian taxes are somewhat similar to EU VAT and what Vertex offered was not even a minimum viable product for Canada." (User discussing Vertex for NetSuite; context suggests dissatisfaction with a specific implementation/fit.)
- NetSuite implementation nuance:
- A user contrasted Avalara vs Vertex behavior in NetSuite, stating: "In contrast, Vertex does not have a script running on fieldChanged; they only have their Client script triggering off of the ‘Preview Tax’ button." (This indicates workflow differences that can matter operationally.)
- Tax determination oddities (NetSuite):
- A user complaint described the GST code being set to a fixed rate and questioned applying that rate to a specific tax code, suggesting configuration/mapping issues, integration behavior, or tax content expectations.
- General awareness of communications tax engines:
- In a telecom-related thread, a commenter described a process where companies collect tax changes and distribute update files, and noted that some organizations continue to use the Vertex tax engine; this is anecdotal and not an authoritative source, but indicates Vertex is perceived as a commonly used engine in some telecom contexts.
- Why customers chose Vertex (inferred from reviews and positioning)
- Familiarity with auditors and enterprise-level recognition in some reviewer comments.
- Support ecosystem and partner integrations referenced in reviews.
- The need to automate complex, high-volume, multi-jurisdiction tax calculation.
- Why some customers left for competitors (what evidence suggests)
- Sources provide stronger evidence for reasons organizations consider alternatives than for documented churn. Community discussions compare complexity and integration behavior; some users indicate Vertex can be comparatively expensive or more complex than simpler tools.