CONFIGURABLE FINANCE CONTROLS
Your policy, your rules. Extensible over time.
REME's fraud detection is the AI layer. The configurable controls layer is your finance team's layer. Two controls are live today. New controls are added quarterly based on customer requests. Recent additions include category ratio rules, location-aware rules, and time-of-day restrictions. This is how enterprise policy enforcement works when it does not require rebuilding your platform.
Two layers of protection at every claim submission
REME runs two parallel enforcement layers on every claim, before approval. Layer one is AI: six fraud detection agents looking for patterns your team would miss even with unlimited review time. Layer two is configurable controls: policy rules your finance team enforces manually today, running automatically through our engine. A claim only gets through if it passes both.
Layer 1: AI fraud detection
Six specialized AI agents. Pattern-based, learns from your data, gets more accurate over time. Duplicate detection, handwritten validation, currency mismatch, out-of-country, disallowed multi-currency, data mismatch.
Details on the six agentsLayer 2: Configurable finance controls
Rule-based, configured by your finance team, extensible over time. Two controls live today, more added quarterly based on customer requests. Your policy, enforced automatically.
See the controls belowLive in production today
Two configurable controls are live for all REME customers today. Both are configured during onboarding and can be adjusted anytime through the REME dashboard.
High-risk rules
What it does
Maintain a list of high-risk vendors, categories, or amount thresholds. Any claim matching an entry is automatically flagged for manual review before approval.
Common configurations
- High-risk vendor list: specific vendors that require manual review regardless of amount (previously flagged fraud attempts, vendors with billing disputes, etc.)
- Category blocklist: specific expense categories that always require manual review (alcohol, entertainment above threshold, cash advances, etc.)
- Amount thresholds: claims above a specific dollar amount always require senior finance approval, regardless of category
- Time-window rules: claims submitted after specific dates or cutoff windows automatically flagged
Use case example
A common example: a company blocks a specific taxi vendor after repeated overbilling. Any claim naming that vendor is auto-flagged for finance review. Finance sees the flag with the reason 'high-risk vendor' and can approve or reject with full context.
Auto-approval
What it does
Set pre-approved vendors and pre-approved amount thresholds for routine claims that should flow through automatically. Small routine expenses do not need finance attention.
Common configurations
- Pre-approved vendors: Uber, Grab, Ola, Starbucks, and other vendors your team uses regularly for routine expenses
- Amount thresholds per category: taxi under $30, coffee under $15, meals under $50, etc.
- Employee-role limits: junior employees have lower auto-approval thresholds; senior employees have higher
- Time-window auto-approval: pre-approved for specific business trip dates and locations
Use case example
A common example: your team's routine daily coffee and taxi expenses. Employee submits Grab receipt for $12. Vendor is pre-approved, amount is under threshold. Auto-approves. Finance never sees it. Employee gets reimbursed automatically. Finance time is preserved for the claims that actually matter.
Added quarterly based on customer requests
The controls layer is architected for extensibility. New controls are added to REME quarterly, based on what our customers actually need. When a finance team asks 'we need to enforce X policy automatically', we evaluate it for the next quarterly release. Some controls are added in weeks, some in months, depending on complexity. Recent additions and roadmap examples below.
Category ratio rules
Enforce percentage limits across expense categories within a single claim or over a period. Example: alcohol spend must not exceed 20 percent of food spend on the same client entertainment claim. Example: total conference expenses must not exceed 40 percent of business trip total.
Released Q1 2026
Location-aware (GPS) rules
GPS-based restrictions on specific expense types. Example: no taxi claims where the origin or destination is the employee's office. Example: expense claims only valid within authorized travel radius from client site.
Released Q2 2026
Time-of-day rules
Weekend and after-hours claim restrictions. Example: no meal claims outside standard business hours without pre-approval. Example: alcohol claims only after 6pm.
Released Q3 2026 (rolling out to all customers)
On the roadmap for Q4 2026 and beyond: multi-employee reconciliation rules, per-project budget enforcement, integration with company calendar for meeting-context validation. If your finance team runs a specific policy check manually today that you wish were automatic, mention it during your demo. Customer requests get evaluated for future quarterly releases.
How controls work alongside AI fraud detection
The two layers do different work. AI fraud detection catches patterns you might not know to look for. Configurable controls enforce policies you already know you need. Together, they cover the full spectrum of expense fraud prevention.
| Aspect | AI Fraud Detection | Configurable Controls |
|---|---|---|
| Nature | Pattern-based | Rule-based |
| Configuration | Learns from your data | Configured by finance |
| Detects | What you don’t know to look for | What your policy explicitly requires |
| Adapts | Continuously | On configuration change |
| Best for | Fraud you cannot describe in advance | Policy you can articulate |
Neither layer replaces the other. A claim submitted through REME runs through both layers. Approval requires passing both. Rejection by either layer flags the claim for finance review.
How your finance team configures controls
Controls are configured during onboarding and can be adjusted anytime through the REME dashboard. Three-step workflow:
Initial configuration during onboarding
During REME implementation (typically 1-2 weeks), our team walks your finance leaders through control configuration. We ask about your existing manual policy checks and translate each into a control. You review the configured controls before go-live.
Adjustment through dashboard
Any authorized finance admin can adjust control configurations through the REME dashboard. Add or remove high-risk vendors. Change amount thresholds. Update auto-approval limits. Changes take effect immediately for new claims.
Request new controls quarterly
If you need a control we do not offer today, request it through your account manager. We evaluate for the next quarterly release. Requests are prioritized based on how many customers would benefit and implementation complexity.
FAQ
Common questions about configurable controls
Yes. Controls can be configured at multiple levels: company-wide, per department, per employee role, per business unit. Configuration during onboarding sets up the hierarchy. Adjustments are made through the dashboard.
Same workflow as AI fraud detection catches. Finance sees the flag with the specific control that triggered ("high-risk vendor match" or "amount above threshold"). Finance can approve with a note explaining the exception. Legitimate exceptions are common; the control's job is to surface them for review.
Yes. Auto-approval thresholds are commonly adjusted based on observed fraud patterns and finance workload. If auto-approval is catching too many fraud attempts, tighten the thresholds. If auto-approval is not covering enough routine claims and finance is overwhelmed, loosen the thresholds. Data from your first 3-6 months of REME usage informs the right calibration.
Two starting points. First: an amount threshold above which all claims require finance review, calibrated to what your existing finance workflow can handle. Second: an auto-approval list for the top 5-10 vendors your team uses routinely (taxi services, coffee shops, mobile phone providers). These two alone typically cover 70 percent of routine expense volume while flagging the higher-value claims for attention.
Yes. New controls are added to the platform and immediately available to all customers. You do not need to upgrade or migrate. Your account manager notifies you when new controls are released and works with you to evaluate whether to enable them for your team.
Roadmap is discussed in the demo, not published publicly. Priority is based on customer request volume and implementation complexity. Roughly one new control category ships each quarter, plus refinements to existing controls.
See how controls work on your specific policy
A twenty-minute demo walks through the two live controls, recent roadmap additions, and how your finance team's existing manual policy checks translate to REME's configurable layer.