Philippines staffing blog
Accounts payable guides, page 12
September 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.
September 14: Check invoice file readiness before data entry
Define what to do with incomplete, unreadable, protected, altered, or mismatched invoice files.
September 14: Build a case file for returned supplier payments
Trace a returned payment through the bank event, supplier verification, correction, reapproval, and ledger outcome.
September 14: Maintain a recurring invoice expectation list that catches gaps
Compare expected invoices with received documents without treating a forecast as proof of liability.
September 11: Normalize invoice numbers without erasing the supplier record
Make invoice searches and duplicate checks consistent while retaining the value printed on the document.
September 11: Investigate supplier credit balances before choosing a remedy
Build a source-linked worksheet for credits, overpayments, refunds, offsets, and unresolved supplier balances.
September 11: Review split-coded invoices line by line
Keep allocation support, coding logic, approver responsibility, and later corrections traceable.
September 11: Anchor supplier-statement reviews to a clear cutoff
Keep a reconciliation from mixing statement dates, ledger extracts, later invoices, and payments in transit.
September 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.
September 11: Validate invoice dates without guessing what the supplier meant
Separate printed dates, receipt dates, service periods, posting dates, and policy decisions.
September 11: Give rush payment requests a controlled intake lane
Capture the business reason, evidence, timing, requester authority, and exceptions without promising payment.
September 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.
September 11: Use a vendor alias register without merging distinct suppliers
Connect trading names and payment descriptors to approved master records while keeping uncertain matches open.
September 11: Check invoice file readiness before data entry
Define what to do with incomplete, unreadable, protected, altered, or mismatched invoice files.
September 11: Build a case file for returned supplier payments
Trace a returned payment through the bank event, supplier verification, correction, reapproval, and ledger outcome.
September 11: Maintain a recurring invoice expectation list that catches gaps
Compare expected invoices with received documents without treating a forecast as proof of liability.
Normalize invoice numbers without erasing the supplier record
Make invoice searches and duplicate checks consistent while retaining the value printed on the document.
Investigate supplier credit balances before choosing a remedy
Build a source-linked worksheet for credits, overpayments, refunds, offsets, and unresolved supplier balances.
Review split-coded invoices line by line
Keep allocation support, coding logic, approver responsibility, and later corrections traceable.
Anchor supplier-statement reviews to a clear cutoff
Keep a reconciliation from mixing statement dates, ledger extracts, later invoices, and payments in transit.