CompareComparison
Empty Spaces vs Ledge: What approvers sign, what posts on its own, and which to choose
19 min read
Empty Spaces vs Ledge at a glance (November 8, 2026)
| What's compared | Ledge | Empty Spaces |
|---|---|---|
| What it is | “The close, prepared”: Accounting Agents prepare “reconciliations, working papers, and JEs” for your team to review and approve | AI agents for month-end close, reconciliation and FP&A |
| Who prepares | Accounting Agents per close task, which your team can build in its no-code Agent Studio | The Close Agent, task by task through the month |
| What the approver approves | A journal entry card, with single and bulk “Approve & post” | The exact lines of each entry, and each approval covers one write |
| Posting setups | NetSuite routing, “approve in Ledge and auto-post,” or dual approval in Ledge and NetSuite | One: a named approver approves before anything posts |
| Reviewer on each task | Optional, with segregation of duties as a setting | Required, separate from the preparer |
| Entries post to | NetSuite, the only ERP Ledge's live pages and docs describe posting to | Six ERPs, plus read access to Odoo |
| Where it runs | Ledge's cloud, on AWS US East-1 per its Slack Marketplace listing | SaaS, your own cloud, a private cloud, or on-premises |
| Price | Quote only, as a platform fee with no per-seat fees | No public price |
Key takeaways
- Ledge and our Close Agent both use AI to prepare the close and hand the work to people to approve. They differ on what approvers sign, what posts without one, which ERPs each posts to, and where each runs.
- Ledge is the deeper NetSuite product: a certified SuiteApp with Excel workpapers and no per-seat fees. Our Close Agent posts approved entries to six ERPs and runs as SaaS, in your own cloud, in a private cloud, or on-premises.
- Ledge's pages describe more than one posting setup, from dual approval to recurring entries posted automatically. Ask Ledge which one your contract and setup use, then test both tools on the same closed month.
Empty Spaces vs Ledge compares two products that both use AI agents to prepare the month-end close, so the choice turns on controls and setup. Knowing exactly what each approver signs, and what can post without one, tells you which control setup can support your audit requirements. This guide covers approvals, posting modes, a worked example, ERP and deployment coverage, price, a demo scorecard, and how to choose.
We make one of the two products compared on this page. We hold ourselves to the same test we ask you to run on Ledge, and every Ledge fact below comes from Ledge's own live pages and docs, read on November 8, 2026, unless another source and date are named. Our agents do the finance work itself (reconciliations, exceptions, entries, variance analysis, reports) and hand it to your team to approve, on top of your existing ERP.
Empty Spaces vs Ledge: What's the difference?
Both prepare close work with AI agents and hand it to people to approve. Ledge is NetSuite-first, vendor-hosted, and offers several posting setups. Our Close Agent posts to six ERPs only after a named approver approves each entry's exact lines, and it can run in your own cloud.
- Exact-line approvalA named person approves the specific lines of one entry, and the approval covers only that version of it
- Posting modeThe setting that decides whether an approved entry posts straight to the ERP, waits for a second approval in the ERP, or follows the ERP's own routing
- Segregation of dutiesThe person who prepares an entry and the person who approves it are different, and the system enforces it
If you're new to the process both tools support, start with What is month-end close?
What's the difference between Ledge and FloQast?
Ledge's comparison page says “Ledge automates what other platforms only organize.” FloQast's pricing page, read November 8, 2026, lists AI agents and journal entry posting in its Close AI package, so compare who prepares each task in a demo. See FloQast alternatives.
What does the approver actually approve in each?
With our Close Agent, a named approver approves the exact lines of each entry: if the payload changes, the approval no longer applies, and the requester can't approve it. In Ledge's docs, the approver clicks “Approve & post” on a journal entry card, and bulk approval is available.
Journal entry controls, in each vendor's words (November 8, 2026)
| Control | Ledge (docs, journal entry and close automation pages) | Empty Spaces (Close Agent) |
|---|---|---|
| What the approver sees | A card with “Debit and credit lines with account, amount, and memo,” then a “Confirm final approval” dialog showing “total items, approved by, and approved on” | Each entry's lines, preparer, and source task, with Approve or Send back |
| The approval action | “Approve & post,” after which “Ledge posts the entry directly to ERP” | Approval of the exact lines; the entry posts once, after approval |
| Bulk approval | “Select entries with the checkboxes” and bulk “Approve & post” | “Each approval covers one write” |
| Edits | “At any point, you can edit journal entries manually or by asking the agent.” Whether an edit clears an earlier approval is not listed on Ledge's live pages as of November 8, 2026; ask Ledge | “If the payload changes, the approval no longer applies.” |
| Who can approve | “Approval workflows can require specific individuals or roles before an entry moves to the NetSuite posting stage” | Named approvers by amount tier; the requester can never approve their own entry |
| After posting | “Depending on your organization's policies,” posted entries can be edited, deleted, or reversed from Ledge | Each entry keeps who prepared it, who approved it, why, and its full change history in an append-only log |
| Reasoning | “Review the full log of reasoning, steps, and decisions behind each prepared task” | Every step is visible, including each ERP query with its parameters and results |
Both keep a full audit trail: Ledge's SOX FAQ lists “full audit trail (every step logged)” and dual authorization. The open question is binding, so ask Ledge to show that the version an approver saw is the version that posted. For the entries most teams post each month, see month-end journal entries.
Does Ledge post journal entries automatically?
It depends on the setup, and Ledge's pages describe more than one. Its journal entry FAQ calls dual approval “a hard architectural constraint,” its security page lets you choose a posting model, and two of its articles say recurring entries are “detected and posted automatically.”
How Ledge describes posting, by page (read November 8, 2026)
| Ledge page | Date shown | What it says |
|---|---|---|
| Journal entries solution page, FAQ | None | “No. Ledge drafts journal entries and presents them for human review.” Posting “requires dual approval,” in Ledge and then in NetSuite. “Nothing posts to your ERP without explicit human authorization at both stages. This is a hard architectural constraint, not an optional setting.” |
| Security page, FAQ | None | “You choose the approval model: use your existing NetSuite approval routing, approve in Ledge and auto-post, or require dual approval in both systems. All other interactions are read-only.” |
| Docs: Require NetSuite Authentication for Posting | None | A “Posting mode” setting: “Ledge can require users to be authenticated in NetSuite before allowing any posting activity.” |
| Docs: NetSuite overview | None | “All posting operations require explicit user approval.” |
| Article: Automating the financial close | Published October 9, 2025; updated May 10, 2026 | “With Ledge, recurring journal entries are detected and posted automatically throughout the month, keeping the GL current. Exception entries are drafted by AI agents with full transaction context and supporting documentation attached for review and approval.” |
| Article: How to speed up your NetSuite close with Ledge | Published October 6, 2025; updated May 10, 2026 | “Recurring journal entries are detected and posted daily with full context and audit traceability” |
In the security page's wording, “approve in Ledge and auto-post” reads as one approval in Ledge, then automatic posting to NetSuite with no second approval there. Pages written at different times can describe different releases, so treat Ledge's answer and your contract as the source of truth. Ask Ledge which mode your setup uses, with these three questions in writing:
- Which posting mode will our contract and setup use: NetSuite routing, approve in Ledge and auto-post, or dual approval?
- Can a recurring entry be generated and posted each month without an individual approval event?
- Who can change the posting mode, and does the change appear in the audit trail?
Can AI post journal entries without approval?
It can if the software allows it, so the control has to sit in the system. With our Close Agent, nothing posts until a named approver approves the exact lines, recurring entries included. See AI in month-end close.
How does each handle a recurring depreciation entry? A worked example
Both can prepare a monthly depreciation entry from your fixed asset register and post it to NetSuite. The difference is whether a recurring entry waits for a named approver every month, which matters most in the month the register changes.
Example
Your company runs NetSuite, and September's depreciation entry was $7,100. On October 1, 2026, a $28,800 network upgrade goes into service with a 36-month life, adding $28,800 ÷ 36 = $800 a month. Your policy uses two review triggers: a recurring entry that moves more than 5% from the prior month gets a second reviewer, and entries above $10,000 go to the controller. All figures are illustrative, straight-line, with no salvage value, and depreciation starts in the month an asset is placed in service.
Fixed asset register, October 2026 ($)
| Asset | Cost | Life (months) | Monthly charge |
|---|---|---|---|
| Servers | 186,000 | 60 | 3,100 |
| Laptops | 43,200 | 36 | 1,200 |
| Office furniture | 58,800 | 84 | 700 |
| Leasehold improvements | 252,000 | 120 (lease term) | 2,100 |
| Network upgrade, new October 1 | 28,800 | 36 | 800 |
| Total | 568,800 | 7,900 |
Depreciation entry, October 31, 2026 ($)
| Account | Debit | Credit |
|---|---|---|
| Depreciation expense | 5,800 | |
| Amortization expense, leasehold improvements | 2,100 | |
| Accumulated depreciation, computer equipment | 5,100 | |
| Accumulated depreciation, furniture and fixtures | 700 | |
| Accumulated amortization, leasehold improvements | 2,100 | |
| Total | 7,900 | 7,900 |
Computer equipment carries servers, laptops, and the network upgrade: $3,100 + $1,200 + $800 = $5,100. October's entry is $7,900 − $7,100 = $800 above September's, an 11.3% move, so it crosses the 5% trigger and gets a second reviewer. At $7,900, it stays under the $10,000 controller trigger.
The same entry in each tool
| Step | Ledge (per its pages) | Empty Spaces (Close Agent) |
|---|---|---|
| Prepare | Agents “Carry forward prior-period entry structure, mappings, and logic,” and an Agent Studio playbook “runs autonomously on schedule every period going forward” | Prepares the five-line entry and a workpaper from the register, including the new asset |
| Spot the change | Plain-language Agent Guidelines, such as “flag anything over $500 variance for review,” cover reconciliation, flux, and cash application; ask whether they cover recurring entries | Every entry waits for a named approver, so the $800 change reaches a person before it posts |
| Review | Depends on the posting mode: automatic under the recurring-entry articles, or two approvals under dual approval | A named approver approves the exact five lines; under your policy, the 5% move also gets a second reviewer |
| Change after approval | If someone changes the network upgrade's life to 48 months, its line becomes $600 and the entry $7,700; ask Ledge whether that clears the approval | The same edit voids the approval, and the $7,700 entry needs a new one |
| Post | After “Approve & post,” or through your NetSuite routing | Posts once to NetSuite after approval |
| Closed period | If October is locked in NetSuite, the post fails; “Fix with agent” reads the ERP error, including a “locked period,” and drafts a corrected entry | October can't lock until every task is signed off; once locked, an entry dated October is blocked |
Auto-posting saves 12 approvals a year per recurring entry and keeps the ledger current mid-month. Per-entry approval costs those 12 approvals, but a register change like October's $800 is seen before it posts. If any tool carried forward September's $7,100, depreciation would be understated by $800 a month, or $2,400 by December 31. For how depreciation fits with other month-end adjustments, see adjusting entries.
Segregation of duties, reviewers, and closed periods: Default or optional?
In Ledge's approval workflows, only a preparer step is required, and reviewer steps and segregation of duties are options you add. With our Close Agent, every task needs a named reviewer separate from the preparer, and the month can't lock until every task is signed off.
| Control | Ledge (Approval Workflows docs and industry pages) | Empty Spaces (Close Agent) |
|---|---|---|
| Reviewer on each task | “At minimum, a workflow includes a preparer step. Optionally, you can add one or more reviewer steps, as well as enforce segregation of duties.” | Every task needs a named reviewer |
| Skipping review | “If no reviewer steps are added, tasks complete directly after the last preparer signs off (skip review).” | Not available: the month can't lock until every task is signed off |
| Preparer vs reviewer | Its SaaS industry page says “Reviews, approvals, and segregation of duties are enforced as work happens.” | The reviewer is separate from the preparer, and the requester can't approve their own entry |
| Closed periods | NetSuite's own period lock applies, and failed posts go to “Fix with agent” | Closed periods stay locked, and closed months block ERP writes |
Ledge's flexibility suits a team that sets its controls task by task. Its docs also note that changing a workflow “does not automatically apply to tasks or templates created before the change,” so ask Ledge to export the current settings for every task your auditors will test.
Which ERPs does each one post approved entries to?
Ledge's live pages document journal posting for NetSuite, through its certified SuiteApp, and describe SAP S/4HANA, Dynamics 365, and QuickBooks as data sources. Our Close Agent reads from and posts approved entries to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, and QuickBooks, and reads from Odoo.
ERP coverage, from Ledge's live pages and docs and our own (November 8, 2026)
| ERP | Ledge | Empty Spaces (Close Agent) |
|---|---|---|
| NetSuite | “Ledge's NetSuite integration is its deepest ERP integration,” with “Write: JE posting only (human-approved)”; its docs also list writing payments and deposits | Reads and posts approved entries |
| Sage Intacct | Its setup guide gives Ledge's integration role “List, View, Add, Edit, Delete, Reclass, Reverse” access to journal entries; posting not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Not on our list |
| QuickBooks | “QuickBooks is treated as the business process data source”; posting not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Reads and posts approved entries |
| SAP S/4HANA | “SAP S/4HANA is treated as the ERP data source that feeds close workflows” | Reads and posts approved entries |
| Microsoft Dynamics 365 | Described as “the ERP data source that feeds close workflows” | Reads and posts approved entries |
| Xero | Has an integration page; posting not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Not on our list |
| Oracle | Not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Reads and posts approved entries |
| Business Central | Not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Reads and posts approved entries |
| Odoo | Not listed on Ledge's live pages as of November 8, 2026; ask Ledge | Reads only |
Ledge's SAP and Dynamics pages answer “Is anything posted automatically?” with “No. All work is reviewed and approved by your team before posting.” One Gemini answer tested on November 8, 2026, said Ledge posts to SAP S/4HANA and Dynamics 365, which its live pages don't show. If you run entities on SAP, or split between SAP and NetSuite, ask Ledge to post a test journal into your sandbox. The Close Agent posts approved entries to both, under one approval model.
Is Ledge worth it on QuickBooks Online?
A Ledge FAQ article says “A simple single-entity environment may not require this level of automation.” Its QuickBooks page describes a data source for workpapers and reconciliations. If you want approved entries posted back to QuickBooks, ask Ledge to show it; the Close Agent posts there today.
Where does each run, and whose AI models does it use?
Ledge runs as a vendor-hosted service: its Slack Marketplace listing says data sits in AWS US East-1 and inference uses Anthropic models under Ledge-controlled accounts. Our agents run as SaaS, in your own cloud (BYOC), in a private cloud, or on-premises, with the model you choose and your own keys.
Deployment and models (November 8, 2026)
| What's compared | Ledge (security page, AI cost article, and Slack Marketplace listing) | Empty Spaces |
|---|---|---|
| Deployment | “Ledge operates on cloud infrastructure with encryption at rest and in transit,” and the Slack listing says data is “hosted in the cloud on AWS US East-1 data center, mainly on S3 and RDS”; customer-cloud and on-premises options not listed on Ledge's live pages as of November 8, 2026; ask Ledge | SaaS, your own cloud (BYOC), a private cloud, or on-premises |
| Isolation | “Data isolation between customers” | Single-tenant |
| Model provider | Anthropic, with “Requests are made under Ledge-controlled accounts/projects” (Slack listing) | You choose the model and can bring your own keys |
| AI cost | Inside the platform fee: Ledge “takes responsibility for managing that complexity” | Per-group AI spend caps |
| Data use | “Your data is never used to train AI models”; the Slack listing adds “LLM providers might retain data up to 30 days” | Credentials are encrypted and never shown to models |
| Certifications | SOC 1, SOC 2, ISO 42001, and GDPR badges | SOC 2 Type I and Type II |
Is Ledge SOC 2?
Yes. Its pricing FAQ says “Ledge is SOC 1 and SOC 2 certified.” A SOC 1 report matters if your auditors rely on a vendor's controls over financial reporting, so ask Ledge for the report period.
With your own keys, model calls run under your account, so usage, retention terms, and spend sit with you. With vendor keys, as in Ledge's setup, the vendor holds that relationship and bundles the cost, which keeps the bill predictable.
Where Ledge is stronger
Ledge leads on NetSuite: it's a certified SuiteApp whose agents can work NetSuite screens the API doesn't reach. It also builds auditor-friendly Excel workpapers and can require approval in both Ledge and NetSuite.
- NetSuite depth“continuous bi-directional sync through NetSuite's official SuiteApp framework,” auto-detection of new accounts and subsidiaries, and agents that “automate repetitive NetSuite UI tasks like running reports, downloading attachments, and handling workflows that are not fully available through APIs.”
- Workpapers auditors can use“fully editable Excel workpapers with live formulas,” versioned saves, external reviewers as read-only viewers, and the working paper attached to the NetSuite entry.
- Agent StudioA no-code builder where you upload an existing working paper or start from scratch, and the engine “presents a transparent, step-by-step plan” before doing any work.
- Repeatable runs“Every Accounting Agent runs bespoke, deterministic code, written once and run reliably every period,” and its home page promises “Same inputs, same output, every period.”
- ReachIt “connects to 11,000+ banks worldwide” and has “150+ native integrations.”
Ledge says customers “typically move from 6-15 day closes to 3-5 day closes.” That's a vendor claim, so ask for a reference customer close to your size and ERP.
Is Ledge legit, and who's behind it?
Yes. Its about page names Tal Kirschenbaum as CEO and Asaf Kotzer as CTO, and its security page lists offices in New York and Tel Aviv. TechCrunch reported on February 16, 2023, that Ledge had raised $9 million, and Calcalist described it the same day as a seed round for automated payments, where Ledge started before the close.
What do accountants on Reddit say about Ledge?
Not much yet. A buyer's post in r/Accounting's “Ledge vs Floqast” thread, read November 8, 2026, said “Ledge seems to be heavily leaned into agentic AI” and “Ledge is a newer software.” A Perplexity summary of Reddit threads the same day called sentiment “still limited but broadly favorable,” with doubts about newness and a small review base; G2 listed 6 reviews.
How much does each cost?
Neither publishes a price. Ledge sells Track, Execute, and Enterprise plans as one platform fee based on the workflows you automate, with unlimited seats and no implementation fee. We publish no price, so compare quotes for the same entities, ERPs, and workflows.
| What's compared | Ledge (pricing page) | Empty Spaces |
|---|---|---|
| Public price | None: “Request pricing” | None |
| Pricing basis | “Workflow-based: pricing reflects the complexity and number of close workflows you automate,” with “no per-seat fees” | Not published |
| Plans | Track (“1 ERP + 1 bank integrations”), Execute (“Agentic close execution: AI-generated WPs and JEs”), and Enterprise (API and webhooks, “Upcoming: SOX compliance management and automation”) | Not published |
| What to ask | Which plan includes agents and posting, how many workflows the fee covers, and which posting mode the contract allows | What the quote covers for your entities, ERPs, and deployment choice |
One Gemini answer tested on November 8, 2026, gave Ledge a price range with no source, so anchor on your own quote. On a Track plan, check that your ERP and main bank are the two integrations you need.
How long does each take to go live?
Ledge advertises “Live in 1 day,” meaning checklist import and ERP connection, and its implementation guide recommends a parallel first close and a phased rollout. Our Close Agent works on top of your ERP without replacing it, can start read-only, and switches posting on when you're ready.
| Stage | Ledge (pricing FAQ and implementation guide, updated July 1, 2026) | Empty Spaces (Close Agent) |
|---|---|---|
| Connect | “Usually within a day. You can import your existing checklist and connect to your ERP in just a few clicks.” | Connects to the ERP you keep, read-only if you choose |
| First close | “Ledge generally recommends running in parallel during the first month-end close” | Runs read-only beside your current process for comparison |
| Expand | Phase 2 adds reconciliations, flux, and agents; phase 3 makes Ledge the primary system | Pick two or three task areas, with named reviewers |
| Posting | Set by the posting mode you choose | Switched on later, for the areas you pick, with named approvers |
Neither replaces your ERP: Ledge's NetSuite FAQ answers “Does Ledge replace NetSuite?” with “No.”
How to test both on your own data
Give both the same closed month and the same 10 tests, starting with the controls: edit an approved entry, have the preparer approve, bulk-approve, post into a closed period, and post to each ERP you run. Then check the work itself.
Demo scorecard: Ledge vs Empty Spaces
| # | Test | What you do | What passes | Ledge | Empty Spaces |
|---|---|---|---|---|---|
| 1 | Posting mode | Ask to see the posting setting in your workspace and who can change it | A written answer, and a log entry when it changes | ||
| 2 | Recurring entry | Add the October network upgrade from the example above | The entry shows $7,900, flags the $800 change, and waits for approval | ||
| 3 | Change after approval | Change the upgrade's life to 48 months after approval | The $7,700 entry needs approval again | ||
| 4 | Self-approval | Have the preparer try to approve their own entry | Blocked | ||
| 5 | Bulk approval | Approve 10 entries at once | Each posted entry shows who approved which lines | ||
| 6 | Skipped review | Try to complete a task with no reviewer | Blocked, or flagged under your policy | ||
| 7 | Closed period | Lock October, then post an entry dated October | Blocked | ||
| 8 | Each ERP | Post one test journal to every ERP you run | Only the approved lines post, once, and the ERP returns a journal ID | ||
| 9 | Missing data | Remove one bank statement before the run | The tool asks for it instead of guessing | ||
| 10 | Trace and export | Export the trail for one posted entry | Preparer, approver, reasoning steps, source documents, and change history |
Record pass or fail for each test, then measure the work: reconciliations prepared, corrections needed, and reviewer hours.
Which should a controller choose?
Choose Ledge if you run NetSuite, want Excel-native workpapers and no per-seat fees, and are comfortable confirming its posting mode. Choose our Close Agent if you post to SAP S/4HANA, Dynamics 365, or several ERPs, want exact-line approval and period locks by default, or need your own cloud and keys.
| Signal | Points to |
|---|---|
| You run NetSuite and want SuiteApp depth, including agents that work NetSuite screens | Ledge |
| Your auditors want Excel workpapers with live formulas and read-only access | Ledge |
| You want approval in the close tool and again in NetSuite | Ledge (dual approval mode) |
| You post to SAP S/4HANA, Oracle, Dynamics 365, or Business Central, or several ERPs at once | Empty Spaces |
| Your auditors want a named approver on the exact lines of every entry, recurring ones included | Empty Spaces |
| You want reviewers and segregation of duties on by default, not per task | Empty Spaces |
| Security requires your own cloud, a private cloud, on-premises, or your own model keys | Empty Spaces |
For a 300-person company on NetSuite, both fit the ERP: weigh Ledge's NetSuite depth against default controls, and let the scorecard decide. For other agent tools, see Best AI agents for finance teams. For every close tool side by side, see Best month-end close software.
How we approach it
Our Close Agent prepares the reconciliations, entries, and workpapers across your close checklist, recurring entries like depreciation included. A named approver approves the exact lines of each entry before it posts to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, or QuickBooks, and it runs as SaaS, in your own cloud, in a private cloud, or on-premises. Explore the Close Agent on a closed month of your own data.
Share this article