March 26, 2026

Permission Profiles In Team & Access

Changed

• Replaced the old role-first member editor with built-in permission profiles such as Controller, Bookkeeper, AP Clerk, AR Manager, Inventory Manager, Tax Manager, Viewer, and External Accountant.
• Made /settings/team-access the single home for invites, membership updates, access history, and security policy changes.
• Kept Clerk responsible for membership existence and the coarse org:admin / org:member tier, while Eclipse now stores the profile key, effective permission snapshot, and any per-seat custom overrides.
• Expanded the live permission catalog to cover finance, invoices, bills, expenses, inventory, estimates, documents, jobs, properties, payroll, taxes, time tracking, banking, reports, settings, team, integrations, and chart of accounts.

Why It Matters

Teams can assign access that matches real accounting work without inventing ad hoc roles or over-granting permissions. Profile-based defaults also make audits, invites, Clerk sync, and future permission expansion more predictable because Eclipse keeps the detailed access state in one place.

eBay Two-Way Listing Publish

Changed

• Updated the eBay integration surface to treat eBay as a two-way connection in Eclipse instead of an import-only channel.
• Standardized listing creation on the real draft-to-publish flow at /listings and /listings/create.
• Added publish-readiness checks so Eclipse can tell when an eBay connection is ready to publish listings and when it needs a reconnect for newer write scopes.
• Kept older read-only eBay connections working for imports while showing a clear reconnect path before users try to publish listings.

Why It Matters

Teams can now use Eclipse as the operational home for eBay listing drafts and live publishes without losing the import sync behavior they already rely on. Older eBay connections also fail more gracefully because Eclipse now explains when a reconnect is required for publishing instead of surfacing a late API error.

Veeqo Shipping Sync Repair

Changed

• Repaired Veeqo sync, cron, webhook, health, and diagnostics paths to resolve API-key credentials from the encrypted token columns used by the live connection flow.
• Moved Veeqo order enrichment ahead of shipment expense creation so shipments can match canonical channel orders by channel reference first and Veeqo cross-references second.
• Expanded Veeqo shipment processing to keep carrier, service, tracking, shipment dates, shipping cost, and raw shipment data attached to matched orders even when a shipment has no billable label cost.
• Added auditable sync counters for matched shipments, unmatched shipments, approval fallbacks, duplicate expenses, and pending shipping allocations.
• Updated product analytics and profitability views so allocated shipping from shipping_cost_allocations.allocation_details flows into lifecycle shipping totals and net profit.

Why It Matters

Tax-week Veeqo backfills now bring in usable shipping cost and tracking data without relying on legacy plaintext API-key columns, and product-level profitability now reflects the shipping allocations created from those synced expenses.

Recurring Spend Monitor

Changed

• Upgraded Subscriptions & Recurring to combine recurring-expense detection with bank-detected recurring charges.
• Added a monitor state for recurring charges seen in banking that do not yet have a matching recurring expense pattern.
• Updated recurring-spend totals and upcoming-charge visibility so linked bank activity and tracked expenses can be reviewed in one place.

Why It Matters

This makes the recurring spend view behave more like the subscription monitors users expect from products like Rocket Money or Monarch. Eclipse can now flag likely subscriptions even when someone has not fully tracked them in expenses yet, which makes it easier to catch forgotten spend before it drifts.

AI Review Queue Reduction

Changed

• Added triage metadata to the unified review queue so Eclipse can classify items as auto-resolve, batch review, or manual review.
• Added smart batch grouping to /approvals so similar exceptions can be reviewed and applied together instead of one row at a time.
• Added a background approvals processor cron that can auto-resolve safe product-link and categorization cases using learned history, rules, and deterministic matches.
• Added queue APIs for smart batches and safe-action application so the review queue can shrink without manually opening every item.

Why It Matters

Large review backlogs now collapse into a smaller set of exception batches, and Eclipse can safely clear repeatable low-risk work in the background. That means teams spend less time clicking through obvious approvals and more time reviewing the exceptions that actually need judgment.