☜ Finance Street
YI.FLOW
Try the Demo ➜

Your finance team doesn't need to be in one place.

Yi.Flow is the workspace we built for our own accounting firm — connecting tickets, tasks, chat, team load and approvals across every timezone, without replacing the systems already in use. Here's what a normal day looks like.

Cover — Your finance team doesn't need to be in one place. Your work does. A finance manager and her team give a thumbs up as Yi and AI Agent Yi hover above a world map. Yi.Flow — the global finance team workspace. Episode 1 — Yi Never Sleeps. Different countries, different time zones, one finance team: India 6:30am, Singapore 9am, Vietnam 8am, Korea 10am. The Singapore finance manager opens Yi.Flow and sees tasks by status, my tasks, and recent activity in one dashboard — 'I can see everything!' She wonders who is doing what, who is overloaded, and what needs her approval, while her India, Korea, Vietnam and Singapore teammates each work from their own office. 'So many tickets to assign...' 'Leave the assigning to us!' Yi transforms into AI Agent Yi — AI mode activated. Episode 2 — Every client request is accounted for; nothing sits unseen in Gmail. A client email arrives and AI Agent Yi turns it straight into a ticket — client, subject, category and summary captured, ticket created and assigned. Task progress moves from open to accepted to in progress. When a teammate asks a clarifying question, a clarification-requested alert notifies the right person automatically — no need to chase. The discussion thread keeps the question and answer together, clarification resolved, and the draft reply is approved and sent, source email archived, ticket closed. Yi.Flow — email in, work out. Episode 3 — @Your Assistant greets the finance manager each morning with what needs attention: overdue items, items due today, and a team escalation. The Team Load view shows Alex overloaded and Jamie with capacity, with a one-click chat button next to each teammate — 'someone may need help.' She opens a chat with Alex without leaving the Team Load screen, finds the client in the Client Directory without switching workspaces, and mentions @Jamie in a new chat; the assistant suggests turning that mention into a task, coaching the user and confirming intent rather than silently creating one. Task created, Jamie accepts, team load updates. Yi.Flow — work together without changing workspaces. Episode 4 — It feels just like the chat the team already knows, but it understands how finance teams work. A message in #accounts about Northstar Trading's month-end closing becomes a task with client, function, assignee, deadline and documents attached — conversation captured, task created. The task detail panel keeps the original creator, assignee, deadline, description, documents, discussion and activity together: 'the task remembers more than the message.' When Alex is overloaded, the task is reassigned to Jamie with a handover summary of what's done and what's outstanding, so Jamie can continue from there. Teammates in Singapore, Vietnam, India and Korea each work their piece — accounts, closing, tax, review — on one shared task, and the full activity trail shows everyone what already happened. Yi.Flow — chat where the work lives. Episode 5 — Why don't the balances agree? A Horizon Group consolidation shows a $4,000 mismatch between the Singapore receivable and the Vietnam payable. An intercompany reconciliation task is created and assigned to Singapore Group Finance and Vietnam Local Accounts with supporting schedules attached — issue captured, teams connected, no separate email chains. The two teams discuss directly on the task with ledger, invoice, payment and reconciliation attachments; an AI fact summary identifies the $4,000 difference and the invoice missing from Vietnam's books, and a human reviews and approves the adjusting entry. Singapore, Vietnam, India and Korea each confirm their piece of the same consolidation task. Balances agree, and the explanation stays with the task. Yi.Flow — one group, one context. The ledger holds the number, the task holds the reason.

See it for yourself.

Read the story, then take Yi.Flow for a spin — no sign-up needed.