Transactions

The Transactions section reflects the transactional data from your financial integrations or uploaded CSV files with Zluri. We currently support integrations with Intuit Quickbooks, Zoho Books, Zoho Expense, Expensify, Netsuite and many more. Zluri will build more integrations in future and add to this list.

From the Zluri Home page, if we go to Sources - - > Integrations - - > Browse Catalog, we can get all the financial integrations currently supported if we search “finance” under Categories. Please refer to the below snapshots:



 This is how the Transactions section currently looks:

    
There are five sections within Transactions:

  1. Recognised Transactions: These are the transactions which Zluri has recognised from the financial integrations and has mapped to an application and are SaaS related. For mapping the transaction, we use the Transaction Description. If the Transaction Description matches the application name, Zluri maps the transaction to that application.

  2. Unrecognised Transactions: These are the transactions unrelated to SaaS, or Zluri has not been able to recognise from the financial integrations and has not mapped to any application.

  3. Archived Transactions: These are the transactions which are non-SaaS related. Also, any other transaction that customers don’t want to be included can be archived. Customers can move these types of transactions to Archive so that their data is not visible on the dashboard.

  4. Payment Methods: Customers can add payment methods like Credit cards, Bank Accounts and other Payment Options on this page. Zluri sends notifications to customers if any payment method is nearing its expiry date. 

  5. Uploads: The customer can upload the transaction data as a CSV file which needs to have data in a specific format to upload the data.

Recognised Transactions


In Recognised transactions, the customer will be able to see the Application name, transaction description, transaction date, Amount of transaction, the currency of transaction, and payment method used.

The transactions table would now also have the following new columns: 
Vendor, Amortisation Start Date, Amortisation End Date, Cost Centres, and PO Number (Purchase Order Number)


More columns can be added from the select column option near filters. The customer has the option to export the transactions in CSV format.

The customer can filter out the transactions in the Recognised section by clicking on the “+ Add Filters” button highlighted below:

Once the customer clicks on Add Filters, a Filter panel screen comes on the right-hand side of the platform, which includes a list of filters that can be applied. For example, customers can filter based on transaction date, transaction id, transaction amount, etc.

If the customer selects transaction amount, they need to click the “+” button on Transaction Date and select the required filter—for example,  Greater than, Smaller than, Range, and Equal to.


After selecting the required option, the customer can click the “Apply” button to view the filtered transactions.
Customers can add a new transaction manually by clicking on the “+ Add” button. 
Please refer to the below screenshot:

Here, the customer needs to add the application name, choose the relevant currency from the dropdown, enter the amount, and select the date and the Payment Method used. After entering all the details, the transaction can be saved by clicking on the “Add Transaction”  button.


Also, if the customer selects multiple applications by clicking on the checkboxes near the application name, they can see two additional options on top near the search box: Change Payment Method and Bulk Edit. Please refer to the below snapshot:




Change Payment Method:


Once the customer clicks on “Change Payment Method”, a dropdown will be displayed with the following options:



Here, the customer can assign any payment method to the selected transactions in the Zluri system.


Bulk Edit:


If the customer clicks on Bulk Edit, the following options will appear:



Here, the customer can unassign the selected apps or move them into the Archive section.


If the customer clicks on “Unassign Apps”, the below screen will appear:



Here, Zluri will provide a few suggestions: 


  1. Zluri will automatically detect similar transactions w.r.t. what the customer has currently selected.

  2. Zluri will provide an option to include all similar transactions for the bulk edit option or proceed with the manually selected transactions. The customer can click the “Include All” or “Select Manually” radio button to choose the preferred option.

  3. Zluri will also provide an “Automatically unassign all future transactions from this app” option. The customer can click this checkbox to select this option for future transactions.


Once the selections are made, the customer can click the “Unassign App” button to implement the Bulk Edit operation.


Similar options will appear for the customer if he selects “Archive” under the Bulk Edit option.

If the customer selects a transaction and clicks on the three dots in the top right corner, he can re-calculate the “spends” from the date he wants to consider. Once recalculated, the refreshed spends will be updated across the Zluri platform.


The customer can directly change the payment method of a transaction by hovering on the Payment Method field. If the customer clicks on the edit pen symbol, a dropdown will show up containing a list of all available payment methods. 



From this list, the customer can select a new payment method for this transaction.


Unrecognised Transactions


