Colorado and Minnesota Retail Delivery Fee (RDF) Finally Tracked Automatically in QuickBooks Online — WeIntegrate Is the Only Shopify Integration That Does This

Colorado Shopify merchants have been navigating the Retail Delivery Fee (RDF) since July 1, 2022. Minnesota merchants joined them on July 1, 2024. For both states, the obligation is the same: a state-mandated surcharge collected from customers on qualifying retail deliveries, calculated per transaction, remitted to the state, and passed through the merchant’s books on its way there. Shopify records the RDF automatically on applicable orders as a separate line item. What Shopify has not been able to do — until WeIntegrate — is route that collected fee to the right QuickBooks Online account automatically.

For Colorado merchants, that gap has been open for four years. Every qualifying order sent to a Colorado address with at least one taxable item has required a manual accounting decision: identify the RDF amount from Shopify’s order data, post an offsetting entry to the correct liability account, and keep a separate reconciliation to track how much has been collected and how much remains outstanding. Minnesota merchants inherited the same problem at their July 2024 start date.

No other Shopify-to-QuickBooks Online integration has offered a dedicated account setting for the Retail Delivery Fee. WeIntegrate now does — and for Colorado and Minnesota merchants, it resolves a manual accounting burden that has existed since the day the fee went live.

What the Retail Delivery Fee Is and Why It Belongs in a Liability Account

Colorado’s RDF applies to any retail delivery made to a Colorado address where at least one item in the order is taxable. The fee is a fixed per-transaction charge — not a percentage of the sale amount — that the merchant collects from the buyer at checkout and remits to the Colorado Department of Revenue. Full details on current rates, exemptions, and filing requirements are on the Colorado Department of Revenue’s Retail Delivery Fee page. Minnesota’s RDF applies similarly under MN Stat. § 168E.03, effective July 1, 2024, on qualifying retail deliveries to Minnesota addresses.

In both cases, the RDF is:

Collected from the buyer as a separate, visible surcharge at checkout
Owed to the state from the moment it is collected — the merchant is the conduit, not the beneficiary
Never merchant revenue — it passes through the merchant’s account briefly, then belongs to a government authority

The correct QuickBooks Online account type for the RDF is Other Current Liability. The merchant holds this money temporarily and owes it to the state. Posting it to an income account overstates revenue by the collected fee amount on every qualifying order. Posting it to an expense account misrepresents the business’s cost structure — the merchant did not spend the fee, they collected and forwarded it. Absorbing it into the net payout deposit makes the obligation invisible on the balance sheet entirely.

None of these outcomes produce a P&L or balance sheet that reflects what actually happened on Colorado or Minnesota orders. WeIntegrate produces one that does.

How WeIntegrate Records the RDF Correctly

WeIntegrate’s Retail Delivery Fee (RDF) setting — available under Destination Fees & Surcharges in the integration’s settings — allows merchants and their accountants to designate a dedicated Other Current Liability account in QuickBooks Online for all RDF amounts Shopify records on qualifying orders.

When this setting is configured, every Shopify Sales Receipt for a qualifying Colorado or Minnesota delivery includes a dedicated RDF line item posted to the designated liability account. The line carries the exact fee amount Shopify recorded for that order. Orders that do not include an RDF — orders to other states, orders with no taxable items, orders where Shopify did not assess the fee — receive no RDF line. No placeholder entries, no zero-amount clutter on unaffected orders.

Refunds are handled correctly. When a refunded order included an RDF charge, the corresponding Refund Receipt in QuickBooks includes an RDF credit line that reduces the liability account balance by the refunded fee amount. The liability account reflects only what has been collected and not yet remitted — accurate through every order, every return, and every reconciliation.

For merchants using QBO Classes for multi-location or departmental reporting, class assignment on RDF lines is supported — enabling per-location tracking of fee obligations without manual journal entry work.

The result: the RDF obligation builds in QBO automatically, order by order, from the first qualifying Colorado or Minnesota delivery after the setting is enabled. When remittance time arrives, the merchant clears the balance against the liability account. The documentation that supports the remittance has been accumulating in QBO since day one.

Why This Resolves a Long-Standing Issue in Colorado — and a Growing One in Minnesota

