Skip to main content
Metrics type: Key Metrics • Category: Ecommerce Platform
The killer reconciliation finding for mid-market ecom ops: dollar value of orders that never made it to Oracle ERP Cloud GL plus the reason.

​
At a glance

The dollar value of commerce-platform revenue that has not yet hit the Oracle ERP Cloud General Ledger, broken down by reason. Calculated as commerce_total_revenue minus oracle_revenue_booked_gl for the same window, with reason codes attached to each missing dollar.

​
Calculation

Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US Fortune 500 wholesale apparel distributor (annual revenue ~$420M) running Oracle ERP Cloud with three Business Units. Connected commerce platforms: Shopify Plus DTC, Salesforce Commerce Cloud B2B with Net-30 terms, Adobe Commerce wholesale portal. The 30-day window covers 14 Mar 26 to 12 Apr 26. Reason breakdown the card surfaces: Five things to notice:
  1. **The biggest leak is AutoInvoice Pending (2.42M).∗∗Thisisnotlostrevenue,itisstuckworkingcapital.Shippinghashappened,customerisonthehook,butnoReceivablestransactionmeansnoARrecord,noDSOclock,andnoGLbooking.ThecardletstheControllerdrillintotheSOlistandchaseOrderManagementtopushAutoInvoicemanuallyforthehighest−valuecases.AtFortune500scale,freezing2.42M).** This is not lost revenue, it is stuck working capital. Shipping has happened, customer is on the hook, but no Receivables transaction means no AR record, no DSO clock, and no GL booking. The card lets the Controller drill into the SO list and chase Order Management to push AutoInvoice manually for the highest-value cases. At Fortune 500 scale, freezing 2.4M of working capital for 4 days is real money in a high-rate environment.
  2. Unmapped Customer ($384K) is real revenue at risk. If the Customer mapping is wrong on Adobe Commerce, those orders may never sync. The Controller pings the Oracle Functional Consultant to fix the mapping in the customer hub; otherwise next month’s gap is even bigger and the orders eventually age out of the integration retry queue.
  3. Credit Memo Refunds ($820K) is policy, not error. This is the structural gap between gross commerce headlines and net GL booking. It will always exist; what matters is whether the rate is constant or rising. Rising = quality / fulfilment / pricing problem. Constant = baseline noise.
  4. The $62K Unknown bucket is the leakage signal. It is small enough not to alarm but it is where reconciliation problems live. The Controller hands this list to the Oracle Admin every Monday morning during the close cycle.
  5. Alert fires at >$10K unreconciled in the Unknown bucket. AutoInvoice Pending and Credit Memos are explained gaps; only Unknown trips the sentiment.

​
Sibling cards merchants should reference together

This card is the trigger; the action lives on its companions.

​
Reconciling against the vendor’s own dashboard

Where to look in Oracle ERP Cloud: There is no single native Oracle Fusion report for this metric, that is precisely why Vortex IQ surfaces it. The closest manual approach inside Oracle is:
Build an OTBI analysis on the Receivables Real Time Subject Area filtered to Transaction Status = 'Pending AutoInvoice' and sum Transaction Amount. Then compare manually to the commerce platform’s last-30-day total revenue export.
An Oracle Functional Consultant can build this OTBI analysis in 30 minutes. Most do not, because the cross-platform comparison requires pulling commerce data manually, and the moment you do that you have lost reproducibility. Vortex IQ runs this every 15 minutes. Adjacent Oracle reports that look related but are not:
  • Sales Order Inquiry: shows all open SOs but without commerce-side comparison.
  • Customer Account Inquiry: AR-balance based, looks at unpaid Invoices not pre-Invoice gap.
  • Income Statement (Financial Reporting Center): smooths the gap into a monthly trendline; loses the per-order traceability.
Why our number may legitimately differ from a manual reconciliation: Cross-connector reconciliation, the killer finding: This card IS the cross-connector reconciliation; it has no counterpart on the commerce platforms themselves. The closest sibling on the commerce side is the Pending vs Captured Revenue card on Stripe (which catches Stripe-routed payment captures awaiting settlement) but that compares Stripe-internal state, not commerce-to-ERP. The full audit trail with originating order IDs lives on Revenue Gap, Detailed Breakdown. That is the worklist; this card is the headline.

​
Known limitations / merchant FAQs