Unrecognised transactions have similar columns as present in the Recognised tab except for the Application name. Here, the customer can assign a transaction to an application.

Again, the customer can select multiple transactions at once. Once selected, the “Change Payment Method” and “Bulk Edit” buttons will appear on the top. The only difference in the Bulk Edit option is that the customer can assign the apps by clicking on the “Assign App” option instead of “Unassign Apps”. The rest of the operations remain the same. Please refer to the screenshot:




We can use the “Assign to App” option in the Assign_app column to directly assign an application to a single transaction. Please refer to the snapshot:



Once the customer clicks on the “Assign to App” button, the below screen will appear:




Here, the customer can select the application name they want to assign to this transaction. 


Also, they can select the checkbox “Automatically assign all the future transactions to this app” to automate the assignment process for future transactions. The automatic assignment of transactions is done basis of the Transactions Description. Zluri will remember the transaction description for application mapping and will replicate it in the future.



Archived Transactions


Archived transactions are those transactions which are not software related or any transaction that customers don't want to be included in the transaction can be archived


Hence, the customer can mark some transactions in the Archive category.


If we select one or multiple transactions, we can Bulk Edit all to UnArchive category. Once done, all the transactions will move to the Unrecgnised tab.



The rest of the functionalities remain the same on this tab.


Payment Methods

The customer can add payment methods like Credit cards, Bank Accounts or any other Payment Options.



If they click on the “+ Add” button in the top right corner, they can add a new Payment option. Please refer to the below screenshot:



If the customer selects the “Credit Card” option, they have to enter the below details and click on “Add Card” to save.



If they select the “Bank Account” option, they can enter the below details to save:



Finally, if they select the “Other” payment option, the below screen will appear, and they have to enter the details to save the payment option:



If you click on 3 dots on a credit card payment method, you will get two options: 
Edit Card and Delete Card.



If the customer selects the “Edit card” option, they will be able to edit the card details and, in the end, can click on the “Edit Card” button in the below screen to save the edited data:



If the customer clicks the “Delete Card" option, he can delete this payment method. Once done, a pop window will appear for confirmation like the below:


Once deleted, the platform will be refreshed, and the selected card will be deleted.


Uploads


There are five columns in the Uploads section: 
File Name, Date of Upload, Entries(number of entries), Recognised, and Unrecognised.


The customer can upload the transactions on this tab manually if required. They can upload a CSV file with the relevant details. 


Customers can use the filter option in the Uploads section to filter out the transactions they want to view on the platform. Please refer to the following snapshot:


 

Two filter options are the Date of Upload and the Number of entries in a CSV file.


For Uploading a new file, the customer needs to click on the “+ Add” button in the top right corner shown below:




Once the customer clicks on Add, the below screen will appear on the right-hand side of the screen:



From here, the customer can download the sample CSV file, enter the details and upload the updated CSV back. Sample CSV:



In the case of Vendor and Cost Centres, if the names in the CSV match with existing Vendor Names and Cost Centre names, then Zluri maps the transaction to the specific Vendor or Cost Centre. If not, then new Vendors/Cost Centres are created with the same name as entered in the CSV.


The data can also be sourced from financial integrations provided:
1. The fields are available in the API response of the expense management system 

2. The client maintains the data the in their expense management system

If the customer selects a CSV file in the File Name column, the “Deactivate” button will appear in the top right corner. Please refer to the below snapshot:


If they click on Deactivate button, the selected CSV file will be deactivated. Please refer to the snapshot:


After deactivating a file, the below screen will appear:


Similarly, the customer can activate a deactivated file by mistake. Please refer to the below screenshot:


Once, the customer clicks on the “Activate” button, the file will be activated:


If the customer clicks on any file name in the Uploads section, it will open up new tabs inside the Uploads section with details of Recognised, Unrecognised and Archived transactions within that file.

For example, in the below screenshot, the first file has 3 transactions: 2 recognised and 1 unrecognised.


Uploads - Recognised


The number of transactions in the recognised tab is 2, as per the above example.

As shown earlier, the customer can change the payment method and do the bulk edit by selecting one or more transactions:



Also, the customer can change the payment method of any transaction by clicking on the down arrow button under Payment Method - Add Payment Method.




Uploads - Unrecognised

The number of transactions in the unrecognised tab is 1, as per the above example.



The customer can move the unrecognised transaction to the recognised category by clicking the “Assign to App” button.