Colorado’s RDF has been law since July 1, 2022. For four years, qualifying Shopify orders — every retail delivery to a Colorado address with at least one taxable item — have required a manual accounting workaround because no integration handled it automatically. Merchants who have been recording the RDF correctly have done it by hand: pulling RDF amounts from Shopify’s order export, entering journal entries to separate the fee from revenue, maintaining a running balance of what’s been collected and what’s been remitted.

At low order volume, this is manageable — inconvenient, but manageable. At any meaningful scale into Colorado, it is recurring monthly work that compounds into significant overhead across every close cycle since 2022.

Minnesota merchants have been in the same position since July 2024. Two years in, the manual workaround has the same structural problem: it relies on a human remembering to run it, every month, for every qualifying order.

WeIntegrate eliminates both workarounds with a single configuration change. One setting. One QBO account selected. Every qualifying order thereafter records the RDF correctly, automatically, without any ongoing manual intervention. No other Shopify-to-QuickBooks Online integration or automation solution offers this capability.

The Complete Picture: Every Fee and Tax, Every Account, Automatically Classified

The Retail Delivery Fee setting completes a comprehensive account-level classification infrastructure that makes WeIntegrate’s Shopify-to-QBO records the most complete available in any integration configuration. Every component of every Shopify order and every Shopify payout now has a designated QBO account:

On every Sales Receipt (per order):

Product revenue → designated income accounts by QBO item
Shipping collected from customer → separate shipping income account
Tips → dedicated tips income account via Service Item (for merchants collecting gratuity)
Sales tax → Other Current Liability account (never touching income)
Retail Delivery Fee (RDF) → dedicated Other Current Liability account
Discounts → reflected as reductions against revenue

On every QBO Deposit (per Shopify payout):

Order totals → assembled from individual Sales Receipts via Undeposited Funds
Processing fees → dedicated expense account
Transaction fees → dedicated expense account
Marketplace sales tax → dedicated Other Current Liability account
Shipping label fees → dedicated expense account
Import tax → dedicated Other Current Liability account
Customs duties → dedicated Other Current Liability account (separate from import tax)

Each setting operates independently. A Colorado merchant who also ships internationally, purchases Shopify Shipping labels, and collects tips at checkout can have every component of every order and every payout — RDF on individual Sales Receipts, customs duties on payout deposit line items — classified correctly and automatically. No journal entries. No month-end adjustments. No reconstruction from Shopify export files.

This is the accounting infrastructure that no journal-entry Shopify integration can replicate. Journal entries collapse all of this per-order and per-payout detail into a net figure before it ever reaches QBO. Individual account classifications — including the RDF liability that Colorado and Minnesota merchants have been tracking manually for years — are gone the moment the journal entry is posted.

Who This Matters For

Colorado Shopify merchants who have been manually accounting for the RDF since July 2022: WeIntegrate’s dedicated setting eliminates the recurring workaround. Every qualifying order records the fee to the correct liability account automatically from the day the setting is configured. Four years of manual effort, resolved with one setting.

Minnesota Shopify merchants who have been managing the fee since July 2024: the same result — per-order RDF liability recording, automated from the first qualifying delivery, with no ongoing manual intervention required.

Accountants and bookkeepers managing Shopify clients in Colorado or Minnesota: correctly classified RDF entries on every qualifying Sales Receipt mean the balance sheet reflects the actual outstanding fee obligation at every point in the period. Month-end close does not require a separate RDF reconciliation pass. The liability account shows exactly what was collected, exactly what was credited via returns, and exactly what remains outstanding.

Operators evaluating their current integration: if your current Shopify-to-QuickBooks integration cannot route the Retail Delivery Fee to a dedicated liability account, it is almost certainly not handling marketplace sales tax, import tax, or customs duties correctly either. The RDF setting is a reliable indicator of whether an integration was designed to handle the full complexity of Shopify’s fee and tax structure — or whether it was built for a simpler version of the problem than the one Colorado and Minnesota merchants actually face.

Any merchant in states considering RDF legislation: Colorado and Minnesota are not the only states evaluating retail delivery fee frameworks. WeIntegrate’s account-level support for the RDF establishes the infrastructure to handle the fee correctly wherever and whenever it arrives — without a manual workaround as the interim solution.