Skip to main content
All CollectionsInvoice Web V2Functions
How to sort your invoice on the Web App
How to sort your invoice on the Web App

Learn how to sort an invoice on the web app

Michelle avatar
Written by Michelle
Updated over 3 months ago

How to sort your invoice on the Web App

Learn how to sort your invoice on the web with these simple steps:

Please note that the documents will be displayed in the order they were created. With the sort feature, You can arrange them based on the following criteria:

  1. Invoice Status

  2. Invoice Number

  3. Customer's name in alphabetical order

  4. Amount

  5. Due date

  6. Issued date

To use the sort feature, just click on the arrow icon next to the desired sorting option.


Sorting by Invoice Status:

Your invoices will be displayed in the order they were created or issued by default.

Once you click on the arrow button next to Status, the invoices will be sorted according to these statuses:

  • Read

  • Failed to deliver

  • Draft

  • Paid

  • Partially paid


Sorting by Invoice Number:

To sort by Invoice number, click on the arrow button next to Invoice.

Please note that when sorting by invoice number the template must be uniform for proper sorting.


Sorting by Customer:

When sorting by customer, your customers will be organized in alphabetical order. The initial click will sort them in descending order (Z-A).


Sorting by Due Date:

When sorting by due date, your invoice will be sequenced from the previous to the latest date or vice versa.


Sorting by Issued Date:

When sorting by issued date, your invoice will be sequenced from the previous to the latest date or vice versa.


Continue to click the arrow button until you have sorted them according to your preference.


Discover more tutorials for Bookipi Invoice Web App

Discover more tips on how to get the most out of Bookipi Invoice web app with our Bookipi Invoice guides.

Want to send invoices easily? Download the Bookipi Invoice mobile app and check out our Bookipi Invoice mobile app guides.

Did this answer your question?