One-tap approvals.
Zero email chains.

REME's routing engine considers four dimensions of every claim: (1) amount-based routing (different thresholds escalate to different roles), (2) category-based routing (software goes to IT, entertainment to account leads), (3) project-based routing (project tags route to project managers), and (4) policy-exception routing (violations route to whoever owns exception authority). Configure these rules once during onboarding; the engine handles every claim from then on. No more manual "who should approve this?" decisions.

24-hour auto-escalation kicks in. At T+0, the claim routes to the primary approver via WhatsApp + email. At T+12 hours, a reminder nudge. At T+24 hours, the claim auto-escalates to the configured backup approver (department head, secondary manager, or CFO). At T+48 hours, final escalation to finance leadership. The principle: claims don't sit indefinitely. Configurable per company -- adjust escalation timing for urgent claims (4 hours) or routine reimbursements (72 hours).

Yes. REME meets approvers in WhatsApp, email, or Slack -- wherever they already process work. WhatsApp is the most-used channel (90%+ of approvals in customers with WhatsApp-native workflows), with average decision time of 22 seconds. Email is the senior-approver default (1 minute 40 seconds average). Web dashboard is for power users batching through queues (12 seconds per claim in batch). Approvers see full context -- claim, policy status, employee history, rule check results -- before deciding.

End-to-end latency from submission to approver notification: 300-500 milliseconds. The approver's decision happens within 24 hours of submission for 90%+ of claims (industry benchmark for automated workflows shows up to 75% reduction in processing time vs manual approval flows). For routine claims under $500 with no policy violations, decisions typically happen within 4 hours during business hours.

Yes. Approval flows can vary by department, entity, project, region, or any combination. Engineering claims might route through the engineering manager + finance. Sales travel might route through the regional sales lead. International claims might route through local entity heads + global finance. The engine supports nested approval hierarchies and parallel approvals (e.g., manager AND finance both approve before payment). All configurable without code changes.

Every approval decision is automatically logged with the full context: the claim details, the rule check results, the approver identity, the decision timestamp, the channel used (WhatsApp/email/web), and any approver comments. Audit trail is permanent, queryable, and exportable to standard formats (CSV, JSON, PDF) for compliance review. SOC 2 Type II and ISO 27001 certified storage. Quarterly audit prep that used to take 40 hours typically drops to under 8 hours with REME's audit-ready trails.

Yes. The approval analytics dashboard surfaces (1) average decision time across all approvers and trends month-over-month, (2) which approvers consistently take longer than peers (often a routing problem, not a manager problem), (3) auto-escalation trigger rate (rising = primary approvers are dropping the ball), (4) policy-exception patterns by employee, and (5) approval velocity correlated with spend (slowing approvals = employees absorbing expenses themselves). Finance sees the bottleneck before it becomes a problem.

Approval routing is the third layer in a four-layer chain. Layer 1: WhatsApp submission captures the receipt and OCR-extracts data. Layer 2: Policy enforcement runs 5 rule categories in parallel (threshold, category, documentation, routing, timing). Layer 3: Fraud detection runs 7 AI agents in parallel (duplicates, fake receipts, merchant verification, etc.). Layer 4: Approval routing assigns the right human to make the final call. All four layers happen in under 400 milliseconds, before any approver sees the claim. Approval is the human-in-the-loop step after AI handles the rest.