> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Revenue Gap, Detailed Breakdown, Oracle ERP Cloud > The killer reconciliation card. Shows commerce-vs-Oracle ERP Cloud gap broken down by reason, not just the dollar number. How to read it, why it matters, a... **Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > The killer reconciliation card. Shows commerce-vs-Oracle ERP Cloud gap broken down by reason, not just the dollar number. ## At a glance > The drill-down detail behind [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-vs-commerce). Each missing dollar with originating commerce order ID, Oracle Sales Order ID (or absent), reason code, and audit comments. The Controller's daily worklist for the Fortune 500 close cycle. | | | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Per-row record for each commerce order in the window that does not reconcile cleanly to an Oracle GL revenue line. Columns: Commerce Order ID, Commerce Platform, Order Date, Customer, Order Amount, Oracle SO ID (or NULL), Oracle Receivables Trx ID (or NULL), Reason Code, Days Outstanding, Last Action Owner. | | **Tax treatment** | Net of tax. | | **Reason codes** | AutoInvoice Pending, Voided / Cancelled, Credit Memo Refund, Unmapped Customer, Period Boundary Timing, FX Translation, RMCS Deferred, Unknown. | | **Currency** | Reporting ledger consolidated. | | **Multi-Ledger** | Per-Business-Unit drill-down. | | **Time window** | `30D` (matches the headline gap card) | | **Alert trigger** | `>5% gap unreconciled` (rolled to the headline card) | | **Roles** | owner, finance | ## 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 distributor on Oracle ERP Cloud with Salesforce Commerce Cloud B2B and Adobe Commerce. The headline [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-vs-commerce) card shows \$4.83M unreconciled. This card is the per-order detail behind that headline. **Sample of 8 representative rows from the 1,847-row breakdown:** | Commerce ID | Platform | Order \$ | Oracle SO ID | Reason | Days | Owner | | ----------- | -------- | --------- | ------------ | ---------------------- | ---- | --------------------- | | SFCC-247201 | SFCC B2B | \$84,200 | OE-1024782 | AutoInvoice Pending | 3 | Order Mgmt | | SFCC-247199 | SFCC B2B | \$42,800 | (none) | Unmapped Customer | 5 | Functional Consultant | | ADO-018482 | Adobe | \$128,400 | OE-1024801 | AutoInvoice Pending | 6 | Order Mgmt | | SFCC-247144 | SFCC B2B | \$18,200 | OE-1024633 | Credit Memo Refund | 2 | n/a (policy) | | ADO-018400 | Adobe | \$4,200 | OE-1024612 | Voided / Cancelled | 1 | n/a (cust cancel) | | SFCC-247098 | SFCC B2B | \$8,400 | (none) | Period Boundary Timing | 1 | n/a (next period) | | SFCC-246920 | SFCC B2B | \$32,800 | OE-1024401 | RMCS Deferred | 22 | n/a (recognition) | | ADO-018211 | Adobe | \$2,800 | OE-1024488 | Unknown | 14 | Investigation | **The Controller's worklist:** 1. **Unmapped Customer rows (column "Owner = Functional Consultant")**: 22 rows totalling \$384K. Action: send the customer-key list to the Oracle Functional Consultant, who maps them in Customer Hub. Resolves the gap on next sync. 2. **Unknown rows ("Owner = Investigation")**: 14 rows totalling \$62K. Action: open a JIRA ticket per row to Operations to determine why the order failed. Most resolve as customer-data-quality issues that should not have been allowed at order entry. 3. **AutoInvoice Pending rows**: high-volume, low-individual-effort. Action: confirm the AutoInvoice schedule is running on cadence; escalate any rows >7 days old to Order Management leadership. 4. **Voided / Cancelled, Credit Memo Refund, RMCS Deferred, Period Boundary**: explained gaps, no action. Reviewed monthly to ensure rates are not climbing. **Daily / weekly use:** * **Daily** during the close cycle: open this card, sort by Days Outstanding descending, work the top 20 unreconciled rows. * **Weekly** stand-alone review: pivot by Reason Code, examine which buckets are growing. * **Monthly** with Functional Consultant: address the systemic causes (customer mapping rules, AutoInvoice schedule, custom SLA rules). ## Sibling cards merchants should reference together | Card | Why pair it with Revenue Gap, Detailed Breakdown | | ------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-vs-commerce) | The headline this card breaks down. | | [Commerce Orders Without Oracle Sales Order](/nerve-centre/kpi-cards/oracle-erp/commerce-orders-without-oracle-erp-cloud-sales-order) | The Unmapped Customer subset as its own card. | | [Open Sales Order Value](/nerve-centre/kpi-cards/oracle-erp/oerp-open-so-value) | The AutoInvoice Pending universe lives in here. | | [Sales Orders Blocked on Inventory or Credit](/nerve-centre/kpi-cards/oracle-erp/sales-orders-blocked-on-inventory-or-credit) | Why some AutoInvoice Pending rows are stuck. | | [Credit Memo Value](/nerve-centre/kpi-cards/oracle-erp/oerp-credit-memos-value) | Credit Memo Refund bucket trend. | | [Sales Order to Invoice Lead Time](/nerve-centre/kpi-cards/oracle-erp/sales-order-to-invoice-lead-time) | Cycle-time view of what becomes AutoInvoice Pending. | ## Reconciling against the vendor's own dashboard **Where to look in Oracle ERP Cloud:** This card has no native equivalent, that is the point. Oracle Fusion alone cannot show you what is missing, only what is present. The closest manual approach: > Build an OTBI **Order Management** + **Receivables** combined analysis showing each Sales Order with a flag for `Receivables Trx Created Y/N`. Then export the commerce-platform 30-day order list and outer-join in Excel. The manual reconciliation typically takes 6 to 12 hours per close. This card runs continuously every 15 minutes. **Why our list may legitimately differ from a manual reconciliation:** | Reason | Direction | Why | | ----------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Order matching key** | Either | Card matches commerce order\_id ↔ Oracle reference\_number / commerce\_order\_id field. If the integration uses a different key, mapping must be configured. | | **Multi-line orders** | Either | Some orders split into multiple Oracle SOs; the card aggregates by commerce order, not Oracle SO. | | **Returns vs original sales** | Either | A return creates a new commerce order line and a Credit Memo in Oracle; the card pairs them as a Credit Memo Refund row. | **Cross-connector reconciliation:** This IS the cross-connector reconciliation card. The constituents: | Card | Direction | Notes | | ----------------------------------------------------------------------------------- | ----------- | ----------------------------------- | | Commerce-platform total revenue | Numerator | The summed gross commerce. | | [Revenue Booked into GL](/nerve-centre/kpi-cards/oracle-erp/revenue-booked-into-gl) | Denominator | The Oracle-side booked total. | | [Open Sales Order Value](/nerve-centre/kpi-cards/oracle-erp/oerp-open-so-value) | Subset | AutoInvoice Pending rows live here. | ## Known limitations / merchant FAQs **How big is this list typically?** Healthy Fortune 500: 500 to 3,000 rows in a 30D window depending on order volume. Of those, 60-80% are explained gaps (AutoInvoice Pending in normal range, Credit Memos, RMCS deferred); the worklist is the remaining 20-40%. **Why does it take days to clear unmapped customers?** Customer Hub mapping in Oracle Fusion goes through a Functional Consultant or admin user with the right role. The mapping creates a new Customer record with all required attributes (TaxID, address, terms, currency). For Fortune 500 with strict data governance, this is a 1 to 3 day process per customer. Vortex IQ surfaces the queue but the gating is process. **Can I export the list to Excel for offline review?** Yes via the dashboard's CSV export. Most Controllers prefer the in-product view because the deeplinks (Commerce ID → commerce platform UI; Oracle SO ID → Oracle Manage Orders) are clickable. **The Owner column is automated, how?** Reason Code → Owner mapping is in the field map. Customisable per workspace. Default mappings: Unmapped Customer → Functional Consultant; Unknown → Investigation queue; AutoInvoice Pending → Order Management leadership; rest → no action. **Does Ask Viq help with this card?** Yes. Common queries: "What is the top reason for the gap this week?", "Which customer has the most unmapped orders?", "Show me Unknown rows older than 14 days." Ask Viq surfaces the answer with the row drill-down. **OIC vs Vortex IQ for the same problem?** OIC is the integration platform, moves data between Oracle and external systems. It can log integration failures but it cannot see commerce platform truth. Vortex IQ reads both sides and reconciles. They are complementary; many Fortune 500 customers use OIC for inbound data flow and Vortex IQ for outbound reconciliation. **Multi-currency, what is in the Order \$ column?** Reporting ledger currency at period-average FX. Drill-down shows transaction currency for audit. The FX Translation reason isolates the residual after the period-average is applied. **My commerce platform sometimes shows "test" orders that should not reconcile. Are they here?** Configurable. Default: orders flagged as test in commerce platform metadata are excluded. The field map controls. *** ### Tracked live in Vortex IQ Nerve Centre *Revenue Gap, Detailed Breakdown* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.