Standard prices and fees
Professional fees, rent, subscriptions, retainers, finance payments and fixed service charges can repeat at clean values with valid support.
Round-amount transaction testing
Review unusual round amounts in Xero and QuickBooks without treating them as automatic fraud indicators
Datplan identifies values close to user-selected round-number multiples and tolerances. The chart shows where matches concentrate, while Audit Evidence exposes the individual transactions so the reviewer can understand their commercial and accounting context.
How do I test round-amount transactions?
Select a comparable Xero or QuickBooks population, choose a meaningful period, configure the round multiple and tolerance, review the distribution of matches, then open the underlying records. Compare the exceptions with normal pricing, approval limits, recurring charges and source documents before deciding whether follow-up is required.
Test design
The right multiple depends on the currency and normal transaction values
A £100 multiple may be informative in one expense population and meaningless in another. The test should respond to the actual risk and business pattern.
| Setting or filter | Question it controls | Review risk |
|---|---|---|
| Population | Are you testing supplier bills, payments, journals, sales or another comparable class? | Mixed transaction types can combine valid round values with unrelated accounting entries. |
| Period | Does the test cover the reporting period, a risk window or a comparison period? | A short period may exaggerate a small number of routine transactions. |
| Round multiple | Should the test identify values around tens, hundreds, thousands or another unit? | A multiple that is too small flags ordinary pricing; one that is too large misses relevant patterns. |
| Tolerance | How close must a value be to the selected multiple? | A broad tolerance can classify much of the population as round; a zero tolerance may miss amounts intentionally placed just above or below. |
| Materiality or lower threshold | Which matches are large enough to matter for the procedure? | Removing small items can improve focus but may hide repeated control failures or split transactions. |
Review workflow
Explain why the amount is round before judging the transaction
- Understand normal pricingIdentify standard fees, rent, payroll bands, subscriptions, tax payments and other values expected to be rounded.
- Choose the accounting populationKeep document type, direction and currency sufficiently consistent for comparison.
- Configure the multiple and toleranceDocument why the selected settings respond to the risk being reviewed.
- Review concentrationsLook for owners, accounts, counterparties, dates or document types that dominate the matches.
- Open Audit EvidenceInspect the transactions behind the chart and trace them to invoices, contracts, approvals and payment evidence.
- Test related explanationsConsider approval thresholds, split purchases, estimates, manual journals, recurring charges and subsequent correction or reversal.
- Record the conclusionDistinguish expected commercial rounding from an error, control exception or unresolved item.
Questions for each exception
- Is the value normal for this supplier, customer or account?
- Does a contract, invoice or price list support it?
- Is it just below or above a formal approval threshold?
- Were several related transactions posted close together?
- Was the amount estimated and later corrected?
- Does the platform history identify unusual creation or approval behaviour?
- Is there a valid bank settlement or other corroborating evidence?
Legitimate causes
A high match count can describe the business rather than a control problem
Use segmentation to separate expected rounded populations from transactions where rounding is genuinely unusual.
Payroll and tax
Salary bands, pension payments, tax settlements and statutory charges can create legitimate round or near-round amounts.
Manual estimates
Accruals, provisions and budget-based journals may be rounded because the exact amount is not yet known. Review the basis and later true-up.
Approval behaviour
Values close to a control limit deserve context. Check the policy, related items, approval trail and whether purchases were intentionally split.
Both accounting sources
Apply consistent reasoning across Xero and QuickBooks
The same Datplan analysis is available for supported Xero and QuickBooks populations. Source documents, transaction types, identifiers and platform audit history remain source-specific, so the explanation for a match must be confirmed in the original accounting system.
Review the Xero Audit Analytics workflow or review the QuickBooks workflow.
Round does not mean fabricated
The test identifies a numerical characteristic. It cannot infer who chose the amount, whether it was estimated, whether a control was bypassed or whether the underlying transaction occurred. Those conclusions require other evidence.
Related tests
Use another analytical question when it responds to a different risk
Possible duplicates
Check whether repeated round values produce groups with the same counterparty, date and reference characteristics.
Review possible duplicates →Period-end activity
Check whether round estimates or manual adjustments concentrate around month-end reporting cut-offs.
Review period-end activity →Rare high-value counterparties
Separate routine rounded charges from large values posted to counterparties that appear only rarely.
Review rare counterparties →Round-amount questions
Choose settings that match the population
Why review round-amount transactions?
Round values can arise from estimates, manual entries, approval limits, standard fees or fabricated amounts, but they are also common in legitimate business. The test helps identify concentrations for review; it does not assign intent.
How does Datplan define a round amount?
The analysis uses configurable round-number multiples and tolerances. The reviewer selects settings appropriate to the currency, population, normal transaction size and purpose of the procedure.
Can I run the round-amount test on Xero and QuickBooks?
Yes. The same analysis is available for supported Xero and QuickBooks populations, with Audit Evidence drill-down to the records included in the result.
Does an amount just below an approval limit prove control avoidance?
No. A value near a threshold can be coincidental or commercially valid. Check the applicable policy, approval history, related transactions, source document and who entered or approved the record.
Which populations may be unsuitable?
Populations dominated by fixed tariffs, subscriptions, payroll bands, standard price lists, tax payments or other intentionally rounded values can produce many expected matches and may need narrower segmentation.
Inspect the records behind round-amount patterns
Run the configurable analysis on supported Xero or QuickBooks data, then use Audit Evidence and source documentation before reaching a conclusion.