A bookkeeper enters bills, maintains vendor records and prepares payments for six clients. A saved bank login for each client sits in the browser. Nothing has gone wrong yet. But if one vendor email is fake or one password leaks, nobody stands between the request and the money leaving the account.
AP internal controls close that gap. For most practices, segregation of duties does not mean hiring. It means three things: the client approves, everyone uses their own login, and there is a record of who did what.
This guide gives bookkeepers a segregation of duties matrix for small teams, practical safeguards against accounts payable fraud and duplicate payments, and a controls checklist to run on every client.
AP internal controls are the approvals, access limits and reviews that make sure every payment is legitimate, accurate, authorized and traceable. They cover the full accounts payable process, from adding a vendor to reconciling the bank account.
The COSO Internal Control framework groups approvals, verifications, reconciliations and segregation of duties under "control activities." It pairs them with monitoring, which checks that those controls keep working over time.
Accounts payable internal controls come in three types:
The stakes are real. According to the ACFE's Occupational Fraud 2026: A Report to the Nations, organizations lose an estimated 5% of revenue to fraud each year, and the median case cost $104,000 USD. More than half of the cases involved either a lack of internal controls or an override of existing ones.
Bookkeepers often hold more access than anyone at the client except the owner. Three patterns drive most of the exposure:
When a payment goes wrong, the bookkeeper's reputation and the client relationship take the hit, even if the bookkeeper did nothing wrong. That is the liability bookkeepers carry when controls live in someone's head instead of in writing. A good control fixes this with three parts: an owner, a trigger and evidence that it ran.
Segregation of duties in accounts payable means no single person controls a payment from start to finish. Split the AP cycle into five stages and ask two questions at each one: who does this, and who checks it?
A segregation of duties matrix assigns each AP task to a named role so conflicting duties never sit with the same person unchecked. It works even for a team of two.
Can a two-person team segregate AP duties? Yes. The trick is counting the client as part of the control. In a solo practice, the "team" is the bookkeeper plus the client owner who approves bills and releases payments.
The matrix below covers three common practice sizes. The roles are illustrative, so adjust them to each client. Map the roles to how each client actually works, not to job titles.
|
AP duty |
Solo bookkeeper + client owner |
Growing practice (bookkeeper + senior reviewer + client) |
Established firm (junior and senior bookkeepers + client) |
|
Vendor setup |
Bookkeeper |
Bookkeeper |
Junior bookkeeper |
|
Verify vendor bank changes |
Client owner, by callback |
Senior reviewer, client confirms |
Senior bookkeeper, client confirms |
|
Bill entry and coding |
Bookkeeper |
Bookkeeper |
Junior bookkeeper |
|
Bill approval |
Client owner |
Client owner or manager |
Client manager |
|
Payment preparation |
Bookkeeper |
Bookkeeper |
Junior bookkeeper |
|
Payment release |
Client owner |
Client owner |
Client owner; second approver above threshold |
|
Reconciliation |
Bookkeeper |
Bookkeeper |
Junior bookkeeper |
|
Reconciliation review |
Client owner |
Senior reviewer |
Senior bookkeeper |
Compensating controls are extra checks that lower risk when one person has to hold two conflicting jobs. Match them to the practice size:
Owner-initiated payments and reimbursements deserve a second look at every size. The ACFE found that median losses caused by owners and executives were more than nine times greater than those caused by employees. Where the owner is the risk, recommend an outside review instead of asking the owner to approve their own requests.
Some pairs of duties let one person both commit a fraud and hide it. Never let one person, unchecked:
The engagement letter should spell out who does what and reference any written internal control procedures. Include:
State plainly that bookkeeping is not an audit or assurance engagement. Clear scope protects both sides if something goes wrong.
Most accounts payable fraud exploits a gap in approval, verification or review, not clever technology. The ACFE ranks billing schemes and cheque and payment tampering among the most significant fraud risks. Here are the schemes bookkeepers see most, and the controls that stop them. Several overlap with the most common payment fraud risks small businesses face.
A fake vendor is a shell business set up to collect payment for goods or services that never arrive. Padded invoices inflate the quantity or price on a real vendor's bill. A related trick splits one large invoice into several small ones to stay under an approval limit.
Watch for these warning signs:
Verify every vendor before activating it, and review the vendor list each quarter for duplicates and dormant records. Strong vendor payments management makes these checks routine instead of occasional.
Business email compromise (BEC) happens when a criminal spoofs or takes over a real email account and asks for payment to a new bank account. The RCMP notes that spear phishing, which includes BEC, remains one of the top reported scams among roughly 40 fraud types the Canadian Anti-Fraud Centre (CAFC) tracks. The CAFC reported that Canadian businesses lost more than $58 million to spear phishing in 2023.
In the AFP's 2025 survey of US organizations, 79% faced attempted or actual payment fraud in 2024.
A real-looking email thread is not verification. A common version, flagged by the federal Get Cyber Safe campaign, is a duplicate invoice from an existing supplier with "updated" payment details. Protect clients with three habits:
Cheque fraud includes altered payees or amounts, stolen or washed cheques and forged signatures. Payment tampering is the electronic version: someone edits a payment file after it was approved.
Moving vendors from cheques to electronic funds transfer (EFT) removes most of this exposure. ShelvingMate stopped cheque fraud after someone added an extra zero to a supplier cheque twice in one month. The company moved supplier payments online and kept final approval with its founder.
Speed limits the damage. In the ACFE study, frauds caught within six months had a median loss of $40,000 USD, while schemes that ran more than five years topped $1.1 million USD. If a payment looks wrong:
Investigation and recovery belong to the bank, police and forensic specialists. The bookkeeper's job is to stop the payment, protect the record and escalate.
You prevent duplicate payments by sending every bill through one intake channel, checking each bill against vendor, invoice number, amount and date before approval, and reconciling vendor statements and bank activity every month. Most duplicates come from process gaps, not fraud.
Most duplicates start in one of these gaps:
Every duplicate also eats time: finding it, chasing it and fixing the books. That labour adds to the cost of manual payments most practices already underestimate.
Payment automation enforces AP internal controls by building them into the workflow, so they run every time instead of whenever someone remembers. For bookkeepers, three features do most of the work:
AP automation software can enhance internal controls in the AP system. It does not replace the callback that verifies a bank change or the human review of a reconciliation. Treat automation as the enforcement layer, not the whole control system.
For a client-by-client approach to setting up approval rules, follow the AP automation implementation guide.
How Plooto helps bookkeepers keep controls in place
With Plooto, clients approve before money moves, so bookkeepers never need to hold a client's bank login again. Set custom approval rules and user permissions for each client, track every payment from creation to release, and sync bills and payments both ways with QuickBooks Online and Xero.
Plooto has completed a SOC 2 Type 2 audit and offers two-factor authentication; see Plooto security for details. It is accounts payable and receivable software built for practices that manage payments for many clients.
An AP controls checklist confirms each control actually ran, not just that it exists on paper.
Pick one recent payment cycle for each client. Include a new vendor and a bank-detail change if either happened in that period. For each control, look for proof: a log, an approval record or a signed reconciliation. "We always do that" is not proof.
Keep that proof. The Canada Revenue Agency generally requires business records to be kept for six years from the end of the last tax year they relate to, and approval and payment records support those books.
|
Control |
Evidence to check |
Result |
|
New vendors verified and approved |
Vendor approval record |
Pass / Partial / Gap |
|
Bank-detail changes confirmed by callback |
Verification log |
Pass / Partial / Gap |
|
Individual logins, no shared credentials |
User list and roles |
Pass / Partial / Gap |
|
Duties split or independently reviewed |
Matrix for this client |
Pass / Partial / Gap |
|
Bills supported and matched |
Bill and supporting documents |
Pass / Partial / Gap |
|
Duplicates screened |
Exception report |
Pass / Partial / Gap |
|
Client approval before release |
Approval history |
Pass / Partial / Gap |
|
Release limited to named people |
Payment release log |
Pass / Partial / Gap |
|
Bank and AP reconciled and reviewed |
Signed reconciliation |
Pass / Partial / Gap |
|
Exceptions and changes reviewed monthly |
Review log |
Pass / Partial / Gap |
Rank each gap by how much money could leave without anyone noticing.
Record the owner, target date and evidence for each fix, so next year's review can confirm it held.
Run the checklist when a client signs on and repeat it each year. Between reviews, track control exceptions per client: unverified bank changes, approval overrides and unresolved reconciliation items. A rising count is an early warning that a control is slipping. The implementation guide linked above covers rollout across a full client list and the KPIs worth tracking.
Strong AP internal controls come down to clear ownership. The client approves. Bank changes are verified by phone. Duplicates are caught before and after payment. Someone other than the preparer reviews the reconciliation.
None of this needs a bigger team. It needs a written split of duties and tools that enforce it.