Start with the Microsoft product boundary
01A comparison with Business Central answers a different question from one with Finance and Supply Chain Management. List the actual applications and environments in the shortlist, including separate sales, service, commerce, analytics or industry components. Evaluate Tellency against the resulting requirements. Choosing a product by company headcount alone misses the controls, operational complexity, data volumes and reporting that determine fit.
Test the financial and operational handoffs
02Demonstrate a customer requirement through fulfilment, invoicing, payment and bank reconciliation. Add stock moving between locations, a failed inspection and an overdue invoice. Review source records, approvals, role boundaries and final reports. Tellency has implemented stock-transfer stages, inspection outcomes, bank reconciliation approvals and reminder logs; confirm the complete configured process rather than assuming every handoff is automatic.
Make manufacturing requirements explicit
03Use a BOM revision, component cost estimate, production hold and rework or scrap decision. Tellency supports these workflows, but advanced MRP calculations, finite-capacity scheduling, specialist costing and high-volume performance need their own demonstration. Use the same quantities, exceptions and reporting criteria in each vendor’s acceptance pack, and record any additional configuration, integration or development required.
Evaluate integrations as business workflows
04For each Microsoft 365 or other connection, specify the records exchanged, direction, timing, authentication and owner. Test rejected records, duplicate events and recovery. An integration name alone does not show that a workflow is ready. Do not assume Tellency provides equivalent Outlook, Teams or Power BI connections without a demonstration, or that choosing Microsoft removes integration and data-governance work.
Compare implementation and ongoing responsibility
05Request comparable scope for users, modules, historical data, environments, training, support, updates and third-party services. Confirm who manages extensions, export access, incidents and recovery. Tellency starts at $79 USD per user per month; this is not an all-modules implementation price or proof of savings. Around eight weeks is a Tellency planning reference, subject to discovery, data readiness, integrations and acceptance.
Validate every operating jurisdiction
06For US, Canadian, Asian and MENA operations, list the entities, currencies, languages, tax outputs, payroll documents and invoicing connections required. Test each with your advisers and implementation team. An accounting module or country landing page does not establish statutory filing support. Include opening balances, stock totals and reporting reconciliation in the cutover criteria.