What's new

Document View

• Activity timeline — Document view pages now show a timeline of all activities (created, updated, emailed, fiscalized) with cursor-based pagination
• Simplified fiscalization card — Replaced verbose FURS/FINA detail displays with a clean status badge and manual retry button
• Payment refresh — Document details and PDF preview now auto-refresh after adding or editing a payment

Tax & Compliance

• Issuer and operator info — Fiscalization data on documents now includes the issuer tax number and operator details for both FURS and FINA

SDK & API

• Custom document creation in SDK — createCustom() methods now available for invoices, estimates, credit notes, and advance invoices
• Request log filtering — Web app session calls are now excluded from API request logs, showing only external API usage

Web App

• API downtime detection — Users are redirected to the login page with status info when the API is temporarily unavailable

• 404 pages — Custom not-found pages for root, /app, and /account routes with translations

• Email modal — Wider dialog and taller message area for a better writing experience

• Create standard, /app and /account 404 page Create standard, /app and /account 404 page

• Add subscription page to web /account and fix entity add… Add subscription page to web /account and fix entity add gate link, base subscription info on website page

• Add document activity timeline to document view Document view pages now show a timeline of all activities (created, updated, emailed, fiscalized, etc.) with cursor-based pagination for long histories.

• Add issuer and operator info to fiscalization data Fiscalization data on documents now includes the issuer tax number and operator details for both FURS (Slovenia) and FINA (Croatia), providing a complete audit trail on every fiscalized document.

• Fix document view not refreshing after payment Document details and PDF preview now automatically refresh when adding, editing, or deleting a payment on the document view page.

• Add document activities to document view with pagination Add document activities to document view with pagination

• Add custom document creation to JS SDK Expose custom document creation through the official JavaScript SDK so integrations can create custom invoices, estimates, credit notes, advance invoices, and delivery notes using high-level SDK methods.

• Improve PDF text contrast for custom brand colors PDF invoice accent colors now automatically adjust text contrast based on the brand color, ensuring readability on both light and dark backgrounds.

• Improve email modal layout and input size The email sending dialog is now wider and has a taller message text area for a better writing experience.

• Fix document view page Fix document view page

Take the document create or add page as the baseline. It is good now don't touch it, don't change it but update the document view page to reflect the same flow where the right-side PDF is wrapper is fixed and the PDF preview scrolls inside. This part already works correctly but the left-side scrolls correctly although after scrolling to the bottom, the whole page scrolls up including the PDF preview which hides then under the top. So mostly done just one detail

• Add API downtime detection with login redirect When the API is temporarily unavailable, users are now redirected to the login page which shows downtime information, instead of seeing a broken page.

• Simplify the fiscalization card on document view Simplify the fiscalization card on document view

Just status if it was supposed to be fiscalized, if it's not used or document was specifically skipped fiscalization. Also add a button to attempt manual fiscalization if failed.

• Add support for invoice for advance Add support for invoice for advance

Add support for creating invoice for previously issued advance (related document) where the invocie needs to show the relation to the advance in terms of values and taxes and should support partial coverage where the invoice is larger, research how if needed

Invoicing & Documents

• Croatia FINA B2C fiscalization — Full integration with Croatia's FINA tax authority for B2C invoice fiscal verification, mirroring the existing Slovenia FURS support
• Soft delete — Documents, customers, and items are now soft-deleted instead of permanently removed, with restore support
• Tax subject field for customers — Customers can now be marked as tax subjects, matching the existing entity setting
• Croatian localization — Croatian translations for invoices, UI, and email templates with HR date/number formatting

Customer Management

• Customer detail page — View full customer details and history in a dedicated page
• Customer CRUD in web app — Create, edit, and delete customers directly from the web interface

International Support

• Poland support — Poland added as a supported country with PLN currency and entity defaults
• Entity defaults for all languages — Default document templates and settings for all supported languages

Web App

• Item detail page — View and edit item details in a dedicated page
• Improved loading states — Smoother loading experience with centered spinner replacing plain text
• White-label branding — White-label web apps now show the white-label name instead of Space Invoices branding
• Compact entity list — Redesigned entity list with a cleaner, more compact layout
• Mobile improvements — Web app and marketing website optimized for mobile devices
• Fix document scroll — Document preview now scrolls independently from the data entry form

Developer Tools

