An invoice should move forward because it matches an authorized purchase and verified receipt, not because the supplier is familiar or the due date is close. A queue that merely forwards attachments can accelerate duplicates, unexpected price changes, and payment-detail fraud.
This workflow supports bookkeeping administration. The owner or authorized finance role approves spending, accounting treatment, disputes, and payment.
Register the invoice before routing it
Assign a queue ID and capture the supplier record, invoice number, invoice date, service period, purchase reference, amount, currency, tax, due date, location or department, submitter, and accounting-system reference. Store the document in the approved repository and link to it rather than attaching copies to several chat threads.
Check that the supplier name and legal or trading identity match the established vendor record. A familiar logo is not proof. If the sender, domain, or document format differs unexpectedly, mark the item for verification.
Separate received date from invoice date. Aging and service targets should use the event the business has defined, while preserving both facts.
Search for duplicates before doing detailed work
Compare supplier, invoice number, amount, date, purchase order, service period, and attachment hash where available. Suppliers sometimes resend the same invoice with "copy" in the title or a different email subject. A changed invoice number can still cover the same service.
Search paid, approved, rejected, and credit-pending records, not only the open queue. Record the possible match and let the authorized reviewer decide whether it is a duplicate, corrected invoice, or separate charge.
Do not delete the new submission. Preserve its receipt event and link it to the earlier record so the business can explain what happened.
Match order, receipt, and bill
Where the business uses purchase orders, compare what was authorized, what was received, and what was invoiced. Check item or service description, quantity, unit price, delivery or service date, tax, freight, discount, and total.
Receiving evidence should come from the person or system that observed delivery. A delivery note, asset record, service report, or approved completion can support the match. An invoice stating "work complete" is not independent receiving evidence.
For subscriptions and recurring services, compare the contract rate, billing interval, covered locations or users, renewal date, approved changes, and cancellation status. A recurring supplier is not exempt from review.
Keep discrepancies visible
Use specific exception reasons: missing purchase reference, no receiving evidence, quantity mismatch, price variance, duplicate risk, tax question, wrong entity, changed bank details, unapproved service, disputed quality, or credit expected.
State the amount affected and the person who can resolve it. Return clerical omissions to the requester, commercial disputes to the owner, and technical service questions to the receiving manager. Avoid a generic "on hold" state with no next step.
Preserve supplier correspondence in the controlled record. Do not rewrite the invoice or create an adjusted total merely to make it match. Corrections should come through the approved accounting route.
Verify payment-detail changes out of band
A new bank account, payment link, mailing address, or remittance instruction deserves a separate verification. Contact the supplier through a known number or established portal, not only the contact information printed on the changed invoice or included in the same email.
Record that verification occurred, who performed it, the known channel used, and the supplier contact. Keep bank details out of the broad approval queue and restrict them to the accounting system.
Urgency, secrecy, and requests to bypass normal approval are warning signs. Stop processing and notify the finance or security owner under the business's incident procedure.
Prepare the approval packet
Present the invoice, purchase authority, receiving evidence, match result, coding suggestion if the role permits it, due date, discounts, exception history, and requested decision. The approver should not have to search across inboxes to understand the spend.
Show the approver's limit and the amount already committed under the same order. Splitting invoices should not be used to evade an approval threshold. If several locations share the cost, record the approved allocation rather than guessing from the delivery address.
The assistant may suggest an established supplier or expense code, but the qualified accounting role confirms treatment where judgment is required.
Record approval as a distinct event
Approval should name the decision maker, date, amount, currency, scope, and any condition. "Looks fine" in a message can be captured only if it comes from an authorized person and clearly refers to the correct invoice version.
Rejected and partially approved items remain in history. State the reason and next owner. If a corrected invoice arrives, connect it to the rejected version rather than replacing the file silently.
Approval does not mean payment occurred. Move the invoice to the payment stage with its approved amount and required date.
Reconcile the payment result
After the payment run, capture the batch or transaction reference, date, amount, settlement state, and remittance event. Compare those facts with the approved invoice. Failed or returned payments need a new owner and should not appear as paid merely because they entered a batch.
Confirm that the accounting ledger and queue show the same balance. Watch for partial payments, withholding, currency differences, fees, and unapplied credits.
If the supplier says payment is missing, use the transaction reference and bank-confirmed status. Do not send screenshots containing unrelated payments or full account details.
Track credits to actual application
A promised credit is not a closed exception. Record the expected credit amount, reason, supplier reference, due date, and invoice it should offset. When the credit note arrives, verify and enter it through the accounting process.
Keep the item open until the credit is applied, refunded, or formally resolved. Review old credit-pending items separately; they often disappear from ordinary invoice aging reports.
The final packet should connect authorization, receipt, invoice, approval, payment, and credit outcome. That chain allows another reviewer to understand the transaction without relying on memory.
The FTC advises businesses to know what personal information they hold, keep only what they need, protect it, dispose of it securely, and plan for incidents. CISA recommends strong unique passwords and multifactor authentication. Apply those practices to accounting accounts, vendor portals, invoice exports, and offboarding. The listed sources were checked October 1, 2026.
A fitness virtual assistant can register invoices, check duplicates, assemble match evidence, route exceptions, and reconcile payment events. Spending authority, accounting judgment, disputes, bank-detail approval, and payment release remain with the operator. Put that boundary in the broader Fitness VA task list.