# Put the decision in the right hands.

Canonical page: https://finanzer.ai/business/approvals

> Review business payments with Finanzer. Keep the invoice, beneficiary, funding account, approval policy and decision record connected before release.

Prepare financial actions with the amount, beneficiary and supporting records attached. Route them to the responsible people and see whose approval is still needed.

## ‘Please approve’ should come with the details.

Give the approver the beneficiary, amount, currency, funding source and supporting record in the same review. A decision should refer to a specific financial action.

In the example, one approver has completed their review and one remains. The payment is still awaiting approval; it has not been released simply because a proposal exists.

## Decide who needs to decide.

Use your organization’s policy to define authority before a payment or change reaches the queue.

| Rule | Purpose |

| --- | --- |

| Threshold-based approval | Add the required review when an amount reaches a defined threshold. |

| Two-person approval | Require another authorized decision for a qualifying action. |

| Department ownership | Connect spending responsibility to the relevant team. |

| Beneficiary controls | Review the destinations approved for use. |

| Scheduled payment review | Keep the approval and intended payment date connected. |

## Apply oversight where money is committed.

The product’s approval model covers financial actions with different consequences.

### Payments and beneficiaries

Review where funds go and any new destination before a payment is released.

### Cards and limits

Treat issuing spending access or raising a limit as an authorization decision.

### Treasury allocations

Review moving money into a different access or risk category.

### Capital drawdowns

Connect use of a facility to the authority and conditions attached to it.

## Prepared. Reviewed. Then released.

Keep the state of the operation clear to everyone involved.

### Prepare the request

Attach the required details, source account and supporting records.

### Collect the required decisions

Follow the approval policy and show what remains outstanding.

### Track execution separately

Approval, processing and completion are different states. Follow the payment outcome after authority is granted.

## Designing your approval process

### Can the person preparing a payment be different from the approver?

Yes. Roles distinguish financial preparation from approval and oversight. Configure those responsibilities for your organization.

### Does an approval mean the money has arrived?

No. Approval is an authorization step. The operation still needs to be released, processed and completed through its payment route.

### Can Agent approve for someone?

The displayed Agent workflow can prepare a proposal, but it cannot independently approve or execute it. The required human authority remains in place.

### What should we define before a demo?

List the types of financial action, amount thresholds, departments and people who must approve. Include new beneficiaries and exceptions that need extra review.

## Make every approval an informed one.

Bring your decision rules and the handoffs that currently slow the team down.

[Discuss your setup](https://finanzer.ai/contact?topic=Business%20demo#enquiry)

[Explore payment operations](https://finanzer.ai/business/payments)