It is for invoice data extraction. I am using the latest version. We have it on-premises, but my understanding is that they have cloud-based and on-premises solutions.
Head of RPA COE at a transportation company with 10,001+ employees
Real User
2021-02-18T20:36:00Z
Feb 18, 2021
Our initial use cases are mainly for finance. We are doing account payable, accounts receivable, reconciliation, and those types of things with the automation. In terms of accounts payable, we automate the invoice processing since it is an end-to-end. This means that the vendor will send an invoice to email, which will be picked up by the bot automatically. Then, it will extract the information from the invoices and post it to our SAP. It is a web-based solution but hosted on our server.
IT Manager at a tech services company with 51-200 employees
Real User
2021-01-28T07:35:00Z
Jan 28, 2021
We have two different use cases: * Bank conflation. * Wage Protection System (WPS), which is a new way to do salaries per person. We are trying to migrate to the latest version. We are planning to migrate onto their SaaS model.
Managing Director, Business Transformation at a transportation company with 10,001+ employees
Real User
2021-01-26T21:21:00Z
Jan 26, 2021
We have a number of use cases. We've intentionally started with a focus in our finance controller organization as well as our supply chain organization. The bulk of our bots that have been deployed are in those two areas, doing a number of different business processes across those areas.
Digital Project Manager at a aerospace/defense firm with 501-1,000 employees
Real User
2021-01-26T10:26:00Z
Jan 26, 2021
We mostly use Jiffy.ai in finance, for accounts payable, accounts receivable, for scanning invoices, and fetching invoices from the suppliers' websites. The new division I'm in, which is a non-finance division, requires some automation as well. We are an engineering division, and the RPA team is starting to look into the non-finance processes. In our division, the processes are along the lines of document scanning and organization of those documents. We need to scan documents and identify the document types and put them in the right folder. It's a very manual, labor-intensive job that we are doing now. But so far, it is mostly used in finance processes.
National Professional Officer at a international affairs institute with 5,001-10,000 employees
Real User
Top 10
2021-01-14T14:26:00Z
Jan 14, 2021
We are primarily using it for processing documents, particularly for procurement and payroll. We have a case for HR to deliver a document for attestations for people who are leaving the organization. They are provided with an attestation letter. We are primarily using it for payroll and procurement, so far. We have our own virtual servers where we host on our own servers, but they are virtual and not physical. The machines running the bots are virtual machines as well.
We are using it in production for driving our Windows application, extracting content from it, and using it for our desktop automation. In our test environment, we are using the OCR features of the Jiffy.ai application. Essentially, we submit the images into the application, then we use the training model for the data. The actual images are being extracted and returned back to us as a document. We automated a fairly complicated process, but it was revolving around a single application. We are not doing content switching among multiple applications. It was mainly driving a single application and extracting information out of it. We are using version 3 in production, and we are using version 4 in our test environment.
Founded with the mission to radically change how enterprises automate complex business processes, JIFFY.ai puts the power of real-time innovation in business users’ hands. JIFFY.ai delivers an app-based, cognitive automation platform that includes capabilities ranging from intelligent document processing, natural language processing capabilities, RPA and Low Code/No Code development.
We use the solution to upload and download the documents.
It is for invoice data extraction. I am using the latest version. We have it on-premises, but my understanding is that they have cloud-based and on-premises solutions.
Our initial use cases are mainly for finance. We are doing account payable, accounts receivable, reconciliation, and those types of things with the automation. In terms of accounts payable, we automate the invoice processing since it is an end-to-end. This means that the vendor will send an invoice to email, which will be picked up by the bot automatically. Then, it will extract the information from the invoices and post it to our SAP. It is a web-based solution but hosted on our server.
We have two different use cases: * Bank conflation. * Wage Protection System (WPS), which is a new way to do salaries per person. We are trying to migrate to the latest version. We are planning to migrate onto their SaaS model.
We have a number of use cases. We've intentionally started with a focus in our finance controller organization as well as our supply chain organization. The bulk of our bots that have been deployed are in those two areas, doing a number of different business processes across those areas.
We mostly use Jiffy.ai in finance, for accounts payable, accounts receivable, for scanning invoices, and fetching invoices from the suppliers' websites. The new division I'm in, which is a non-finance division, requires some automation as well. We are an engineering division, and the RPA team is starting to look into the non-finance processes. In our division, the processes are along the lines of document scanning and organization of those documents. We need to scan documents and identify the document types and put them in the right folder. It's a very manual, labor-intensive job that we are doing now. But so far, it is mostly used in finance processes.
We are primarily using it for processing documents, particularly for procurement and payroll. We have a case for HR to deliver a document for attestations for people who are leaving the organization. They are provided with an attestation letter. We are primarily using it for payroll and procurement, so far. We have our own virtual servers where we host on our own servers, but they are virtual and not physical. The machines running the bots are virtual machines as well.
We are using it in production for driving our Windows application, extracting content from it, and using it for our desktop automation. In our test environment, we are using the OCR features of the Jiffy.ai application. Essentially, we submit the images into the application, then we use the training model for the data. The actual images are being extracted and returned back to us as a document. We automated a fairly complicated process, but it was revolving around a single application. We are not doing content switching among multiple applications. It was mainly driving a single application and extracting information out of it. We are using version 3 in production, and we are using version 4 in our test environment.