The path from a working preview to supported books
The published package has a bounded accounting starter spanning customer and supplier documents, payments and optional stock workflows. Each next step needs reconciled examples, access checks and review before it becomes a supported capability.
This roadmap describes development scope, not a delivery-date or regulatory-compliance promise.
Development sequence
- AvailableDevelopment preview
0.4.0-preview
Core AR/AP documents, partial payments, credits, ageing and control reconciliation; optional Purchasing and Inventory; manual inclusive/exclusive tax; accounts, journals and traceable corrections; reviewed opening conversion; period and bank CSV controls; reports and CSV exports. Owners can hide AR/AP navigation and enable optional modules without erasing history.
- AvailableRead access shipped
API and MCP read access
Scoped read API and MCP connections shipped in 0.2.1 and remain available. Dedicated tokens and per-user OAuth restrict access; the published client matrix identifies tested client versions and pending integrations.
- Next reviewResearch and review
Practical evaluation, account catalogues and UX
Gather reproducible feedback on the starter. Review country-aware account catalogues, deeper synthetic companies and interface prototypes before implementing those later changes. The current release does not include those new catalogues or expanded example packs.
- Regional integrationsPlanned
Tax and e-invoicing connectors
The core stays country-neutral. Pakistan FBR is one planned connector, alongside other regional tax/e-invoicing integrations. Countries and currencies do not activate these capabilities automatically.
- Business modulesPlanned
Advanced stock, shop POS and e-commerce
Extend the shared stock, AR/AP and tax services with reviewed vertical capabilities. Route, delivery and collection modules must reuse shared receivables. Quotes remain a separate future plugin; controlled API/MCP commands, restaurant and specialist modules have their own later gates.
- Across the productPlanned
Languages, owner equity and queued entry
Urdu, then Arabic and RTL with English fallback; reviewed owner/partner equity reports; browser draft queues and planned desktop/Android clients. Posting, period control and reversal always execute on the server.
- Accounting acceptanceUnfinished
Reviewed reporting
Versioned account mappings, true comparatives, completeness checks, reproducible report snapshots and qualified review for the chosen entity and framework. The current reports are management previews, not issued statutory statements.
- Parallel priorityHigh priority
SEO discovery and launch preparation
Maintain crawlable public documentation and release news, verify search ownership and indexing, and prepare evidence-based campaign material. Account setup and campaign execution are tracked separately from product capability.
Help test a real task
Useful contributions include synthetic worked accounting examples, installation results, reproducible bugs and feedback from owners and bookkeepers. Independent security, accounting and observed usability review remain open gates.
Frequently asked questions
When will a stable release be available?
There is no committed stable-release date. A supported release needs reconciled accounting examples, qualified accounting review, observed usability, installation and recovery checks, and clear support scope.
Does choosing a country or currency activate local accounting rules?
No. Each book uses one base currency. Country and currency choices do not activate tax calculations, statutory reporting, foreign-currency posting or additional accounting books. The core is country-neutral. Pakistan FBR is one planned connector; each regional accounting or tax integration needs separate research, implementation and review.
How can I help shape the next release?
Share a synthetic workflow example, installation report or reproducible issue through the project repository. Accountants, business owners and contributors can also use the Support page to prepare an email about review or pilot participation.
Which parts are ready to evaluate?
Use the release boundary to choose a test task; a schema foundation does not mean the operator workflow is available.
| Available in 0.4.0 | Still to build or accept |
|---|---|
| Invoices, bills, partial payments, credits and historical ageing | Advances, unapplied credits, overpayments and refunds |
| Shared party/contact forms and identity duplicate controls | Vetting enforcement and vendor bank change control |
| Manual document currency snapshots and realised FX settlement mechanics | Automated rate feeds, revaluation and consolidation |
| Optional one-location Inventory and Purchasing; core manual tax | Advanced stock, country rules, filing and qualified statement acceptance |
How will the next milestone be accepted?
Examples must reconcile document, open-item and general-ledger balances, including partial payments and corrections.
- Complete the published synthetic invoice, bill, payment and stock exercises.
- Check document, open-item, inventory and general-ledger reconciliation.
- Review account catalogue proposals and UX prototypes before later implementation.
- Rehearse installation, upgrade, restore, corrections and closed-period behavior on the intended host.
- Obtain qualified accounting and observed operator review before claiming supported business use.