Appian Corporation [Private Offer Only]

I primarily use Appian  for digital remittance, storing information, processing transactions, and regulatory reporting, and I mainly use it for the digital remittance register.

Whenever we receive an MT103 from our corresponding bank, we upload the messages into our Appian-based digital remittance register. Appian  extracts data from different fields of MT103 or even MT202, and that information is cleaned and segregated into different fields and columns. After that, we process the remittance, and subsequently, after completing the transaction, we report it to our central bank. Appian generates the report, which is quite handy and useful. My team can interact with peer members while using Appian; for example, when a maker uploads a transaction, the checker reviews it. If there is any discrepancy or error, the checker can directly reject the transaction so that the maker can rectify and reprocess it. If everything looks good, then the checker can approve the transaction directly, making it quite time-saving and reducing errors while ensuring pure compliance.

Appian is quite smooth by nature. We have used other software and tools, but most often we used to get lags and disruptions; however, Appian is quite smooth and we did not notice any major issues. The best feature would be its reliability and smoothness. While using it, we can store data, extract data, download, and generate reports anytime, which makes it quite handy.

Remittance is a crucial part of my integral operation, so any disruption would majorly impact our clients. After switching to Appian, we never faced any disruption as it is reliable and we can generate data at any point in time, quite faster than other tools in my personal opinion. Regulators can ask for data from us at any time, and with Appian, we download data from our Appian tools to share it with them whenever they ask. I would share a real-life example: a customer's transaction processed more than a year ago. Suddenly the customer came back asking for all the details. In our previous tool, it was quite difficult to generate transaction details from over a year ago; however, while using Appian, we can pull up data using different key search fields, such as a customer's cell phone number, remittance tracking number, or MT103 reference number. We shared it with the customer instantly, and the customer was surprised we could provide all the details in such a short time. It added reputational value for our organization, thanks to Appian.

You have pointed out two major things: time-saving and reduction of error, which are key points while processing remittance. Previously, while using another tool, it was quite time-consuming to process remittance, but after switching to Appian, it can extract data from MT103, eliminating the need for manual data entry. The process has become fully automated. Previously we could process only five to ten transactions within an hour, but now, after switching to Appian, we can process about 100 transactions in an hour, making it 10 times faster. In terms of error detection, since Appian extracts data from MT103, the extraction rate is quite good, and the error rate is negligible, lower than 0.001%. We can share accurate, error-free data with the regulator, which is essential for us. Appian benefits us significantly. After receiving an MT103, we check what the remitter is, the amount, if it is under threshold for processing, and if it is from a high-priority remitter or client. Since Appian extracts data from MT103 messages and identifies top-level clients from the database, it can notify us to process their transactions with priority. Due to automated data extraction, there are fewer instances of error. In our previous tool, we reported regulatory data to the central bank manually and often received complaints about invalid purpose codes due to manual data entry. Appian handles this automatically, and after switching, our error rate has dropped significantly, resulting in positive feedback from the Central Bank of Bangladesh regarding our reduced error rates. This has greatly enhanced our organization's reputation.

Appian is fully on-premises, and we have our own system.

Appian can be improved by adding a geo-location tagging feature, which would be really helpful for identifying remitter addresses. If Appian can suggest the country based on that address, it would significantly decrease error rates in processing remittance. So far, Appian is excellent, but this addition would be a revolutionary improvement.

If Appian can handle geo-location tagging, it will increase our speed by 20 times. I suggest this improvement and hope for the best.

I have been using Appian for more than two years.

Appian is absolutely stable and reliable in my experience.

We have tested Appian during peak usage and off-peak times, and we have not experienced any issues such as lagging or system disruptions. It is running smoothly, and we hope it will continue to provide us with the same support and reliability in the future.

In terms of scalability, we have not encountered any major issues. Our volume has increased by 20% in the two years since using Appian, and it can handle the increased volume effectively.

While deploying Appian, we reached out to customer support, and their assistance was great. They were very helpful, friendly, and their professional attitude impressed us tremendously.

I would give Appian's customer support 10 out of 10 due to their next-level support.

We previously used different tools such as Finastra  and Oracle for data extraction and report generation. After switching to Appian, we realized we made the right choice, as it is much faster and more helpful than those tools, including some Microsoft products we tried previously.

It was really easy to deploy Appian for our organization; it is user-friendly and we deployed it without any major difficulties. Our development team thoroughly enjoyed the deployment process, and we completed the entire system rollout within 15 days, which was remarkably fast.

I was part of our Appian deployment team, and we deployed it for our organization.

Appian has increased our remittance processing speed by 10 times. It allows us to process a large volume of remittance in a short time, improving customer service. Using Appian is saving us five full-time employees, which is significant since we currently have only four team members. The manual processing we used to require would necessitate an additional five employees, so Appian has truly been a miracle for us.

Compared to other tools, which I prefer not to name due to privacy, Appian provides value for money, is easy to use, has a straightforward setup procedure, and offers great support from the Appian team. Therefore, my overall experience has been quite impressive.

We evaluated some Microsoft products before choosing Appian, although I cannot name them due to an NDA. After thorough assessment and testing, we found that Appian was faster and would provide the most benefit compared to the other options we considered.

