Finance operations where every invoice exception reaches the person who can resolve it

Mi Retail is an operations center that manages the human work around your finance systems. The accounting system or ERP keeps the ledger, invoices and payments; Mi Retail handles what happens when one of those records needs a person — an invoice that does not match, an approval, a missing receipt, a question for purchasing. Each of those situations becomes an Operational Work Item with an owner, a state, a due date and evidence, and it travels between finance, purchasing, branches and approvers until it is resolved. Finance sees what is blocked and why, and nobody has to chase anyone by email to find out.

No. Your accounting system remains the system of record for ledgers, invoices, payments, taxes and closing, and Mi Retail never keeps a second copy of the books. Mi Retail covers the part the accounting system was not built for: coordinating the people who must act when a record has a problem. The accounting system can tell you an invoice has a difference; Mi Retail manages who must resolve it, what it is waiting for, when it must escalate and with which evidence it can close. Keep your accounting system; Mi Retail takes over where the work leaves it.

When an invoice does not match its purchase order or goods receipt, accounts payable opens an exception work item that holds the whole case. From it, child work items go to the people who hold each missing piece: purchasing validates the price, the branch attaches the signed delivery slip, and the controller approves the difference if it is justified. Each child has its own owner and state, and a blocked item carries its reason, so everyone can see exactly what is missing. When the pieces are in, the exception closes with its evidence and the payment is scheduled in the accounting system.

An approval is a work item in the approver’s queue, with the case, the amount, the supporting documents and a due date, not a message buried in an inbox. The approver approves or rejects from the work item, and the decision is recorded with its reason. If the due date passes, the coordinator sees it as at risk and can reassign it or escalate it to the next level, which then receives the same context instead of a forwarded email. Leadership only sees the approvals that truly exceed the lower levels, so its attention goes to exceptions and not to routine sign-offs.

Month-end close depends on dozens of small pieces coming from other areas: receipts, accruals, reconciliations, approvals and explanations. In Mi Retail each of those pieces is a work item with an owner and a due date inside the close workspace, so the controller starts from a live list of what is done, what is waiting and what is blocked, and why. Instead of rebuilding status from spreadsheets and chasing people in the last two days, the team sees the risk early and acts on it. The accounting system still performs the close itself; Mi Retail makes sure the people behind it deliver on time.

Every work item keeps who acted, when, what they decided and which documents supported the decision. For an invoice exception, that means the original mismatch, the purchasing validation, the delivery slip, the approval with its reason and the payment reference, all linked to the same case. Control & Assurance lets internal or external auditors review those trails, record findings and request corrections without asking the team to dig through email. Because the evidence is captured while the work happens, the organization does not have to reconstruct it weeks later, and approvals can be shown exactly as they occurred.

People outside finance do not need to learn the accounting system. They receive the work items that need them — attach a receipt, confirm a delivery, explain an expense, approve a purchase — in their own My Work, alongside the rest of their day, with a clear description of what is needed and by when. When they finish, the work item returns to finance with the evidence attached. This is how finance stops being the department that chases everyone: the request reaches the right person with its context, and its state is visible to both sides until it is resolved.

Yes, when they have their own organization on Mi Retail. A request to a supplier — a corrected invoice, a credit note, a missing certificate — can be sent as a derived work item that lands in the supplier’s own queue; you follow its state and result without seeing their internal work, and your case closes when theirs does. An external accounting or audit firm can take part the same way, or as an external collaborator with a limited surface that only shows the shared work and the documents they must provide. Either way, the exchange stops depending on email threads that nobody can audit.

A CFO or controller does not need to follow every invoice. Operational Portfolio shows how the finance operation is doing: exceptions by age, approvals at risk, items blocked by other areas and the progress of the close. Executive Operations surfaces only what needs a decision at that level, such as a large exception, a recurring mismatch with the same supplier or a branch that keeps missing its evidence. Each item carries its context and history, so the decision can be made from Mi Retail without a meeting to reconstruct the facts, and the result is recorded for the next review.

The Finance suite of StoneOS brings apps for the domain work of finance — accounting, billing, receivables, payables, treasury, expenses, budgets, fixed assets, tax and consolidation — on top of the Business Core apps every team uses, such as Sheets, Docs, Drive, Chat and To-do. Those apps keep the depth of each financial domain. Mi Retail is where the work they generate meets the people who must act on it: a payable exception, an expense that needs approval or a budget overrun lands as a work item in the right person’s queue. If you keep your current accounting system, it stays the record and connects the same way.

Yes. In a small business the same person often requests, approves, pays and checks, and Mi Retail adapts to that: the experience collapses to the essentials, without approval chains or teams that do not exist. The value is still the same — every pending invoice, missing receipt and promise to a supplier is a work item with a due date instead of a note or a memory. As the business grows and responsibilities split between purchasing, branches and a controller, the same work items start moving between those people, and nothing has to be migrated or redesigned.

Start with the flow that costs the most follow-up: usually invoice exceptions or approvals. Create a finance workspace, invite accounts payable, purchasing and the approvers, and open the next exceptions as work items instead of emails. After a few weeks you will know where invoices wait, which approvals are slow and which areas are missing evidence. Then bring month-end close into its own workspace, connect the accounting system you already use and, if it fits, add the Finance suite apps from StoneOS. Mi Retail is free to start, so you can prove the value with one flow before extending it.