Glantus Holdings

If you need a single end-to-end P2P/AP suite

• If primary requirements are OCR capture, workflow approvals, supplier portals, and payments, full-suite vendors (Coupa, Basware core, SAP) may provide a more suitable integrated solution.

If your ERP environment is unusually complex and you lack integration resources

• Available evidence indicates integration can require third-party consultants in some ERP contexts (Dynamics AX example). If integration funding and resources are not available, time to value will be delayed.

If you require extensive independent review validation

• Public review coverage for Glantus/AP Protect is thinner than major competitors, which can make it harder to verify support experiences and negative outcomes at scale.

If you need transparent self-serve pricing

• Pricing for enterprise AP tools is commonly quote-based. If procurement requires published list pricing, expect friction; the UK G-Cloud listing may be an exception for eligible public-sector buyers.

Current limitations acknowledged by the vendor

• Rebranding and migration complexity: Vendor messaging indicates glantus.com will redirect to basware.com and DataShark is becoming Basware AP Protect; this can introduce practical confusion during procurement and support transitions.

Roadmap and availability

• Basware event materials discuss ongoing AI and product evolution post-acquisition, but public timelines for AP Protect feature evolution are not clearly documented in accessible sources.

Scale limitations

• No public documentation was found describing specific scale limits.

Security or compliance gaps

• While ISO certifications were referenced in historical Glantus materials, public documentation for SOC 2, data residency options, and detailed enterprise IAM controls was not found in the accessible sources.

API limitations or integration constraints

• Public information on API capabilities and integration constraints is limited; reported integration complexity in at least one ERP environment implies integration workstreams may be non-trivial.

Competitive advantages validated by customer feedback (evidence-based)

• Some reviewers reported effective ERP integration in their specific environments and faster document retrieval that reduced paper storage.
• The product's specialization is on profit leakage prevention and recovery and on fraud detection signals layered over existing AP/ERP systems.

Differentiation from competitors (evidence-based)

• Glantus is positioned as a specialized control layer for overpayment/fraud detection rather than a general-purpose P2P workflow or payments platform. The acquisition by Basware was presented publicly as an effort to expand overpayment and fraud detection capabilities within Basware’s broader AP offering.

Areas where competitors have clear advantages

• AppZen: Broader cross-process audit coverage (AP and expense) and a larger public profile in AI-based auditing.
• apexanalytix: Established presence in recovery and supplier risk programs with visible review coverage in some analyst portals.

Review platform availability and coverage constraints (important context)

• DataShark has a G2 listing with a small number of reviews from earlier years, with mostly positive ratings and limited negative feedback in publicly accessible excerpts.
• A Glantus/DataShark page on several other major review platforms was not located in accessible search results, which may indicate branding/listing gaps.

Representative reviewer feedback (paraphrased for clarity)

• Positive: A reviewer described the product as efficient for document retrieval, reporting infrequent issues and noting that it integrates with their ERP system.
• Positive: Another reviewer described Glantus Data as an effective and efficient provider and noted a user-friendly interface.

Critical or caveated reviewer feedback (paraphrased)

• Implementation friction: One reviewer reported that integration into their ERP (Dynamics AX) required engagement of a third‑party consultant due to ERP complexity, indicating potential integration effort for some environments.

Why customers chose this product over alternatives (evidence from reviews/case materials)

• Reported reasons include faster document retrieval and digitization (reducing paper storage), and successful ERP integration for some customers.

Why some customers left for competitors (churn reasons)

• No credible public churn narratives were found. A general procurement risk is that post-acquisition rebranding and consolidation can cause procurement and support navigation challenges.

Specific outcomes customers claimed (with caveats)

• A reviewer claimed a substantial reduction in AP headcount following implementation; this is a reviewer statement and not independently verified. Buyers should request before/after staffing and process metrics.

Deal-breakers and reasons customers didn't purchase

• Not available in accessible sources.

• Detecting and preventing AP profit leakage (duplicate/erroneous payments, overpayments)
• Fraud detection signals (including vendor/bank detail changes and anomalous patterns)
• Reconciliation and visibility across ERPs and legal entities

• Enterprise and larger organizations or scaling companies with significant AP volumes and multi-ERP complexity.
• Use case emphasis is on profit protection (pre-payment prevention and post-payment recovery analytics) rather than simply invoice capture and workflow.