Philippines staffing blog
Accounts payable guides, page 13
Log the payment-file handoff without widening AP authority
Record what AP prepared, what treasury received, and which checks remain before upload and release.
Validate invoice dates without guessing what the supplier meant
Separate printed dates, receipt dates, service periods, posting dates, and policy decisions.
Give rush payment requests a controlled intake lane
Capture the business reason, evidence, timing, requester authority, and exceptions without promising payment.
Keep purchase order versions visible during invoice matching
Make quantity, price, terms, and closure changes inspectable instead of matching only against the latest screen.
Use a vendor alias register without merging distinct suppliers
Connect trading names and payment descriptors to approved master records while keeping uncertain matches open.
Check invoice file readiness before data entry
Define what to do with incomplete, unreadable, protected, altered, or mismatched invoice files.
Build a case file for returned supplier payments
Trace a returned payment through the bank event, supplier verification, correction, reapproval, and ledger outcome.
Maintain a recurring invoice expectation list that catches gaps
Compare expected invoices with received documents without treating a forecast as proof of liability.
Make every invoice hold—and every release—explainable
Keep the evidence, owner, aging, and release decision together when an invoice cannot move forward.
Close the gap between payment and remittance advice
Track whether usable remittance reached the right supplier contact without treating delivery as proof of application.
Review purchase orders before AP treats them as closed
Separate invoice matching facts from the business decision to close an order or release its remaining commitment.
Inventory vendor-portal access before it becomes invisible
Document who can enter supplier portals, what they can see or change, and when access must be reviewed.
Hand off supplier prepayments without losing the future schedule
Connect the original approval and cash event to delivery evidence, recognition dates, exceptions, and reconciliation.
Record which supplier contacts may answer which AP questions
Distinguish routine correspondence from instructions that require independent company verification.
Build invoice-accrual packets that survive the close
Preserve how an expected liability was identified, estimated, approved, posted, and later cleared.
Treat duplicate-payment recovery as a case file
Link the suspected duplicate, validated payment events, supplier response, recovery method, and final ledger result.
Keep foreign-currency invoice rate evidence with the posting
Show which date, source, rate, calculation, and policy owner support a converted invoice amount.
Check service-entry evidence without inventing receipt
Identify missing service confirmation and route it to the accountable business owner.
Route small AP balances without turning thresholds into permission
Prepare aged residuals and evidence while leaving write-off policy and accounting approval with named owners.
Use approval-return reasons that lead to a next action
Replace vague rejections with factual categories, retained comments, ownership, and a traceable resubmission.