CPA-Help
● IN DEVThe next generation of accounting-practice management, multi-firm from the ground up
Next.jsTypeScriptDrizzle ORMPostgres RLSBetter AuthResend
The business and the pain
An accounting firm spends its days chasing: documents for capital declarations, clients who haven’t paid, Tax Authority deadlines. Requests arrive over WhatsApp, email and phone with no single source of truth. “When did you even ask for that?” becomes an argument, yearly recurring tasks depend on someone’s memory, and the firm’s own money waits for someone to find time to chase it.
What the system does
A complete practice-management system, built multi-firm from the ground up. Every client request becomes a ticket with an owner and a due date. Long processes like capital declarations run through clear stations: the client uploads documents from their phone through a single link, no password, and the moment they finish, a task opens for the team. Boards of recurring tasks carry the running year (reports, withholdings, advances), letters and broadcasts go out from templates by audience, and the collections engine works alone: an unopened letter, a missing payment, a growing delay, each state gets its own reminder. And the client? Sees everything in a portal, without calling.
The details that prove deep specification
- Every ticket carries two statuses: six internal states for the team, three simple ones for the client. The nuance stays inside; the client gets a clean picture.
- A capital declaration cannot skip a station by mistake: an illegal transition is blocked, with a Hebrew message explaining why.
- All scheduling runs on Jerusalem time. A collections reminder never goes out on Shabbat, and the weekly manager report waits for Sunday morning.
