Docs
Changelog

June 2026

What shipped in Numezis in June 2026.

Highlights

  • Agents and MCP became production-grade surfaces — June added public MCP tool catalogs, safer governed tool execution, approval hand-offs, stronger OAuth/session handling, compliance knowledge search and better agent run events.
  • WhatsApp and Telegram workflows moved forward — channel agents now handle document ingestion, outbound replies, approval cards and session scoping more consistently across messaging channels.
  • ListEngine and TableView were standardized — list pages now share stronger pagination, filtering, column, bulk-action, loading and error-state contracts across company, tenant, partner, internal and superadmin portals.
  • Business modules expanded materially — sales, purchases, accounting, projects, HR, CRM and partner operations all received new user-facing flows, not only documentation updates.
  • Public documentation, migrations, search and SEO shipped — the docs site now includes migration guides, stronger localized metadata, structured data, search and four-language coverage.

Agents, MCP and Codex-assisted workflows

  • Published company, tenant and partner MCP tool catalogs so agent clients can discover supported actions more predictably.
  • Hardened MCP mutation execution with explicit approval hand-offs, safer execution results and clearer handling for actions that still need human review.
  • Improved MCP OAuth, token refresh and session stability so connected agent clients recover more reliably.
  • Strengthened MCP prompt, argument normalization, PII handling, exception governance and coverage checks.
  • Added outbound payment operations to the MCP surface and expanded governed tool coverage across CRM, contacts, notes, projects, tasks, approvals, accounting and partner workflows.
  • Improved the company intelligence hub, tenant intelligence configuration and automation catalogs for agent-driven workflows.
  • Added compliance knowledge search support through documented API and MCP paths, with better recall for Swiss SME legal and compliance questions.
  • Tightened agent run streams, run-event contracts and approval UI continuation so users can understand what an agent did and what still needs confirmation.
  • Improved Codex-assisted QA and release workflows with clearer detached UAT sessions, feature evidence discipline and agent-friendly validation paths, without exposing internal release artifacts publicly.

WhatsApp and Telegram channels

  • Improved WhatsApp webhook handling for inbound messages, delivery status updates, duplicate suppression and asynchronous processing.
  • Strengthened WhatsApp linking, access scoping and session resolution so messages are routed to the right user, tenant and company context.
  • Added stronger queue, dead-letter and retry foundations for WhatsApp message processing.
  • Improved media/document handling so channel documents can feed the purchase inbox and document-to-entity pipeline.
  • Channel agents can now send outbound replies immediately after a response is produced instead of waiting for a later batch path.
  • Telegram agent output and approval-card handling were stabilized, including approval, rejection and read-only review paths.
  • Shared channel session, action-token and human-action handling were consolidated across messaging channels.

ListEngine and TableView

  • Added a cross-portal ListEngine and TableView capability matrix covering company, tenant, partner, internal and superadmin usage.
  • Standardized list pagination, row selection, bulk-action eligibility and bulk action dock behavior.
  • Improved column management, filters, search state, saved views, export and aggregation readiness.
  • Aligned list loading, empty, error and stale-data states with the canonical page-state model.
  • Hardened list metadata and collection mapping for CRM, automations, accounting and shared list contracts.
  • Added targeted UAT and Playwright coverage for query behavior, columns, selection, dialogs, responsive layout and portal sweeps.

Migrations

  • New migration hub at /docs/migrations/overview, grouped by practical categories: Swiss SME cloud, Swiss ERP, desktop accounting, international ERP, freelancer/invoicing and legacy/discontinued systems.
  • Each provider page explains the three supported paths: API extraction when available, files/CSV exports, or a Numezis support-led migration.
  • Provider pages now call out when API is not the primary path, so desktop and file-led tools do not imply an unsupported connector.
  • The migration registry is source-backed and tested so every provider keeps a slug, aliases, category, methods, source URLs and localized content.

Sales and revenue operations

  • Added Swiss QR-bill 2.4 compliance work and stronger QR-reference reconciliation for bank payments.
  • Expanded invoice email sending, customer reminders, recurring invoice automation and reminder automation.
  • Improved invoice PDF generation, PDF/email template overrides and customer-facing invoice presentation.
  • Added online invoice payment checkout and guest access foundations for external invoice interactions.
  • Improved partial payment, overdue reminder and two-step payment posting behavior.
  • Expanded order-to-cash coverage, delivery notes, country-specific sales lifecycles and sales bulk operations.
  • Added eBill sandbox submission support and improved payment/reconciliation coverage around Swiss invoice flows.

