The built-in duplicate report allows FINANCE to view similar transactions, serving as a foundation for post-processing of exported or posted transactions.

Article content:

• Enabling Duplicate Control:
• Use the duplicate report for control
• How the Duplicate Report Works
• Duplicate Check criterias

Enabling Duplicate Control:

You need ADMIN rights in Acubiz to enable or disable the duplicate report. Access Your Settings as follows:

Click on LOCAL SETTINGS to access DUBLICATES and set the report active or inactive.

In the "Send report to" field, enter one or more full email addresses. Recipients will receive an email with a link to the report, but the report won't be attached. The link directs to the same report found under FINANCE => RECONCILIATION => DUPLICATE REPORT.

Use the duplicate report for control

The duplicate report is available in Acubiz under FINANCE for the specific company:

The reports are displayed next.

If duplicates exist, you can open the report to verify them.

How the Duplicate Report Works

The report lists transactions compared using these methods:

• Cash expense => Cash expense
• Credit card => Cash expense

Duplicate Check criterias

To appear on the duplicate report, transactions must meet these criteria:

1. The same user must have created the transactions (outlay and credit card transactions)
2. Amounts are within (+/-) 1% of each other
3. Submitted for approval within the last 30 days

The duplicate report may list the same transaction multiple times since the check spans a longer period. Example:

• In week 1 Peter has a transaction of DKK 100.00 (a)
  • At the end of week 1 (Saturday) the duplicatecheck executes and there are no duplicates in the report
  • The check compares back in time (30 days <============== Week 1)
• In Week 2 Peter has another transaction of DKK 100.00 (b)
  • At the end of week 2 (Saturday) the duplicatecheck executes and transaction (a) will now appear in the report, as a duplicate of transaction (b).
  • The check compares back in time (30 days <============== Week 2)
• In week 3 Peter has another transaction of DKK 100.00 (c)
  • At the end of week 3 (Saturday) the duplicatecheck executes and transaction (a) + (b) will now appear in the report as a duplicate of transaction (c).
  • The check compares back in time (30 days <============== Week 3)
• In week 4 Peter has another transaction of DKK 100.00 (d)
  • At the end of week 4 (Saturday) the duplicatecheck executes and transaction (a) + (b) + (c) will now appear in the report, as a duplicate of transaction (d).
  • The check compares back in time (30 days <============== Week 4)
• In week 5 Peter has another transaction of DKK 100.00 (e)
  • At the end of week 5 (Saturday), the duplicatecheck executes and transaction (b) + (c) + (d) will now appear in the report, as a duplicate of transaction (e).
  • The control compares back in time (30 days <============== Week 5) and therefore transaction (a) is now out of the control period.

This is a simplified method for checking and reporting.