Philippines AP staffing guide

Follow up a merchant credit on an employee expense report

Link the original charge, return evidence, expected credit, card statement, and employee response without netting unrelated expenses.

Published: October 2, 2026 · 12 minute read · Philippines-only staffing

Follow up a merchant credit on an employee expense report illustration

Direct answer

What this role should do

Link the original charge, return evidence, expected credit, card statement, and employee response without netting unrelated expenses. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

Open the case from the original charge

Record employee, card or reimbursement method, merchant, transaction date, posted date, currency, amount, report ID, business purpose, receipt, and approval. Keep the original expense unchanged while the credit is investigated. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

An employee returns a $740 monitor after the report was approved. The case links the approved charge rather than deleting it from the submitted report. The expense owner confirms the original transaction and return reason. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. Check the following statement cycle before treating a delayed credit as missing.

Document the return or cancellation

Collect the return receipt, cancellation notice, merchant case, shipment tracking, refund promise, expected amount, destination, and promised timing. Separate merchant acceptance from the employee shipping an item. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

Tracking shows delivery on Monday, but the merchant accepts the return on Thursday with a stated restocking fee. The employee or purchasing owner resolves commercial disputes about the accepted amount. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. If the merchant changes its answer, add a milestone instead of rewriting the first account.

Search the correct settlement record

Compare pending and posted card transactions, statement periods, processor references, reimbursement records, and cash receipts using approved access. Check both the original card and any replacement account identified by the card administrator. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

The refund does not appear on the current statement because it posted on the first day of the next cycle under a shortened merchant name. The card administrator confirms where the credit settled. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. Check the following statement cycle before treating a delayed credit as missing.

Reconcile partial and foreign-currency credits

Show original amount, refunded amount, fees, exchange effects, tax, and residual in their source currencies. Do not call a difference employee owed without owner review. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

A hotel refunds the room charge but keeps a cancellation fee; a foreign-currency credit also converts at a different rate from the original purchase. Finance determines the accounting for fees and currency differences. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. If the merchant changes its answer, add a milestone instead of rewriting the first account.

Prevent double recovery

Search employee repayments, payroll deductions, expense offsets, merchant credits, card disputes, and prior journals before proposing action. Link every recovery path to the same case. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

The employee already repaid the company while the merchant credit was pending. When the credit posts, finance must decide how to return or apply the excess. Finance approves any reimbursement, clearing entry, or payroll correction. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. Check the following statement cycle before treating a delayed credit as missing.

Close against the ledger and statement

Retain the posted credit, statement reference, approved treatment, system entry, employee communication, and any residual owner. Reopen the case if a provisional credit reverses later. Build the explanation around the employee transaction and merchant event, then compare it with the card or reimbursement record. Avoid netting the expected credit against another expense. Keep statement-cycle timing visible. AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

A card dispute creates a temporary credit that disappears after merchant evidence is reviewed, so the case stays open until the outcome is final. The finance owner confirms that the expense and credit are fully reconciled. Show the original charge, expected refund, actual settlement, difference, and current owner. Retain the employee statement and financial evidence in their approved systems. If the merchant changes its answer, add a milestone instead of rewriting the first account.

Continue with expense report review and the scope the AP support role.

Review the case before handoff

Source records and identifiers remain intact
Conflicts and missing evidence are stated precisely
The next decision and owner are named
Corrections preserve the earlier state
Preparation, approval, and release authority remain separate

Common questions

Accounts payable virtual assistant FAQs

What question should this employee expense merchant credit follow-up answer?

Did the merchant issue the expected credit, did it reach the correct card or account, and how should the company resolve any difference?

Which authority stays with the company?

AP support traces evidence and maintains the follow-up; the employee confirms the purchase event, card administrators trace card activity, and finance approves accounting treatment.

How should the workflow begin?

Start with a bounded sample, named source systems, explicit stop conditions, and review by the company owner before expanding the queue.

Factual checks

Sources

These sources support the tax-form, access-control, and phishing guidance in this article. The planning numbers above are labeled examples and do not come from these sources.

GAO Standards for Internal Control in the Federal GovernmentAuthoritative framework supporting documented transactions, review, and assigned responsibility.
NIST least privilege glossarySupports narrow preparation access and retained decision authority.
CISA guidance on phishingSupports verified communication paths when a message, sender, or request changes.

International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.