We Audited DualEntry's Own Docs. Here Are the 28 Things It Says It Can't Do.
Most vendor documentation is written to close sales. It describes what the platform does. It goes quiet about what the platform does not do. The buyer discovers those gaps during evaluation, or worse, after signing. The pattern is so consistent across the enterprise software category that anyone evaluating an accounting platform has learned to read the marketing skeptically and assume the silent gaps are the ones that will hurt.
DualEntry is different. Their documentation is unusually candid about product gaps. The recurring phrase across their FAQ pages is "not part of the documented product today." Read carefully, the docs functionally publish their own product-gap list, in their own words, for anyone willing to sit and read them. That is not the standard behaviour in this category, and it deserves recognition. It also creates an opportunity for the honest audit that this post attempts.
I read the DualEntry documentation systematically over several sessions, catalogued every stated gap or limitation, and organized them here into ten thematic categories. Twenty-eight distinct capabilities are documented as either not supported, not addressed, or explicitly out of scope. Each item below is sourced to DualEntry's own materials. None of this is speculation. None of this is competitive positioning. This is what the vendor itself says the product does not do.
The framing matters. This is not a hit piece. DualEntry is a serious platform built by a serious team with $90M in Series A funding from Lightspeed, Khosla, and GV, and a documented 4.9-star G2 rating across 120+ reviews. Their product is genuinely differentiated for the mid-market ERP category, and their transparency about gaps is itself a competitive strength that deserves respect. But their target customer, a company outgrowing QuickBooks Online with $10M to $1B in revenue, needs to know what the platform does and does not do before signing. This post exists to make that decision easier.
Everything below is verified against DualEntry's documentation as of 14 September 2026. The product ships fast, and any specific gap here may close in the coming months. Where a workaround exists in the current product, I name it. Where the gap is genuinely material for a specific customer profile, I say so. The goal is a fair, useful reference that respects both the vendor's candor and the buyer's need to make an informed choice.
💡 Key Takeaways
DualEntry publishes 28 documented gaps or limitations in its own materials, an unusual level of transparency for enterprise ERP
Seven of the 28 gaps affect specific verticals that DualEntry is not built for: project accounting, nonprofit fund accounting, government contracting
The absence of automated three-way match is a real AP control gap that requires compensating controls in workflow design
MACRS depreciation is not supported, which affects US tax book handling and typically requires external tax preparer workflow
DualEntry does not originate ACH or file taxes electronically, functioning as a system of record with external partners for those functions
Consolidation does not address ownership percentages or non-controlling interest, a real functional gap versus NetSuite and Sage Intacct
The "Budgeting and Forecasting" page does not include forecasting, which is documented candidly in the product materials
These gaps do not disqualify DualEntry for its target customer profile, but each one deserves consideration during evaluation
Verified 14 September 2026: DualEntry ships rapidly, and specific gaps may close in future releases
What "Documented Gap" Means in This Post
Before the list itself, a note on how I am defining terms. A gap in this post means one of three things:
The documentation explicitly states the capability is not supported. For example, the FAQ text stating that MACRS is not among the four supported depreciation methods.
The documentation stops short of addressing a capability that a buyer in the target market would reasonably expect. For example, the consolidation section not addressing ownership percentages or non-controlling interest.
The documentation includes a capability in a feature title but the underlying content reveals the feature is not actually delivered. For example, the "Budgeting and Forecasting" page not documenting forecasting functionality.
Each gap is sourced to a specific area of the docs. Where DualEntry documents a workaround using existing features (such as using classifications instead of native project accounting), I describe the workaround honestly. Where the workaround materially changes the customer's operational reality, I note that.
I have deliberately excluded gaps that are common across most cloud accounting platforms and would not surprise a knowledgeable buyer. The list here is DualEntry-specific and material to the evaluation.
Category 1: Specialized Vertical Accounting
DualEntry is built for general-purpose mid-market accounting on a modern architecture. Seven documented gaps affect businesses whose accounting requirements are shaped by a specific vertical rather than general purpose.
Gap 1: No project accounting module
DualEntry supports projects as classifications only, meaning you can tag a transaction with a project code and report by project, but the platform does not include a native project accounting module with project-level margin analysis, WIP tracking, project revenue recognition, or project-specific budgets. This is a material gap for any professional services firm, construction company, or engineering consultancy where project profitability is the primary financial lens.
Gap 2: No per-project budgets, project billing, or WIP tracking
Following from Gap 1, the absence of a project accounting module means the specific workflows that make project-based businesses work are absent. Per-project budgets, project billing with time and materials, and work-in-progress tracking on unbilled work are all documented as not supported. A professional services firm running an operating model on time and materials will find this a hard stop.
Gap 3: No nonprofit fund accounting
Fund accounting is the distinct accounting framework used by nonprofits, government entities, and other purpose-restricted organizations to track restricted funds, temporarily restricted funds, and unrestricted funds separately. DualEntry does not support fund accounting natively. The recommended workaround uses classifications, which allows reporting by fund but does not enforce the separation of net asset classes that GAAP requires for nonprofit financial statements.
Gap 4: No net asset release tracking or donor restriction handling
Following from Gap 3, the specific nonprofit workflows of tracking donor restrictions, releasing net assets as restrictions are satisfied, and reporting restricted versus unrestricted net assets are not supported. A nonprofit organization needing to produce GAAP-compliant financial statements will find this a hard stop.
Gap 5: No named government contracting vehicles
Government contractors work under specific contract types with distinct accounting requirements. Cost-plus-fixed-fee (CPFF), time-and-materials (T&M), Other Transaction Authority (OTA), and Small Business Innovation Research (SBIR) contracts each require specific tracking mechanisms. DualEntry does not address these by name in the documentation, meaning any government contractor evaluating the platform would need to construct their own contract tracking framework rather than using a native module.
Gap 6: No indirect cost pools
Indirect cost pool accounting, the standard framework for allocating overhead, fringe, general and administrative expenses, and shared services across cost objectives, is not a documented capability. This affects both government contractors (where DCAA-compliant indirect cost pool accounting is often contractually required) and professional services firms doing sophisticated project-level margin analysis.
Gap 7: No indirect rates
The DualEntry documentation states that indirect rates are "not in scope today." This is unusually candid language and functionally confirms that the entire cost allocation framework built on indirect rates, whether for government contract billing or internal management reporting, is not supported. A business whose financial model depends on maintaining and applying indirect rate structures will need to run that framework outside DualEntry.
What this category means for buyers. If your business is a professional services firm, nonprofit, government contractor, or anything else where vertical-specific accounting workflows drive the financial model, DualEntry is likely the wrong platform today regardless of its other strengths. NetSuite, Sage Intacct, and vertical-specific competitors (like Deltek for government contracting, or Sage Intacct's nonprofit edition) are built for these workflows. This is the largest concentration of gaps in the list.
Category 2: AP Controls and Procurement
Gap 8: No native timekeeping or timesheets
DualEntry does not include native timekeeping or timesheet functionality. Time tracking must flow through payroll or HR integrations (Gusto, Rippling, and similar). This is a workflow gap rather than an accounting gap, but it materially affects any business where employee time is billed to customers or allocated to projects. Combined with the absence of project accounting (Gap 1), professional services firms face a compounding limitation.
Gap 9: No automated three-way match
This gap is stated twice in the DualEntry documentation, once in the purchase order module and once in the AP module. The docs state: "Comparing the vendor's invoice against the PO and the receipt is a review you perform, not a control DualEntry enforces." There is no automated three-way match, no match exception queue, and no tolerance threshold that blocks approval when the vendor's invoice differs from the PO. The compensating control described in the docs is that "the bill's approval workflow is where that variance should be caught."
This is a genuine control gap for businesses that rely on three-way matching as a primary AP control. It does not mean AP controls are impossible in DualEntry, but it does mean the control has to live in the approval workflow design and human reviewer discipline rather than in automated software enforcement. For businesses with SOX obligations or robust internal control requirements, this is worth thinking through carefully during evaluation.
What this category means for buyers. The absence of automated three-way match is not disqualifying, but it does shift AP control burden from software to workflow. Any business evaluating DualEntry with material AP volume should discuss the intended control design with DualEntry sales explicitly and document the compensating controls before adoption.
Category 3: Fixed Assets and Tax Depreciation
Gap 10: No MACRS depreciation method
DualEntry supports four depreciation methods: straight-line, declining balance, sum-of-years-digits, and units-of-production. The Modified Accelerated Cost Recovery System (MACRS), the standard US tax depreciation method, is not among them. For any US-based business that maintains separate GAAP and tax books for fixed assets (which is most businesses with material fixed assets), this means the tax depreciation calculation lives outside DualEntry, typically in the tax preparer's fixed asset workpaper or a specialized tool.
This is not a hard stop, but it is a workflow reality worth planning for. Multi-book accounting for GAAP versus tax basis is a documented capability in DualEntry, but the tax book depreciation calculation itself requires external computation and posting.
Gap 11: No dedicated impairment record type
Fixed asset impairment, the accounting recognition that an asset's carrying value exceeds its recoverable amount, is typically handled through a dedicated impairment transaction that documents the impairment amount, the impairment event, and the impacted asset. DualEntry does not have a dedicated impairment record type. The documented workaround uses the Asset Revaluation function to write down the asset's carrying value.
This works accounting-wise but affects the audit trail. An auditor reviewing impairment activity will see a revaluation entry rather than an impairment entry, which requires supplemental documentation to establish that the transaction was in fact an impairment recognition. For businesses with periodic impairment activity (real estate, capital-intensive manufacturing), this workflow adjustment is worth planning for.
What this category means for buyers. DualEntry works well as a GAAP fixed asset system for straightforward asset portfolios but requires external workflow for MACRS tax depreciation and careful documentation for impairment activity. Businesses with sophisticated fixed asset requirements should assess these gaps against their specific portfolio.
Category 4: Payment Rails and Tax Filing
Gap 12: No NACHA or ACH file generation
DualEntry is not a payment rail. The documentation is explicit: "Banking connections are read-only. DualEntry does not originate ACH, wire payments, or account changes." The platform records payments that you initiate at your bank, but it does not produce NACHA or ACH batch files that you can upload to your bank for execution. Payments must be initiated at the bank directly, whether through the bank's own portal or through an integrated payment platform.
This is a design choice with legitimate reasoning. Payment origination is a regulated activity, and building it into the ERP creates security and compliance surface that DualEntry has chosen to leave to specialized payment providers. But the practical implication is that your AP workflow needs a payment initiation step outside DualEntry, and you need to plan that workflow before adoption.
Gap 13: No electronic tax return filing (US sales tax, VAT, GST)
DualEntry generates tax data (sales tax collected, VAT payable, GST amounts by jurisdiction) but does not electronically file returns directly. The docs state: "DualEntry does not e-file returns directly today; prepare and submit through the country's portal." An Avalara integration exists as an alternative US sales tax engine, but the filing itself happens outside DualEntry.
This affects any business with material sales tax, VAT, or GST filing obligations. The workflow is: DualEntry produces the tax data, you or your tax preparer submits the return through the jurisdiction's portal or through a third-party tax filing service (Avalara, TaxJar for US sales tax; various regional providers for VAT and GST).
Gap 14: No IRS 1099 electronic filing
Similar to Gap 13, DualEntry generates 1099 reports (1099-NEC, 1099-MISC) but does not file with the IRS on your behalf. A Tax1099 integration handles the actual e-filing. The docs also carry a warning worth quoting: "If you void or reverse a payment after generating the 1099 report, re-run the report. DualEntry does not automatically update a previously generated report." This is a workflow discipline point that any AP team using DualEntry for 1099 reporting needs to be aware of.
Gap 15: No 1099-K or credit card payment method exclusions
Payment-method exclusions matter for 1099 reporting because payments made via credit card or third-party network are reportable on 1099-K by the payment processor rather than on 1099-NEC by the payer. Excluding these payments from 1099-NEC totals is a standard 1099 report configuration in most accounting platforms.
The DualEntry documentation does not address payment method exclusions anywhere. This means the platform's 1099 report may include amounts paid via credit card, which would need to be manually adjusted before filing to avoid double-reporting. For any business paying contractors by credit card at material volume (an e-commerce business paying warehousing and fulfillment contractors, for example), this is a real workflow gap.
What this category means for buyers. DualEntry is designed to be a system of record for tax data, not a filing platform. If your business has straightforward tax obligations, this works fine with the recommended integrations (Avalara, Tax1099). If your tax operations are more complex, particularly around 1099-K exclusions or multi-jurisdiction filing, you need to think through the workflow before adoption.
Category 5: Fiscal Calendar and Basis Reporting
Gap 16: No 4-4-5, 4-5-4, 5-4-4, 13-period, or 53rd-week fiscal calendars
DualEntry supports calendar-month fiscal periods. The retail industry's 4-4-5 fiscal calendar (13-week quarters with weeks distributed as 4-4-5), the alternative 4-5-4 and 5-4-4 variants, 13-period fiscal years (used by some manufacturing and airlines industries), and the 53rd-week adjustment used to align 52-week fiscal years to calendar years are not supported.
This affects retail, manufacturing, and other industries where fiscal calendar structure is standardized around merchandising or production cycles rather than calendar months. For these industries, the gap is not a workaround-and-continue situation, it is a hard stop because the entire financial reporting cycle assumes the industry-standard calendar.
Gap 17: No cash-basis versus accrual-basis reporting toggle
Most accounting platforms allow reports to be run on either cash basis (recognizing revenue when cash is received, expenses when cash is paid) or accrual basis (recognizing revenue when earned, expenses when incurred). This dual-basis reporting is particularly useful for small businesses that report on cash basis for tax purposes but on accrual basis for management or investor reporting.
DualEntry's documentation does not describe a cash-basis reporting mode. The platform is accrual-basis native. This is not a gap for businesses that only report on accrual basis (which is most mid-market companies), but for businesses that need to produce both cash-basis and accrual-basis reports, this is a workflow consideration worth raising during evaluation.
What this category means for buyers. Standard calendar-month fiscal years and accrual-basis reporting cover the majority of mid-market businesses, but industries with specialized fiscal calendars (retail, some manufacturing) or businesses needing both cash and accrual reporting should discuss these gaps directly with DualEntry sales.
Category 6: Consolidation Depth
Gap 18: No ownership percentage, NCI, or partial-ownership consolidation
This is a significant gap that deserves specific attention because it affects multi-entity businesses at scale. DualEntry supports consolidation across multiple entities, but the documentation "never addresses ownership percentages, non-controlling interest (NCI), or partial-ownership consolidation." 100% ownership is effectively assumed throughout the consolidation module.
For businesses with wholly-owned subsidiaries, this works fine. For businesses with joint ventures, minority-owned subsidiaries, or complex ownership structures where NCI recognition is required, this is a real gap versus NetSuite and Sage Intacct, both of which handle partial-ownership consolidation natively.
The workaround, where feasible, is to handle NCI calculations outside DualEntry and post consolidation adjustments manually. But at scale this becomes operationally burdensome and error-prone, and any business anticipating growth into complex ownership structures should raise this specifically with DualEntry sales to understand whether it is on the near-term roadmap.
What this category means for buyers. Simple multi-entity structures with 100% ownership are well-served. Complex ownership structures with NCI or minority interests are not. If your business anticipates growth into these structures, ask about the roadmap explicitly.
Category 7: Planning and Forecasting
Gap 19: No forecasting, allocations, driver-based planning, or budget approvals
This gap is unusual enough to require careful phrasing. DualEntry has a page titled "Budgeting and Forecasting." Read the actual documentation and the docs describe budgeting functionality but not forecasting. There is no forecasting engine, no allocations mechanism, no driver-based planning, and no budget approval workflow. The docs describe the current state as budgeting only, with period granularity of monthly only.
This is a candid gap in a place where you might not expect candor. Most platforms that have a "Budgeting and Forecasting" page would deliver at least basic forecasting capabilities. DualEntry has chosen to expose the gap rather than claim capability it does not have, which respects the buyer's evaluation process. But it is a gap.
The practical implication is that budgeting and forecasting workflows live outside DualEntry, typically in specialized FP&A tools (Cube, Vena, Anaplan, or Excel-based workpapers) that read data from DualEntry and produce the planning outputs. For businesses with mature FP&A functions, this is often acceptable because those functions already use specialized planning tools. For businesses expecting the ERP to handle basic forecasting, this is a workflow adjustment.
What this category means for buyers. DualEntry is a general ledger and transaction system, not a planning platform. If planning is a critical requirement, plan for a specialized FP&A tool alongside DualEntry rather than expecting the ERP to deliver it.
Category 8: Revenue, Statements, and Workflow
Gap 20: No named percentage-of-completion revenue strategy
Percentage-of-completion (POC) is a revenue recognition strategy used for long-duration contracts (typically construction, engineering, or complex project-based services) where revenue is recognized based on the proportion of work completed. DualEntry documentation states: "DualEntry does not offer a named percentage-of-completion (POC) strategy." The recommended alternatives are usage-based or milestone-based recognition.
For a construction firm or long-duration project business, this is a material gap because POC is often the appropriate revenue recognition framework under ASC 606. The workaround using milestone-based recognition may work for some business models but not others, and any business with material POC revenue should discuss this with DualEntry sales during evaluation.
Gap 21: No vendor or AP statements
Vendor statements, the summary sent to a vendor showing invoices and payments over a period, are a standard AP function. DualEntry does not have this feature. The gap is worth naming because it affects AP operations for businesses that need to reconcile vendor accounts formally, particularly around aged payables reviews and vendor account cleanup.
Gap 22: One customer statement type only
Customer statements typically come in two formats: open-item statements listing all unpaid invoices, and balance-forward statements showing the aggregate balance carried forward with recent transactions. DualEntry supports one statement type only. Businesses whose customer relationships require balance-forward statements (common in wholesale, distribution, and some service businesses) will need to adapt to open-item statements or produce their own.
Gap 23: No approval delegation, escalation, or notifications documented
Approval workflows in enterprise systems typically support delegation (when the approver is unavailable, the approval routes to a designated alternate), escalation (when an approval sits unaddressed, it escalates automatically), and notifications (email or in-app alerts about pending approvals). DualEntry's documentation does not describe these mechanisms.
For businesses with sophisticated approval workflows, particularly around AP approval or expense reimbursement approval, this is a workflow gap. The absence of documentation does not necessarily mean the capability is absent, but it does mean the buyer needs to ask specifically about workflow behavior during evaluation.
What this category means for buyers. Specific revenue recognition frameworks (POC), traditional AP and AR statement workflows, and sophisticated approval routing are gaps worth naming in the evaluation conversation. Some may be roadmap items; some are structural.
Category 9: Enterprise Identity and Audit
Gap 24: SAML, OIDC beyond Google and Microsoft, and SCIM are not documented
DualEntry's single sign-on is described as available through Google and Microsoft OIDC. Broader SAML support and SCIM (System for Cross-domain Identity Management, the standard for automated user provisioning between identity providers and applications) are documented as "not part of the documented product today."
For mid-market businesses that use Google Workspace or Microsoft 365, this is not a gap. For larger enterprises that use Okta, OneLogin, or other identity providers, or that require SCIM-based provisioning as part of their IT governance, this is a real gap. Enterprise IT teams evaluating DualEntry should specifically confirm identity provider compatibility before adoption.
Gap 25: No audit trail API access or SIEM integration
Audit trails in DualEntry are visible in the application but the documentation states that the API does not expose audit trail events, webhooks cover business records only (not security events), and there is no direct SIEM (Security Information and Event Management) integration.
For businesses with formal security operations, particularly those with SOX obligations or PCI compliance requirements that require centralized log aggregation and monitoring, this is a real gap. The compensating control is to rely on DualEntry's in-application audit trail viewing, which is functional but does not integrate with the centralized security monitoring these organizations typically require.
What this category means for buyers. Enterprise IT and security requirements are the least mature area of DualEntry's product. Companies with sophisticated identity, security, and audit requirements should evaluate these gaps carefully.
Category 10: Product and Compliance Disclosures
Gap 26: No mobile app
DualEntry is a web application only. Multiple public reviews mention the absence of a mobile app as a limitation. For businesses whose users need to approve invoices, view financials, or perform other functions from mobile devices, this workflow accessibility gap is worth planning for.
Gap 27: No claimed certifications for ISO 27001, GDPR, CCPA, HIPAA, PCI DSS
DualEntry's Trust Center is more restrained about compliance claims than most enterprise ERP vendors. ISO 27001, GDPR, CCPA, HIPAA, and PCI DSS are not claimed as current certifications or compliance frameworks. This does not mean DualEntry cannot be used by businesses subject to these frameworks. It does mean that the compliance burden for these frameworks falls on the customer and their compensating controls rather than being addressed through vendor certification.
For any business subject to formal compliance frameworks, this is worth discussing directly with DualEntry sales to understand what documentation and controls are available to support the customer's compliance obligations.
Gap 28: Data residency, MFA options, and RTO/RPO not published
Data residency (which geographic region customer data is stored in), multifactor authentication options beyond the baseline, and recovery time objective (RTO) and recovery point objective (RPO) for business continuity are not published in the Trust Center. This gap is common across many SaaS vendors and is often addressed through direct customer discussions rather than public documentation, but it is worth naming because it affects security and continuity assessments.
What this category means for buyers. DualEntry is transparent about what it has not yet published, which is consistent with its overall documentation posture. Enterprise buyers should expect to have direct conversations with DualEntry about these specific details rather than finding all answers in public materials.
What DualEntry Does Very Well
The list above is uncomfortable reading if the reader stops there. Twenty-eight gaps sound like a lot. Context matters. DualEntry is genuinely differentiated in ways worth naming explicitly to keep the honest picture in view.
AI-native architecture. DualEntry has thought carefully about where AI belongs in the accounting stack and where it does not. In-product AI works as draft-generation with human review as the safety pattern. Scheduled agents are structurally read-only, with write and send tools stripped from the tool set before unattended runs begin. This is a defensible AI posture that most competitors have not matched.
QuickBooks Online migration. The Next Day Migration Engine from QuickBooks Online and Xero is genuinely differentiated. Businesses that have outgrown QBO and need to move to a mid-market ERP have historically faced a NetSuite implementation that runs 4-12 months and costs $50,000-$500,000. DualEntry's migration approach compresses that to something materially different. This is the platform's signature capability and it is real.
Modern user experience. For businesses that have used NetSuite or Sage Intacct, the aging user experience of legacy mid-market ERPs is a real productivity drag. DualEntry's UX is measurably better across every function I have evaluated. This matters for adoption and daily use in ways that are hard to quantify but significant in practice.
Revenue recognition depth. ASC 606 revenue recognition is genuinely well-implemented in DualEntry. The performance obligation model, standalone selling price allocation, contract modification handling, and multi-year ramp deals with equal-SSP treatment all work as expected. For a growing SaaS company crossing the point where QBO's revenue recognition stops being adequate, this is a meaningful capability.
Reasonable pricing philosophy. DualEntry publishes tier names without specific dollar figures in most public materials, but the pricing philosophy communicated through sales conversations is materially below NetSuite total cost of ownership. Implementation is included at $0 in the pricing tiers, which is a significant differentiator from NetSuite's implementation-project model.
Multi-entity accounting. For businesses with multiple wholly-owned entities, DualEntry's consolidation capabilities are strong. The gap is specifically around partial-ownership and NCI (Gap 18), but for 100%-owned multi-entity structures, the platform delivers.
Documented product philosophy. Perhaps most importantly, DualEntry's documentation quality is exceptional. The candor about gaps that this entire post is built on is the same candor that helps customers plan their operations realistically. A vendor that tells you what its product does not do is a vendor that respects your evaluation process.
What This List Means for Buyers
Twenty-eight gaps in a single vendor's product may sound alarming out of context. In context, it is the natural result of a well-scoped mid-market ERP that has chosen depth in specific areas over breadth across every possible use case. The right framing for a buyer is not "how many gaps does DualEntry have" but "which of these gaps affect my business."
For most mid-market SaaS companies, technology companies, and general operating businesses in the $10M-$1B revenue range, the vast majority of the 28 gaps do not affect the buying decision. The AI-native architecture, the migration capability, the modern UX, and the revenue recognition depth deliver clear value against the customer's actual needs. Gaps 1-7 (specialized verticals), Gap 16 (retail fiscal calendars), and some of the enterprise identity gaps (Gap 24) simply do not apply.
For specific verticals, the picture changes:
Professional services firms need to consider Gaps 1, 2, and 8 carefully. If project accounting is central to your financial model, DualEntry is not the right platform today.
Nonprofits need to consider Gaps 3 and 4. Fund accounting is a hard stop.
Government contractors need to consider Gaps 5, 6, and 7. Indirect cost pool accounting and named contract vehicle support are structural gaps.
Retail and standardized-calendar manufacturing need to consider Gap 16. Non-calendar-month fiscal periods are not supported.
Complex multi-entity structures with partial ownership need to consider Gap 18. NCI accounting is a hard stop.
Enterprise security and compliance need to consider Gaps 24, 25, 27, and 28. These are the least mature areas of the product.
Most other buyers face a manageable set of workflow considerations (payment initiation outside DualEntry, tax filing through Avalara or Tax1099, MACRS depreciation through the tax preparer's workpaper) rather than structural blockers.
The strongest recommendation for any prospective DualEntry customer is to run through this list explicitly during evaluation, identify which gaps apply to your specific business, and discuss the roadmap with DualEntry sales for any gap that materially affects the buying decision. The vendor's transparency in documenting these gaps is an invitation to have that direct conversation rather than discover the gaps after signing.
The Bottom Line
Twenty-eight documented gaps is a lot to publish in one place. DualEntry deserves recognition for making that possible, because their own documentation is the source for every gap named above. This is not a critique that competitors can level from the outside. This is DualEntry's own honest self-description, organized for buyer convenience.
The gaps do not disqualify DualEntry for its target customer profile. They shape the fit. For a general mid-market business outgrowing QuickBooks Online with a modern fintech stack, the AI-native architecture, migration capability, and revenue recognition depth are genuinely differentiated value. For businesses in specialized verticals with complex compliance requirements or partial-ownership structures, other platforms are likely better fits today.
The right posture for any buyer is to evaluate DualEntry with clear eyes about both its strengths and its documented gaps. That is what the documentation itself invites. This post exists to make that evaluation faster and more useful, and to model the kind of platform-agnostic analysis that any CPA advising on ERP selection should be doing anyway.
DualEntry ships fast. Any specific gap named here may close in the coming months. The list is a snapshot as of 14 September 2026, not a permanent characterization. Prospective customers should verify current status directly with DualEntry sales for any gap that matters to their decision.
Ready to evaluate DualEntry for your business honestly?
Most CPAs advising on ERP selection are trained on one platform and pitch that platform regardless of fit. This post attempts a different posture. Catch Up Clean Up is a Certified Puzzle Advisor, and I am actively evaluating DualEntry for the moment client demand justifies deeper adoption. My recommendations are platform-agnostic across QuickBooks Online, Puzzle, Xero, and DualEntry based on genuine fit rather than platform advocacy.
For US-based businesses evaluating DualEntry as a potential destination from QuickBooks Online, I can help work through this gap list against your specific requirements, identify which gaps are material to your decision, and coordinate directly with DualEntry sales on the roadmap questions that emerge. If DualEntry fits, I can support the migration and ongoing operations. If it does not fit, I will tell you honestly which platforms are better matches and support that decision instead.
What you get:
A diagnostic call to identify which of the 28 documented gaps affect your specific business
Honest fit assessment across DualEntry, Puzzle, QuickBooks Online, Xero, NetSuite, and Sage Intacct
Direct coordination with DualEntry sales on gap-specific roadmap questions
QuickBooks Online cleanup before migration if your books need it first
Migration execution support if DualEntry is the right destination
Ongoing bookkeeping across whichever platform fits your business
Certified Puzzle Advisor perspective combined with broader mid-market ERP expertise
No platform advocacy: recommendations based on your business, not our certifications
Book a free consultation and we will evaluate DualEntry against your specific requirements honestly.
Frequently Asked Questions
Is DualEntry a good ERP despite these gaps?
For its target customer profile of US-based mid-market businesses in the $10M-$1B revenue range with a modern fintech stack, DualEntry is a strong ERP option. The gaps documented here are the ones DualEntry itself publishes and represent conscious product scope decisions rather than product quality issues. The AI-native architecture, migration capability, and modern UX are genuinely differentiated. Whether the platform fits your specific business depends on which gaps apply to your operations.
Can DualEntry handle project accounting through classifications?
Classifications provide a project tagging and reporting mechanism but do not replicate a native project accounting module. Per-project budgets, project revenue recognition, WIP tracking, and project-specific billing workflows are not supported. For professional services firms where project accounting is central, this workaround is typically insufficient.
Does DualEntry integrate with Avalara for tax filing?
Yes. DualEntry generates tax data and Avalara handles US sales tax calculation and filing. Tax1099 handles 1099 e-filing. VAT and GST filings for supported jurisdictions require manual submission through the country's portal. This integration architecture works well for most businesses but should be planned during evaluation.
Is the absence of MACRS depreciation a hard stop?
Not for most businesses. GAAP fixed asset accounting works fine in DualEntry with the four supported depreciation methods. MACRS calculations for tax purposes typically live in the tax preparer's fixed asset workpaper or specialized tax depreciation tools, which is standard practice regardless of the accounting platform.
Does DualEntry support businesses with partial-ownership subsidiaries?
The consolidation module works for 100%-owned structures but does not address ownership percentages, non-controlling interest, or partial-ownership consolidation. Businesses with joint ventures, minority-owned subsidiaries, or complex ownership structures should raise this specifically with DualEntry sales to understand roadmap timing.
How does the missing three-way match affect AP controls?
The compensating control is that variance review moves from automated software enforcement to the bill approval workflow. This works but requires deliberate workflow design and reviewer discipline. Businesses with SOX obligations or robust internal control requirements should document the compensating controls explicitly during evaluation.
Should Catch Up Clean Up recommend DualEntry?
Catch Up Clean Up recommends the platform that fits each client's specific situation. For clients whose profile matches DualEntry's target customer (US-based, mid-market, outgrowing QuickBooks Online, on modern fintech stacks, without vertical-specific requirements that hit the gap list), DualEntry is often a good recommendation. For clients in specialized verticals or with the specific complexity the gap list captures, other platforms are typically better matches.
Comments