Table of Contents

Total Amount Discrepancies

Context:
When integrating with POS systems, discrepancies between the expected total amount (as calculated by UEAT) and the POS-reported total can occur. These differences often stem from variations in tax calculation, rounding rules, promotions, or other adjustments applied at different stages of the order lifecycle.

Common Causes

  1. Tax Calculation Differences

    • Jurisdictional Variations: Different tax rates or exemptions applied by POS vs. UEAT. Or new taxes not applied at the same moment.

  2. Promotions and Discounts

    • POS-Exclusive Promotions: Discounts applied at POS but not communicated to UEAT.
    • UEAT Promotions: Online discounts not fully recognized by POS.
    • Stacking Rules: Differences in how multiple discounts are combined.

  3. Service Charges and Fees

    • Delivery Fees: POS may apply fees differently or include them in taxable amounts.
    • Tips: Variations in tip handling (pre-tax vs. post-tax). See 3rd Party Delivery Tip for specifics around the tip calculation.

  4. Currency and Precision

    • Decimal Precision: POS may truncate or round differently (e.g., 2 vs. 3 decimal places).

Impact

  • Order Validation Failures: POS may reject orders if totals don’t match.
  • Accounting Inconsistencies: Reports may show mismatched revenue.
  • Customer Experience Issues: Incorrect totals displayed to customers.

Best Practices

  • Define a Tolerance Threshold: Allow small discrepancies (e.g., ±$0.05) to avoid unnecessary rejections. Make sure to communicate the POS decision to UEAT on the configuration.
  • Synchronize Tax Rules: Ensure UEAT and POS share the same tax configuration.
  • Communicate Promotions Clearly: Use API fields for discounts and promotions consistently.
  • Log Discrepancies: Implement audit logs for debugging and reconciliation.
  • Validation not done on Payment: Total validation should not be done on the payment information but in the total.

API Considerations

  • Fields to Monitor:
    • order.totalAmount
    • order.taxAmount
    • order.discountAmount
  • Error Handling:
    • Use warning or soft validation for minor discrepancies.
    • Hard reject only for significant mismatches.