# Round Dollar Transactions: When They Signal Fraud

- Author: PreciseBankFlow (https://www.precisebankflow.com)
- Published: 2025-07-14
- Updated: 2025-07-14
- Category: Fraud and forensic review
- Canonical: https://www.precisebankflow.com/blog/round-dollar-transactions

> When round dollar transactions in bank data signal fraud: running the test, normal round amounts to exclude and how to follow up on what remains.
Round dollar transactions signal possible fraud when whole-number amounts cluster with one payee, repeat without invoices, or sit just under an approval limit, after you remove the round amounts that are normal, such as rent, loan payments and payroll transfers. The test is a lead generator: it narrows the list, and documents decide each item.

## Why do round dollar transactions draw a reviewer's attention?

A round dollar transaction is an amount ending in .00, and often in 00 or 000 before the decimal. Real purchases rarely land on such figures, because invoices come from quantities, unit prices and sales tax. An amount that someone typed in, rather than one an invoice produced, is more likely to be round.

That is the whole logic of the test. A person inventing a payment to themselves picks 2,500.00, not 2,487.36. A person inventing a fake invoice often does the same, because nothing forces the figure to be odd.

The weakness is just as plain. Plenty of honest payments are round by design. So the test only works after you strip those out, and its result is a set of payees to look at, not a finding about any of them.

## Running a round dollar transactions test on bank data

A round dollar test flags each amount divisible by a chosen unit, such as 100 or 1,000, then summarizes the flags by payee and month. The summary matters more than the flags, because one round payment means little while a payee paid only in round amounts stands out.

1. Build one table of debits from every account in scope, with payee, date, amount and a page reference.
2. Add a flag column. In a spreadsheet, `=MOD(ABS(C2),100)=0` marks multiples of 100. Use 1,000 for a stricter test.
3. Remove the exclusions listed in the next section and keep a list of what you removed.
4. Pivot by payee: count of payments, count of round payments, share that are round, total value.
5. Sort by share round, then by total value.
6. Read the top of the list against the vendor file and approval policy.

| Payee (example) | Payments | Round | Share round | Round total |
| --- | ---: | ---: | ---: | ---: |
| Example Consulting LLC | 18 | 18 | 100% | 63,000.00 |
| J. Morales (reimbursement) | 11 | 9 | 82% | 13,500.00 |
| Office supply vendor | 40 | 1 | 3% | 200.00 |

The values are invented. The first two rows deserve a closer look. The third is noise.

## Round dollar payments to exclude before you review

Exclusions are the payments that are round for a known, documented reason. Removing them first keeps the result short enough to read. Most come from contracts or internal transfers, and the vendor file or a short talk with the bookkeeper will name them in minutes.

Typical exclusions:

- Rent and lease payments set by contract.
- Loan principal payments and fixed installment plans.
- Transfers between the entity's own accounts.
- Payroll funding transfers to a payroll provider.
- Owner draws and capital contributions, which are tested separately.
- Retainers and fixed monthly fees under a signed agreement.
- Tax deposits rounded to the dollar by policy.

Exclude by payee and by contract, never by amount alone. If you drop every 5,000.00 payment because the rent is 5,000.00, a fake vendor paid 5,000.00 vanishes with it.

## What do you do with round dollar transactions that remain?

Round dollar transactions that remain after exclusions go to document review: for each payee at the top of the list, find the invoice, the approval and proof the goods or services arrived. Most will have a reason. The ones that do not are the real result of the test.

Work through each flagged payee in this order. Confirm the payee exists and has an address and tax ID on file. Pull three invoices and match each to a payment. Check who approved them and whether the amounts sit just below that person's limit. Then look at timing: round payments that started soon after someone gained approval authority, or that stopped when they left, tell a story.

If the statements came from the person you are reviewing, check them first; [the tests that expose fake or altered bank statements](/blog/how-to-detect-fake-bank-statements) come before any pattern test, since a forger controls the amounts. For the time this review takes across many clients, [estimating reconciliation software ROI in hours and errors](/blog/reconciliation-software-roi) gives a way to cost manual review honestly. [PreciseBankFlow](/) reads every statement line and exports the lines to Excel, which gives step 1 its table, though the judgment about each payee stays with you.

## Round dollar deposits: a different question from round payments

Round dollar deposits raise a separate question. A round payment out may be a fake invoice; a series of round cash deposits in may be money from a source the account holder will not name, or cash split to stay under a reporting threshold. Test credits on their own, never mixed with debits.

For a business that takes card payments, round deposits are rare, since card settlements carry odd cents. Repeated round cash deposits, especially just under the $10,000 currency reporting threshold that the [IRS manual section on structuring](https://www.irs.gov/irm/part4/irm_04-026-013) describes, or spread across days, fit the pattern described in [structured cash deposits and how they look in bank statements](/blog/structured-cash-deposits). Large round transfers in from unrelated third parties, quickly sent on, are one of the [money laundering red flags in bank statements](/blog/money-laundering-red-flags-in-bank-statements), and that post covers when to escalate.