Uploads - Archived

As per the above example, out of three transactions, none was archived. Hence, the below section will have 0 transactions.



Filter Option - Details

The Transactions Module presents the entire transaction data for the users, which can be filtered by using the following filters:


  1. Transaction ID: This is an ID which is stored in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validation or troubleshooting.   

  2. Applications:  here, the users can choose applications they want to see the transactions. The user can enter the name of the application under the ‘Text Contains’ section.

  3. Transaction Description: the transactions have certain data under the Transactions Description column, and if the users wish to filter transactions on this, then this filter can be enabled.

  4. Transaction Date: transactions for 1.) Specific Date 2.)Before a specific date 3.)After a specific date, and 4.)A date range can be viewed by using this filter

  5. Transaction Amount:  if transactions are to be filtered based on the amount
    a.)Transaction Amount greater than
    b.Transaction Amount lesser than
    c.) Transaction Amount is in a specific range

                d.)Transaction Amount is equal to a specific amount

  1. Currency: transactions in the default currency of the organisations

  2. Original Transaction Amount: transaction amount after conversion to the default currency of the organisation

  3. Original Currency: currency in which the transaction was actually carried out

  4. Source: Source here refers to the source of the transactions - this could either be from an expense management system from an uploaded CSV, manually uploaded transaction etc.

  5. Source Id:  this is an ID for which we store in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validations or troubleshooting.   

  6. Payment Method Id: this is an ID for which we store in the backend

  7. Payment Method: the payment method assigned to the transaction 

  8. Last Digits:  the last four digits of the payment method can be used to filter the transactions using this filter.

  9. Transaction Type: can be filtered using Text contains and Text does not contain options.

  10. Vendor Name: name of the vendor

  11. Vendor ID: this is an ID for each vendor which is stored in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validation or trouble shooting.   

  12. Amortization Start Date: The date from which amortisation needs to be enabled.

  13. Amortization End Date: The date till which amortisation needs to be enabled.

  14. Cost Center: cost centre of each business unit/department.

  15. PO Number: purchase order number for each order.




Can’t find what you are looking for? Let us help you!

Transactions

Modified on Mon, 26 Jun 2023 at 02:52 PM

The Transactions section reflects the transactional data from your financial integrations or uploaded CSV files with Zluri. We currently support integrations with Intuit Quickbooks, Zoho Books, Zoho Expense, Expensify, Netsuite and many more. Zluri will build more integrations in future and add to this list.

From the Zluri Home page, if we go to Sources - - > Integrations - - > Browse Catalog, we can get all the financial integrations currently supported if we search “finance” under Categories. Please refer to the below snapshots:



 This is how the Transactions section currently looks:

    
There are five sections within Transactions:

  1. Recognised Transactions: These are the transactions which Zluri has recognised from the financial integrations and has mapped to an application and are SaaS related. For mapping the transaction, we use the Transaction Description. If the Transaction Description matches the application name, Zluri maps the transaction to that application.

  2. Unrecognised Transactions: These are the transactions unrelated to SaaS, or Zluri has not been able to recognise from the financial integrations and has not mapped to any application.

  3. Archived Transactions: These are the transactions which are non-SaaS related. Also, any other transaction that customers don’t want to be included can be archived. Customers can move these types of transactions to Archive so that their data is not visible on the dashboard.

  4. Payment Methods: Customers can add payment methods like Credit cards, Bank Accounts and other Payment Options on this page. Zluri sends notifications to customers if any payment method is nearing its expiry date. 

  5. Uploads: The customer can upload the transaction data as a CSV file which needs to have data in a specific format to upload the data.

Recognised Transactions


In Recognised transactions, the customer will be able to see the Application name, transaction description, transaction date, Amount of transaction, the currency of transaction, and payment method used.

The transactions table would now also have the following new columns: 
Vendor, Amortisation Start Date, Amortisation End Date, Cost Centres, and PO Number (Purchase Order Number)


More columns can be added from the select column option near filters. The customer has the option to export the transactions in CSV format.

The customer can filter out the transactions in the Recognised section by clicking on the “+ Add Filters” button highlighted below:

Once the customer clicks on Add Filters, a Filter panel screen comes on the right-hand side of the platform, which includes a list of filters that can be applied. For example, customers can filter based on transaction date, transaction id, transaction amount, etc.