Should this gap ever be zero? No, and you should be suspicious if it is. A small structural gap (AutoInvoice Pending + Credit Memos + period-boundary timing) is healthy. Zero gap means either the connector is not pulling new commerce orders, or someone is force-closing the books before reconciliation. Aim for a stable gap that scales with revenue, with the Unknown bucket near zero. How big should the gap be vs total revenue? A typical Fortune 500 commerce business runs at 8 to 15% gross commerce vs net GL revenue gap inside a 30-day window:
  • AutoInvoice Pending: 4 to 9% (higher for B2B Net-30 / Net-60, lower for DTC).
  • Credit Memo Refunds: 3 to 8% (varies by category, apparel skews high; electronics low).
  • Voided / Cancelled: 1 to 3%.
  • RMCS Deferred: 1 to 4% if you have subscription / extended-warranty revenue.
  • Unknown: ideally < 0.3% of commerce gross.
If your gap is > 20%, something structural is wrong with the integration or accounting policy. Vortex IQ logs the breakdown so the cause is visible. What is the difference between this and the Revenue Gap, Detailed Breakdown card? This card is the headline ($X total gap, classified by reason). The detailed breakdown is the per-order list with commerce IDs, Oracle SO IDs (or absent), and audit comments. The Controller checks this card; the Oracle Admin works the breakdown. Why is Salesforce Commerce Cloud B2B always the biggest gap? B2B Net-30 / Net-60 introduces a structural ship-to-bill lag of 10 to 30 days. Orders ship from the warehouse, but Receivables Invoices generate on a billing schedule that can wait until the order is fully fulfilled or until a billing-cycle batch run. During that lag the order is real revenue economically but not yet GL revenue. DTC orders typically AutoInvoice at fulfilment within 4 hours. Does the card account for ASC 606 deferred revenue? Yes. If your account uses Oracle Revenue Management Cloud (RMCS), the Oracle GL booked figure already excludes deferred revenue. Commerce gross still includes the full sale (it is a customer payment, not a recognition decision). The gap surfaces as RMCS Deferred in the breakdown, which is policy-correct, not a defect. Multi-currency stores: does the FX Translation bucket overstate? The bucket isolates the residual after period-average FX is applied. If your Business Units transact in 5+ currencies, expect the FX bucket to be 0.5 to 2% of commerce gross. Anything larger usually means the field map’s FX rate source is misconfigured against the GL Daily Rates table. What does the alert look like in practice? At >10KUnknown,theNerveCentrefiresasentimentalertandAskViqsurfacesthequestion"Whatisthe10K Unknown, the Nerve Centre fires a sentiment alert and Ask Viq surfaces the question "What is the 62K reconciliation drift this week?” with a deep-link to the breakdown card. The Controller typically resolves it in 15 to 30 minutes by mapping a missing Customer or escalating a stuck SO to the Oracle Functional Consultant. Multi-Ledger vs single-Ledger, does the card behave differently? Same logic, simpler scope. Single-Ledger skips the FX Translation bucket and the Financial Consolidation Hub elimination logic. Most fields are identical. Does this differ from the equivalent NetSuite card? Conceptually identical, mechanically different. NetSuite has Subsidiaries and a single integrated GL; Oracle has Business Units and a Multi-Ledger architecture with Subledger Accounting as a customisable rule layer. The Oracle card has additional reason codes (RMCS Deferred, AutoInvoice Pending) reflecting Oracle-specific posting mechanics. Companies migrating from NetSuite up to Oracle Fusion (a common pattern under Oracle’s portfolio strategy) keep the Vortex IQ reconciliation logic intact across the move. Sales Order vs AutoInvoice vs Cash Receipt, where does each fit?
  • Commerce order → Oracle Sales Order: fast (minutes via OIC or REST API). If this fails, gap appears as Unmapped Customer.
  • Sales Order → AutoInvoice Receivables transaction: slow (hours to days). If this is stuck, gap appears as AutoInvoice Pending.
  • Receivables → Cash Receipt application: slow (days to weeks). NOT in this card; this gap is captured by DSO.
  • Refund → Credit Memo: variable. Captured as Credit Memo Refunds bucket.
Oracle Integration Cloud (OIC) is supposed to handle this. Why am I seeing gaps? OIC moves data; it does not validate cross-system completeness. If a commerce order fails OIC’s customer-lookup step, OIC logs the failure but the order does not appear in Oracle. Vortex IQ reads both sides and surfaces the gap. Many of our Fortune 500 customers run OIC for the integration plumbing and Vortex IQ for the reconciliation visibility; the two are complementary.

​
Tracked live in Vortex IQ Nerve Centre

Revenue Gap vs Commerce is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.