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. 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 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 |
- 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.
- 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.
- 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.
- Voided / Cancelled, Credit Memo Refund, RMCS Deferred, Period Boundary: explained gaps, no action. Reviewed monthly to ensure rates are not climbing.
- 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 | The headline this card breaks down. |
| Commerce Orders Without Oracle Sales Order | The Unmapped Customer subset as its own card. |
| Open Sales Order Value | The AutoInvoice Pending universe lives in here. |
| Sales Orders Blocked on Inventory or Credit | Why some AutoInvoice Pending rows are stuck. |
| Credit Memo Value | Credit Memo Refund bucket trend. |
| 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. |
| Card | Direction | Notes |
|---|---|---|
| Commerce-platform total revenue | Numerator | The summed gross commerce. |
| Revenue Booked into GL | Denominator | The Oracle-side booked total. |
| Open Sales Order Value | Subset | AutoInvoice Pending rows live here. |