Two months of weekly releases, gathered into one page. If you signed up at launch and haven’t looked since, this is what changed.
A ninth vertical
Events & MICE is now a vertical of its own, not a trip with a budget attached. Projects carry a line-item budget with cost and sell held apart, a minute-by-minute call sheet whose client edition drops internal lines and crew phone numbers automatically, and a dossier — budget, crew list and run of show — as one landscape PDF or CSV. Crew records are shared with the charter side, so day rates land in the project’s cost lines instead of someone’s memory. Margin and sales analytics work exactly as they do everywhere else.
Accounting stopped being the part you finish elsewhere
- ERP push is live, not rolling out. Invoices, payments, expenses and bank journals go to Logo, Mikro and Xero on their own, and failed pushes retry without anyone watching.
- Bank feeds — Yapı Kredi, TrueLayer, Plaid, or plain CSV — reconcile against the ledger, with rules for the lines you never want to see again.
- Payables matching: the estimated cost you raised when you sold the service is matched against the supplier’s real invoice, so the same cost is never counted twice and you can see where the difference came from.
- Treasury shows every bank account, company card and card terminal as one normalised cash position, with manual entries and transfers between them.
- Recurring invoicing — define a bot per account: when it wakes, what it collects, how far back it goes. No period is ever billed twice.
- Collections desk queues what has gone overdue by aging band, one click to remind.
- Accounting health puts the loose ends on one page: trial balance out of balance, integrator credit running low, e-documents not yet filed, invoice number gaps, suppliers missing an IBAN.
For Turkey, outbound e-Fatura and e-Arşiv now go through the Veriban integrator, and inbound purchase invoices are pulled from Veriban or Logo straight into draft supplier bills.
Documents that carry your brand, not ours
A voucher designer across seven verticals: brand colours, logo placement, letterhead or watermark, block order, and the fields printed inside each block — starting from Classic, Modern, Compact or Corporate. Write your own opening and closing note per language, with values like the hotel name or check-in date placed inside the text.
The same design renders on the PDF and on the online voucher page a guest opens from the QR code. Invoices got the same treatment: a branded standard layout or a block-level visual designer, embedded inside the e-invoice itself.
The agency network
Two Lydira agencies can now trade directly. One issues; the other’s books receive the ticket, its passengers and the invoice without anyone re-keying them. Nothing posts to your ledger until a person accepts it, and cancellations and time changes always wait for a human. Receiving is free on every plan; publishing is Studio and up.
Roles that actually close a door
Custom roles now switch off whole modules — a closed module leaves the menu and won’t open by typing the address — permission actions one by one, and mask cost, sell, personal data and passport numbers from the roles that shouldn’t see them. Masking holds in exports and reports, not only on screen.
Reports
23 preset reports, and the custom builder now covers 16 entities — every vertical, plus movements and complimentary grants. You can also describe the report in plain language and let AI assemble the configuration for you.
AI you can point at the wall
Beyond the credit ledger: a master switch, per-feature and per-data-class off, EU-only residency, and a lawful basis recorded per customer — choose “no processing” for someone and no call is ever made about them. Personal data is tokenised before a prompt leaves, and every call is logged with its basis.
The embedding model behind semantic search now runs on our own servers. The text behind “find me a similar trip” never reaches a third-party model — which is also why team search costs zero credits.
Trust
We split observability across two vendors: Sentry keeps errors, and AppSignal now handles performance monitoring — request and job timing, database queries, scheduled-job check-ins, uptime. AppSignal has been added to the sub-processor list accordingly. Exception messages are scrubbed of personal data before they leave, and where scrubbing fails the message is dropped rather than sent raw.