Manual JEs as % of Total

Card class: Non-Hero • Category: Ecommerce Platform

Manual journal entries as a share of all journals. High manual share signals automation gaps, control risk, and audit scrutiny.

​

At a glance

The proportion of all journal entries in the period that were keyed by hand rather than posted automatically by a sub-ledger or connector. This is one of the most watched control metrics in finance, because every manual journal is a judgement call with no system control behind it: it can be wrong, it can be unauthorised, and it is the first place an auditor looks for earnings management. A low, stable manual share means your automation is carrying the load and your controls are sound. A rising share means the automated machine is failing somewhere and humans are patching the gap, which is slower, riskier, and more expensive. Sage Intacct stamps each batch with its source; the card divides the manual-JE count by the total to render the share.

​

Calculation

Calculated automatically from your Sage data by dividing the count of manual journal entries by the total journal count for the period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​

Worked example

A UK ecommerce group on Sage Intacct, two entities (UK Trading Ltd in GBP, EU Trading BV in EUR), consolidated monthly. Annual revenue ~£22M across Shopify and a BigCommerce B2B portal. Snapshot taken 9 Jun 26 covering the trailing 30 days. Default alert threshold of 25%. The card renders a gauge. Five things to notice:

1. 24.9% sits right under the 25% alert, and the proximity to the line is itself the story. A manual share approaching a quarter of all journals is high for an ecommerce business that should be running mostly on automation. The card has not technically fired, but a Controller who waits for it to cross 25% is missing the point: the trend is what matters, and a share this close to the threshold means the automated posting machine is leaking somewhere significant. The right read is not “we are still under the limit” but “why is a quarter of our ledger being keyed by hand.” That question is what this card exists to provoke.
2. The fix is almost always at the mapping layer, not in a control crackdown on the finance team. A high manual share is usually a symptom of unmapped transactions, not undisciplined accountants. On this account the manual slice cut by GL account showed that most of the 1,790 manual entries were daily PSP fee journals and marketplace settlement reclasses, both of which should post automatically once the fee descriptors and settlement formats are mapped. Telling the team to do fewer manual journals would just delay the work; mapping the PSP fees and the marketplace settlements eliminated about 1,400 of the 1,790 entries, dropping the share from 24.9% to roughly 5%. The lesson is that this card is a pointer to an automation gap, and the cure is engineering and configuration, not exhortation.
3. High manual share is the single biggest red flag for an external auditor. Auditors sample manual journals heavily because they are the entries most exposed to error and to manipulation: a manual JE can move revenue between periods, reclassify an expense to capital, or plug a number to hit a target, and none of those have a system control stopping them. A business carrying a 25% manual share will face more audit sampling, more questions, and more documentation requests than one at 5%. Reducing the manual share is therefore not just operational tidiness; it materially reduces audit friction and the risk of a finding.
4. A rising trend is more alarming than a high-but-stable level. A business that has always sat at 18% because of genuine consolidation complexity is in a different position from one that has climbed from 8% to 18% over three months. The trailing comparison on the card is what distinguishes the two. A climbing share means something that used to automate has stopped: a feed broke, a new channel was added without mapping, a new PSP appeared, or a vendor changed its invoice format. On this account the share had crept up over two months as a new Amazon marketplace settlement type started arriving unmapped, which the trailing view caught before it became structural.
5. Pair with Journals by Source Module for the full mix and Smart Coding Queue Depth (24h) for the upstream cause. This card is the alert; the source-module card shows the whole distribution; the Smart Coding queue shows the uncoded transactions that force the manual entries in the first place. Read as a trio they form a clean causal chain: the queue backs up because something is unrecognised, finance clears it by hand-keying journals, and the manual share rises. Fix the recognition rule at the top of the chain and all three cards improve together. On this account that is exactly how the fix played out.

​

Sibling cards merchants should reference together

​

Reconciling against Sage

Where to look in Sage Intacct: The native Sage Intacct views to run side by side with this card:

General Ledger → All → Journal Entries filtered to manual entries for the period, counted against the total journal count General Ledger → All → Manual Journal Entries (the dedicated manual-JE list) for the numerator Audit Trail on the manual entries to attribute them to preparers and to see the create/approve/post chain Reports → General Ledger → GL Detail grouped by source, exported to compute the manual share against the total Interactive Custom Report (ICR) on the GL data source counting manual-source batches divided by total batches over the trailing window, grouped by GL account to reveal what is being manually posted

Intacct distinguishes manual journals from sub-ledger and connector postings via the batch source stamp, which is what makes this ratio reliable. The card’s numerator matches a native Manual Journal Entries count for the same period, and the denominator matches a native total-journal count, as long as both use batch-level counting and the same period boundary. For Multi-Entity Console accounts compute the share per entity at the dashboard scope, because manual reliance often concentrates in the entity with the most complex consolidation work. Common reconciliation pitfalls:

