
Making expense reports obsolete
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Abacus replaced the monthly expense report with individual transactions that employees could submit and managers could review as spending happened. Founded in 2013 by Omar Qari, Ted Power and Josh Halickman, the YC Winter 2014 company reached more than 1,000 customers before Certify acquired it in July 2018. The buyer retained the product and used its technology within a broader portfolio.[1][2]
The product continues as Emburse Spend. An official rebranding notice dates the change to April 23, 2025; abacus.com now redirects to its login. As of October 2, 2026, Spend promotes real-time review, existing-card connections and accounting sync. The outcome is a strategic acquisition with product continuity. Public terms do not establish the founders’ or investors’ financial returns.[3][4]
Image 1 / 1
The founders approached expense reporting as work that software could reorganize. Power brought design experience from Foursquare; Halickman had worked as an engineer at Etsy. After YC, the team returned to New York. In a 2016 interview, Qari explained the desired outcome: “Productivity to us doesn’t mean spending time in Abacus, it means getting your work done.”[5]
That goal influenced both interface and workflow. Instead of improving the form people filled out at month-end, Abacus captured context while it was still fresh and routed the expense immediately. The employee’s task became smaller; finance could receive a continuous stream instead of a late pile.
Qari’s fundraising interview shows the company already had customers before its seed round. He described more than 50 customers and early revenue after over a year of work. Bessemer Venture Partners and General Catalyst led the $3.5 million round. Participants included Stripe’s Collison brothers, ZenPayroll’s Josh Reeves and Venmo’s founders. Their presence connected Abacus with operators in adjacent payments and payroll markets, although the interview does not measure resulting distribution.[6]
Abacus made each expense an object with its own receipt, amount, merchant, employee, category and approval path. Receipt recognition and card matching reduced entry work. Comments and policy checks supplied context to reviewers. Approved expenses could flow to reimbursement and accounting systems.[14]
The workflow evolved with customer behavior. TechCrunch reported that customers had already reimbursed over 2,000 candidates through temporary accounts before formal support launched.[7] This was demand revealed through a workaround. Reach later let employers invite external travelers, receive their receipts and route approval. Its launch announcement listed availability across Abacus, Certify, Nexonia and Chrome River.[12]
Distribution also happened inside other tools. Abacus’s original Slack announcement describes receipt uploads and approval buttons, with notifications limited by automatic rules. Built In’s interview also describes a Lever integration for candidate expenses. NetSuite connected the workflow to larger companies’ accounting systems. These relationships reduced the need to visit a separate app and helped Abacus reach work already underway.[9][5][8]
Capital One’s 2017 announcement names Abacus among contracted API recipients. That relationship addressed a different dependency: access to transaction data. Faster interfaces need reliable feeds; a product cannot review an expense it has not received.[10]
Abacus began with small employers and expanded toward companies with more complex approval requirements. Qari’s 2014 interview describes customers with hundreds of employees. At acquisition, Certify said most Abacus clients had fewer than 500 staff, with larger customers such as Dropbox also using it.[6][14]
The reviewed sources do not establish Abacus’s addressable spending or revenue share. Its reported customer base supports adoption, not a market-size calculation. Employer size, activity and workflow differ; a subscription price cannot be multiplied by every employee to infer revenue.
Certify and Expensify introduced real-time functions, but customers did not uniformly prefer individual approval. Business Travel News interviewed both CEOs: some customers still wanted a definitive report for a trip or period. Certify’s acquisition let it offer both methods. The lesson is broader than feature copying: the buyer could serve different workflow preferences without forcing one model on every customer.[14]
Today, existing cards are not a unique wedge. Emburse Spend supports multiple card programs and ledger mappings. Expensify advertises card-agnostic receipt matching, approvals and accounting integrations. New entrants must test a narrower problem than “keep your cards.”[4][15]
Qari described monthly SaaS pricing at $5 per active user. The unit aligned payment with people who used the product instead of charging for every employee. He also described the move from simple reimbursement to stronger controls as larger customers arrived.[6]
Public sources establish the $3.5 million round and acquisition, but not revenue, retention, margins or sale price. There is no sound return calculation. The buyer’s rationale is better documented: product capabilities, management experience and an opportunity to expand the portfolio.[1]
The acquisition announcement claimed more than 1,000 customers, including Betterment, GLG and North American Substation Services. It also named Dropbox, Quora and California Closets. These are company-reported adoption markers, not independently measured financial results.[1]
Candidate workarounds and integrations show different kinds of traction: customers extended the product, while partners embedded it into existing work. Neither proves every integration drove sales. Qari’s 2016 interview claimed roughly 80% of compliant expenses could be approved behind the scenes; no independent benchmark was supplied.[5]
Qari described joining Certify as “the fastest way to achieve our goals.” That statement supports a strategic expansion rationale, while remaining a seller’s public account. It does not establish that independence was impossible or that competition forced the sale.[1]
The observed mechanism is product reuse within a portfolio. Emburse’s January 2020 announcement committed to six expense products and sharing real-time expense, capture and card-integration technology. Qari and Power joined its executive team. The same capabilities could support different company sizes and geographies rather than one standalone brand.[11]
Abacus also faced a change-management problem. Qari’s NetSuite interview described replacing established business processes, while the acquisition interviews showed customers retaining batch preferences. Faster technology did not remove those preferences. The sale expanded the range of workflows available to the buyer; its financial value remains private.[8][14]
The surviving product keeps evolving. Its March 2026 notes describe optional risk checks at capture, submission and approval, alongside fixes for transaction reliability and exports. This reinforces a practical limit on rebuilding: classification alone is insufficient, and reliable data movement remains part of the product.[13]