Purchases and procure-to-pay

  • Expanded bill lifecycle support across submit, post and pay states.
  • Added multi-currency purchase bill handling and stronger purchase configuration coverage.
  • Improved email ingestion into the purchase workbench and document-to-entity purchase flows.
  • Strengthened standalone expense lifecycle, purchase-order backed flows and full procure-to-pay coverage.
  • Added purchase reporting for vendor analysis and budget variance.

Accounting and compliance

  • Added accounting closing runs and readiness checks for monthly, quarterly and annual close workflows.
  • Added Swiss VAT eCH/AFC proof coverage and stronger VAT readiness.
  • Added outbound payment runs and mapped outbound payment operations into governed agent tooling.
  • Improved workflow logic and approval automations tied to accounting and purchase controls.
  • Hardened bank, reconciliation, ledger, currency and accounting policy behavior through service and release coverage.
  • Expanded compliance knowledge search and public compliance documentation without publishing confidential source material.

Projects, HR and CRM

  • Projects gained tasks, timesheet entries, resource allocation and reporting, capacity planning and project AI automations.
  • Project finance coverage expanded with expense evidence and approvals, invoice-to-cash/accounting, revenue recognition and Jira/Asana task integrations.
  • HR gained employee self-service workspace work, salary and work certificate support, payroll bank handoff and break-minute time tracking data.
  • CRM gained lead capture intake/routing, activity follow-up reminders and stronger list metadata handling.
  • Collaboration gained company knowledge notes and release-safe note metadata handling.

Partner, fiduciary and public website

  • Partner portal coverage expanded with team access, client delegation grants, delegation templates and client KYC profile work.
  • Partner operations gained capacity allocation, team staffing, timesheets, advisory reporting, mandate templates and mandate exit checklist support.
  • Partner fleet views expanded across document collection, documents, VAT and accounting work items.
  • The Swiss fiduciary directory gained public guide work, internal CMS support and partner profile self-service.
  • The public website received a richer product preview hero, denser modular-app storytelling and better portal scope clarity.

Documentation, search and SEO

  • The docs home now surfaces migrations as a visible entry point instead of hiding them only in the sidebar.
  • Changelog navigation now includes both May and June 2026.
  • Public docs catalog entries can reference German and Italian MDX paths for pages that ship in all locales.
  • The docs payload was reduced by avoiding full client-side i18n message delivery on documentation pages.
  • Added a server-side search route for docs search using the Fumadocs search adapter.
  • Added canonical and alternate locale metadata for documentation pages.
  • Added TechArticle and BreadcrumbList structured data for docs pages.
  • Added a docs SEO contract check to keep canonical, hreflang, sitemap and migration snippet quality from regressing.
  • Expanded public docs in German and Italian to full catalog coverage.
  • Added and refreshed public guides for developers, fiduciaries, MCP tools, messaging channels, collaboration notes and platform onboarding.

Reliability, security and quality

  • Hardened authentication refresh behavior and OAuth token routes.
  • Added centralized notification preference links and deduplication for in-flight notification deliveries.
  • Improved public route checks, Docker/docs build context, release gates and generated API/client snapshots.
  • Added production traffic anomaly alerting and stronger availability checks, described publicly only at the reliability level.
  • Reduced stale ESLint suppressions and strengthened frontend API, i18n, entity-surface, field-icon, runtime-proof and UAT governance.
  • Added migration-provider tests covering inventory completeness, localized MDX generation and forbidden promise language such as “zero effort” or guaranteed migration.
  • Extended docs preflight with SEO checks and kept the internal-links, translation and locale-parity gates green.
  • Added or refreshed tests across MCP, channels, compliance knowledge search, list behavior, service coverage, notifications, purchases, sales, accounting, CRM, HR, projects and partner flows.

Compatibility notes

No intentional public API breaking change is listed for June. MCP, channel-agent and list contracts were hardened; integrations should rely on documented public API and MCP surfaces rather than internal payloads or release artifacts.

What's next

  • More source-specific migration examples and import-preparation checklists.
  • More partner and fiduciary onboarding paths.
  • More public examples for MCP, agent approvals and messaging-channel workflows.
  • Additional screenshots where they reduce ambiguity for setup, imports or approvals.