Treasury
Payment requests
The initiator asks for money, the route defines the signers, the treasurer pays.
Money leaves the company only against a request. A request goes from draft to payment, and before approval the product itself checks what a person can easily miss. Decisions are made on one request or in a batch.
Included in the “Business” edition and higherCompare editions
What is inside
- Statuses: draft, pending approval, approved, in register, paid, partially paid
- Rejection, withdrawal and return for rework with a comment
- Check for a new counterparty and an amount just under the auto-approval threshold
- Search for a similar recent request so as not to pay twice
- The remaining budget for the item right in the request record
- Limit policy: warn, add an approval step or block
Frequently asked questions
What happens if a request exceeds the item budget?
It depends on the limit policy: the product warns, adds an extra approval step or does not let the request proceed.
Can several requests be approved at once?
Yes. A decision is made on one request or on a selected batch, and the comment is saved in the history of each.
More in this section
See it on your own data
We will connect an export from your accounting system, set up the mapping and show how the feature works on real numbers.