If the customer selects transaction amount, they need to click the “+” button on Transaction Date and select the required filter—for example,  Greater than, Smaller than, Range, and Equal to.


After selecting the required option, the customer can click the “Apply” button to view the filtered transactions.
Customers can add a new transaction manually by clicking on the “+ Add” button. 
Please refer to the below screenshot:

Here, the customer needs to add the application name, choose the relevant currency from the dropdown, enter the amount, and select the date and the Payment Method used. After entering all the details, the transaction can be saved by clicking on the “Add Transaction”  button.


Also, if the customer selects multiple applications by clicking on the checkboxes near the application name, they can see two additional options on top near the search box: Change Payment Method and Bulk Edit. Please refer to the below snapshot:




Change Payment Method:


Once the customer clicks on “Change Payment Method”, a dropdown will be displayed with the following options:



Here, the customer can assign any payment method to the selected transactions in the Zluri system.


Bulk Edit:


If the customer clicks on Bulk Edit, the following options will appear:



Here, the customer can unassign the selected apps or move them into the Archive section.


If the customer clicks on “Unassign Apps”, the below screen will appear:



Here, Zluri will provide a few suggestions: 


  1. Zluri will automatically detect similar transactions w.r.t. what the customer has currently selected.

  2. Zluri will provide an option to include all similar transactions for the bulk edit option or proceed with the manually selected transactions. The customer can click the “Include All” or “Select Manually” radio button to choose the preferred option.

  3. Zluri will also provide an “Automatically unassign all future transactions from this app” option. The customer can click this checkbox to select this option for future transactions.


Once the selections are made, the customer can click the “Unassign App” button to implement the Bulk Edit operation.


Similar options will appear for the customer if he selects “Archive” under the Bulk Edit option.

If the customer selects a transaction and clicks on the three dots in the top right corner, he can re-calculate the “spends” from the date he wants to consider. Once recalculated, the refreshed spends will be updated across the Zluri platform.


The customer can directly change the payment method of a transaction by hovering on the Payment Method field. If the customer clicks on the edit pen symbol, a dropdown will show up containing a list of all available payment methods. 



From this list, the customer can select a new payment method for this transaction.


Unrecognised Transactions


Unrecognised transactions have similar columns as present in the Recognised tab except for the Application name. Here, the customer can assign a transaction to an application.

Again, the customer can select multiple transactions at once. Once selected, the “Change Payment Method” and “Bulk Edit” buttons will appear on the top. The only difference in the Bulk Edit option is that the customer can assign the apps by clicking on the “Assign App” option instead of “Unassign Apps”. The rest of the operations remain the same. Please refer to the screenshot:




We can use the “Assign to App” option in the Assign_app column to directly assign an application to a single transaction. Please refer to the snapshot:



Once the customer clicks on the “Assign to App” button, the below screen will appear:




Here, the customer can select the application name they want to assign to this transaction. 


Also, they can select the checkbox “Automatically assign all the future transactions to this app” to automate the assignment process for future transactions. The automatic assignment of transactions is done basis of the Transactions Description. Zluri will remember the transaction description for application mapping and will replicate it in the future.



Archived Transactions


Archived transactions are those transactions which are not software related or any transaction that customers don't want to be included in the transaction can be archived


Hence, the customer can mark some transactions in the Archive category.


If we select one or multiple transactions, we can Bulk Edit all to UnArchive category. Once done, all the transactions will move to the Unrecgnised tab.



The rest of the functionalities remain the same on this tab.


Payment Methods

The customer can add payment methods like Credit cards, Bank Accounts or any other Payment Options.



If they click on the “+ Add” button in the top right corner, they can add a new Payment option. Please refer to the below screenshot:



If the customer selects the “Credit Card” option, they have to enter the below details and click on “Add Card” to save.



If they select the “Bank Account” option, they can enter the below details to save:



Finally, if they select the “Other” payment option, the below screen will appear, and they have to enter the details to save the payment option:



If you click on 3 dots on a credit card payment method, you will get two options: 
Edit Card and Delete Card.



If the customer selects the “Edit card” option, they will be able to edit the card details and, in the end, can click on the “Edit Card” button in the below screen to save the edited data:



If the customer clicks the “Delete Card" option, he can delete this payment method. Once done, a pop window will appear for confirmation like the below:


Once deleted, the platform will be refreshed, and the selected card will be deleted.


