Data Modelling
Part of No-code calculations and business rules
Handling rounding in a business calculation
Choose the rounding point, precision and function for a no-code calculation, then check item totals, ties and negative values.
A rounding rule needs three decisions: what is rounded, when it is rounded and how boundary cases are handled. “Show two decimal places” describes presentation; it does not fully specify the calculation. Write the rule before choosing a function in a no-code builder.
Choose the point in the calculation
Consider three illustrative line items, each with an unrounded value of 0.334. Rounding each item to two decimal places before adding gives 0.33 + 0.33 + 0.33 = 0.99. Adding first gives 1.002, which rounds to 1.00 to two decimal places under nearest-value rounding. The one-cent difference comes from the order of operations.
Neither sequence is a universal rule. Decide which amount the workflow requires and whether it must retain rounded items, unrounded inputs or both. If another system issues the final amount, establish which calculation governs the app's result.
Check the function in your builder
The same function name can hide different interfaces. Power Fx documents Round(Number, DecimalPlaces) and separate RoundDown and RoundUp functions. Check the syntax and behaviour of the rounding function in your chosen builder rather than transferring a formula solely because it has the same name.
Direction words also need care with negative values. Power Fx RoundUp moves away from zero, while RoundDown moves towards zero. Include credits or negative adjustments in the rule and checks if the field permits them. Verify tie behaviour in the chosen app if needed.
Rounding Function Reference by Platform
- Power Fx: Round(Number, DecimalPlaces)
- Standard rounding (round half up)
- Google AppSheet: Round(value, digits)
- Nearest value, ties round up
- Airtable: ROUND(number, precision)
- Round half up; supports negative precision
Build a compact check
Record expected results just below, at and just above a relevant rounding boundary. Include a negative value if permitted, and a multi-item case that distinguishes rounding items from rounding the total. Compare the calculated number, displayed number and value sent to a decision or export.
Make the required rounding step explicit in the formula or workflow, and document it beside the rule. Financial, tax or accounting requirements may impose a particular method; this example does not prescribe one.