• Frontend embed SDK — JavaScript SDK for embedding Space Invoices pages in third-party websites via iframes
• Webhooks — Subscribe to events (invoice created, payment received, etc.) with automatic retries and delivery tracking
• Webhook documentation — Complete guide with integration examples
• Idempotency documentation — Guide covering the Idempotency-Key header, supported endpoints, and retry behavior
• Pagination documentation — Guide for cursor-based pagination with code examples
• Sandbox data reset — Reset all test data in sandbox environments with one click
• Bulk sandbox delete — Delete test data in bulk from sandbox environments
• UI library on GitHub — Component library published as a public GitHub repository

Platform

• Demo account — Daily-refreshed demo account showcasing app features with sample data

• Uptime monitoring — Public status page for service health and uptime history

• Pricing update — Platform fee updated to €49/month

• Roadmap page — Public roadmap added to the website

• Changelog page — Changelog added to the documentation site

• Improve language detection for new visitors New visitors now see the app in their preferred language, auto-detected from their location. The language choice persists across sessions and devices.

• Improve language support with 7 European locales The web app, UI components, and API now support 7 additional European languages: Italian, French, Spanish, Portuguese, Dutch, Polish, and Croatian — in addition to the existing English, Slovenian, and German.

• Add EPC QR code support for invoices Add EPC QR code (EPC069-12) generation on invoices to enable one-scan SEPA credit transfers. Widely used in Germany and other SEPA countries. The QR code encodes beneficiary IBAN, name, BIC, amount, and payment reference so banking apps can pre-fill transfer details.

• Add related documents to document API responses Users cannot discover linked documents (e.g., auto-generated credit note after FURS invoice cancellation) via the API. The document_relations table exists and is populated, but there's no way to query it.

Two changes needed:

1. ?include=document_relations on all document GET endpoints — Add document_relations to includableRelations for invoices, credit notes, estimates, and advance invoices. When included, call documentRelationsService.findByDocument() and attach to the response. This is the general-purpose solution for navigating between linked documents.

2. Return created credit note info in the void/cancel response — When POST /invoices/{id}/void auto-generates a credit note for a FURS-fiscalized invoice, include the credit note ID/number in the response so the caller knows immediately without a second query.

Cleanup: Remove voided_invoice_id / voided_invoice_number from credit note metadata in the void service — metadata is user-editable and unreliable for this. Document relations are the canonical link.

• Fix embed document creation crash Fixed a crash when creating invoices through the embedded SDK document creation page.

• Fix API key dialog dropdown width and display value The entity scope dropdown in the API key creation dialog is now full width and shows the human-readable entity name instead of the raw ID.

• Fix FURS certificate upload failing on production Fixed an issue where uploading a FURS fiscalization certificate would fail with a 422 error on production servers that don't have OpenSSL installed. Replaced OpenSSL CLI dependency with a pure JavaScript implementation.

• Fix error toast text overflow in notifications Error notifications now properly contain long error text within their boundaries instead of overflowing outside the toast container.

• Improve entity cookie storage to use ID only Reduced cookie size by storing only the entity ID instead of the full entity object, preventing cookie overflow issues for accounts with complex settings.

• Improve Return to Account navigation The "Return to Account" button now correctly navigates to the account dashboard instead of the entity list.

• Improve URL structure with bookmarkable pages All pages now include resource IDs in the URL (entity and account IDs), making every page directly linkable and bookmarkable. Sharing a URL now opens the exact same view.

• Add order management module Order management module for e-commerce integrations. Receives orders from external systems (Shopify, WooCommerce, etc.) via webhooks, normalizes them into a single source-agnostic order model, and automatically processes them into invoices. Supports auto-invoicing for paid orders, payment tracking, order cancellation with invoice voiding, and reissue flows.

• Add recurring invoices automation Implement recurring invoice automation: frequency settings (daily, weekly, monthly, yearly), start/end dates, auto-generation on schedule, auto-send option, pause/resume capability. Critical for subscription-based businesses.

• Add e-commerce integration framework (Shopify, WooCommerce) Build a generic webhook receiver framework for e-commerce platforms. Start with Shopify and WooCommerce: order webhook processing, customer sync, discount handling, auto-invoice generation. Design as plugin architecture for easy addition of new platforms.

• Add delivery note document type Add delivery note as a new document type. Include packing list generation, link to invoice, and inventory deduction on finalization. Important for product-based businesses.

• Add activity tracking to accounts-payable documents Ensure all create, update, and delete operations on invoices, estimates, credit notes, and advance invoices consistently emit activity events and webhook notifications. Audit existing integrations and fill any gaps.

• Add overdue notification settings UI The overdue notifications backend exists (API routes, service, cron job) but there's no frontend UI to configure notification settings per entity. Add a settings page to the web app for configuring overdue notification preferences: enable/disable, reminder schedule, email templates.

Historical release reconciliation

