A clearer employee expense journey
Capture receipts, currencies, mileage and cost allocations in one submission; optional local OCR only suggests fields for review.
Coordinate leave, employee requests and expense workflows in one clear experience. Keep approvals with the company. Firms can organize clients into named portfolios, while each user sees only individually assigned companies and authorized data.
Employees can submit expenses with currencies, mileage allowances and split analytical allocations; optional local receipt reading can prefill fields for human verification. The company reviews the file, and assigned accounting-firm users consult only the monthly indicators and documents their permissions allow. The next beta can co-design a request-to-correction and import-feedback loop with the firm; its accounting software and format must be selected first. A multilingual closing assistant answers a limited, cited set of questions about documented preparation signals for assigned companies; it does not review payroll variables or close accounts. The firm can also track manual line statuses, current totals across its 200 most recent accessible exports, and average time to the first response; timing starts with changes recorded after migration. OGRH has no direct accounting-software connection. Request tracking also makes the next responsible side and the time since the last recorded status visible.
Capture receipts, currencies, mileage and cost allocations in one submission; optional local OCR only suggests fields for review.
The firm can review four documented preparation signals, agreed target dates and permitted requests for assigned companies. A separate human-review signal can show changed, added or removed payroll-variable pair counts when both months are available; it is excluded from the preparation score and is not a payroll diagnosis. The firm can also ask the read-only closing assistant supported questions in French, English, Spanish, Italian or German; answers are cited and limited to assigned companies.
Clients implementing the Model Context Protocol (MCP) can consult selected data after authentication and server-side permission checks. Accounting-firm users can also follow technical transmission statuses for assigned companies, without transmitted content or employee identities.
Export and manually import generic client onboarding checklists and approval workflows between accessible cabinets or dedicated instances. Preview each model before applying it. Templates carry no employee records and create no accounts, permissions, companies or connectors.
Explore the cabinet setup guides →No. It complements your existing tools and keeps approvals in your configured workflows.
Not yet. Approved expense rows can be exported as generic CSV; the firm and company must validate the mapping and import. The export does not trigger payment.
The interface and conversation support French, English, Spanish, Italian and German. Some business content remains in its original language; cabinet message translations are optional and user-provided.
Only companies assigned to its account and data allowed by its separate permissions. Monthly indicators do not certify payroll or accounting close.