Journals by Source Module

Card class: Non-Hero • Category: Ecommerce Platform

Distribution of journal entries by originating module (Order Entry, AP, AR, Inventory, Cash Management, manual JE, connector). A spike in manual JE share is a control-quality signal.

​

At a glance

A breakdown of where your journal entries come from: Order Entry, Accounts Payable, Accounts Receivable, Inventory Control, Cash Management, manual journal entries, and the commerce connectors. In a well-run Sage Intacct ledger the overwhelming majority of postings flow automatically from the operational sub-ledgers, and manual JEs are a thin slice reserved for genuine adjustments. The shape of this distribution is a direct read on the health of your automation and your controls. A growing manual-JE slice means the automated machine is failing somewhere and people are patching the gap by hand, which is slower, more error-prone, and exactly what auditors scrutinise.

​

Calculation

Calculated automatically from your Sage data by grouping each journal entry by its originating module and computing the share of each. 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 ecommerce group on Sage Intacct, single entity, annual revenue ~$35M across Shopify, Amazon, and a wholesale BigCommerce B2B portal. Highly automated order-to-GL posting. Snapshot taken 9 Jun 26 covering the trailing 30 days. The card renders a donut of journal counts by source module. Five things to notice:

1. 61% from Order Entry connector feeds is the healthy shape, because that is the operational volume posting itself automatically. In a high-volume ecommerce business the bulk of journals should be order-driven and machine-posted: every Shopify, Amazon, and BigCommerce order that flows to the GL is a journal nobody had to key. A distribution where Order Entry dominates and manual JE is a thin slice is exactly what you want to see. The card confirms the automation is carrying the load. If this slice suddenly shrank, the question would be whether the order feed had broken, which would also show up in Commerce Orders Without Sage Intacct Order.
2. The manual-JE slice rising from 2% to 3.7% is the one movement worth chasing, even though it is still small in absolute terms. A near-doubling of the manual share in one period is a control-quality signal regardless of the low base. Something that used to post automatically is now being keyed by hand, or a new adjustment pattern has emerged. The card surfaces the shift; the next step is to cut the manual slice by preparer (via the Audit Trail) and by GL account to see what is being manually posted. On this account the increase traced to a new PSP whose fee transactions were not yet mapped, so finance was manually journaling the fees each day, which is exactly the kind of automation gap that should be fixed at the mapping layer, not papered over with daily manual entries.
3. The connector slice is the bridge between the commerce world and the ledger, and its size tells you how commerce-driven your GL is. At 61%, this business runs almost entirely on automated commerce postings, which is normal for a pure ecommerce operation. A traditional distributor with phone and EDI orders would show a smaller connector slice and a larger AP/AR slice. Neither is wrong; the shape just describes the business. What matters is stability: a connector slice that lurches up or down period to period usually means a feed changed, a channel was added, or an integration started double-posting, all of which are worth a look.
4. AP and AR slices behave like a vital sign for the back office. A sudden jump in the AP slice can mean a supplier-invoice catch-up after a backlog, or a new vendor onboarding wave; a jump in AR can mean a billing run or a credit-memo cleanup. These are usually benign and explainable, but reading them in context stops a finance lead from being surprised by a question in the close review. The trailing comparison is what separates a normal monthly rhythm from a genuine structural change in where journals originate.
5. Pair with Manual JEs as % of Total for the alerting layer and Transaction Imbalances for the integrity layer. This card is the diagnostic distribution; the manual-JE card carries the threshold alert; the imbalances card catches the case where a feed is not just busy but broken. Read as a trio they answer three questions: where do journals come from, is the manual share creeping up, and is any feed posting unbalanced data. On this account the trio together showed the manual slice was rising for a benign reason (the unmapped PSP), no feed was imbalanced, and the fix was a mapping change rather than a control crackdown.

​

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 the period and grouped by source, which is the closest native equivalent to this card’s distribution General Ledger → All → Open Batches and posted batches, each carrying its source-module stamp Reports → General Ledger → GL Detail with a source-module column added, exported and pivoted to count by module Audit Trail on the manual-JE slice to attribute hand-keyed journals to specific preparers Interactive Custom Report (ICR) on the GL data source grouping the batch count by MODULEKEY (the source-module field) over the trailing window

Intacct stamps every batch with the module that created it, which is what makes this distribution clean and reliable. The card’s count matches a native Journal Entries listing grouped by source, as long as both use the same period boundary and the same definition of “journal” (batch-level vs line-level). For Multi-Entity Console accounts group by source at the same entity scope as the dashboard filter, because connector feeds and manual entries can concentrate in particular subsidiaries. Common reconciliation pitfalls:

