# Processing stages

Processors are presented with a tabbed view of all their timesheets. Each tab is a collection of timesheets that are all in a particular state. Each state represents a stage in the processing work that's typically performed in a staffing agency.

{% hint style="info" %}
Not all users of Zipwire will work in this way, but they may have analogs to these stages in their own domain. In future, Zipwire will allow customization of these states and stages.
{% endhint %}

### New

Approved timesheets land in the new tab where they can be quickly screened for errors and accepted or rejected.

### Prep

Once accepted, there's normally some activities to be done to prepare to pay its sender, and potentially charge the end client. For some agencies, this may include drawing down money from a credit line to fund payroll. The client's invoice can be prepared and sent, too.

### Pay

Once these preparations are complete, the sender can usually be paid. Timesheets in this tab have not been paid and have a button to indicate payment has been made and move the timesheet on.

### Receive

In most situations, the contractor is paid well before the end client pays their invoice and so timesheets may sit in this tab for weeks. Each timesheet has a button to mark the sheet as having had its client moneys received, or that they are late.

### Late

Timesheets in this tab were marked late in the previous stage and need chasing or following closely by credit control.

### Done

Finally, timesheets with no further outstanding actions come to rest in the done state. At this point, they can be archived.


---

# 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.zipwire.io/zipwire-approve/processing-stages.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.