Central, a Y Combinator-backed fintech, redefined bookkeeping by creating an AI-powered Slackbot using Puzzle’s modern accounting APIs. After facing limitations with QuickBooks, Central leveraged Puzzle’s real-time data, developer-friendly APIs, and AI-ready platform to build a Slack-integrated solution that automates tasks, provides instant financial insights, and enhances customer experience. Learn how this innovation transformed their operations and set a new standard for accounting in fintech.

Central, an AI-native HR and fintech company (now part of Mercury following its April 2026 acquisition), partnered with Puzzle to eliminate back-office headaches for startups. By building on Puzzle's modern general ledger and powerful APIs, Central rebuilt the way they deliver bookkeeping services: real-time transaction categorization, AI-native Slack queries, and a unified place for payroll, benefits, and accounting.
TLDR:
As a technology-first company automating back-office and financial operations, Central built an all-in-one solution for payroll, benefits, bookkeeping, tax filing, and other government compliance requirements (like state tax account registrations, unemployment insurance rate changes, and CTA Beneficial Ownership Information Reporting). The goal: a "no-headache" experience so founders could focus on their businesses—not on administrative overhead. (Central has since joined Mercury, expanding that mission further.)
But bringing bookkeeping into that same frictionless experience was challenging. Central's engineering team needed a modern accounting platform that offered real-time data access, deep APIs, and the flexibility to build an AI-powered Slackbot. The tools they initially tried (like QuickBooks) were limited by outdated architecture and lacked the deep API integration that Central's vision required. Startups seeking AI accounting alternatives to QuickBooks run into this same wall repeatedly.
"QuickBooks just wasn't built for the kind of product we wanted to create," explains Josh Wymer, CEO of Central. "The APIs were limited, and trying to build workarounds was frustrating and time-consuming. We needed a platform that could handle all the great ideas we wanted to build."
Central found in Puzzle a modern general ledger and accounting platform purpose-built for developer success. By partnering with Puzzle, Central now automates everything needed to operate a compliant startup, from payroll to real-time bookkeeping, and can embed accounting functionality where their customers spend the most time: Slack. Key capabilities that made their vision possible:
By combining Puzzle's general ledger with Central's payroll, benefits, and compliance offerings, they've created an AI-native, automated back office for startups.
"Puzzle's APIs and real-time data flow were the key," notes Wymer. "We didn't have to fight the platform to make it work for us. Instead, Puzzle felt like it was built to support exactly the kind of forward-thinking tools we're creating."
With Puzzle under the hood, Central has realized four major outcomes to eliminate back-office busywork, a model for what accounting agent AI automation looks like in practice:
| Outcome | What It Means in Practice |
|---|---|
| Unified Back Office | Payroll, benefits, and accounting in one AI-native interface: no tab-switching between tools. |
| Faster Book Closing | Puzzle auto-categorizes most transactions; founders confirm the rest via a quick Slack prompt, no spreadsheets. |
| Real-Time Financial Answers | Users ask cash flow, burn rate, or tax questions directly in Slack and get answers sourced from live general ledger data. |
| Faster Feature Development | Modern API architecture lets Central prototype and ship new features quickly, something impossible with legacy accounting systems. |
Founders can access payroll, benefits, and accounting all in one interface, and it is all AI-native. Central has become a strong solution for busy operators who hate administrative hassle.
Central's Slackbot automates or greatly simplifies bookkeeping tasks. Most transactions get intelligently categorized by Puzzle; for the rest, founders just give the bot a quick explanation. No tedious spreadsheets required.
Central bot already handles payroll changes, health benefits info, and expenses. Now, with Puzzle's powerful query APIs, users can ask real-time questions about their company's finances (like cash flow status or upcoming tax obligations) directly in Slack.
With a modern API architecture, Central's team can quickly prototype and launch new features, something that wasn't possible with legacy accounting systems. This keeps them ahead of the curve in a competitive fintech environment.
"Puzzle has fundamentally improved our bookkeeping processes," says Wymer. "The tight integration with our Slackbot has allowed us to create something just not possible before: an entire accounting back office based in Slack using ChatGPT and Puzzle."
Central and Puzzle's partnership didn't just solve a single workflow problem: it positioned both companies squarely at the center of the industry's biggest shift. AI adoption among accounting professionals has surged from 22% to 40% in the past year alone, according to Thomson Reuters, and the global AI-in-accounting market hit $10.87 billion in 2026, growing at a 44.6% CAGR. For context on what AI agents in accounting actually do, that growth reflects a genuine shift in how books get closed. Automated bookkeeping is the fastest-growing sub-segment of that market, and that is exactly where Central operates.
The pressure is real: 73% of finance professionals say their business is growing faster than their team can handle manually. Legacy tools like QuickBooks have responded with bolt-on AI features, but the architecture gap remains. Platforms built on modern, developer-friendly general ledgers (not retrofitted onto decades-old systems) are the ones actually delivering continuous, real-time books. For startups comparing accounting agent software, that architectural difference is the deciding factor. That's the bet Central made, and the data is catching up to it.
By mid-2026, the "AI in accounting" narrative has split in two. On one side: adoption metrics that look strong on paper. 98% of accounting professionals globally report using AI in some form, and the AI-in-accounting market hit $10.87 billion this year, growing at a 44.6% CAGR (Mordor Intelligence). On the other: an execution gap that's widening. Gartner's latest data shows 59% of finance leaders actively use AI in their finance function, nearly flat from 58% in 2024, and 73% of AP teams have still not fully automated their core workflows. Over 40% of agentic AI projects are forecast to be cancelled by end of 2027, largely because teams adopted tools before their data and integrations were ready to support them.
That gap is exactly where Central and Puzzle operate. The firms closing books in real time (not fighting to match up week-old data) are the ones that started on modern, API-first infrastructure. Bolt-on AI features layered onto legacy architecture don't fix the underlying data problem; they just paper over it. Central's Slackbot works because the general ledger underneath it is live. That's an architectural bet, not a product feature, and the 2026 data is making clear which side of that bet is paying off.
The signal that defined mid-2026 wasn't a single product launch: it was a category shift. Accounting Today's 2026 Top New Products report put it plainly: standalone AI no longer impresses. What's winning is embedded AI that runs near-invisibly inside core accounting systems, handling complex workflows as an ambient layer, not a bolt-on tool. That's the architectural bet Central and Puzzle made years ago, and the industry has now caught up to the framing.
The investment side confirms the momentum. AI accounting startups are attracting serious capital in 2026: audit automation platform DataSnipper crossed a $1 billion valuation on the back of a $100 million Series B, citing 90% automation of menial audit tasks and a doubled customer base. Danish startup Light closed a $30 million Series A in August to push its AI accounting automation into the US market. The thesis across these rounds is consistent: the firms that redesign their workflows around AI from the ground up outperform those that add AI features to existing processes. That's Central's entire product premise, and it's why the Puzzle general ledger underneath it matters as much as the Slackbot on top.
For most firms onboarding onto Puzzle, the workflow breaks into three phases. In the first week, you connect your client's bank accounts and fintech integrations (Stripe, Mercury, Ramp, Brex, Gusto) and Puzzle's AI begins categorizing transactions immediately, typically hitting 95%+ auto-categorization within the first few days as it learns your chart of accounts. In weeks two through four, you review the flagged transactions, set category rules for recurring vendors, and close your first month. That close is the real milestone: it's the moment you know the books are live and accurate. From month two onward, the workflow is largely automated: Puzzle runs the categorization, surfaces exceptions, and maintains both cash and accrual books simultaneously. Teams building out AI agent workflows for month-end close will recognize this pattern as the standard adoption arc. For firms just getting started, the practical milestone sequence is: connected → first clean close → rules tuned → ongoing review-only workflow.
Puzzle supports both paths. If you're a startup or solo founder with a straightforward setup (single entity, standard fintech stack), you can connect your accounts and have live books running in under an hour, no call required. If you're an accounting firm onboarding multiple clients, or if you have a more complex chart of accounts or historical data to import, Puzzle's team offers guided onboarding to make sure the setup is right from day one. In either case, the goal is the same: your first month close should feel routine, not painful. Most firms report being fully live within one to two weeks of starting.
Direct business customers (founders using Puzzle to run their own books) get self-serve onboarding with access to Puzzle's support team for questions. Accounting firm partners get a dedicated onboarding experience: a partner success contact, priority support, and access to firm-specific workflows like multi-client dashboards and white-label options. Puzzle's partner model is built on the premise that the firm's expertise is irreplaceable. The platform handles the automation so your team can focus on advisory, not data entry. If you're considering Puzzle for a firm, start with the partner track over the standard signup flow.
Puzzle works well for early-stage bookkeeping firms, even those without a large existing client base. The platform scales from one client to hundreds, and per-client overhead stays low because automation handles most of the categorization work. To get started: sign up as a firm partner, onboard your first client, and run one full month-end close. That first close tells you everything about fit. The key advantage for new firms is margin: because Puzzle automates the grunt work, a two-person team can serve clients that would otherwise require three or four staff. The platform is also built with clean audit trails and cash and accrual books maintained simultaneously from day one, so you're not accumulating technical debt you'll have to clean up later.
For accounts that don't support direct bank feeds, Puzzle can extract transactions from uploaded PDF bank statements using document parsing and OCR. The system reads the statement structure, identifies the transaction table, extracts dates, amounts, and descriptions, and imports them directly into the general ledger with no manual re-entry required. From there, the same AI categorization logic applies: merchant recognition, chart-of-accounts matching, and rule-based logic run on the extracted transactions exactly as they would on live-feed data. This is especially useful for accounts at smaller banks or credit unions that don't support Plaid or direct API connections. The resulting ledger entries are indistinguishable from those sourced via live feed.
Yes. Puzzle's AI chat is designed for task-level accounting work, going beyond simple question-answering. You can ask it to split a transaction across multiple expense categories (for example, a mixed SaaS invoice that covers both software and professional services), flag potential fixed assets based on amount thresholds and vendor type, or generate a point-in-time P&L summary filtered by date range or account. Central's Slackbot is built on top of these same capabilities: founders ask real questions about cash balance, upcoming tax obligations, and burn rate, and get accurate answers sourced directly from Puzzle's general ledger. The underlying model has access to your actual books, which is what makes task-level actions reliable and precise.
The constraint isn't headcount: it's how much manual work sits between a transaction and a closed book. Firms that scale without hiring do it by eliminating that gap. On a modern AI-native platform like Puzzle, auto-categorization handles 95%+ of transactions from day one, which means a bookkeeper's time moves from data entry to review and exception-handling. A two-person team can realistically serve the client load that previously required four staff, because the categorization, rule application, and ledger maintenance run automatically. The second lever is workflow standardization: when every client onboards to the same connection stack (Stripe, Mercury, Ramp, Brex, Gusto) and the same chart-of-accounts structure, your team stops context-switching between bespoke setups. Each new client becomes a repeatable process, not a custom project. The third lever is the month-end close itself: firms using Puzzle report that close time compresses from days to hours because exceptions surface automatically, not buried inside a manual reconciliation. Taken together, these three levers (auto-categorization, standardized onboarding, compressed close) are how accounting firms grow revenue per staff member, not headcount in lockstep with clients.
The shift from monthly PDFs to live dashboards is an infrastructure problem, not a reporting problem. PDFs are monthly because the underlying books are monthly: the close happens once, the report gets exported, and the client waits 30 days for the next one. When the general ledger is live (transactions categorized in real time as they hit the bank feed), the data needed to power a dashboard is always current. Firms on Puzzle give clients access to a live view of burn rate, cash position, and runway that updates daily, not because someone ran a report, but because the ledger underneath never stops. For advisory-focused firms, this changes the client relationship: instead of presenting history, you're discussing what's happening now and what to do about it. The practical step is straightforward: connect the client's accounts, let Puzzle's AI run categorization continuously, and point the client to their dashboard. The monthly PDF becomes optional context, not the primary deliverable.
The safest migration path starts with a clean export before you cut over. From QuickBooks Online, export your Chart of Accounts, all transaction history (including journal entries), and your audit log via the Reports section. Most modern platforms (including Puzzle) support importing that data in standard formats (CSV or QBO file). Puzzle's onboarding team maps your existing categories to the new chart of accounts so historical transactions carry over accurately. The key rule: never cancel your QuickBooks subscription until you've completed at least one full month-end close in the new platform side-by-side. That overlap period is your safety net. Central's team went through this same transition and chose Puzzle because its API-first architecture made it possible to connect their existing payroll and compliance data without rebuilding from scratch.
Modern platforms like Puzzle use a combination of machine learning trained on large transaction datasets, merchant name recognition, and rule-based logic applied to your bank feeds. When a transaction comes in (say, a charge from AWS), the system matches the merchant against known categories (cloud infrastructure → software & hosting), checks prior categorizations for that vendor in your account, and applies the most confident label automatically. Transactions that fall below a confidence threshold get flagged for human review instead of being auto-categorized, which is how accuracy stays high without introducing errors. Central built its Slackbot on top of Puzzle's categorization APIs: most transactions are categorized instantly; for the remainder, the bot surfaces a quick prompt to the founder in Slack to confirm the category, no spreadsheet required.
If you're running payroll through Gusto or Rippling, the general ledger entry for each payroll run (gross wages, employer taxes, net pay, and benefit deductions) needs to land in your books automatically, not as a manual journal entry each cycle. Puzzle's integrations pull payroll data from Gusto and Rippling in real time: each pay run creates the corresponding journal entries in the general ledger, split by the correct expense accounts and mapped to the right liability accounts for taxes and deductions. Central's platform sits on top of this architecture, meaning founders who run payroll through Central get those journal entries reflected in their books immediately, with no accountant needed to log in and post entries after every payroll date.
The categorization model improves through two mechanisms: account-level learning and explicit rule creation. When Puzzle first sees a new vendor, it matches against a trained merchant dataset (AWS → cloud infrastructure, Stripe → payment processing) and applies a starting category. Each time you confirm or correct a categorization, that signal is recorded against your account. After two or three consistent corrections for the same vendor, Puzzle locks in a rule: every future transaction from that merchant is categorized the same way, automatically, with no review prompt. You can also create rules manually (by vendor name, transaction description pattern, or amount range) and they apply to all future and historical transactions in scope. The practical effect: the first month has the most review work; by month three, the exception queue is a fraction of what it was on day one. Central's Slackbot is built on this same rule engine: most transactions categorize silently, and only genuine edge cases surface as a Slack prompt.
The core difference is architectural, not cosmetic. QuickBooks was built in the 1990s and has added AI features on top of a legacy data model, which means live bank feeds, real-time categorization, and developer APIs are bounded by what that underlying structure can support. Puzzle was built AI-native from day one: the general ledger is live, the APIs are first-class, and automation is baked into the data model, not layered on top. In practice, that gap shows up in three places clients care about. First, close speed: firms on Puzzle report compressing month-end close from days to hours because categorization runs continuously, not in a batch at month-end. Second, real-time answers: clients can check burn rate or cash position any day of the month, even outside the close window. Third, developer flexibility: Central's entire Slackbot (real-time financial queries, auto-categorization, payroll journal entries) runs on Puzzle's APIs because the architecture supports it. QuickBooks' API limitations are exactly why Central switched. When positioning this to clients, lead with the outcome: "Your books are current every day, even outside the close window," then explain the architectural reason why.
Reconciliation and accruals represent two of the biggest time sinks in a traditional close, and they work differently on an AI-native platform. For reconciliation: because Puzzle's general ledger ingests transactions from live bank feeds and categorizes them continuously, the reconciliation step at month-end becomes a review of exceptions, not a line-by-line matching exercise. Most firms report that reconciliation time drops from several hours to under 30 minutes per client, because the ledger is already aligned with the bank by the time you open the close checklist. Firms adopting agentic AI for month-end close report the same compression pattern. For accruals: Puzzle maintains both cash and accrual books simultaneously from day one, so you're not running a manual conversion at close; the accrual entries exist in real time alongside the cash view. Prepaid schedules, deferred revenue, and recurring accruals can be templated and applied automatically. Taken together, the manual work that remains is genuinely exceptional: edge cases, unusual vendors, and judgment calls that should have a human involved anyway. The data-entry-and-matching work (which accounts for the bulk of close hours in a legacy setup) is largely gone.
Central and Puzzle's partnership continues to evolve. "We're automating everything needed to operate a compliant startup," Wymer explains. By offering a unified place for back-office tasks, Central reduces the risk of missed deadlines or fines and frees up founders to focus on growth.
As more startups demand real-time insights, less manual data entry, and integrated compliance, Central is positioned to deliver an ever-expanding suite of AI-driven back-office services. By building on Puzzle's developer-friendly APIs, Central can push the boundaries of what an all-in-one back-office solution can do, eliminating "back-office BS" for good.
-
Learn more about Central at centralhq.com





