Duplicate-payment prevention policy
Before submitting or releasing a payment, search for the invoice number, vendor, amount, date, order, and payment reference. Confirm that a similar transaction is not already pending, approved, processing, or completed. Correct the original record when appropriate. If a duplicate is suspected after release, stop further processing where possible and escalate immediately with both record references.
Related Articles
How to process an expense payment
Expense Payments is the finance workspace for paying approved employee and internal spend requests that were not paid automatically by policy. What appears in Expense Payments An approved Cash Request, Payment Request, or Reimbursement Request moves ...
How to make a vendor advance payment
Use Create Advance Payment when the organisation needs to pay a vendor before there is a supplier bill to select. This is different from a bill payment and must later be applied or reconciled according to your accounting process. Who can do this ...
How to make a bill payment
Use Accounting > Bill Payments to pay an existing supplier bill that has already been uploaded or created in Spendive. Use Create Advance Payment instead when paying a vendor before there is a bill to settle. Who can do this Finance administrators ...
Business expense policy
Business expenses must be necessary, reasonable, properly authorized, and supported by evidence. Personal, duplicate, fictitious, or inadequately explained expenses are prohibited. Users must select accurate categories, dates, amounts, currencies, ...
Business expense policy
Business expenses must be necessary, reasonable, authorized, and supported. Personal, duplicate, fictitious, or inadequately explained expenses are prohibited. Users must enter accurate dates, amounts, currencies, categories, projects, and budgets. ...