commit 96ae4a9245a455da36c4f9bcf97dc8564c8bd88d Author: dirk39e894987 Date: Fri Nov 20 15:49:08 2026 +0000 Add How to set dual approval for payments: the threshold question diff --git a/How-to-set-dual-approval-for-payments%3A-the-threshold-question.md b/How-to-set-dual-approval-for-payments%3A-the-threshold-question.md new file mode 100644 index 0000000..64c00e5 --- /dev/null +++ b/How-to-set-dual-approval-for-payments%3A-the-threshold-question.md @@ -0,0 +1,120 @@ +
Knowing how to set dual approval for payments starts with one question: how much could a single bad payment cost before anyone notices? The answer draws the threshold. Payments above that line go to a second approver, and so does every payment to a new vendor or a changed bank account, whatever the amount.
+ +Why one signature stops being enough as payments grow + +
One signature works while one person knows every vendor, every invoice and every amount that should leave the account. The trouble starts when the business adds staff, a second location or another bank account. The owner still signs, but she no longer reads each line, and that gap is where duplicate payments and invented invoices slip through.
+ +
The symptom is usually quiet. Cash sits lower than the books suggest, a supplier asks about a bill you thought was paid, or the month-end reconciliation turns up a transfer nobody remembers approving. Owners often blame the bookkeeper or the bank first. The likelier cause is simpler: nobody other than the person who keyed or released the payment looked at it before it left.
+ +
The correction is dual approval. A payment needs two people, usually one who creates it and another who releases it. The second person does not redo the bookkeeping. Their job is a short checklist: is this vendor known, does the amount match the invoice or contract, and do the bank details match what is on file?
+ +
Dual approval has limits, and it helps to say them out loud. A second signer who approves everything without reading adds a signature but no control. Two people who agree to misuse the process can still get around it. What the control does well is raise the cost of an honest mistake or a single-person fraud, and it leaves a record you can review later.
+ +
Bookkeeping tells you what happened to the money. Approval decides what gets to leave the account next. Confusing those two jobs is where many owners either pay for oversight they do not need or leave the door open because they assume the monthly review will catch problems. The monthly review catches them weeks later, when the money is already gone.
+ +Single approval or dual approval: where each one fits + +
Neither option is correct everywhere. Single approval can be reasonable for a small, stable set of recurring bills paid to vendors the owner knows well, especially when the amounts are predictable and easy to reverse. Dual approval fits better when payments are irregular, when the people releasing them change often, or when one error would strain the cash balance for the month.
+ +
Four criteria do most of the sorting. The first is size relative to cash: a payment that is a rounding error for one company can be a crisis for another. The second is reversibility. A card charge can sometimes be disputed, but a wire to the wrong account often cannot be recalled in time. The third is novelty, since a payee you have never paid before deserves a second look no matter how small the bill. The fourth is how many people can touch the money.
+ +
Consider two hypothetical companies with the same monthly payroll. The first has one operations manager who pays vendors from a single online bank login. The second has three managers, two bank accounts and a supplier list that changes every quarter. The first may be fine with single approval on routine bills and a short list of exceptions. The second is more exposed, because no one can say with confidence who saw each payment.
+ +
A useful test is to ask who would notice a wrong payment and how long it would take. If the answer is "the owner, during the weekly review, if she happens to look," the control is weaker than it feels. If the answer is "a second person, before the payment leaves the bank," you have dual approval in practice, even if the software does not label it that way.
+ +
Mixed models are common and often sensible. Routine recurring payments may run through a simpler path, while new payees, large amounts and changes to bank details always need a second person. The goal is not to pick one model for the whole company. The goal is to write down which payments follow which path, so the rule does not depend on memory.
+ +Finding the threshold from your own payment history + +
The threshold should come from your own records, not from a round number someone else chose. Export a year of payments from the bank or accounting system, sort them by amount, and look at the shape of the distribution. Many businesses find that most payments are small and routine, while a few large ones carry most of the risk. The threshold belongs between those two groups.
+ +
Start with a question you can answer: what is the largest single payment the business could absorb in one month without missing payroll or a loan payment? If that figure is a meaningful share of a normal month's cash, the threshold should sit well below it. If the cash cushion is thick, the threshold can be higher. This is an operating decision, so write it down with the date and the reason, and the next person will understand it.
+ +
Imagine a hypothetical services firm that pays most vendors between 300 and 2,000 dollars, with a few equipment purchases around 15,000 dollars each. Its owner sets the threshold at 2,500 dollars. Routine bills go through a single release, while the equipment purchases always need two people. The rule is simple to explain, and the second approver is not buried in small invoices.
+ +
Be careful with the threshold's shape, because a single cutoff can be gamed. If the rule is 2,500 dollars, someone who wants to slip past it may split a 4,000 dollar invoice into two payments of 2,000. Good thresholds come with a rule against splitting and a review of payments that cluster just under the line. Those clusters are often the first sign that the threshold is being tested.
+ +
Revisit the threshold when the business changes: a new location, a larger loan, a growth round or a shift in how many people can release payments. A threshold that made sense for a team of four can be too loose for a team of fourteen. Keep the reasoning in a short document beside the rule, so a future controller or advisor can see why the number is what it is.
+ +Payments that need a second approver regardless of amount + +
Some payments should never depend on the amount alone. The risk comes from what the payment does, not only how much it moves. Most businesses should keep the following on an always-review list:
+ + +A payment to a vendor or payee that has never been paid before. +Any change to a vendor's bank account, remittance address or contact details. +Changes to payroll records, direct deposit information or employee pay rates. +Transfers to owners, shareholders or related parties. +International wires and payments in a currency other than your operating currency. +Refunds, credits and manual journal entries that move cash or reduce a payable. + + +
The bank-detail change deserves the most attention, because it is a common route for fraud. A message that appears to come from a supplier asks you to send future payments to a new account. It looks routine, and that is the danger. The safe habit is to confirm the change through a phone number already on file, not the number or email in the new request, and to require a second person to approve the update before any payment goes to the new account.
+ +
Payroll is different from vendor payments and often needs its own path. The people who can add an employee or change pay rates should not be the same people who release payroll. Many small companies ask one trusted person to do both, which is efficient until a mistake or a dispute goes unchecked. Separating those roles, even partly, makes the record easier to audit.
+ +
Payments to owners and related parties are often the most sensitive. They are rarely wrong in an obvious way, and they can be entirely legitimate, such as repaying a shareholder loan. The approval step is less about suspicion and more about documentation. A second approver should be able to see the reason and the agreement behind the payment, so the transaction is explained when an auditor, lender or buyer asks questions later.
+ +
Write the always-review list down and keep it close to the approval settings. Lists kept only in someone's memory tend to shrink over time, usually after a busy quarter when an exception seemed harmless. A short written list with dates protects the company and gives the next person a clear starting point.
+ +Who should hold each role, and why the roles must stay apart + +
Dual approval works only when the two people are actually separate. The core idea is segregation of duties: the person who records a bill, the person who releases the payment and the person who reconciles the bank account should not all be the same person. When one person does all three, the company has no independent check, no matter how many screens show an approval button.
+ +
A practical setup for a small team has three roles. One person prepares the payment, usually the bookkeeper or an accounts payable clerk. A second person approves it, typically the owner, a manager or a finance lead with authority over the account. A third person, separate from both, reconciles the bank statement each month and looks for payments that do not match an approved invoice.
+ +
The approver must have the authority and the information to say no. Approving a payment because the bookkeeper sounds confident is not a control. The approver should see the invoice or contract, the payee and the amount, and should feel free to reject a payment that lacks support. Companies that treat approval as a formality usually discover this only after a payment they should have stopped has already gone out.
+ +
Watch for the approver who is also the person who wants the payment made. A department head who requests a purchase and then approves it creates a loop with no outside check. The fix is to route the request to someone above or beside that role, [what is part-time CFO services in Miami](https://Venturegrowthpartners.com/locations/florida-miami-part-time-cfo-services/) even if it adds a day to the process. Delay has a cost, but an unchecked purchase is usually more expensive.
+ +
Limit the number of people who can release payments and keep access current. When someone leaves, their bank login and approval rights should close the same day. Review the access list every quarter. Many companies find old users still able to approve payments because nobody removed them when their role changed.
+ +Setting the rule inside your bank portal and accounting software + +
Most business banks and accounting platforms offer some form of approval workflow, but the features vary and are easy to misread. QuickBooks, NetSuite and Sage Intacct each handle bill approval and payment controls differently, and bank portals have their own user roles and dual authorization options. Before you rely on any of them, [read This Article](https://Venturegrowthpartners.com/locations/florida-miami-part-time-cfo-services/) the current documentation for your version and confirm what the system actually enforces, not what the button label suggests.
+ +
The most useful test is a controlled one. Create a test vendor or use a dummy record, submit a payment that should require a second approval, and confirm that the system holds it until the second person acts. Then try the forbidden path: have the same user approve their own request, or change a bank detail and see whether the system flags it. If the software lets you bypass the rule, the rule is only a suggestion.
+ +
Check how the rule interacts with the bank. Some setups approve payments inside the accounting system but release them through the bank with a single login. In that case, the accounting approval is a useful record but not a full control, because the bank does not know who approved what. Map the whole path from bill entry to money leaving the account, and mark each point where a person must act.
+ +
Keep settings in writing. Export or screenshot the role assignments, the approval thresholds and the list of users with release rights, and store them with the date. This helps during an audit, a lender review or a change of staff. It also helps you catch drift, because a settings export from January can be compared with the live system in June.
+ +
Do not let software choose the threshold for you. Platforms ask for a number, and whoever fills in the field often picks a default or the first figure that comes to mind. The threshold is a finance decision. It should be set by the person accountable for the cash position, checked against payment history and recorded where the team can see it.
+ +Where a part-time CFO, a controller and a bookkeeper each fit + +
Owners often ask who should design the approval rule, and the honest answer depends on the company. A bookkeeper keeps the records accurate and usually prepares payments. A controller owns the close, the internal controls and the reconciliation process. A part-time or fractional CFO looks at cash, forecasts and the link between payments and the plan. An accountant often handles tax filings and may review controls, but is rarely the person who runs them day to day.
+ +
The table below compares these roles on criteria that matter for what is part-time CFO services in Miami dual approval. It is a general guide, not a description of any firm's staff or scope. Actual responsibilities depend on the contract, the size of the team and the systems in use.
+ + + +RoleUsually ownsUsually does not ownFit for dual approval + + +BookkeeperRecording bills, preparing payments, keeping vendor filesSetting the threshold, final release authorityPrepares payments and flags exceptions +ControllerMonth-end close, reconciliations, written control proceduresLong-range cash planning, financing decisionsDesigns the workflow and audits it +AccountantTax filings, year-end statements, tax planningDaily payment flowReviews controls for tax and reporting purposes +Part-time CFOCash forecasting, the link between payments and the plan, the threshold decisionDaily data entry, routine approvalsSets the threshold and reviews exceptions with leadership + + + +
The overlap is where companies get confused. A part-time CFO can set the threshold and review trends, but may not want to approve daily payments, and a bookkeeper should not be left to decide how much risk the company accepts. Clarity about who decides what prevents two problems: paying senior time for routine work, and leaving a gap that nobody owns.
+ +
Consider what happens when an engagement ends. If the threshold, the always-review list and the access settings exist only in an advisor's notes, the company loses them the day the arrangement stops. Ask for written procedures that the internal team can run alone, [[empty]](https://silatdating.com/@nora0528632531) and make sure at least one employee understands why each rule exists. A good handover is measured by whether the process still works without the advisor.
+ +
Integration with an existing accounting team needs a plain agreement about who approves what. If you already have a controller, the CFO's role might be to set policy and review exceptions, while the controller runs the workflow. If you have only a bookkeeper, the owner may need to take the approver role for a while, with a clear plan to add a second person. Nothing here requires one specific arrangement. It requires one that is written down and followed.
+ +
Compare the cost of each option carefully, but do not judge it by job title alone. A controller who runs the control daily and a part-time CFO who sets policy are not interchangeable. The better question is which person would catch the problem you most fear, and how quickly they would act. Fees, timing and terms vary by firm and situation, so get them in writing from each provider rather than relying on general estimates.
+ +The costliest mistake: a threshold nobody reviews after it is set + +
The most expensive mistake in dual approval is rarely the wrong number on day one. It is setting a threshold once, forgetting it and letting the business outgrow it. The symptom is a control that looks active on paper while the real payment flow has moved somewhere else: new bank accounts, new suppliers, a second team that releases payments without the rule. Nobody notices, because nobody is asked to look.
+ +
The likely cause is that approval settings feel like technical setup rather than a management decision. The IT or operations person configures them, the owner signs off once, and the matter goes into a drawer. Meanwhile, payment volume grows, staff turns over and a supplier changes banks. A threshold that protected a small team can leave a larger one exposed, especially when many small payments add up to a large total.
+ +
The correction is a short, scheduled review. Once a quarter, pull the approval report, compare it with the bank statement and check three things: whether every payment above the threshold had a second approver, whether any payments clustered just below the line, and whether anyone with release rights has changed roles. Record the date, the reviewer and any change made. The review takes less effort than most owners expect, and it creates the evidence that a lender, buyer or auditor will ask for.
+ +
Reviews also show whether the people involved understand the rule. If the second approver cannot explain why a payment needed review, the control is not working as designed, even if every box is ticked. Use the review to ask simple questions, and update the written procedure when the answers reveal a gap. A procedure that matches the way people actually work is more useful than a perfect one nobody follows.
+ +
Keep this mistake in view when the business changes. A new location, a financing round or a planned sale all alter the risk profile, and each one is a moment to reset the threshold and the always-review list. Set the date of the next review before you finish this one, and assign it to a named person. A rule that someone owns will outlast the advisor who helped design it, and that is the outcome that matters.
\ No newline at end of file