• What counts as manual: Intacct’s adjustment journals, statistical journals, and inter-entity journals can each be classified as manual or not depending on configuration. The card uses the source stamp; a native report that filters differently will produce a different numerator.
• Recurring journals: a recurring template that posts automatically should not count as manual even though a person designed it. The card classifies by posting source; a naive filter on “created by a user” would over-count.
• Approval-routed manual JEs: a manual JE that went through Intacct’s approval workflow is still a manual entry for this ratio. Some teams mentally exclude approved ones as “controlled”; the card counts them, because the control is approval, not automation.

Why our number may legitimately differ from a Sage Intacct manual-JE count: Cross-connector reconciliation: The cross-connector value is that the manual share is usually a downstream symptom of an upstream recognition gap that lives at the connector boundary. When a PSP changes its fee descriptor, a marketplace adds a new settlement format, or a new vendor appears, the transactions arrive unrecognised, pile into the Smart Coding queue, and finance clears them by hand. Reading this card against the Smart Coding queue and the commerce connectors shows the cause, not just the symptom, which means the fix is a one-time mapping change at the top of the chain rather than an endless stream of manual journals at the bottom.

​

Known limitations / merchant FAQs

What manual share should I aim for? Lower is better, but the right floor depends on the business. A highly automated pure-ecommerce operation can get under 10%. A complex multi-entity group with heavy consolidation, intercompany, and reclassification work may legitimately sit at 15-20%. The default alert is 25%. What matters most is the trend: a stable low share is healthy; a rising share signals an automation gap regardless of the level. Is a high manual share always a control problem? Not always a control problem, but always a question worth answering. Sometimes it is a temporary automation gap (an unmapped PSP, a new channel) that is fixable at the mapping layer. Sometimes it reflects genuine accounting complexity that needs manual judgement. The card surfaces the share; cutting it by GL account and preparer tells you whether the cause is fixable automation or genuine adjustment work. Why do auditors care so much about manual journals? Because manual journals have no system control behind them and can do things automated postings cannot: move revenue between periods, reclassify expense to capital, plug a number. They are the entries most exposed to both error and manipulation, so auditors sample them heavily. A lower manual share means less audit sampling, fewer questions, and lower risk of a finding. How do I actually reduce the manual share? Find what is being keyed and automate it. Cut the manual slice by GL account to see the repeat offenders (usually PSP fees, marketplace settlements, recurring reclasses), then map those transactions so they post automatically. The cure is configuration and integration work, not telling the finance team to journal less, because the work still has to happen somewhere. Do recurring journals count as manual? No, if they post automatically from a template. The card classifies by the actual posting source, so an auto-posting recurring depreciation or rent journal is not manual even though a person designed the template. A filter based on “who created it” would wrongly count these; the card does not. Do approval-routed manual JEs still count? Yes. A manual JE that went through an approval workflow is still a manual entry for this ratio, because the control is approval, not automation, and the entry is still a hand-keyed judgement. Approval reduces the risk of a bad manual JE; it does not turn it into an automated posting. Sage Intacct vs Sage 50 / 200 on manual-JE tracking? Intacct’s batch source stamp makes manual entries cleanly distinguishable from automated postings, which is what this ratio depends on. Sage 50 and Sage 200 classify journal sources differently and with less granularity. This connector targets Intacct; reach out about availability and the reconciliation differences on other Sage products. Does multi-entity change the read? The logic is identical per entity, but manual reliance often concentrates in the entity doing the most consolidation and intercompany work. The most useful read is per-entity, because a manual-share spike in one subsidiary points straight at that team’s process or an unmapped feed in that entity. The card reports at the dashboard scope and drills per entity. Is the count-based or value-based view better? The count-based ratio (default) is the better control read, because control risk scales with the number of judgement calls, not their size. The value-weighted drill is useful for materiality: a few large manual journals can matter more to the financial statements than many small ones. Read the count for control risk and the value for materiality. How fresh is the ratio? It reflects the GL at typical Intacct refresh cadence (around 5 to 15 minutes), computed over a trailing 30-day window. Intraday postings barely move it; the meaningful signal is the period-over-period shift, which the trailing comparison surfaces before it becomes structural. Implementation Partner role on this metric? The Partner usually owns the integration mappings and the automation rules that determine how much posts automatically. When the manual share rises, the Partner is typically the right person to extend a mapping or build a rule so the work returns to automation. Align the manual-vs-automated source classification in the Vortex IQ field map so the ratio matches your control definitions.

---

​

Tracked live in Vortex IQ Nerve Centre

Manual JEs as % of Total is one of hundreds of KPI pulses Vortex IQ tracks across Sage 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.