Skip to main content
Approval is a separate axis from everything else in Financials. An invoice’s status records whether it has been paid. Its approval records whether anyone authorized paying it. The two are independent facts about the same invoice.

The Rule

Money cannot go out on an unapproved invoice. An invoice that requires approval must be approved before a payment can be recorded against it.

Which Invoices Require Approval

Approval protects a decision to send money out. Every Invoice Type, claims and policy alike, has one setting: Money-out invoices require approval.
  • Money out on a type whose setting is on requires approval.
  • Money out on a type whose setting is off does not.
  • Money in never requires approval, whatever its type: the payer already decided, so recording the payment states a fact.
Whether an invoice is money out comes from its own total, not from its type: a refund of an overpaid salvage is money out on a salvage invoice. A zero total follows its type’s expected direction. A new claims type starts with the setting on and a new policy invoice type with it off. Each invoice records whether it requires approval when it is created, so its history never depends on today’s settings. An invoice that does not require approval shows no approval badge and takes payments without one; nothing approves it, and an approval it already carries stays on record.

Changing the Setting

Change the setting where the Invoice Type is edited, under Admin → Financials. When the type already has open money-out invoices (draft, owed or partially paid) whose requirement would change, the app shows how many and how much is unpaid, and asks whether to apply the change to them too:
  • Turning approval on preselects applying it, so open invoices wait for approval before their next payment.
  • Turning approval off preselects New invoices only, so open invoices keep waiting for approval unless you choose otherwise.
Applying the change records it on each listed invoice, with who changed it and when. Paid, voided and deleted invoices are never changed. A change made through the API or a configuration import reaches new invoices only.

Approval Is Usually Implicit

When a user with authority to approve an invoice records a payment against one that requires approval, the app approves it as part of the same action. The approval is implied by the authority; no separate step is required. Approvals become visible in two situations:
  • The user lacks authority. The payment is refused, and the invoice stays unapproved until someone with authority approves it.
  • Approval and payment are done by different people. One person reviews and approves; another records the payment later.
For that second case, approval is also an explicit action: open an invoice and approve it, or select several in a listing and use Actions → Approve.
Full Update Invoice page for INV-339460-693 with the Actions menu open to Edit, Approve, Revert All Payments, and Void, plus its Owed status and line-item total

An open Owed invoice exposes Approve under Actions next to its Not Approved badge and line-item balance.

In the listing, Owed and Owed · Approved make the two axes visible side by side. Selecting an unapproved row enables Actions → Approve without changing the invoice’s payment-derived status.
Full company-wide invoice list with an unapproved Owed invoice selected, the Actions menu showing Approve, and complete Owed · Approved and Partially Paid statuses visible in neighboring rows

Approve is an explicit bulk action, while the Status column distinguishes Owed from Owed · Approved.

Approval Is Irrevocable Once Money Has Moved

Approval can be revoked — but only while the invoice is still unpaid. Once any payment has been recorded, the approval that authorized it cannot be taken back. Un-approving such an invoice requires removing its payments first, which returns it to Owed, and then revoking.
  • Approval is only ever removed deliberately. Nothing clears an approval as a side effect. Removing a paid invoice’s payments returns it to Owed and leaves it approved — it simply becomes revocable again. Leaving it unapproved requires a second, explicit step.
  • Editing an invoice does not reset its approval. What was approved — the type and the line item amounts — cannot change after creation, so an edit cannot change what was approved.
  • Approval is not part of the status. A Paid invoice is always approved, because money moved. An Owed invoice may be approved or not, and both are normal — the listing writes the approved case as Owed · Approved, the one place the two axes are shown together.
Approval is therefore asymmetric: it arrives implicitly, as a side effect of an authorized user recording a payment, and it leaves only on explicit request. That asymmetry ensures an approval is never lost by accident while the invoice is being worked on.

Configuring Approval Authority

Approval authority is set under Admin → Financials Configuration → Approvals. The Approvals configuration page shows how to create roles and assign company users to them. Two conditions decide who can approve an invoice in the app, and both must hold:
  1. Role permission. The person’s company role includes the Approve an invoice permission. Without it, no approval rule grants authority.
  2. Approval rules. By default there are no custom rules, so anyone with that permission can approve any invoice, of any Invoice Type and amount. This is the default before approvals are configured, and it suits a small team.
Enabling custom rules narrows the second condition. There are two parts:
1

Define roles

A role is a named level of authority. Each role sets a per-invoice-type ceiling — the largest amount someone with that role may approve on that type.
  • A type with a ceiling of, say, $5,000 → invoices up to $5,000.
  • A type with no limit → any amount.
  • A type set to $0, or not listed on the role at all → the role cannot approve that type at all.
There is also a built-in Financial Administrator role: unlimited authority over every Invoice Type, including types created later.
2

List approvers

Select a specific user from the company’s user directory and assign that person one role. Repeat this for each approver: different users can hold different roles, and each person’s authority comes from the limits on their assigned role. Anyone not on the list has no approval authority. Being on the list does not replace the first condition: an approver still needs a company role with the Approve an invoice permission.See the Approvals configuration page for the setup details and an example with different roles assigned to different users.
A custom role denies any Invoice Type it does not explicitly name. When a new Invoice Type is added, existing custom roles cannot approve it until granted authority — while Financial Administrators can approve it immediately. This is deliberate: new types start locked down.

API and Integration Callers

An invoice paid through the external API follows the same rule, resolved differently. A machine caller’s authority is its API key’s payment-approve permission — nothing else. Approval roles are matched by a person’s email address, which a machine caller does not have, so the company’s custom rules are never consulted for API traffic. A key with the permission auto-approves on payment, exactly as an authorized person does.