Requesters and Finance teams... Now is your time to make sure that you never upload the same expense twice! 😇

Expense claims duplicates

Expense claims duplicate flagging can happen this way:

  • If the Requester submits the same expense claims twice.
  • If the Requester submits an expense claim similar to a payment he's already made with his Spendesk physical card.
  • If the Requester submits a receipt that has already been uploaded by him.

The different checks our tool makes are on:

  • the receipt
  • date+amount+supplier
  • date+amount (if the supplier has not been filled or detected)

🔥 If the Requester submits the expense even though it's a duplicate, the Controller is warned on the request.

🔥 If the Requester submits the expense another user has already submitted, the link to the previous (equivalent) request is displayed.

Invoice duplicates

As a Requester, I want to avoid submitting the same invoice several times. As a Controller, I want to make sure I don't pay the same supplier twice!

This is why we flag invoice duplicates.

Requesters

When Requesters submit an invoice that has already been submitted (i.e the same file or same supplier + invoice number), then they immediately get a warning at the bottom of the request panel, and can either delete the invoice or submit it anyway.

Controllers

As a Controller, if the user reviews an invoice that has already been reviewed, they get a warning so as to reject it and to avoid paying it twice.

What do we check?

The document added by the users and the information it contains.

Did this answer your question?