> For the complete documentation index, see [llms.txt](https://echelp.weaver.com.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://echelp.weaver.com.co/workflows/7-practice.md).

# 7 Practice

## Design a reimbursement workflow

Please follow below instruction to design a new workflow

The form should include applicant, department, application date, document number, relevant project, relevant customer, currency, total amount, total tax amount; a repeat table to support user to input multiple invoice record\[Invoice date, invoice number, description, supplier, category, original currency, invoice currency, exchange rate, tax amount, total amount, attachment]

All the staff able to initial the request, after submit the request, department head should approval first, if the total amount less than 5,000SGD, then follow to finance team, else if total amount more than 5,000SGD, need division manager approval, if amount more than 20,000SGD, need VP approval, then flow to finance manager. After the process complete, requester can print the request as pdf file, please design a proper print template in word template

Create a report to analysis the expense by category, by department, by month


---

# 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://echelp.weaver.com.co/workflows/7-practice.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.