Ap en

Essentials:
Accounts Payable
Contents
Page Analytic Name
4 Duplicate payments
AP Analytic 01
6 Duplicate invoices
AP Analytic 02
8 Duplicate invoices using vendor’s numeric invoice values

AP Analytic 03
10 Duplicate invoices sub analytics

AP Analytic 04
12 Future dated invoices

AP Analytic 05
14 Recurring sundry expense review

AP Analytic 06
16 Invoices for one-time vendors

AP Analytic 07
18 Vendor payments made over a weekend

AP Analytic 08
20 Invoices captured over a weekend

AP Analytic 09
22 Invoices greater than a threshold

AP Analytic 10
24 Purchase order date after the invoice date

AP Analytic 11
26 Vendor paid by both purchase order and sundry expense

AP Analytic 12
28 Invoices greater than approved purchase orders

AP Analytic 13
30 Manually released invoices (no 3-way match)

AP Analytic 14
Version 6.2.0 – 2019/04

Contents
Page Analytic Name
32 Three way match re-performance

AP Analytic 15
34 Outlier invoices
AP Analytic 16
36 Early payment of invoices

AP Analytic 17
Version 6.2.0 – 2019/04

ACCOUNTS PAYABLE
Duplicate Payments
AP_ANALYTIC_01_APCS102
Identifies all potential duplicate payments to the same vendor for the same amount made
within a configurable time period
Essentials – Accounts Payable Page 4

Duplicate Payments
Risk
A vendor is paid twice or more, often through administrative errors or fictitious vendor invoices being
submitted for payment with details similar to an original valid invoice. This may result in overpayment to
Context vendors or irrecoverable financial losses.
High volumes of payments
from all areas of the business Procedure
are processed through the Identifies potential duplicate payments made to the same vendor for the same amount within a
Finance function every day or configurable time period (e.g. 14 days, 30 days).
payment cycle. It is vital to
closely and continuously Analytic Logic
monitor these payments to Extracts payments within a user-determined period of days and identifies potential duplicate payments to
detect potential fraud or the same vendor (using system vendor ID) with the same value (using document/original currency), while
errors. excluding reversed transactions.
Variables
Period (number of days) for payment analysis.
Example
VENDOR_ID VENDOR_NAME_1 ACCOUNTING_DOC_NUMBER DOCUMENT_DATE AMT_DOC_CURRE
NCY
Exception
100000523 ABC Inc 1500080094 1/11/2017 1000
100000523 ABC Inc 1500080841 15/11/2017 1000
100000479 XYZ Ltd 1500081862 2/11/2017 5000
Fields used for analytics logic
Output Results Fields

Company Code Company Name Vendor ID Vendor Name 1 Vendor Name 2 Pay User Name
Accounting Document Number Clearing Document Number Line Item Account Document Number Pay User ID
Item Description Debit / Credit Indicator Amount in Reporting Currency Report Currency Clearing Date
Amount in Document Currency Document Currency Document Type Document Date Day Document Entered
Output Visualization Example
Duplicate payments grouped by user
Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_01_APCS102 Page 5

ACCOUNTS PAYABLE
Duplicate Invoices
Identifies potential duplicate invoices after stripping out any special characters in the
invoice numbers

