A clearer start for business setup, made for how business works here.
Your business records, right where you left them.
Your workspace is ready to be set up.
Core setup, not financial balances
Account setup changes are recorded for the workspace.
We’re setting up isolation, chart structure and accounting periods before enabling transactions or financial reporting.
Prepare the account structure and fiscal calendar before any posting is available.
Organized for traceable double-entry accounting
| ACCOUNT CODE | ACCOUNT NAME | TYPE | LEVEL | STATUS |
|---|
Adjust the search or add a new account.
Monthly periods inherit an open fiscal-year status
| PERIOD | FISCAL YEAR | STARTS | ENDS | STATUS |
|---|
Create a fiscal year to establish your calendar.
Choose the kinds of assistance your workspace may use as modules are implemented.
Skill availability is saved per business. Skill toggles describe workspace availability only; this release does not call a third-party model or create/approve/post financial transactions.
Workspace preferences · execution depends on a real implementation
Choose a provider only after its API, access and business permissions are verified.
Saving a definition does not authenticate or connect a provider. Credentials are never collected or stored by connector definitions; verified provider-specific authentication is not included in Phase 1.
Adapter directory · availability depends on provider access and compliance validation
Saved metadata only — not active connections
Choose an adapter to begin a safe configuration record.
Automate small, auditable workspace actions when a supported event occurs.
Event rules run only on new Phase 1 setup events. Scheduled rules use Manus Heartbeat after a workspace user configures one on the published site. Actions are idempotent and never alter financial transactions.
Explore the planned paths, prerequisites, and current readiness before enabling anything.
Try a different search or category.
Create a rule for a supported setup event.
A rule only runs after its matching event occurs.
Foundation behavior is distinguished from planned, non-executable blueprints.
Try another search or group.
This area is part of the product plan and is not implemented in the current Phase 1 release.
Transactions and financial reporting will follow only after tenant isolation, permissions, audit history, and double-entry posting have been validated.
Apna BusinessFoundation, privacy boundaries and change history for this business.
—
PKR · Asia/Karachi—
OwnerEvery foundation record is scoped to your authenticated business membership.
Tenant-scoped recordsBusiness setup changes will be captured here.
This Phase 1 foundation uses managed database storage and application sessions. It does not implement a general ledger, transaction posting, financial reporting, or a verified security/compliance program. Do not enter live financial, tax, payroll, or customer-financial records.