Open (Not Posted) Journal Entries, Microsoft Dynamics 365

Open (Not Posted) Journal Entries: journal lines stuck in NotPosted, ReadyToPost or InProcess states. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Ecommerce Platform

The count of journal lines sitting unposted in the in-process queue. A growing queue delays close and can hide errors.

At a glance

The live count of journal lines that have been created but not yet posted to the General Ledger: anything in NotPosted, ReadyToPost, or InProcess state. These are entries the system or a user has staged but not committed. A small steady number is normal work-in-progress; a growing number is a backlog that pushes out period close and can quietly conceal balancing errors that only surface at posting.

What it counts	Journal lines not yet posted to the GL. In Finance & Operations these are LedgerJournalTrans lines whose posting status is NotPosted / ReadyToPost / InProcess (still inside an open LedgerJournalTable batch). In Business Central these are lines sitting in a General Journal / Sales Journal / Purchase Journal batch that have not been posted yet.
What it excludes	Posted journals (they are on Journals by Source Module) and journals rejected at posting (on Journal Imbalances (rejected at posting)). This card is strictly the staged-but-not-committed queue.
Unit	Count of unposted journal lines (a live KPI).
Currency	The count is currency-agnostic. An amount view consolidates staged value in the Reporting Currency.
Multi-Company	Aggregated across selected legal entities. Filter to one entity to find which entity owns the backlog.
Time window	RT (real-time live count)
Alert trigger	>50
Roles	owner, finance

Calculation

Calculated automatically from your Microsoft Dynamics 365 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 UK multi-brand retailer on Finance & Operations, two legal entities, snapshot 12 Jun 26 (live count, mid-morning). Close for the previous period is due in three working days.

Posting status	UK Retail Ltd	UK Wholesale Ltd	Total
NotPosted	41	18	59
ReadyToPost	22	9	31
InProcess	3	1	4
Total unposted	66	28	94

The live count is 94, well over the 50 alert line, so the card is amber and the Nerve Centre has flagged it.

Four things to notice:

1. 94 against a threshold of 50 means the close queue is backing up. With three days to close, this is the early-warning signal you want. Clearing it now is far cheaper than discovering it on close day.
2. UK Retail Ltd owns 66 of the 94. Drill into that entity first. Concentration in one entity usually points at one stuck batch or one person’s worklist, not a systemic problem.
3. The 4 InProcess lines deserve a look. InProcess can mean a posting that started and stalled (a batch job that died part-way, or a workflow waiting on approval). Those are the ones that silently hold up close.
4. A flat queue is fine, a rising queue is not. A steady 30 to 40 lines is healthy work-in-progress. The danger is the trendline climbing day on day, which means entries are arriving faster than they clear.

Sibling cards merchants should reference together

Open (Not Posted) Journal Entries is a leading indicator for close strain. Pair it with these to find what is stuck and why.

Card	Why pair
Journals by Source Module	The posted counterpart. If posted volume stalls while this queue grows, postings are not clearing.
Journal Imbalances (rejected at posting)	The next stage. Unposted lines that fail validation land there. A growing queue often precedes a spike in rejections.
Manual Journals as % of Total	Manual entries are the most likely to sit unposted. A high manual share explains a stubborn queue.
Ledger Period Close Status	You cannot close a period cleanly with unposted lines for it. This card is the work standing between you and close.
Batch Job Error Queue (24h)	InProcess lines often trace to a failed posting batch. Check the error queue when InProcess lines linger.

Reconciling against Microsoft Dynamics 365

Where to look in Business Central / Finance & Operations:

Finance & Operations: General ledger > Journal entries > General journals (filter to Not posted; the line count is this card) Finance & Operations: General ledger > Journal entries > General journals > Lines (status column shows NotPosted / InProcess) Business Central: Finance > Journals > General Journals (open batches with unposted lines) Business Central: Sales / Purchase Journals (batch lines awaiting posting)

To tie out: open the relevant journal list, filter to the not-posted status, and count the lines across the same legal entities. The card matches the live view subject to the OData / DMF sync window.

Why our number may legitimately differ:

Reason	Direction	Why
Status definition	Either	The card counts NotPosted, ReadyToPost, and InProcess together. A native filter set to only one of those will read lower.
Line vs voucher count	Card higher	The card counts lines. A native journal-header count reads lower for multi-line batches.
In-flight batch posting	Either	If a posting batch is running at the moment you compare, InProcess lines may clear between the native refresh and the card refresh.
Legal-entity scope	Either	The card aggregates selected entities. A native list scoped to one entity will not match a consolidated view.
OData / DMF sync lag	Card up to 15 min behind	A just-created line may appear in F&O / BC before the card refreshes, or a just-posted line may still show on the card briefly.

This card is GL-internal with no commerce-side equivalent. The indirect link is operational: when commerce order volume surges, integration-created journals can pile into this queue faster than the close process drains them, so a spike here can be the downstream symptom of a Shopify or BigCommerce volume surge.

Known limitations / merchant FAQs

What is the difference between NotPosted, ReadyToPost, and InProcess? NotPosted means the line is drafted but no one has tried to post it. ReadyToPost means it has passed validation and is queued. InProcess means a posting attempt is underway, or stalled part-way. All three count here because all three are uncommitted to the GL.

Why is this a hero card with a real-time window? Because it is a live operational queue that directly gates period close. Unlike a trend metric, the number matters right now, today, which is why it is tracked in real time and surfaced as a hero KPI for Finance.

Is a non-zero number a problem? No. A steady small queue is normal work-in-progress. The signal is the trend and the threshold: a queue climbing day on day, or sitting above 50, is the warning.

Why can InProcess lines get stuck? A posting batch that errored mid-run, a workflow step waiting on an approver, or a record lock can leave a line in InProcess. These are the most important ones to clear because they silently block close. Cross-check Batch Job Error Queue (24h).

Does a large queue mean my numbers are wrong? Not necessarily, but it means they are incomplete. Unposted entries are not yet in the GL, so revenue, AR, and balances reported elsewhere do not include them. Clear the queue before trusting period-end figures.

How do I clear it fastest? Filter the native journal list to the not-posted status, sort by the entity with the biggest backlog, validate, and post in batches. Fix any line that fails validation before it becomes a rejection on Journal Imbalances (rejected at posting).

Same on Business Central and Finance & Operations? Yes. The status terminology and screens differ slightly but the card normalises both into a single unposted-line count.

---

Tracked live in Vortex IQ Nerve Centre

Open (Not Posted) Journal Entries is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 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.