Skip to content

Ronald Jantzi

← Customer Feedback for QuickBooks Online

My feedback

1 result found

  1. Tags per line item/journal entry

    16 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    8 comments  ·  QuickBooks Mobile Feedback Forum » Transactions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Ronald Jantzi commented  · 

    QuickBooks Online needs a second line-level tracking dimension, similar to Classes, that can be filtered in Profit & Loss reports.
    Problem
    Many industries ... including agriculture ... (agriculture, construction, manufacturing, nonprofits) incur costs in one calendar year that generate revenue in another. QuickBooks Online forces users to rely on transaction dates or transaction-level custom fields, which breaks accurate profitability reporting.
    Example (Agriculture):
    • Wheat is planted in fall 2025
    • Harvested and sold in summer 2026
    • Costs belong to Crop Year 2026, not calendar year 2025
    Currently:
    • Classes work at the line level (good)
    • Custom Fields work at the transaction level only (insufficient)
    • Tags were transaction-level and are being phased out
    This makes accurate crop-year or project-phase accounting impossible without artificial workarounds (splitting vendor invoices into multiple bills).
    Requested Enhancement
    Add line-level support for:
    • Custom Fields or
    • A second Class-type dimension (e.g. “Cycle”, “Phase”, or “Year”)
    Requirements:
    • Assignable per transaction line
    • Filterable in Profit & Loss reports
    • Independent of transaction date
    Business Impact
    Without this:
    • Financial reports are misleading
    • Costs and revenue are mismatched across years
    • Users are forced into error-prone workarounds
    • QBO becomes unsuitable for agriculture and multi-year job costing
    With this:
    • Accurate profitability by field / job / phase
    • No increase in UI complexity for basic users
    • Keeps QBO viable for advanced but common use cases
    Closing
    This is not an edge case — it affects:
    • Fall-planted crops
    • Multi-year construction jobs
    • Grant-funded nonprofit programs
    • Manufacturing WIP
    QuickBooks already supports one line-level dimension (Class).
    Extending this to one additional dimension would resolve a long-standing and widely reported limitation.

    Ronald Jantzi supported this idea  · 

Feedback and Knowledge Base

(thinking…)