Duplicate Invoices
Risk
The same vendor invoice is presented twice for payment or fictitious/invalid vendor invoices are paid.
Context This may result in either overpayment or incorrect payment to vendors and often irrecoverable financial
Often the same invoice is losses from fraudulent and/or invalid invoices being paid.
captured multiple times
despite preventive system Procedure
validation and controls being Identifies duplicate paid invoices for the same amount after stripping out any special characters in the
in place. Administrative invoice numbers.
errors or application control
circumvention results in
additional and/or changed
Analytic Logic
characters to the invoice Extracts all paid invoices and removes/strips out special characters (e.g. ~!@#$%) from the invoice
number, causing duplicate number field (which is normally a free text field in the ERP system). Thereafter the script performs a
invoice capturing that would duplicates test using the stripped invoice number and invoice value fields.
otherwise be undetectable.
Example
VENDOR_NAME VENDOR_INV_NO STRIPPED_VENDOR_INV_NO DOCUMENT_DATE AMOUNT_DOC_CURRENCY
Vendor A IN001 IN001 1/11/2017 1000.00
Vendor A IN001$ IN001 15/11/2017 1000.00
Output Results Field Names

Company Code Company Name Vendor ID Vendor Name Vendor Invoice Number Release User Name
Vendor Stripped Invoice Number Document Currency Amount in Document Currency Document Date
Report Currency Amount in Reporting Currency Accounting Document Number Debit/Credit Indicator
Release User
Showing value over time

ACCOUNTS PAYABLE
Duplicate Invoices Using

Vendor’s Numeric Invoice
Values
Identifies potential duplicate invoices after converting invoice numbers to numeric values

Duplicate Invoices Using Vendor’s Numeric Invoice Values
Risk
Context The same vendor invoice is presented twice for payment or fictitious/invalid vendor invoices are paid.
Often the same invoice is This may result in either overpayment or incorrect payment to vendors and often irrecoverable financial
captured multiple times despite losses from fraudulent and/or invalid invoices being paid.
preventive system validation and
controls being in place.
Administrative errors or Procedure
application control circumvention Identifies duplicate paid invoices for the same amount after converting the invoice numbers to numeric
results in additional and/or values.
changed characters to the invoice
number, causing duplicate Analytic Logic
invoice capturing that would Extracts all paid invoices and converts the invoice number from the invoice number field (which is
otherwise be undetectable. normally a free text field in the ERP system) to a numeric value (e.g. “INV101a” to “101”). Thereafter the
script performs a duplicates test using the numeric invoice number and invoice value fields.
Example
VENDOR_NAME VENDOR_INV_NO STRIPPED_VENDOR_INV_NO DOCUMENT_DATE AMOUNT_DOC_CURRENCY
Vendor A IN001 001 1/02/2017 4000.00
Vendor A INv001 001 15/02/2017 4000.00

Company Code Company Name Vendor ID Vendor Name 1 Debit/Credit Indicator
Vendor Invoice Number Vendor Stripped Invoice Number Document Currency Amount in Document Currency
Report Currency Amount in Reporting Currency Accounting Document Number Document Date
Release User Release User Name
Showing value over time

ACCOUNTS PAYABLE
Duplicate Invoices Sub

Analytics
AP_ANALYTIC_04_APCS613.1 TO AP_ANALYTIC_04_APCS613.10
Identifies potential duplicate invoices using various sub analytics

Duplicate Invoices Sub Analytics
Risk
The same vendor invoice is presented twice for payment or fictitious/invalid vendor invoices are paid.
Context
Often the same invoice is Procedure
captured multiple times despite Identifies duplicate paid invoices by analysing for duplicates based on the ten variations in the table
preventive system validation and below.
controls being in place.
Administrative errors or Analytic Logic
application control circumvention Extracts all paid invoices and performs a duplicates test based on the ten variations in the table below,
results in additional and/or for example identifying duplicate invoices where the vendor number and invoice number are the same.
changed characters to the
invoice number, causing
duplicate invoice capturing that
would otherwise be undetectable.

Company Code Company Name Vendor ID Vendor Name 1 Debit/Credit Indicator
Accounting Document Number Vendor Invoice Number Document Date Amount in Document Currency
Document Currency Vendor Address Vendor Postal Code Vendor City Vendor Region
Vendor Bank Account Number Vendor Bank Account Holders Name Vendor Tax Number Analytic Description
Duplicate Payment Sub-analytic Variations
@ - the duplicate analytic is run on these fields i.e. when these fields are the same.
Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_04_APCS613.1 to AP_ANALYTIC_04_APCS613.10 Page 11

ACCOUNTS PAYABLE
Future Dated Invoices

Extracts all invoices with invoice dates in the future

Future Dated Invoices
Risk
Non-payment of invoices due to incorrect invoice date capturing resulting in unnecessary interest or
penalties, or premature invoicing of services that have not been rendered, or potentially fictitious
invoices.
Context
Invoices are expected to have a
Procedure
date subsequent to the provision
Extracts all invoices with invoice dates in the future. The invoice date is manually inputted and not
of goods or services. Invoices
system-generated. They are susceptible to human error during capturing and incorrect dates, including
captured with dates far into the
dates in the future, may be captured.
future indicates either
administrative errors or
premature invoicing of services
Analytic Logic
not yet provided. Extracts all invoices that have invoice dates in the future; for any date more than x days/ months after
the date the analytic is run will become an exception.
Variables
Number of months.

Company Code Company Name Vendor ID Vendor Name Document Date Amount in Reporting Currency
Report Currency Amount in Document Currency Document Currency Debit / Credit Indicator Release User
Accounting Document Number Vendor Invoice Number Vendor Stripped Invoice Number Release User Name
Output Visualization Examples
Analysis of dates per user
Count grouped by user
Essentials |Procure To Pay - Accounts Payable | AP_ANALYTIC_05_APCS341 Page 13

ACCOUNTS PAYABLE
Recurring Sundry Expenses

Review
Identifies all repetitive sundry invoices from the same vendor for the same amount

Recurring Sundry Expenses Review
Risk
Context Unauthorised invoices could be paid because less stringent procurement controls exist for sundry
expenses. This has the potential to result in unauthorised, invalid, excessive or potentially fraudulent
Sundry expenses are incurred
payments.
on a once-off or ad hoc basis,
and don’t require a purchase
Procedure
order. These expenses
Identifies all repetitive sundry invoices to the same vendor for the same amount. These vendors should
require less processing and be reviewed to understand why repetitive invoices are paid as sundry expenses, rather than through
attract less controls and are procurement, when there is an evident continuing business relationship.
not expected to be repetitive
and should be analysed Analytic Logic
further to discover if they need Extracts and filters invoices for sundry expenses using a unique invoice identifier (defined in scoping),
to follow the full procurement and performs a duplicate analysis using the vendor ID and value to provide a listing of all multiple sundry
processes and attract greater expenses.
controls.
Example
VENDOR_NAME ACCOUNTING_DOC_NO DOC_CURRENCY DOCUMENT_DATE INV_AMOUNT_DOC_CURRENCY
Sundry Inc. 1900165432 USD 5/08/2017 21 000.00
Sundry Inc. 1900175489 USD 15/08/2017 15 000.00
Unique sundry invoice identifier

Company Code Company Name Vendor ID Vendor Name Amount in Reporting Currency Report Currency
Amount in Document Currency Document Currency Accounting Document Number Document Date
Document Type Vendor Invoice Number Vendor Stripped Invoice Number Release User Released User Name
Value over time by vendor

ACCOUNTS PAYABLE
Invoices For One-time Vendors

Extracts all invoices made to one-time vendors

Invoices For One-time Vendors
Risk
Context Invoices for one-time vendors could be invalid because the controls are less stringent. This may result in
Vendors are created with an unauthorized payment to vendors or irrecoverable financial losses from fraudulent/invalid invoices being
expectation of a multi-transaction authorized and paid.
relationship. Creation of a vendor
in the ERP system requires Procedure
supporting documentation and Extracts all invoices made to one-time vendors classified as such on the vendor master file. Through
vetting prior to transacting interpretations and visualizations, validation of one-time vendor invoices can proceed, raising
(controls). exceptions for further examination.
One-time vendors do not require
such stringent vendor creation
Analytic Logic
procedures. Abuse or overuse of
Extracts all invoices from companies classified as one-time vendors in the ERP vendor master data, in a
one-time vendors could represent
given period.
control circumvention and/or
fraud.

Company Code Company Name Vendor ID Vendor Name Debit / Credit Indicator Report Currency
Amount in Reporting Currency Amount in Document Currency Document Currency Accounting Document Number
Document Date Vendor Invoice Number Vendor Stripped Invoice Number Release User Released User Name
Data distribution of vendors for invoice value
Count by user

ACCOUNTS PAYABLE
Vendor Payments Made Over A

Weekend
Identifies where the payment release date falls on a weekend

Vendor Payments Made Over A Weekend
Risk
Potentially invalid or fraudulent vendor transactions which may result in overpayment to vendors or often
Context irrecoverable financial losses.
Vendor payments, being a
standard and regular Procedure
organizational process, are
Identifies where the payment release date falls on a weekend. Release dates are utilized as this is the
expected to be executed during
point of authorization and are expected to take place during normal business hours; occurrence on a
normal business hours.
weekend could indicate unusual or unauthorized transactions.
Payments over weekends may
indicate fraudulent or suspicious
activity and should be reviewed Analytic Logic
for such. Analyses all payment release dates in the system and indicates if this date falls on a Saturday or
Sunday whereby it will be listed as an exception.

Company Code Company Name Vendor ID Vendor Name Accounting Document Number Day of Week
Vendor Invoice Number Document Date Clearing Date Debit / Credit Indicator Amount in Reporting Currency
Report Currency Amount in Document Currency Document Currency Pay User ID Pay User Name
Percentage values per vendor
Weekend values group by user

ACCOUNTS PAYABLE
Invoices Captured Over A

Weekend
Identifies where invoices were captured over a weekend

Invoices Captured Over A Weekend
Risk
Context Potentially invalid or fraudulent vendor transactions which may result in overpayment to vendors or often
Invoice capturing, being a irrecoverable financial losses.
standard and regular
organizational process, is Procedure
expected to be executed during Identifies where invoices were captured over a weekend. All invoices captured in the ERP system will
normal business hours. have an automatic entry/capture date attached which cannot be amended. The invoice date (as printed
Capturing over weekends may on an invoice by a supplier) is not the date used for this analytic.
indicate fraudulent/suspicious
activity and should be reviewed Analytic Logic
for such. Extracts where the entry/capture date of invoices fall on a Saturday or Sunday whereby it will be listed
as an exception.

Document Date Vendor Invoice Number Vendor Stripped Invoice Number Day of Week Release User
Released User Name Date Document Entered
Heatmap showing the user and

quantity
Values grouped by vendor

ACCOUNTS PAYABLE
Invoice Greater Than A

Threshold
Produces a list of invoices paid above a configurable threshold to
determine authorization process for testing

Invoice Greater Than A Threshold
Risk
Inappropriately reviewed and authorized transactions which could be caused by a lack of, or outdated,
Context level of authority.
All vendor invoices should be
approved in terms of the correct Procedure
level of authority for the Produces a listing of invoices paid above a configurable minimum and maximum threshold (financial
organization. Differing levels of value) to determine authorization process for testing. These transactions should be tested for accuracy,
authority are required for validity and approval.
purchases or invoices above
certain levels; more senior people Analytic Logic
in the organization approve Extracts invoices greater than the client-configured thresholds to create a listing for level of authority
higher value and materially testing by audit, for example, all invoices greater than $2 500 and up to $5 000.
significant transactions.
Variables
Minimum and maximum threshold value (for selecting invoices).
Company Code Company Name Vendor ID Debit / Credit Indicator Amount in Reporting Currency
Report Currency Amount in Document Currency Document Currency Accounting Document Number
Document Date Vendor Invoice Number Vendor Stripped Invoice Number Release User
Release User Name
Value of transactions by vendor

and releaser
Quantity and value of transactions by

vendor
Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_10_APCS110 Page23

ACCOUNTS PAYABLE
Invoice Date
Identifies where the invoice date precedes the purchase order approval date

Purchase Order Date After The Invoice Date
Risk
Context Ineffective procurement due to finance and procurement procedures not being followed which may
Best practice procurement result in the payment of invalid or unapproved purchases.
procedures dictate that purchase
order approvals should precede Procedure
an invoice. Any purchase orders Identifies where the invoice date precedes the purchase order approval date.
approved after an invoice should
be reviewed and examined to
understand the reasons and if
Analytic Logic
there was a control breakdown. Extracts invoices and related purchase orders where the invoice date is before the purchase order
approval date.

Company Code Company Name Vendor ID Vendor Name Vendor Invoice Number
Accounting Document Number Document Type Document Date Purchase Order Creation Date Days Difference
Purchase Order Number Purchase Order User Name Purchase Order User ID Amount in Reporting Currency
Report Currency Amount in Document Currency Incl VAT Document Currency
Date and materiality comparison
Days difference analysis by vendor

ACCOUNTS PAYABLE
Vendor Paid By Both Purchase

Order And Sundry Expense
Identifies the most recent instances where vendor invoices are paid by both a purchase
order and by a sundry expense

Vendor Paid By Both Purchase Order & Sundry Expense
Risk
Unauthorised invoices outside the scope defined in the purchase order could be paid because less
stringent procurement controls exist for sundry expenses. This may result in unauthorized, invalid,
Context
excessive or potentially fraudulent payments.
Vendor payments are expected to
be as a result of a transaction in
Procedure
either the procurement system
Identifies the most recent instances where vendor invoices are paid by both a purchase order and by a
(via purchase order) or a sundry
sundry expense. These vendors should be reviewed to understand why they are being paid as both a
expense. A vendor should be
procurement and sundry expense when it is expected all transactions should be in line with a purchase
processed through either process
order for a repetitive vendor.
but not both. Sundry expenses
require less processing and
Analytic Logic
attract less controls.
Summarizes vendors' invoices to extract the latest transactions where vendor invoices were processed
through both a sundry expense and a purchase order.
Example
VENDOR_NAME ACCOUNTING_DOC_NO STRIPPED_INV_NO DOCUMENT_DATE AMOUNT_DOC_CURRENCY
ABC Inc. 1899786258 INV00234 01/02/2017 21 000.00
ABC Inc. 5100196587 INV00245 15/02/2017 15 000.00
Different document numbers indicate PO

and sundry
Document Date Vendor Invoice Number Vendor Stripped Invoice Number Document Type Release User
Released User Name
Count of transactions by
vendor

ACCOUNTS PAYABLE
Invoices Greater Than

Approved Purchase Orders
Extracts all invoices exceeding the value of the related approved purchase orders

Invoices Greater Than Approved Purchase Orders
Risk
Invoices exceeding purchase orders could be caused by unauthorised changes to the initially agreed
upon services or goods. This may result in unauthorised spending, overspending or potentially fraudulent
spending.
Procedure
Context Extracts all invoices exceeding the value of the related approved purchase order from a configurable
A vendor invoice should not threshold value and above.
typically exceed the value
approved in the purchase order Analytic Logic
as the underlying procurement Extracts and compares the value on the invoice to the total value of the approved purchase order and
process has vetted the vendor at identifies instances where invoice value exceed the purchase order by the configurable threshold value,
a predetermined price. for example invoices greater than a purchase order from $50 and above.
In some countries, the effect of VAT or Sales tax can be removed from the invoice or added to the
purchase order value before comparison is done.
Variable
Minimum acceptable variance.
Example
PO_TOTAL_AMT_INCL_VAT_DOC INV_AMOUNT_DOC_CURRENC
VENDOR_NAME PO_NUMBER DIFFERENCE
_CURR Y
Fake Corp 5105634213 7 650.00 8 250.00 (600.00)
Real Industries 5105768923 45 000.00 50 000.00 (5000.00)
Believe Ltd 5105891342 213 500. 00 220 000.00 (6 500.00)

Company Code Company Name Vendor ID Vendor Name Purchase Order Amount in Document Currency
Invoice Amount in Document Currency Excl VAT Invoice Amount in Document Currency Document Currency
Invoice Number Purchase Order Number Purchase Order Creation Date Purchase Order User ID
Purchase Order User Name Difference
Showing quantity grouped by the user
Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_13_APCS106 Page

Page29
29
ACCOUNTS PAYABLE
Manually Released Invoices

(No 3-way Match)
Identifies manually paid invoices where the three way match with the purchase order and
goods received note did not result in an automatically released payment, or where the
payment was manually released

Manually Released Invoice (No 3 Way Match)
Risk
Context Fictitious, invalid or incorrect payments are caused by a user manually releasing a payment to a vendor
A three-way-match is performed and not relying on the automatic payment from a successful three-way-match.
between a purchase order, goods
received note and invoice to Procedure
ensure details are correct before
Identifies manually released invoices (paid and unpaid) where a three-way-match, between the invoice,
making payment to the vendor. A
purchase order and goods received note did not occur.
payment should not be
automatically made unless this
match is performed and Analytic Logic
reconciliation achieved. Extracts all invoices and highlights transactions without correct three-way-match which have been
manually released for payment (either before or after payment).
Example
VENDOR_NAME PO_NUMBER INV_AMOUNT_DOC_CURRENCY RELEASE_USER RELEASE_USER_NAME
ABC Inc. 5105634256 250.00 JSOAP Joe Soap
DEF Ltd 5105768925 100.00 ADOE Anne Doe
JHI Corp 5105891356 2 500.00 KSMART Ken Smart
Released by users indicate that not automatically released
Company Code Company Name Vendor ID Vendor Name Amount in Reporting Currency Report Currency
Amount in Document Currency Document Currency Document Date Accounting Document Number
Vendor Invoice Number Vendor Stripped Invoice Number PO Number Release User Released User Name
Three-way-match violations, grouped

by releasing user

ACCOUNTS PAYABLE
Three-way-match
Re-performance
Re-performs the three way match using purchase order and invoice amounts and
purchase order, goods received and invoice quantities

Three-way-match Re-performance
Risk
Context Fictitious, invalid or incorrect payments made on transactions not correctly matched.
A three-way-match is performed
between a purchase order,
goods received note and invoice Procedure
to ensure details are correct Identifies invoices (paid and unpaid) where the invoice amount and purchase order amount differ as
before making payment to the well as where a three-way-match, between the invoice, purchase order and goods received note
vendor. A payment should not be quantities did not occur.
made unless this match is
performed and reconciliation Analytic Logic
achieved. Extracts all invoices and highlights transactions without correct three-way-match between purchase
order, good received note and invoice quantities and invoice and purchase order amounts.

Company Code Company Name Vendor ID Vendor Name Amount in Reporting Currency PO Number
Document Currency Invoice Amount in Document Currency Excl VAT Amount in Document Currency Incl VAT
Purchase Order Amount In Document Currency Excl VAT PO Line Number Purchase Order Creation Date
Purchase Order Quantity Invoice Quantity Good Received Quantity Difference Report Currency
GR Document Number Invoice Number Reason for Exception
Total amount differences between invoice amounts and purchase order amounts

ACCOUNTS PAYABLE
Outlier Invoices
Identify invoice amounts greater than x standard deviations from the median amount of
that vendor

Outlier Invoices
Risk
Fictitious, invalid or incorrect payments made to vendors.
Context
An outlier is an observation point Procedure
that is distant from other Identifies outlier invoices by using standard deviations to determine amounts that deviate significantly
observations. Transactions from the expected amounts posted to a vendor.
outside the norm with vendors
are generally not expected, but Analytic Logic
could go unnoticed if high Extracts all invoice amounts greater than a configurable number of standard deviations from the median
volumes of transactions are amount for that vendor.
processed.
Variable
Number of standard deviations.
Output Results Field Names – Summary by Vendor

Company Code Company Name Vendor ID Vendor Name Invoice Count
Invoice Amount in Document Currency Total Maximum Invoice Number Maximum Invoice Date Maximum Amount
Number of invoices with same max value Minimum Invoice Number Minimum Invoice Date
Number of invoices with same min value Minimum Amount Average Invoice Amount Standard Deviation
Output Results Field Names – Outliers

Company Code Company Name Vendor ID Vendor Name Document Date Item Text
Invoice Amount in Document Currency Vendor Stripped Invoice Number

ACCOUNTS PAYABLE
Early Payment of Invoices

Identify invoices that were paid after the discount dictated in the payment terms and
calculate the value of those missed discounts

Early Payment Of Invoices
Risk
Opportunity cost arising from missing out on the discount.
Context
Many suppliers offer discounts in Procedure
order to encourage early Identifies invoices that were paid after the discount dictated in the payment terms and calculate the lost
settlement of their invoices. opportunity of missing out on that discount.
Taking advantage of these
discounts presents an opportunity Analytic Logic
to improve cash flow. Extracts all invoices that were paid after the discount as per the payment terms and calculates the
discount that could have been claimed had the invoice been paid within the discount payment terms.
Company Code Company Name Vendor ID Vendor Name Debit/ Credit Indicator
Vendor Stripped Invoice Number Document Date Document Currency Amount in Document Currency
Report Currency Invoice Amount Reporting Currency Amount Eligible for cash discount in Document Currency
Accounting Document Number No Days Lapsed Days Overlapped Cash Discount Amount
Vendor Invoice Number Payment Terms Code Payment Terms Description Released User Released User Name
Cash discounts missed by vendor

Ap en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ap en

Uploaded by

Copyright:

Available Formats

Essentials:

8 Duplicate invoices using vendor’s numeric invoice values

10 Duplicate invoices sub analytics

12 Future dated invoices

14 Recurring sundry expense review

16 Invoices for one-time vendors

18 Vendor payments made over a weekend

20 Invoices captured over a weekend

22 Invoices greater than a threshold

24 Purchase order date after the invoice date

26 Vendor paid by both purchase order and sundry expense

28 Invoices greater than approved purchase orders

30 Manually released invoices (no 3-way match)

Version 6.2.0 – 2019/04

32 Three way match re-performance

36 Early payment of invoices

Version 6.2.0 – 2019/04

Essentials – Accounts Payable Page 4

100000523 ABC Inc 1500080841 15/11/2017 1000

100000479 XYZ Ltd 1500081862 2/11/2017 5000

Fields used for analytics logic

Output Results Fields

Output Visualization Example

Duplicate payments grouped by user

Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_01_APCS102 Page 5

Essentials – Accounts Payable Page 6

Vendor A IN001 IN001 1/11/2017 1000.00

Vendor A IN001$ IN001 15/11/2017 1000.00

Fields used for analytics logic

Output Results Field Names

Output Visualization Example

Showing value over time

Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_02_APCS103 Page 7

Duplicate Invoices Using

Essentials – Accounts Payable Page 8

Vendor A IN001 001 1/02/2017 4000.00

Vendor A INv001 001 15/02/2017 4000.00

Fields used for analytics logic

Output Results Field Names

Release User Release User Name

Output Visualization Example

Showing value over time

Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_03_APCS601 Page 9

Duplicate Invoices Sub

Essentials – Accounts Payable Page 10

Output Results Field Names

Duplicate Payment Sub-analytic Variations

Essentials | Procure To Pay - Accounts Payable | AP_ANALYTIC_04_APCS613.1 to AP_ANALYTIC_04_APCS613.10 Page 11

Future Dated Invoices

Essentials – Accounts Payable Page 12

Output Results Field Names

Output Visualization Examples

Analysis of dates per user

Count grouped by user

Essentials |Procure To Pay - Accounts Payable | AP_ANALYTIC_05_APCS341 Page 13

Recurring Sundry Expenses

Essentials – Accounts Payable Page 14

Sundry Inc. 1900165432 USD 5/08/2017 21 000.00

Sundry Inc. 1900175489 USD 15/08/2017 15 000.00

Unique sundry invoice identifier

Output Results Field Names

Output Visualization Example