A WORKED EXAMPLE
Eight rows.
A clearer report.
A small reporting tool checked the sample file below. Five entries passed the checks. Three were flagged and kept out of the totals, with the reasons shown below.
Original demonstration · made-up data · not client work Download the sample transaction file (CSV) ↓What the file adds up to
- Paid
- $330.50
- Refunded
- $40.00
- Net collected
- $290.50
Net collected is paid amounts minus refunds. Another $90.00 is pending, so it is shown separately and is not counted as collected. All amounts are in US dollars.
The five entries included
| Transaction | Status | Amount |
|---|---|---|
| t001 | Paid | $125.00 |
| t002 | Paid | $80.00 |
| t003 | Pending | $90.00 |
| t005 | Refunded | $40.00 |
| t006 | Paid | $125.50 |
Three entries to check
Row numbers count the file’s heading as row 1. These entries remain in the original file; the report does not silently remove or correct them.
| File row | Transaction | Why it was left out |
|---|---|---|
| 5 | t004 | The amount is “not-a-number”, which cannot be used as a dollar amount. |
| 6 | t001 | This transaction ID already appears in row 2. Counting it again would duplicate the payment. |
| 9 | t007 | The amount is “NaN”, which is not a valid dollar amount. |
What the tool checks
- Amounts must be valid, nonnegative US dollar values with no more than two decimal places.
- Duplicate transaction IDs are flagged so they cannot inflate the totals.
- Dates and payment statuses must match the file’s agreed format.
- Money is calculated in whole cents so these totals stay exact.
This is a finished example report. It does not upload your files or connect to a bank. A customer project would use its own agreed format and checks.