• Batch count vs line count: the card counts journal entries (batches) by default, not individual GL lines. A native report that counts lines will read much higher because one Order Entry batch can contain dozens of lines. Align on the unit before comparing.
• Connector feeds bucketed as import/API: Intacct groups connector postings under the import or API source rather than a named commerce module. The card relabels these as connector journals using the integration identity; a raw native report will show them as import/API.
• Recurring and reversing journals: these post under their original module but can inflate the manual slice if created as manual templates. The card classifies by the actual posting source, not the template type.

Why our number may legitimately differ from a Sage Intacct journal listing: Cross-connector reconciliation: The cross-connector value is that the journal mix is the fingerprint of how your operation actually posts to the ledger. When the Order Entry slice falls while the commerce connectors say orders are flowing normally, the feed is dropping postings and the orphaned-orders card will confirm it. When the manual slice rises while the Smart Coding queue is backing up, the cause is unrecognised transactions forcing hand-keying. Reading the distribution against its commerce-side and GL-health siblings turns a static donut into a live diagnosis of where the automation is winning and where it is quietly failing.

​

Known limitations / merchant FAQs

What is a healthy journal mix? For an ecommerce business, most journals should originate from automated sources: Order Entry and the commerce connectors carrying the operational volume, AP and AR carrying the back-office flow, and a thin manual-JE slice for genuine adjustments. There is no single ideal split because it depends on the business model, but a small and stable manual slice is the common thread across healthy ledgers. Why does the connector slice matter? It tells you how much of your ledger is commerce-driven and machine-posted. A large, stable connector slice is the sign of a well-automated ecommerce back office. A connector slice that lurches around usually means a feed changed, a channel was added or removed, or an integration started double-posting, all of which deserve a look. Is a rising manual-JE slice always bad? Not always, but it always deserves an explanation. Sometimes it is benign (a new PSP whose fees are not yet mapped, a one-off cleanup, a billing catch-up). Sometimes it signals an automation gap or a control weakness. The card surfaces the shift; the action is to cut the manual slice by preparer and by account to find the cause, then fix it at the mapping layer rather than living with daily manual entries. Does this card count batches or lines? Batches (journal entries) by default, because that is the meaningful unit for a control read: one Order Entry batch is one posting event even if it contains fifty lines. A line-level native report will read much higher. Align on the unit before comparing the card to a Sage report. How are connector postings labelled? Intacct groups them under the import or API source. The card relabels them as connector journals using the integration identity so you can see commerce-driven postings as their own slice. This is purely a labelling improvement over the raw Intacct source; the underlying batches are the same. Why does this card not have its own alert? Because it is a diagnostic distribution, not a single number with a threshold. The alerting lives on its companion, Manual JEs as % of Total, which watches the slice most predictive of control risk. This card is where you go to understand the full picture once that alert fires. Sage Intacct vs Sage 50 / 200 on source tracking? Intacct stamps every batch with its originating module, which makes this distribution precise. Sage 50 and Sage 200 record journal sources differently and with less granularity, so the equivalent on those products is coarser. This connector targets Intacct; reach out about availability on other Sage products. Does multi-entity change the mix? The logic is identical per entity, but the mix can differ a lot between subsidiaries: one entity might be all-connector ecommerce while another is AP-heavy wholesale. The most useful read is per-entity, because a manual-JE spike concentrated in one subsidiary points straight at that team’s process. The card reports at the dashboard scope and drills per entity. Can recurring journals distort the manual slice? They can if they were created as manual templates. The card classifies by the actual posting source rather than the template type, which keeps recurring rent or depreciation out of the manual-adjustment slice where it belongs. If your recurring journals look like they are inflating the manual share, check how the templates were set up. How fresh is the distribution? It reflects the GL at typical Intacct refresh cadence (around 5 to 15 minutes). Because the mix is a trailing-30-day view, intraday changes barely move it; the meaningful signal is the period-over-period shift in any slice, which the trailing comparison surfaces. Implementation Partner role on this metric? The Partner usually owns the integration mappings and the automation that determines how much posts automatically versus by hand. When the manual slice rises, the Partner is often the right person to extend a mapping or fix a feed so the work moves back to automation. Align the source-module labelling in the Vortex IQ field map so the connector slices match your integration architecture.

---

​

Tracked live in Vortex IQ Nerve Centre

Journals by Source Module 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.