> ## 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. # Manual JEs as % of Total, Oracle ERP Cloud > Manual JEs as % of Total measures hand-keyed journal entries as a share of all GL journals. The single ratio auditors zero in on as an automation and controls red flag. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Manual journals as a percentage of all journals. The higher it climbs, the more your close runs on hand-keying instead of automation. ## At a glance > Manual JEs as % of Total expresses the count of manually entered General Ledger journals as a percentage of all journals posted in the window. It is the distilled controls signal from the broader [Journals by Source](/nerve-centre/kpi-cards/oracle-erp/journals-by-source-jesource) mix. A low ratio means automation (Receivables, Payables, Inventory via Subledger Accounting) is doing the work. A high or rising ratio means humans are hand-keying entries the system should generate, which is the classic audit red flag for both control weakness and error risk. The gauge makes the trend obvious at a glance and fires when the manual share gets uncomfortable. | | | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `Manual journal count / Total journal count` over the window, expressed as a percentage. The numerator is GL journals with a Manual journal source (and, depending on your view, Spreadsheet / ADFdi uploads, which many controllers treat as manual for this purpose). The denominator is all GL journals across every source. | | **Why it matters** | A high manual ratio is one of the first things external auditors test, because manual journals bypass the validations and approvals built into automated subledger posting. It is also an efficiency signal: every manual journal is human time the close should not need. | | **What pushes it up legitimately** | Genuine accruals, reclasses, corrections, intercompany adjustments, and month-end estimates that have no automated source. A modest manual share is normal and healthy; the concern is elevation and trend. | | **What pushes it up as a warning** | A broken integration that people work around by hand, a controls process that lets staff key entries the system should generate, or estimation churn where the same accruals are booked and reversed repeatedly. | | **Business Unit scope** | Respects the dashboard's selected Business Unit and Ledger filter. By default rolls up every Business Unit and primary Ledger the connected role can see. | | **Time window** | `30D` (trailing 30 days) | | **Alert trigger** | `>25%` - a manual share above a quarter of all journals is the warning line for most large-enterprise ledgers | | **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 Fortune 500 omnichannel retailer runs Oracle ERP Cloud across three Business Units. The controller reviews the manual ratio over two consecutive 30-day windows: 14 Feb 26 to 15 Mar 26, then 16 Mar 26 to 14 Apr 26. | Window | Manual journals | Total journals | Manual ratio | Status | | ---------------------- | --------------- | -------------- | ------------ | -------------------- | | 14 Feb 26 to 15 Mar 26 | 240 | 3,200 | 7.5% | Healthy, no alert | | 16 Mar 26 to 14 Apr 26 | 910 | 3,400 | 26.8% | Alert fired (`>25%`) | Four things to notice: 1. **The ratio jumped from 7.5% to 26.8% in one period and crossed the alert line.** The total journal count barely moved (3,200 to 3,400), but the manual count nearly quadrupled. That tells you the rise is real hand-keying, not just higher overall volume. 2. **The cause was a Receivables integration outage.** For nine days, AutoInvoice failed to post a batch of ecommerce revenue automatically, so the close team booked the revenue by hand to keep the period on track. The manual journals were the symptom; the broken automation was the disease. 3. **The right fix is to repair automation, not to celebrate the manual heroics.** Reopening the integration and letting AutoInvoice and Subledger Accounting reprocess the backlog removes the need for the manual entries going forward. The controller can then reverse or supersede the hand-keyed journals as the automated ones land, keeping the GL clean. 4. **At quarter-end this would have been an audit finding.** A manual ratio near 27% with a cluster of large revenue journals keyed by hand is exactly the population an auditor samples. Catching it in real time, with the cause identified, turns a potential finding into a documented and resolved incident. ## Sibling cards merchants should reference together Manual JEs as % of Total is the alarm; the cards below are the diagnosis and the surrounding pipeline. | Card | Why pair it with Manual JEs as % of Total | | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | [Journals by Source (JeSource)](/nerve-centre/kpi-cards/oracle-erp/journals-by-source-jesource) | The full composition behind this single ratio. When the ratio spikes, this card shows which automated source shrank. | | [Subledger-to-GL Posting Interface Errors (24h)](/nerve-centre/kpi-cards/oracle-erp/subledger-to-gl-posting-interface-errors-24h) | A broken subledger posting path is the most common reason people start hand-keying. Watch both. | | [OIC Integration Flow Failures (24h)](/nerve-centre/kpi-cards/oracle-erp/oic-integration-flow-failures-24h) | When the ecommerce-to-Fusion flow fails, manual journals fill the gap. This card shows the upstream cause. | | [Accrual Reversals (last close)](/nerve-centre/kpi-cards/oracle-erp/accrual-reversals-last-close) | Repeated manual accruals and reversals inflate the manual ratio and signal estimation churn. | | [Journals in Error (PostedFlag=E)](/nerve-centre/kpi-cards/oracle-erp/journals-in-error-postedflage) | Hand-keyed journals are more likely to be out of balance and bounce into error. | | [Oracle Fusion Health Score](/nerve-centre/kpi-cards/oracle-erp/oracle-fusion-health-score) | The composite that an elevated manual ratio drags down. | ## Reconciling against Oracle ERP Cloud **Where to look in Oracle ERP Cloud:** The closest native equivalents in the Oracle Fusion UI are: > **Navigator → General Accounting → Journals → Manage Journals** (filter Source = Manual, count headers, compare to all sources) > **Reports and Analytics → OTBI → Financials → General Ledger - Journals Real Time** (build a Manual-count over Total-count ratio) > **Navigator → General Accounting → Period Close → Close Status** (journal counts feeding the close) The simplest reconciliation is to run the OTBI Journals Real Time subject area, count journal headers where Source is Manual, divide by total journal headers for the same period and scope, and compare to the gauge. They should match to within rounding when the period, Business Unit, and Ledger scope are identical. Common mistakes when comparing against Oracle's own reports: * **Counting lines instead of headers.** A single manual journal can have many lines. Decide whether you are counting headers or lines and apply the same basis to both numerator and denominator. The card counts journal headers. * **Including or excluding Spreadsheet inconsistently.** Some controllers treat ADFdi Spreadsheet uploads as manual; others keep them separate. Confirm which convention the card uses and match it in Oracle. * **Different windows.** A trailing 30-day window and a fiscal period rarely line up exactly. Compare like for like. **Why our number may legitimately differ from Oracle's reports:** | Reason | Direction | Why | | -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------- | | **Headers vs lines basis** | Either | Counting journal lines rather than headers changes both numerator and denominator and can shift the ratio. The card uses headers. | | **Spreadsheet treatment** | Either | Whether ADFdi uploads count as manual affects the numerator. Align the convention. | | **Window vs period** | Small | A trailing 30-day window includes or excludes journals near a fiscal-period boundary differently from a period-bounded report. | | **Scope** | Either | The card rolls up every Business Unit and Ledger the role can see; a scoped Oracle query shows a different ratio. | ## Known limitations / merchant FAQs **What manual ratio is normal?** It varies by business and by where you are in the close cycle, but for most large-enterprise commerce-connected ledgers a healthy steady-state sits in the single digits to low teens as a percentage. The alert line of `>25%` is set above typical normal so it fires on genuine elevation, not on a busy but ordinary close. The trend matters as much as the level: a doubling from a low base is a signal even before it crosses the threshold. **Does a high ratio always mean something is wrong?** Not always. Some periods legitimately carry more manual entries: a complex month-end with many accruals and reclasses, an acquisition integration, or a one-off restatement. The card flags the elevation so a human can judge whether it is explained. The danger is a high ratio that nobody can account for, which is when it becomes an automation gap or a controls weakness. **Why do auditors care so much about manual journals?** Because manual journals are where financial-statement misstatement is most likely to be introduced, either by error or intentionally. They bypass the validations and approvals that automated subledger posting enforces. External auditors routinely extract the full manual journal population and test a sample, looking at who posted, the account combinations, round-number amounts, and entries posted near period-end. A consistently low manual ratio is evidence of strong automated controls. **Should I count Spreadsheet (ADFdi) uploads as manual?** Many controllers do, because an ADFdi upload is still a human deciding the amounts and accounts, just loaded in bulk rather than keyed one at a time. The card's convention is documented in the source mix; if you prefer to treat Spreadsheet separately, read this card alongside [Journals by Source](/nerve-centre/kpi-cards/oracle-erp/journals-by-source-jesource), which keeps the slices distinct. **The ratio spiked but our automation is fine. What else causes it?** Two common benign causes: a quiet automation period (fewer Receivables and Payables journals because of a seasonal lull) mathematically lifts the manual share even if the manual count is flat; and a deliberate batch of reclasses or corrections at period-end. Read this card with [Journals by Source](/nerve-centre/kpi-cards/oracle-erp/journals-by-source-jesource) to tell whether the manual count rose or the automated denominator fell. **How do I bring the ratio down?** Fix the automation gaps, not the symptom. Repair broken integrations so Receivables, Payables, and Inventory journals post automatically again; build Subledger Accounting rules for recurring event types people currently key by hand; and convert standing manual accruals into automated allocation or recurring-journal definitions in Oracle. The ratio falls as the system reclaims the work. *** ### Tracked live in Vortex IQ Nerve Centre *Manual JEs as % of Total* 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.