REVENUE ROUNDS FIELD NOTE
Mapping unbalanced categories without breaking history
Can a clearer reporting map be validated without losing the source categories that explain past totals?
Integrations · May 18, 2026 · Revenue Rounds editorial
Revenue Rounds editorial
Can a clearer reporting map be validated without losing the source categories that explain past totals?
Start with the source and period
Start from invoice lines and the source system’s category identifiers. Keep source categories separate from the reporting groups you want to discuss. Preserve an export of the original mapping and its review date. Do not rename or delete production categories merely to make a chart look cleaner.
A worked synthetic example
Synthetic example: September lines total $40,000: Consultations $20,000, Diagnostics $15,000 and an unmapped category $5,000. The unmapped share is 12.5%. After reviewing the underlying lines, $3,000 belongs to Diagnostics and $2,000 to Other. The revised groups are $20,000, $18,000 and $2,000; the total remains $40,000. A changed group share is a classification effect, not new revenue.
Review steps
- Export the original categories, identifiers and totals for a fixed reporting period.
- Review ambiguous lines with someone who understands the practice’s services. Avoid guessing from category names alone.
- Apply only the intended reporting-map changes, then compare totals, group movements and any remaining unmapped share.
- Document the mapping version and recheck the comparison period. Explain whether historical views were recomputed under the new map.
Limits to keep visible
Revenue Rounds includes category mapping paths, but this note does not promise immutable versioned mappings or automatic historical preservation. Confirm the actual recomputation behavior before relying on a trend. Refund and tax handling can affect line totals; review the relevant source conventions with your bookkeeper.
Bring this to the next review
Keep a before-and-after total and a short explanation for each ambiguous classification. A map is ready for discussion when the source total still reconciles and the team can explain what changed.
Explore the product views · Check connection requirements · All resources
Get the next field note.
Register your interest in practical notes by email. Separate from demo requests; no automated mailing-list subscription is confirmed.