On a scale of 1 to 10, I would rate Appian a 7.5. If the geo-location tagging feature gets added, then it will be a 9.5.

I choose 8, because of its reliability, smoothness, error-free report production, and its data extraction capability.

The integration capability of Appian is quite good; we have integrated it with our core banking software, and the integration is fast and reliable. The API works exceptionally well, so in terms of integration, I would rate Appian 9.5 out of 10.

If I compare it with other tools, our team members really enjoy using Appian. It is straightforward and user-friendly, leading to positive feedback and making it highly recommended for new users due to its ease of learning and use.

Appian's security features are quite top-notch as it has a user verification system that verifies users before granting access to the whole system. In terms of regulatory compliance, it is quite helpful since it enables authentic and error-free reporting, which leaves us satisfied.

Appian's documentation is quite helpful; while deploying the system, it assisted us greatly. I would recommend these resources to other users and development teams considering deploying Appian.

Appian's automation capability is excellent; it extracts data automatically, and the scheduler runs smoothly, generating reports in a timely manner. Therefore, Appian is quite effective and helpful in terms of automation.

I highly recommend using Appian to others. My overall review rating for Appian is 7.5 out of 10.

I mostly use Appian  for internal applications in the firm.

The most beneficial aspect of Appian  is its data management capabilities and the process engine in general. It allows for a seamless transition from process-centric to data-centric operations. Additionally, the zero-code integration feature is remarkable, allowing for ease of data transfer and workflow enhancement.

I would like to see more enhancement in the user interface to allow more freedom in designing the sites and pages. The user interface should be updated for a more modern and appealing look.

I have been working with Appian for around fifteen years.

So far, I find Appian reliable and stable.

Appian is scalable, but it depends on how you build your applications. With a proper setup, Appian is scalable.

The technical support is generally good. Though I have had some issues in the past, overall, I consider it effective.

I have experience with Microsoft Power Apps  and have seen OutSystems . However, most of my experience has been with Appian.

The initial setup of Appian was very easy.

No implementation strategy was used. We simply built different platforms like development, testing, UAT, and production.

Appian is very efficient, allowing us to build a lot of applications within a financial year, making it cost-effective.

The pricing of Appian is based on the number of users and generally ranges from 70 to 100 USD per user per month. I would like it to be more flexible, not solely based on the number of users.

As alternatives, I have worked with Microsoft Power Apps  and have explored OutSystems .

I would recommend looking into data management, reporting, and process capabilities of Appian. Overall, I rate Appian as a nine.

I use Appian  for creating applications, including BPM  applications.

Appian  allows us to manage the entire database. I can create tables, perform database-related activities, and create multiple tables. I can directly create foreign keys, connect tables, and manipulate data using expression rules. This feature replaces data workflow from on-premises.

Since I have just started using Appian for three to four months, I haven't explored every part of it, so there might be areas that need improvement that I am unaware of.

I have been using Appian for the last three or four months.

The deployment process is very easy. I create a package for the component I work on and deploy that package to another environment.

Appian is a stable product and works very well.

Initially, without much coding, I can easily handle five thousand records. However, for more than five thousand records, I have to manage with some coding.

Appian has a community where I can put my questions. I haven't had a chance to contact the support team directly.

My experience with the initial setup is normal as I didn't get a chance to work on it. I started directly with creating features after the initial setup.

I would rate Appian nine out of ten. I would definitely recommend it to others. Being an initial user, I haven't had a chance to explore it much. I rate the overall solution nine out of ten.

I am working with all of these products: Pega, Appian , and OutSystems . I use Appian  as a process orchestrator for workflow and rule-based routing, and it is preferred when I am developing an enterprise-wide application. The application is mobile-friendly, allowing me to use it across any device, whether mobile, laptop, or desktop.

It is easy for me to define the process and create configurable workflows. Additionally, they have provided inbuilt integration points and services, which facilitates integration with external services.

If there is a very complex process that includes a lot of data transitioning and memory-centric processes, it consumes a lot of memory. For those use cases, Appian needs to optimize memory utilization. AI-related features should also be more integrated.

I have been in this ecosystem for quite some time. For Pega, it is 20 years, and for Appian, it is more than ten years.

I would rate the stability as eight out of ten. As a product, there are no issues. It depends on how it has been designed and how it has been configured.

Appian is scalable in its architecture.

Their customer service is responsive, and the team is very prompt for support. The response depends on the kind of partnership vendors have and their relationship with them. For step one issues, which impact most of the business on that workflow, I get quick support from the Appian team.

Whenever there is a production deployment, it involves the Appian development team. However, if other systems are also involved, representatives from the integration teams of different systems are needed as well.

There are two buckets. On the pricier side, both Appian and Pega are enterprise-level solutions, placing them on the slightly higher side.

However, the robustness of the products, their features, and their availability justify the pricing.

I have considered Appian, Pega, Uncorp, and Mendix  as alternate solutions.

Overall, everything is eight out of ten.

I am a little bit biased towards Pega. Pega has a lot more standardized processes, which take less time to go to market compared to Appian. Appian provides a platform.