Bill Pay Approval Workflow Settings

One approval requirement for every payment: Applying the same approval rule to low-value and high-value payments may not reflect the company's internal authorization policy.

No required sign-off from key stakeholders: An approval-count requirement alone may not capture the need for sign-off from a finance lead or another designated decision-maker.

Limited flexibility in the maker-checker process: Different teams may have different requirements for reviewing payment details before approval.

No defined processing window: Without a review or approval deadline, payment requests may remain pending until a team member takes action.

Amount-based approval tiers: Set a single-approver limit. Payments within the limit can be approved by any one assigned approver, while payments above the limit follow a multi-approver workflow.

Configurable approval quorum: Define the number of approvals required for payments that meet the quorum-rule threshold.

Mandatory approver support: Require sign-off from a designated approver in addition to satisfying the overall approval count.

Optional maker-checker review: Assign a reviewer to check payment details before approval, or select [Skip this step] when a separate review is not required.

Additional workflow controls: Configure review deadlines, approval deadlines, a small test payout for eligible on-chain withdrawals, and verification rules for consecutive payments. Available options are subject to the settings displayed on the page.

Sign in to Infini Business and expand [Settings] in the left-hand navigation menu.

Click [Approval Settings].

Select [Bill Pay] to view the current approval workflow.

The workflow contains four stages: [A team member submits a payment request], [Creation check], [Payment approval], and [Transfer completed].

Locate [Creation check] in the workflow.

Keep this stage enabled if payment details should be reviewed before approval.

Click [Edit Role] to review or update the assigned [Reviewer(s)]. Any one assigned reviewer can complete the check.

To limit the review window, select [Set a deadline] and configure the [Review deadline].

If a separate maker-checker review is not required, select [Skip this step]. The request will proceed directly to [Payment approval].

Select [Standard] under [Payment approval].

Click [Edit Role] to review or update the assigned [Approver(s)].

Under the standard configuration, any one assigned approver can approve the payment.

Configure [Small test before on-chain withdrawal payment] and the [Approval deadline] if required.

Click [Save Changes] at the bottom of the page.

Select [Advanced] under [Payment approval].

Click [Edit Role] and confirm which team members are assigned as approvers.

Under [Approval rules], configure approval-exempt, any-one, and quorum rules by payment amount. At least one of [Any-one rule] or [Quorum rule] must remain enabled.

Enable [Any-one rule] and define its payment amount range or single-approver limit. Payments within this range can be approved by any one assigned approver.

Enable [Quorum rule]. Define the applicable payment amount range and the number of approvals required.

Where supported, designate a [Mandatory Approver]. The payment must satisfy both the approval-count requirement and the mandatory-approver requirement.

Check for overlapping or uncovered amount ranges. Confirm that the [Current rules] summary reflects your intended workflow.

Enable [Small test before on-chain withdrawal payment] if you want the workflow to initiate a smaller test payout when a transfer reaches the configured trigger threshold. The trigger threshold is not the test payout amount.

To use [Skip verification for consecutive payments], confirm that the workflow uses [Any-one rule]. After three verified payments are completed within ten minutes, subsequent any-one payments may skip email or TOTP verification for the configured period.

[Skip verification for consecutive payments] cannot be enabled together with [Quorum rule]. Disable this option before using a multi-approver workflow.

To limit how long a request can remain pending, select [Set a deadline] and configure the [Approval deadline]. Without a deadline, the request will continue waiting for approval.

Review the creation-check setting, assigned approvers, amount ranges, required approval count, mandatory approver, and payment security options.

Click [Save Changes].

After saving, review the rule summary and toggle states to confirm that the intended configuration is displayed.

Align thresholds with your authorization policy: Set the single-approver limit based on your company's payment policy and typical transaction sizes.

Maintain sufficient approver coverage: Avoid setting the quorum above the number of available approvers. Consider planned leave and other availability constraints.

Assign mandatory approvers carefully: A payment will remain pending if the mandatory approver has not approved it, even when the required approval count has otherwise been reached.

Review roles and rules regularly: Update reviewers, approvers, amount thresholds, and mandatory approvers when team responsibilities or authorization policies change.

Use verification exemptions selectively: Before enabling [Skip verification for consecutive payments], confirm that the option is appropriate for your single-approver workflow and internal operating procedures.

Q: What is the difference between [Standard] and [Advanced]? A: [Standard] allows any one assigned approver to approve a payment. [Advanced] supports amount-based any-one and quorum rules, configurable approval counts, and mandatory approvers.

Q: Can [Any-one rule] and [Quorum rule] be enabled at the same time? A: Yes. You can apply them to different payment amount ranges. For example, payments within the single-approver limit can use [Any-one rule], while payments above that limit can use [Quorum rule]. At least one of these rules must remain enabled.

Q: If the approval count has been reached, can a payment proceed without the mandatory approver? A: No. When a mandatory approver is configured, the request must meet the approval-count requirement and receive that approver's sign-off before completing the internal approval workflow.

Q: Does selecting [Skip this step] remove payment approval? A: No. It skips only the [Creation check] stage. The payment request remains subject to the rules configured under [Payment approval].

Q: What happens if no review or approval deadline is configured? A: The request will remain pending until an assigned reviewer or approver takes action. Consider setting deadlines based on your team's processing requirements.