Philippines AP staffing guide

Maintain a cutoff exception log for payment proposal preparation

Document additions, removals, holds, timing changes, approvals, and final inclusion without giving the preparer release authority.

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

Direct answer

What this role should do

Document additions, removals, holds, timing changes, approvals, and final inclusion without giving the preparer release authority. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

Freeze a reviewable cutoff snapshot

Save the proposal ID, entity, bank account alias, currency, scheduled date, cutoff timestamp, invoice population, total, and extraction source before late changes begin. Compare later versions with this snapshot rather than relying on a total written in chat. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

A 4:00 p.m. snapshot contains 138 invoices. The 4:37 version contains 140, so the log identifies the two added document IDs and their values. The finance owner confirms which snapshot is the authorized starting population. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Reperform the proposal bridge after the change and investigate any unexplained difference.

Log additions as separate decisions

For every late addition, retain the invoice, due date, discount date, approval status, hold status, supplier verification state, requestor, reason, and time received. Check ordinary readiness controls even when the request is urgent. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

A manager asks to add a utility invoice after cutoff. The invoice is approved, but a vendor hold remains, so it stays outside the proposal pending an owner decision. The authorized exception owner decides whether timing justifies inclusion and documents the control treatment. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Confirm the change appears in the final approved population and assign any carryover.

Explain every removal and hold

Capture the proposal line, removal time, actor, reason code, related case, and whether the invoice returns to a later run. Distinguish a deliberate removal from a system filter or failed validation. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

One invoice disappears because its supplier was placed on hold after the first extract; another drops because its payment method is not supported by the selected run. Treasury or finance confirms the disposition and prevents the item from becoming an unowned overdue balance. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Reperform the proposal bridge after the change and investigate any unexplained difference.

Reconcile totals after each approved change

Show opening total, additions, removals, credits, discounts, currency adjustments, and closing total with document-level references. Make the bridge arithmetic reproducible and keep currencies separate. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

Three approved additions increase the run by $18,250, one removal reduces it by $4,100, and a $600 credit produces a net change of $13,550. A reviewer compares the bridged total with the payment system before approval. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Confirm the change appears in the final approved population and assign any carryover.

Protect the release boundary

Record preparer, reviewer, approver, file creator, bank submitter, and releaser as the company process defines them. Stop when a role conflict, missing approval, or unexplained file difference appears. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

The preparer can export the approved list but cannot submit it to the bank. A changed file hash after approval sends the run back for review. Only the designated company users authorize and release funds. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Reperform the proposal bridge after the change and investigate any unexplained difference.

Verify the final run and carryovers

After release, retain the approved proposal, final file or platform reference, bank result, failures, exclusions, and next-run assignments. Trace each cutoff exception to settlement, rejection, or a named carryover. Tie the entry to the proposal version and sequence number so the reviewer can see exactly when the population changed. State what the evidence establishes and what is still awaiting authorization. AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

A late invoice approved for inclusion fails account validation. The log keeps the failed result and assigns it to the remediation queue instead of marking it paid. The run owner signs off the final population and every unresolved item. Add the amount, currency, actor, timestamp, reason, and next checkpoint. Keep the prior version beside the corrected one. Confirm the change appears in the final approved population and assign any carryover.

Continue with payment run preparation 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 payment proposal cutoff exception log answer?

Why did an invoice enter, leave, or change in the proposal after the stated cutoff, and who authorized that treatment?

Which authority stays with the company?

AP support may prepare the proposal and exception evidence; treasury or finance approves exceptions, controls bank access, and releases payment.

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.