Uploads


There are five columns in the Uploads section: 
File Name, Date of Upload, Entries(number of entries), Recognised, and Unrecognised.


The customer can upload the transactions on this tab manually if required. They can upload a CSV file with the relevant details. 


Customers can use the filter option in the Uploads section to filter out the transactions they want to view on the platform. Please refer to the following snapshot:


 

Two filter options are the Date of Upload and the Number of entries in a CSV file.


For Uploading a new file, the customer needs to click on the “+ Add” button in the top right corner shown below:




Once the customer clicks on Add, the below screen will appear on the right-hand side of the screen:



From here, the customer can download the sample CSV file, enter the details and upload the updated CSV back. Sample CSV:



In the case of Vendor and Cost Centres, if the names in the CSV match with existing Vendor Names and Cost Centre names, then Zluri maps the transaction to the specific Vendor or Cost Centre. If not, then new Vendors/Cost Centres are created with the same name as entered in the CSV.


The data can also be sourced from financial integrations provided:
1. The fields are available in the API response of the expense management system 

2. The client maintains the data the in their expense management system

If the customer selects a CSV file in the File Name column, the “Deactivate” button will appear in the top right corner. Please refer to the below snapshot:


If they click on Deactivate button, the selected CSV file will be deactivated. Please refer to the snapshot:


After deactivating a file, the below screen will appear:


Similarly, the customer can activate a deactivated file by mistake. Please refer to the below screenshot:


Once, the customer clicks on the “Activate” button, the file will be activated:


If the customer clicks on any file name in the Uploads section, it will open up new tabs inside the Uploads section with details of Recognised, Unrecognised and Archived transactions within that file.

For example, in the below screenshot, the first file has 3 transactions: 2 recognised and 1 unrecognised.


Uploads - Recognised


The number of transactions in the recognised tab is 2, as per the above example.

As shown earlier, the customer can change the payment method and do the bulk edit by selecting one or more transactions:



Also, the customer can change the payment method of any transaction by clicking on the down arrow button under Payment Method - Add Payment Method.




Uploads - Unrecognised

The number of transactions in the unrecognised tab is 1, as per the above example.



The customer can move the unrecognised transaction to the recognised category by clicking the “Assign to App” button.


Uploads - Archived

As per the above example, out of three transactions, none was archived. Hence, the below section will have 0 transactions.



Filter Option - Details

The Transactions Module presents the entire transaction data for the users, which can be filtered by using the following filters:


  1. Transaction ID: This is an ID which is stored in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validation or troubleshooting.   

  2. Applications:  here, the users can choose applications they want to see the transactions. The user can enter the name of the application under the ‘Text Contains’ section.

  3. Transaction Description: the transactions have certain data under the Transactions Description column, and if the users wish to filter transactions on this, then this filter can be enabled.

  4. Transaction Date: transactions for 1.) Specific Date 2.)Before a specific date 3.)After a specific date, and 4.)A date range can be viewed by using this filter

  5. Transaction Amount:  if transactions are to be filtered based on the amount
    a.)Transaction Amount greater than
    b.Transaction Amount lesser than
    c.) Transaction Amount is in a specific range

                d.)Transaction Amount is equal to a specific amount

  1. Currency: transactions in the default currency of the organisations

  2. Original Transaction Amount: transaction amount after conversion to the default currency of the organisation

  3. Original Currency: currency in which the transaction was actually carried out

  4. Source: Source here refers to the source of the transactions - this could either be from an expense management system from an uploaded CSV, manually uploaded transaction etc.

  5. Source Id:  this is an ID for which we store in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validations or troubleshooting.   

  6. Payment Method Id: this is an ID for which we store in the backend

  7. Payment Method: the payment method assigned to the transaction 

  8. Last Digits:  the last four digits of the payment method can be used to filter the transactions using this filter.

  9. Transaction Type: can be filtered using Text contains and Text does not contain options.

  10. Vendor Name: name of the vendor

  11. Vendor ID: this is an ID for each vendor which is stored in the backend. The users do not have access to these IDs. This is something the Zluri backend team would use for any sort of validation or trouble shooting.   

  12. Amortization Start Date: The date from which amortisation needs to be enabled.

  13. Amortization End Date: The date till which amortisation needs to be enabled.

  14. Cost Center: cost centre of each business unit/department.

  15. PO Number: purchase order number for each order.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article