Supplier invoice completeness

Settings → Advanced → Supplier invoice completeness sets what an incoming (supplier) invoice must carry to count as complete, and how far its payments may differ from it. This is not the same as Contract completeness checks, which concern contracts.

Who can change it

An administrator or a user with the invoices manager role can open this screen. The server accepts changes from administrators only.

The controls on this screen

The screen has one card, Incoming invoices — completeness, with this description: extra conditions counted in the invoice completeness ring. Turning these on lowers current scores until invoices are filled in accordingly. Each switch saves as soon as you flip it, with a Success message, and is off by default.

Require a tag: when on, a missing tag becomes one more check on an incoming invoice, which lowers its completion when it has none.

Require a project assignment: when on, a missing project becomes one more check on an incoming invoice, which lowers its completion when it has none.

Payment difference tolerance: how far, in percent, the payments linked to an invoice may differ from it (for example by the bank's exchange rate) before the difference needs accepting. Enter a percentage from 0 to 20; a value outside that range shows an error and is not saved. The field saves when you leave it. Leave it blank to use the default of 3 percent; a blank field shows Not set. The field appears only when the server supports it.

Example use cases

• An administrator turns on Require a tag so every supplier invoice must be coded before it counts as complete.
• An administrator turns on Require a project assignment to see which supplier invoices are still unassigned.
• An administrator whose suppliers bill in euro but are paid in zloty raises Payment difference tolerance to 5 so small exchange-rate gaps stop raising a warning.