• Invoicing and compliance — Added Croatian B2C fiscalization support, country tax-rate improvements, document API enhancements, and registration-number support.

• Product experience — Improved account navigation, entity management, translations, theme controls, and document PDF verification.

• Documentation and integrations — Expanded API and SDK documentation, validation examples, AI-readable docs, webhooks, and HAL/widget integrations.

• add tax detail page similar to customers and translated tax… add tax detail page similar to customers and translated tax add/edit and other if needed

• Add light/dark switch to login/signup/reset to web app… Add light/dark switch to login/signup/reset to web app similarly to how it's implemented when logged in

• Plan adding posthog to project to best utilize the tool Plan adding posthog to project to best utilize the tool

• If user is identified via widget and they have a… If user is identified via widget and they have a subscription plan we could move them to won stage in crm

• Reorganize docs sidebar navigation The documentation sidebar items need to be reviewed and reordered for better logical flow and grouping.

Current Issues Identified

API Reference (api-sidebar.json)

1. Document endpoint ordering is inconsistent - Within each document type (Invoices, Estimates, etc.), endpoints appear in arbitrary order. Should follow a logical flow:

   • Object description
   • Create → List → Get by ID → Update → Delete/Void (CRUD operations)
   • Version history endpoints
   • Rendering (Preview, HTML, PDF)
   • Sharing operations (Make shareable, Get token, View shareable, Unshare)
   • Draft operations (Finalize, Delete draft)
   • Document number preview

2. "Other" section is a catch-all - Contains disparate items:

   • Email (could be Communication)
   • Exports
   • Activities (audit logs)
   • White Labels + White-Label Subscriptions (related, should be grouped)

3. Files & Uploads - Has "Files" and "Upload" as separate collapsed items but they're closely related

Guides Section (astro.config.mjs)

The current order seems reasonable but could verify:

• Getting Started: Introduction → Core Concepts → Quickstart → Authentication → Idempotency
• Guides: Use Cases → Documents → Data → Compliance

Recommended Changes

1. Reorder document endpoints in api-sidebar.json to follow consistent CRUD-first pattern
2. Consider renaming "Other" or reorganizing its contents
3. Potentially merge Files and Upload under one heading
4. Review if any guides should be reordered based on user journey

• user is requesting create document endpoint with all… user is requesting create document endpoint with all features but skipping calculation so they can pass their own sums, the rest of the logc and expected data for db should be the same, can we produce something like that with minimal changes mbybe by flag or separate endpint?

• Conditional root redirect by account type Change the root / route to redirect based on account type:

• White-label accounts (entity-only): Redirect to /app

• Root accounts (Space Invoices users with account access): Redirect to /account

Currently / always redirects to /app unconditionally. Should use the existing getPostLoginRedirect utility logic.

• Verify bank account info on document PDFs

• Fix sandbox toggle and developer translations Fixed sandbox toggle in account sidebar - dark text was not visible against orange background. Changed to white text on solid orange background. Also removed i18n translations from Developers sidebar menu (English only for developer features).

• Fix menu items elements not translated Fix menu items elements not translated

• Fix entity add page bugs Fixed three bugs on the entity add page:

1. Entity created in wrong environment: When adding entity from /account in sandbox mode, it was created in live. Fixed by passing environment prop through CreateEntityForm.

2. Back button context-awareness: Back button always went to /app. Now uses session storage flag to determine origin - goes to /account if user came from there.

3. Missing sandbox banner: Add entity page didn't show sandbox banner because it checked active entity (which doesn't exist yet). Switched to AccountSandboxBanner which checks environment from context.

Also created UserProvider for clean access to user data and isAccountUser check (regular vs white-label user).

• Add SDK documentation to docs site Add comprehensive documentation for all three SDK packages to the docs site:

• JavaScript SDK (@spaceinvoices/js-sdk): TypeScript SDK auto-generated from OpenAPI

• Embed SDK (@spaceinvoices/embed-sdk): Iframe-based UI embedding for quick integration

• React UI (@spaceinvoices/react-ui): Copy-paste React components

This includes creating a new "SDKs" sidebar section, documentation pages for each SDK, and code examples.

• remove everything related to notes as it was a test remove everything related to notes as it was a test

• add if missing company_number (registration number etc.) to… add if missing company_number (registration number etc.) to entity and customer

• Review web and UI translations

• check chatwithhal.com docs for widget company info… check chatwithhal.com docs for widget company info registration (push account data if non-white label user otherwise skip), on signup stege should be Lead, on first invoice should be Qualified, on subscribe should be Won.

• Add docs example validation system

