Philippines staffing research · Published
On this page
Invoice fraud controls in assistant-prepared payments
A review of the evidence an owner should require when an overseas assistant prepares vendor invoices for approval and payment.
Methodology
This review defines a documentary protocol for purchase and payable packets prepared by an assistant but approved by an owner. The unit is one invoice linked to its vendor record, purchase evidence, bank-detail verification, approval, and payment confirmation. Public guidance from the Federal Bureau of Investigation, NIST, and the Small Business Administration supplies the control vocabulary, not a claim about any organization's loss experience. The protocol records observable evidence and declared rules rather than estimating fraud rates. No live bank credentials or customer payment data were accessed. Findings describe a review design that an owner can apply, not a legal or accounting conclusion.
Key Stats
- 5: packet layers compared per invoice
- 3: public guidance sources reviewed
- 0: loss estimates made
Key Takeaways
- Verify a change to vendor bank details through a known phone number, not the contact information in the request.
- Keep the purchase order, invoice, receiving evidence, and payment approval in one packet so a mismatch is visible.
- Separate the person who prepares the payment from the person who releases it, even in a small team.
- Record the callback attempt and its result, including a failed or unanswered call.
Question and scope
This review asks whether an invoice packet gives an owner enough evidence to approve a payment without reopening every attachment. The population is vendor invoices prepared by an assistant for a small business, and the unit is one invoice linked to its vendor master record, purchase evidence, verification note, approval, and payment confirmation. The question is narrow because a payment packet serves both the decision now and the reconstruction later. Declare the inclusion rule before inspection so a disputed invoice is not quietly left out. Record the payment method and vendor type beside each result because a one-time wire and a recurring card charge carry different risks. The packet is the object of review, not the assistant's trustworthiness.
| Scope | Vendor invoices prepared by an assistant for owner approval |
|---|---|
| Unit | One invoice with vendor record, evidence, approval, confirmation |
The payment packet as the unit
A usable packet should stand on its own when the owner opens it on a phone. It needs the invoice, the purchase order or request, the receiving evidence, the vendor's remittance details, and a short note explaining any difference. It also needs the approval and the payment confirmation that followed. Treat those items as the minimum structure rather than optional attachments. A packet that requires a chat search to understand is incomplete even if every document exists somewhere. The protocol records the packet as a whole so a missing link is visible before money moves.
| Unit | Invoice, order, receipt, remittance, approval, confirmation |
|---|---|
| Standard | Readable without a chat search |
Vendor master data changes
A change to a vendor's bank account or remittance address deserves its own evidence trail. Record who requested the change, the channel used, the date, and the person who verified it. Compare the request with the existing vendor record and look for a mismatch in name, tax identifier, or contact details. The protocol flags any change that arrives close to an invoice or a payment run. A legitimate supplier can change banks, but the process should make an impersonator work harder than sending a new email signature.
| Change | Requester, channel, date, verifier |
|---|---|
| Compare | Name, tax ID, contact, existing record |
Callback verification
Verify a bank-detail change by calling a number already on file, not a number supplied in the request. Record the date, the person reached, the questions asked, and the result. If the call is unanswered, record that fact and hold the payment rather than treating silence as approval. The assistant may prepare the callback script and the evidence, but the owner or a second authorized person should make or confirm the call. The protocol treats a verification note without a source number as weak evidence. This single check prevents a common invoice-fraud path.
| Callback | Known number, date, person, result |
|---|---|
| Hold | Unanswered call blocks payment |
Segregation of duties
Map who can create a vendor, enter an invoice, approve it, release a payment, and change bank details. In a small team one person may hold several roles, so the protocol records the compensating review rather than pretending the separation exists. The assistant who prepares a payment should not be the only person who can approve or release it. If the owner is unavailable, name a backup with the same authority and a clear limit. The review looks for a single person who can complete the entire path without a second set of eyes.
| Roles | Create, enter, approve, release, change details |
|---|---|
| Compensation | Named backup and second review |
Exception routing
Define the exceptions that must stop the payment: a changed bank account, a new vendor, an invoice above a threshold, a missing purchase order, or a mismatch between the invoice and the receipt. Give each exception an owner and a response time. The assistant should route the exception with the evidence rather than asking an open-ended question. Record the decision and the reason so the next invoice from the same vendor does not restart the same debate. The protocol treats an exception that disappears without a decision as unresolved.
| Stops | Changed details, new vendor, threshold, mismatch |
|---|---|
| Routing | Owner, response time, decision recorded |
Threshold rules and approval limits
Set approval thresholds before the assistant prepares a payment, not after an invoice raises a question. A small routine bill may follow a lighter review, while a new vendor, a large amount, or a manual transfer needs a second approver. Record the threshold, the approver, and the evidence required at each level. The assistant should know which queue an invoice belongs to without asking every time. The protocol treats an unexplained exception to the threshold as a finding, because a rule that bends quietly is not a control. Revisit the limits when the business grows or a payment method changes.
| Threshold | Amount, approver, evidence required |
|---|---|
| Exception | Reason recorded and independently reviewed |
Reconciliation after payment
A payment is not complete when the transfer leaves the account. Reconcile the amount, the beneficiary, the reference, and the date against the approved packet. Record the person who performed the reconciliation and any difference found. If the payment fails or is returned, keep the original confirmation and the follow-up evidence together. The protocol samples closed packets to see whether the confirmation actually matches the approval. A tidy payment run can still hide a beneficiary that was never checked.
| Reconcile | Amount, beneficiary, reference, date |
|---|---|
| Evidence | Confirmation and exception kept together |
Review cadence and limits
Review a sample of payment packets each month and look for missing callbacks, unexplained vendor changes, and approvals that arrived after the payment. Do not use the review to grade an assistant's honesty; use it to find a process step that failed. Public guidance describes controls and common fraud patterns but cannot predict whether a particular business will be targeted. Pair the protocol with the bank's own verification tools and a qualified adviser for accounting or legal questions. The owner should know which rule changed and why. The packet is a decision aid, not a guarantee.
| Review | Sample size, fields checked, findings routed |
|---|---|
| Limits | Completeness is not a fraud guarantee |
The protocol stores the invoice, vendor record, callback evidence, approval, and payment confirmation for each packet. Completeness labels describe payment readiness only and say nothing about an individual's conduct.
Sources
- Federal Bureau of Investigation, Internet Crime Complaint Center: Public service announcement on business email compromise and payment fraud.
- NIST, Security and Privacy Controls: Control catalog covering access, audit, and segregation concepts.
- U.S. Small Business Administration: Guidance for small-business financial management.
- Federal Trade Commission: Consumer and business guidance on business email compromise.
FAQs
Can the assistant approve a payment after checking it?
Preparation and approval should be separate; the owner or a named second person releases the payment within a stated limit.
What if the vendor cannot be reached by phone?
Hold the payment and record the failed attempt; silence is not verification.
Does this protocol prevent all invoice fraud?
No. It creates checkable evidence and a stop point, but it cannot guarantee that every deceptive request will be caught.
Related Research
Plan the next step
Bring one payment packet and its vendor-change evidence to a bounded review of callbacks, approvals, and reconciliation.
Plan the next stepRead the daily blog guides · Explore service workflows · Plan your staffing routine
Test the next invoice packet against the eight checks, hold any bank-detail change for a callback, and record who released the payment.