> For the complete documentation index, see [llms.txt](https://docs.techzala.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.techzala.com/home.md).

# Home

## TZone documentation

TZone gives growing businesses one place to manage travel requests, employee expenses, approvals, reimbursements, budgets, and spend visibility.

This documentation helps employees move faster, helps managers approve with context, helps finance stay in control, and helps admins keep the system clean.

### Start with the path that matches your work

#### New to TZone

1. [First-Time Login](/getting-started/first-time-login.md)
2. [Dashboard Overview](/getting-started/dashboard-overview.md)
3. [User Roles & Permissions](/getting-started/user-roles-and-permissions.md)
4. [Approval Workflow Basics](/getting-started/approval-workflow-basics.md)

#### Common actions

1. [Submit an Expense](/documentation/employee-guides/submit-an-expense.md)
2. [Upload Receipts](/documentation/employee-guides/upload-receipts.md)
3. [Create a Travel Request](/documentation/employee-guides/create-a-travel-request.md)
4. [Track Approvals](/documentation/employee-guides/track-approvals.md)
5. [Review Expenses](/documentation/finance-guides/review-expenses.md)

### Explore by role

#### Employees

Employees use TZone to submit business expenses, upload receipts, request travel approval, and follow reimbursement status.

Start in [Employee Guides](/documentation/employee-guides.md).

#### Managers

Managers use TZone to review spend, approve requests, protect budgets, and keep team workflows moving.

Start in [Manager Guides](/documentation/manager-guides.md).

#### Finance teams

Finance teams use TZone to validate policy, process reimbursements, monitor committed and actual spend, and prepare exports.

Start in [Finance Guides](/documentation/finance-guides.md).

#### Organization admins

Admins use TZone to manage users, departments, expense policies, travel rules, and approval routing.

Start in [Organization Admin](/documentation/organization-admin.md).

### What TZone helps you manage

#### Travel requests

Create pre trip requests before booking. Capture purpose, timing, and estimated cost early. Review budget impact before money is committed.

#### Expense management

Submit expenses with clear descriptions and receipts. Route requests through approval. Keep documentation attached to each record.

#### Reimbursements

Track each expense from submission to payment. Give employees visibility into status. Give finance a cleaner path to processing.

#### Budget control

Review planned, committed, and actual spend across departments, projects, and cost centers. Spot budget pressure before it turns into overspend.

#### Policy compliance

Apply receipt rules, category limits, and exception handling consistently. Keep a clean record of approvals and overrides.

### Popular topics

1. [How to submit an expense](/documentation/employee-guides/submit-an-expense.md)
2. [How travel approval works](/getting-started/approval-workflow-basics.md)
3. [How reimbursements move through finance](/documentation/employee-guides/reimbursements.md)
4. [How managers review requests](/documentation/manager-guides/review-requests.md)
5. [How budgets are monitored](/documentation/finance-guides/budget-monitoring.md)
6. [How data is exported for reporting](/documentation/finance-guides/exports-and-reports.md)

### Learn the fundamentals

#### Expense approval flow

1. An employee submits an expense.
2. A manager reviews the business purpose and amount.
3. Finance reviews the record when policy or workflow requires it.
4. Finance processes reimbursement.
5. The employee sees the final status.

#### Travel approval flow

1. An employee creates a travel request.
2. A manager reviews purpose, timing, and estimated cost.
3. Finance joins the review when required.
4. Travel is booked after approval.
5. Actual trip expenses are submitted later.

### Read deeper guidance

1. [The Complete Guide to Business Travel & Expense Management](/articles/the-complete-guide-to-business-travel-and-expense-management.md)
2. [Why Your Business Needs Travel & Expense Management Software](/articles/why-your-business-needs-travel-and-expense-management-software.md)
3. [Expense Policy Best Practices](/articles/expense-policy-best-practices.md)
4. [How to Reduce Travel and Expense Costs](/articles/how-to-reduce-travel-and-expense-costs.md)

### Need help

Use [Support](/support.md) for troubleshooting and access issues.

Use [FAQ](/faq.md) for quick answers.

Use [Release Notes](/release-notes.md) to track product and documentation updates.

### Need more help

Start with [Support](/support.md) if something is blocked.

Use [FAQ](/faq.md) if you want a quick answer.

Use [Articles](/articles.md) if you want deeper guidance and best practices.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.techzala.com/home.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
