What is BreezyCorp?

BreezyCorp is an AI-native corporate-services platform. The defining idea is simple: agents prepare the work, and people decide. Every regulated or external action — a filing, a client-facing dispatch, a posting — passes a mandatory human gate before it happens.

It is built greenfield and multi-tenant by design, on a Tenant → Group → Entity → Branch hierarchy, so a client manages a whole group of companies — across Singapore and India — from one login. Singapore is the first jurisdiction; further jurisdictions are added as data (rule and form packs), not as new code. See The platform model for what that hierarchy means in practice.

The products you operate today

Five products are live on the platform. They share the same client master, hierarchy, files, OCR, notifications, audit trail, and the agentic harness; each owns its own domain.

Payroll automates the monthly cycle around Infotech, the workbook-based payroll engine. The platform chases the client for changes and supporting documents, validates what they send, generates the Infotech import workbook, imports the Infotech output, packages an approval report, and chases the approver. Infotech itself stays in charge of CPF / IRAS / payslip generation.

Bookkeeping automates the document → journal → upload-file flow around Xero, QuickBooks, Zoho, and Tally, plus bank reconciliation. It ingests documents (manual / WhatsApp / Drive), runs OCR, classifies against a per-client chart of accounts and vendor master, lets you review the batch, produces the upload-file artifact, parses bank statements, matches transactions, and chases the client for unreconciled items via the portal. The accountant still posts the upload file manually into the target platform.

Financial Statements automates SFRS-compliant statement preparation. A trial balance is parsed and mapped to the SFRS taxonomy (Claude-assisted, with manual override), the four statements are computed deterministically, a disclosure-interrogation engine surfaces the gaps the preparer must answer, Claude generates the notes and Directors Report against verbatim mandatory policy texts, and the system produces a publication-ready Word document.

XBRL Filing automates ACRA filing. A financial-statement DOCX/PDF is parsed into line items, mapped against the 1871-element ACRA 2026 v1.0 taxonomy, every mapping is human-confirmed, 144 ACRA business rules run, and BizFinx Excel + XBRL XML output is produced. Export is hard-gated: any validation error or any unconfirmed mapping blocks it. The taxonomy version is pinned per filing, so historical filings stay reproducible.

Correspondence is a staff-ops mail-intake pipeline. Statutory and agency mail arriving in the firm's mailbox is OCR'd and classified, the relevant client is matched, an operator reviews, and a per-item dispatch goes out. It is staff-only — there is no client surface. See the Correspondence handbook.

More modules are specified and on the way — Secretarial (the reference workflow), Registered Office, Tax, Immigration, and native Ticketing. See What's coming.

What every module shares

• The workflow spine. Instruction → agent prepares → human decides → loop closes. The shape is the same whether you're approving a payroll cycle or releasing a piece of mail.
• The corporate hierarchy. Work attaches to an Entity (or a Branch), which belongs to a Group, which belongs to a Tenant. Your view rolls up or drills down along that spine.
• Tenant isolation. Every record belongs to exactly one tenant, enforced at the database (row-level security). No role sees across tenants.
• Shared plumbing. One authentication system, one file/OCR pipeline, one notification outbox, one append-only audit trail, one client portal.

What's separate is the domain in each module — payroll cycles, journal batches, FS engagements, XBRL filings, correspondence documents — and the rules and forms that drive it.

What this means when you're in the app

When you log in, the staff dashboard shows the products and entities your role and scope allow. A Bookkeeper sees bookkeeping work; an FS Preparer sees financial-statement engagements. Your URL tells you where you are — /dashboard/payroll/…, /dashboard/bookkeeping/…, /dashboard/financial-statements/…, /dashboard/xbrl/…. (Correspondence is parked — see its handbook.)

If a client subscribes to only some products, the platform only asks for what those products need — product enablement lives on the entity's product subscriptions.

Where to read more

• The platform model — the hierarchy and tenant isolation.
• How the platform works — the review inbox, intake channels, the client portal, the register.
• Roles & permissions — what your role can do.
• The per-module handbooks: Payroll, Bookkeeping, Financial Statements, XBRL, Correspondence.