Philippines staffing blog
Practical role and handoff guides.
Read concise guidance for scoping and managing Filipino support roles. Existing article addresses remain available.
September 14: Normalize invoice numbers without erasing the supplier record
Make invoice searches and duplicate checks consistent while retaining the value printed on the document.
8 min readSeptember 14: Investigate supplier credit balances before choosing a remedy
Build a source-linked worksheet for credits, overpayments, refunds, offsets, and unresolved supplier balances.
8 min readSeptember 14: Review split-coded invoices line by line
Keep allocation support, coding logic, approver responsibility, and later corrections traceable.
8 min readSeptember 14: Anchor supplier-statement reviews to a clear cutoff
Keep a reconciliation from mixing statement dates, ledger extracts, later invoices, and payments in transit.
8 min readSeptember 14: Log the payment-file handoff without widening AP authority
Record what AP prepared, what treasury received, and which checks remain before upload and release.
8 min readSeptember 14: Validate invoice dates without guessing what the supplier meant
Separate printed dates, receipt dates, service periods, posting dates, and policy decisions.
8 min readSeptember 14: Give rush payment requests a controlled intake lane
Capture the business reason, evidence, timing, requester authority, and exceptions without promising payment.
8 min readSeptember 14: Keep purchase order versions visible during invoice matching
Make quantity, price, terms, and closure changes inspectable instead of matching only against the latest screen.
8 min readSeptember 14: Use a vendor alias register without merging distinct suppliers
Connect trading names and payment descriptors to approved master records while keeping uncertain matches open.
8 min readSeptember 14: Check invoice file readiness before data entry
Define what to do with incomplete, unreadable, protected, altered, or mismatched invoice files.
8 min readSeptember 14: Build a case file for returned supplier payments
Trace a returned payment through the bank event, supplier verification, correction, reapproval, and ledger outcome.
8 min readSeptember 14: Maintain a recurring invoice expectation list that catches gaps
Compare expected invoices with received documents without treating a forecast as proof of liability.
8 min readSeptember 11: Normalize invoice numbers without erasing the supplier record
Make invoice searches and duplicate checks consistent while retaining the value printed on the document.
8 min readSeptember 11: Investigate supplier credit balances before choosing a remedy
Build a source-linked worksheet for credits, overpayments, refunds, offsets, and unresolved supplier balances.
8 min readSeptember 11: Review split-coded invoices line by line
Keep allocation support, coding logic, approver responsibility, and later corrections traceable.
8 min readSeptember 11: Anchor supplier-statement reviews to a clear cutoff
Keep a reconciliation from mixing statement dates, ledger extracts, later invoices, and payments in transit.
8 min readSeptember 11: Log the payment-file handoff without widening AP authority
Record what AP prepared, what treasury received, and which checks remain before upload and release.
8 min readSeptember 11: Validate invoice dates without guessing what the supplier meant
Separate printed dates, receipt dates, service periods, posting dates, and policy decisions.
8 min readSeptember 11: Give rush payment requests a controlled intake lane
Capture the business reason, evidence, timing, requester authority, and exceptions without promising payment.
8 min readSeptember 11: Keep purchase order versions visible during invoice matching
Make quantity, price, terms, and closure changes inspectable instead of matching only against the latest screen.
8 min read