Software categories

For suppliersAbout us

Centuri
vs
Azets Expense

Company size

Number of employees

Microenterprises (1-10)
Small business (11-100)
Medium-sized enterprises (101-500)
Large companies (500+)
Microenterprises (1-10)
Small business (11-100)
Medium-sized enterprises (101-500)
Large companies (500+)

Platform

Cloud service
On-premises
Mobile app
Cloud service
On-premises
Mobile app

Price information

Free trial
Price model module
Subscription price model
Price model license
Free trial
Price model module
Subscription price model
Price model license

Product features in Document Management System

Advanced search function
Document templates
e-signing
Integratable
Notices
Permission management
Reading Quotes
Real-time management
Traceable changes
Version management
Advanced search function
Document templates
e-signing
Integratable
Notices
Permission management
Reading Quotes
Real-time management
Traceable changes
Version management

Reviews

Based on 10 reviews

Based on 2 reviews

Ease of use
Cooperation with the supplier
Support and service
Range of functions
Customisation and flexibility
Integration
Value for money
How satisfied are you overall?
Ease of use
Cooperation with the supplier
Support and service
Range of functions
Customisation and flexibility
Integration
Value for money
How satisfied are you overall?

Reviews

Pros

What we appreciate most about Centuri is the scalability. We can add/remove users as needed. WE can also add different uses as needed. This makes us feel comfortable that we pay for what we use.
Automation: Centuri offers powerful automation features that can save time and reduce manual workload. Users can create rules and workflows to automate repetitive tasks and processes.
Azets expense has streamlined receipt management and has the features we need to keep employees and managers happy.

Reviews

Cons

Some basic things like personalised view, even ex documents that are read are still visible.
We miss that Centuri provides record keeping.
What I experienced in the beginning when we implemented Azets was that it could mess up technically and was not perceived as user-friendly. We occasionally hear that some people experience it, but it probably depends more on them than the system.