• Improve FURS docs by splitting into logical sidebar groups

• Add llms.txt for AI-consumable documentation

• Add Documents tag for shared document operations

• Add German translations

• add api updating for properties that are normally updated… add api updating for properties that are normally updated via identify for use on servers

• Add Croatia B2C fiscalization support Add real-time B2C invoice fiscalization for Croatian businesses via the CIS (FINA) tax authority. B2C invoices from Croatian entities are reported to CIS in real-time with ZKI/JIR security codes and QR codes on PDFs. Foreign B2B invoices are allowed without fiscalization. Domestic B2B is out of scope due to strict Fiskalizacija 2.0 requirements.

• Add Hal chat widget for non-white-label users Add an in-app support chat widget for eligible authenticated users across the web app, website, and docs.

• Add entity API key creation in account Add the ability to create entity-scoped API keys (ek_*) from the /account/api-keys page. Previously this page only created account-level keys (sk_*). The embed SDK requires entity keys for security, but users had no way to create them from the account page.

Implementation

• Added optional entity selector to the create key dialog
• No entity selected → creates account key (sk_*) via POST /api-keys
• Entity selected → creates entity key (ek_*) via SDK entityApiKeys.create()
• Added "Scope" column to keys list showing "Account" or entity name
• Unified display of both key types in one view

Bug Fix

Also fixed a 404 error when creating entity API keys in /app/settings/api-keys - the page was calling /entities/{id}/api-keys but the API expects /entities/api-keys with x-entity-id header. Updated to use SDK methods which handle headers correctly.

• Fix Cloudflare Workers deployment Cloudflare wrangler-action was failing because it tried to install wrangler via npm, which doesn't support the workspace: protocol used in the monorepo. Fixed by adding packageManager: bun to all three deploy jobs in the workflow.

• Add separate Steuernummer field alongside USt-IdNr German companies have two distinct tax identifiers: the Steuernummer (local tax number from Finanzamt, varies by state) and the USt-IdNr (EU VAT ID, format DE123456789). Adding a second tax identifier field allows both to be stored and displayed on invoices — Steuernummer for domestic dealings, USt-IdNr for EU B2B. The field is generic and can serve other countries with dual tax ID systems.

• remove adding single payment on document create and allow… remove adding single payment on document create and allow adding multiple and no amounts split between equally

• add webhooks support per project for triggering events in… add webhooks support per project for triggering events in external systems

• Need to add tax rate information for different countries for… Need to add tax rate information for different countries for entities when creating to auto populate, maybe to countries data?

• some dropdown items in lists still aren't translated some dropdown items in lists still aren't translated

• Fix customer object and API spec Investigate why customer records don't have a customer object stored in the database. Also review the customer API spec/schema and compare it against similar resources (e.g. items, documents) to ensure consistency in structure and fields.

• Fix web app root route redirect Root "/" route wasn't redirecting to /account or /app. The IndexRoute component wasn't mounting due to TanStack Router behavior.

• Redesign account dashboard and fix usage charts Redesign the account dashboard entities list from bulky cards to a compact list design, and fix usage charts not rendering bars.

• Review docs important fields per endpoint

• Clean up react-ui README and remove Leka refs The published react-ui repo README has issues:

1. Contains mentions of "leka" (internal codename) that should be removed
2. Copying instructions are confusing - need to be clearer for external users

Repository: https://github.com/space-invoices/react-ui

• Publish changelog for upcoming release Review and publish the draft "Upcoming Release" changelog (ID: cml9nmhn3001f6xqv85glk55u). Currently includes the frontend SDK for embedding web app pages in iframe. Before publishing:

1. Review the draft content for accuracy and completeness
2. Add any other recently completed tasks that should be included
3. Set an appropriate version number
4. Update the title to match the release (e.g., month/year format)
5. Publish the changelog

White-Label Platform

Build your own invoicing product on top of Space Invoices with our new white-label capabilities:

• White-label users & UI access — Create isolated user experiences for your customers with separate login flows and branded interfaces
• Hidden features configuration — Control which features are visible per white-label for different market segments
• Billing configuration — Configure billing settings per white-label for subscription management
• Theme config — Customize colors and styling for the embed SDK per white-label
• Management UI — Full admin interface for managing white-labels in your account

Developer Tools

• JS SDK on npm — Install with npm install @spaceinvoices/js-sdk for full TypeScript support
• CLI for UI components — Install pre-built invoicing UI components into your React project
• Rate limiting — API rate limiting with clear headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset)
• llms.txt — AI-friendly documentation added to docs site

Platform

• Hal AI assistant — In-app AI chat for quick help and support