> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/software-management/scoping-navan-contracts-with-gl-codes.md).

# Scoping Navan Contracts with GL Codes

Use Included GL codes to sync only your software spend from Navan as contracts, and choose how the application catalog filter works alongside it.

Navan records every expense your company pays: flights, hotels, meals and rides as well as software. Harmony turns that spend into contracts, one per vendor, so without scoping your Contracts page would fill up with travel and meals. **Included GL codes** tells Harmony which part of your Navan spend is software.

This guide explains what the setting does, how it works with the application catalog filter, and how to choose your codes.

***

### What a GL code is

Every expense in Navan is booked to a **general ledger (GL) code**, the account in your chart of accounts that your finance team uses to categorize spend. Most companies have one or two codes for software, for example `6100 Software Subscriptions` or `6105 SaaS Expense`, and separate codes for travel, meals and hardware.

Navan shows the GL code on each expense, and your finance or accounting team can tell you which codes mean software.

***

### What Included GL codes does

**Included GL codes** is a comma-separated list of GL code numbers on your Navan integration, for example `6100, 6105`.

| Setting                 | What Harmony syncs                         |
| ----------------------- | ------------------------------------------ |
| **Blank** (the default) | Every expense in Navan                     |
| **One or more codes**   | Only expenses booked to one of those codes |

When codes are set:

* **Expenses booked to other codes are left out**, so travel, meals and anything else never become contracts.
* **Expenses with no GL code are left out too.** Navan does not always require a code, so some card charges arrive uncoded. If a tool you expect is missing, check that its expenses carry one of your codes in Navan.
* **Matching is exact.** `6100` does not include `6100-01`. List every code you want, up to 50.
* **The contract value only counts in-scope expenses.** A vendor with some charges booked to software and others to a different code shows only the software charges.

***

### How it works with the catalog filter

Every contract integration in Harmony has a second setting, **Only sync contracts matching the application catalog**, which is on by default. When it is on, Harmony keeps only vendors that match an application in Harmony's catalog. The two settings work together:

| Included GL codes | Catalog filter | Result                                                                                                                                             |
| ----------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Blank             | On (default)   | Every vendor that matches the catalog, **including travel and food vendors that are also apps** (Uber, Lyft, Airbnb, DoorDash, airlines with apps) |
| Blank             | Off            | Every vendor in Navan. Not recommended                                                                                                             |
| Set               | On             | Software spend, limited to vendors in the catalog. Tools not in the catalog are left out                                                           |
| Set               | Off            | All software spend, including tools not in the catalog. **Recommended** once your codes are right                                                  |

{% hint style="info" %}
With GL codes set, the codes already do the software filtering, so turning the catalog filter off adds the software tools the catalog does not know yet. Leave it on if your team also books non-software items to the same codes and you prefer to miss a tool rather than see an odd entry.
{% endhint %}

***

### Set your GL codes

You can set the codes when you connect Navan, or change them at any time afterwards.

1. Ask your finance team which GL codes you use for software. Leave out codes that mix software with other spend, such as a combined hardware and software code, unless you want both.
2. In Harmony, navigate to **Settings** > **Integrations**.
3. Find **Navan** under **SaaS Procurement** and click the integration card.
4. Under **Included GL codes**, enter the codes separated by commas, for example `6100, 6105`.
5. Choose whether to keep **Only sync contracts matching the application catalog** on or off (see above).
6. Click **Save Changes**.

Harmony checks the connection to Navan when you save. The new settings take effect from the next daily sync.

{% hint style="warning" %}
**Set your codes before the first sync if you can.** Changing them later stops new out-of-scope vendors from syncing, but contracts that were already created stay in Harmony. Remove them from the Contracts page with the bulk **Ignore** action.
{% endhint %}

***

### Check the result

After the next daily sync, open the **Contracts** page and filter by the **Navan** source.

* **Travel or meal vendors still appear.** They were synced before the codes were set, or their expenses are booked to one of your codes in Navan. Ignore the contracts, and review the codes with your finance team.
* **A software tool is missing.** Its expenses may be uncoded or booked to a code you did not list. Check the expense in Navan, then add the code or ask your team to recode it. If the catalog filter is on, the tool may also not be in Harmony's catalog; turn the filter off or contact Harmony Support.
* **Values look lower than a monthly invoice.** A Navan contract covers the last 59 days of spend, the most history Navan's API provides, and has no billing cycle.

***

### Related articles

* [Navan integration](https://docs.harmony.io/integrations/saas-applications/navan)
* [Managing Contracts](https://docs.harmony.io/software-management/managing-contracts.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/software-management/scoping-navan-contracts-with-gl-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
