# Expense Policy Decision Engine

#### Enterprise finance teams face critical bottlenecks in expense management

* 100+ expense reports submitted weekly via **SAP Concur**
* Justification notes scattered across **Salesforce**, **Slack**, and shared docs
* Policy thresholds vary by **region, department, and role**
* Exceptions logged in outdated Notion pages or spreadsheet trackers
* Audit prep requires **manual review and custom dashboarding** in **PowerBI**

{% hint style="info" %}

#### This results in delays, confusion, policy violations, and compliance risk — every quarter.

{% endhint %}

## Features

<table data-view="cards"><thead><tr><th>Feature</th><th>Description</th></tr></thead><tbody><tr><td><strong>Live policy memory</strong></td><td>Tracks caps, exceptions, and thresholds by region, role, and scenario</td></tr><tr><td><strong>Bidirectional integrations</strong></td><td>Connects with SAP Concur, Salesforce, Slack, and audit tools seamlessly</td></tr><tr><td><strong>Automatic expense triage</strong></td><td>Handles approval, denial, flagging, and escalation workflows automatically</td></tr><tr><td><strong>Audit log generation</strong></td><td>Creates machine-readable logs for every decision with full traceability</td></tr></tbody></table>

## Before & After

| **Before GLIK**                                                            | **After GLIK**                                                          |
| -------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| A $412 dinner expense from the Singapore team is submitted in SAP          | GLIK detects the region and applies the updated $450 threshold          |
| Policy tracker says $300 is the limit, but APAC leads emailed a new policy | Updated policy is already stored in memory and applied automatically    |
| Reviewer digs through Slack, Salesforce, and Google Docs for justification | GLIK cross-references Salesforce for justification (“Q3 client summit”) |
| Decision takes hours or is approved with uncertainty                       | Flags entry as within policy and logs full audit justification          |
| No clear traceability or audit readiness                                   | Reviewer is notified via Slack with one-click confirmation              |

<figure><img src="/files/Voqo4RU103DnAJXYIoQ9" alt=""><figcaption><p>GLIK agents don’t just approve or reject — they interpret, classify, explain, and escalate based on live policy memory and enterprise-specific thresholds. The result: Consistent, compliant decisions — no manual bottlenecks, no audit guesswork.</p></figcaption></figure>

## Measurable Results

<table data-view="cards"><thead><tr><th>Metric</th><th>With GLIK</th></tr></thead><tbody><tr><td>Expense approval time</td><td>⬇️ 10x faster</td></tr><tr><td>Manual policy decisions</td><td>⬇️ 80% reduction</td></tr><tr><td>Policy violations per quarter</td><td>⬇️ 60–70%</td></tr><tr><td>Audit readiness time</td><td>⬇️ Days to real-time</td></tr><tr><td>Cost of preventable overages</td><td>⬇️ $100K–$500K saved annually</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glik.ai/enterprise-saas/expense-policy-decision-engine.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.