Digits Puts Accrual Schedules Inside the General Ledger

What did Digits just put inside the general ledger?

Digits Schedules, announced May 7, 2026, brings accrual accounting workflows natively into its AI-native general ledger — detecting, scheduling and managing recurring journal entries without spreadsheets.

For decades, supporting schedules have been one of accounting's most persistent manual workflows. The general ledger records what happened. The spreadsheet off to the side determines how it's recognized over time. That split creates reconciliation gaps, version-control problems and a review trail that lives outside your system of record.

It's a mess. And it's totally predictable.

Digits Schedules closes that gap. The ledger itself identifies which transactions need accrual treatment, drafts the schedule — including assumptions and projected entries — and surfaces it in a Checklist for the accountant to approve, modify or dismiss. Once finalized, recurring journal entries are generated automatically for the life of the schedule.

"QuickBooks can't do this. Xero can't do this. Even mid-market ERPs sell it as a separate product that takes months to implement before the first journal posts. Digits just made it the default behavior of the general ledger," said Craig Walker, Head of Product Strategy at Digits and former Co-Founder and CTO at Xero.

The launch covers fixed assets and prepaid expenses. Revenue recognition and accrued expenses are next on the roadmap, according to Digits' May 7 press release.

Why do accrual schedules still live in spreadsheets?

Most accounting systems record what happened — they don't manage what happens next. That left schedules stranded in spreadsheets, disconnected from the authoritative numbers in the ledger.

Every month-end close, an accounting team runs the same sequence: pull the fixed asset list, roll the depreciation schedule forward, recalculate, post the journal entry by hand and then reconcile back to the balance sheet. The same cycle runs for prepaid expenses — subscriptions, insurance premiums, prepaid rent — each requiring its own spreadsheet row and manual entry each period.

Jeff Seibert, CEO and Founder of Digits, put the problem plainly: "Supporting schedules are one of the most persistent workflows still living outside the ledger. Every firm we work with spends hours every month identifying transactions, rolling spreadsheets forward, recalculating balances, and hand-creating journal entries for work that's almost entirely deterministic."

The math is deterministic. The problem isn't the math. It's execution risk — wrong useful life, missed transaction, version mismatch between the spreadsheet and the ledger. That's not a judgment problem. It's a systems problem.

How is a ledger-native schedule different from a bolt-on module?

Bolt-on tools sync data back to the ledger after the fact. Ledger-native schedules live inside the system of record from the start — no export, no sync gap.

The distinction matters at review time. When a schedule lives in a spreadsheet or a loosely connected module, a reviewer has to trace: Does this journal entry match the schedule? Does the schedule match the source transaction? Did someone modify the spreadsheet between last month and this month? Each step is a potential gap.

With Digits Schedules, every schedule traces from the source transaction through each posted journal entry to the balance sheet. That's one continuous system of record — not a chain of exports held together by hope and version control.

The April 21 MCP Server launch extends this further: accounting firms, business owners and developers can query Digits' real-time ledger data directly inside Claude, ChatGPT and Cursor. Digits processes transactions in real time and auto-books 95%+ of them without human intervention, meaning the data AI tools see is current and clean, not a stale export.

What should a CPA firm review before using AI-generated schedules?

Nothing in Digits Schedules posts without accountant approval — but firms still need to verify the approval path, source trace and documentation hold up at review.

First, the approval path. Digits surfaces proposed schedules with assumptions and projected entries before anything posts. Firms should confirm who in their workflow reviews the proposed schedule and whether that review step is documented in their engagement management system. The accountant is still responsible for the judgment call — useful life on a fixed asset, whether a prepaid should be reclassified, whether the schedule period aligns with the underlying contract.

Second, the source document trace. Verify this in practice on your first few schedules. Pull the source transaction and confirm the schedule uses the right cost basis, acquisition date and account mapping. If you're migrating existing assets into Digits, check that opening balances match your prior workpapers before relying on the automated entries.

Third, the client disclosure conversation. Clients may ask whether AI generated their depreciation schedule. The accurate answer: Digits proposes the schedule and entries. Your firm's accountant reviews and approves. That's defensible — but only if the review happened and is documented.

Is AI handling the judgment, or just the math?

This is the right question, and Digits has a clear answer: the AI handles the math. The accountant retains the judgment.

Digits identifies which transactions need accrual treatment, drafts the schedule using transaction context and surfaces it for review. An accountant confirms the useful life, verifies accounts and finalizes before a single journal entry posts. The system can be overridden or dismissed at any point.

Accrual accounting is "almost entirely deterministic," as Seibert put it. Straight-line depreciation on a $24,000 piece of equipment with a 5-year useful life produces the same $400/month entry whether a human calculates it or a system does. The AI executes the calculation. The accountant validates it.

That distinction matters.

Where judgment still belongs to the accountant: useful life selection, MACRS vs. straight-line for tax purposes, whether a subscription qualifies as prepaid or gets expensed immediately and partial-period depreciation on mid-month acquisitions. Those aren't menu selections. They require professional judgment, and Digits isn't claiming otherwise.

The misconception to avoid is treating automation as an excuse for less oversight. Faster workflow means errors propagate faster if no one is watching the approval queue.