Philippines AP staffing guide
Allocate one supplier invoice across split shipment receipts
Reconcile a single billed quantity to several deliveries, receipt reversals, locations, and open purchase-order balances without manufacturing a match.
Direct answer
What this role should do
Build a line-level allocation that preserves every shipment and receipt event. Match only the quantity and value supported by valid receipts, show reversals separately, and route any remaining difference to the receiving or purchasing owner instead of creating receipt evidence.
Start with the supplier demand, not the easiest receipt
A supplier may put several deliveries on one invoice even though the buyer received them on different days, at different sites, or against separate releases. Begin with an unchanged copy of the invoice and list each billed line, quantity, unit of measure, unit price, tax, freight, shipment reference, and purchase-order reference. Record the supplier account and company entity as well. Do not begin by selecting whichever open receipt makes the invoice total fit. That shortcut can consume evidence needed for another invoice and hide a missing delivery. The first working paper should describe what the supplier is asking the company to pay before it proposes where any portion belongs.
Give the case one stable identifier and link the original purchase order, current order version, packing slips, carrier references, receiving records, earlier invoices, and credits. Preserve the invoice arrival time because discount eligibility and close cutoff may depend on when AP actually received a usable document. If the supplier combined orders or entities, separate those demands in the analysis without altering the source file. A split worksheet is an aid for review, not a replacement invoice. The source invoice, allocation, system postings, and owner decisions must remain connected so another reviewer can reconstruct the result later.
Create a receipt chronology for every delivery
Build the timeline before calculating the match. For each shipment, record the dispatch or service reference, destination, delivery date, receiving timestamp, receiver, purchase-order line, quantity accepted, quantity rejected, and system receipt number. Then add reversals, corrections, returns, and transfers in the order they occurred. A current receipt balance can look sufficient after several corrections while concealing that the original receipt belonged to another shipment. The chronology should retain both the first entry and the correcting entry. It should also distinguish a true reversal from an administrative reposting, since only the process owner can confirm whether the underlying goods or services remained accepted.
Missing chronology points become focused questions. Ask the receiving owner about a delivery reference and date, not whether the whole invoice is acceptable. Ask purchasing which order line covered a substituted product, not whether AP should force the match. If a warehouse recorded the full quantity at one site and later transferred stock internally, confirm whether the transfer changes the purchasing receipt at all. AP support gathers these answers and cites the records. It does not create a backdated receipt or divide one receipt across unrelated lines simply because the invoice is approaching its due date.
Normalize units without erasing the supplier quantities
A split shipment often exposes unit differences. The order may use cases, one site may receive individual units, and the invoice may bill pallets. Show the supplier unit, purchasing unit, receiving unit, and approved conversion factor in separate columns. Retain the original quantities beside the normalized quantities. If a case should contain 24 units, identify the contract, item master, or approved order record that supports 24. Do not infer the pack size from the number needed to clear the invoice. When conversion evidence conflicts, isolate the affected line and let the master-data or purchasing owner decide which controlled value applies.
Reconcile both quantity and value. Twelve cases at one price are not interchangeable with 288 individual units if a price amendment took effect between shipments. For every proposed allocation, show receipt quantity, invoice quantity assigned, unit price, extended amount, tax treatment, and remaining receipt balance. Keep freight and accessorial charges outside the product allocation unless the order and company procedure place them on the same line. A reviewer should be able to sum the proposed pieces back to the invoice and also see what remains available on each receipt after the proposed posting.
Handle reversals and partial acceptance as separate events
Suppose the supplier invoices 140 units from three deliveries. The system shows receipts for 50, 60, and 40, but the last receipt was later reversed by 10 after damage was found. The supported total is not automatically 150, and the 10-unit difference is not a rounding issue. Show 50 plus 60 plus 40 minus the 10-unit reversal, then connect the reversal to the return, replacement, credit, or unresolved claim. If the supplier shipped replacements, locate their delivery and acceptance record rather than restoring the old receipt. This keeps physical events, supplier claims, and system evidence in the same sequence.
Partial acceptance needs the same care. A receiver may acknowledge that a truck arrived while rejecting part of the load. A service owner may accept one milestone and dispute another. Record accepted and disputed portions with their owners and supporting documents. Match only the accepted portion when company policy permits partial processing, and retain the balance in a named exception status. Do not label the whole invoice approved because one line passed. Conversely, do not lose the valid portion inside a general hold. The decision packet should make the payable portion and unresolved portion obvious without implying authority the preparer does not have.
Route the residual difference with an answerable question
After the allocation, calculate the invoice quantity and value not supported by valid receipts. Classify the reason using evidence: receipt not posted, receipt reversed, wrong order line, unit conversion conflict, price amendment, duplicate shipment reference, return in progress, or supplier billing error. Avoid a broad note such as "receipt mismatch." Name the document and amount at issue, the checks already performed, the owner who can resolve it, and the next review date. A precise residual lets the recipient answer without repeating the entire investigation and gives the aging queue a meaningful status.
Provide the owner with the source invoice, allocation table, event chronology, relevant order version, receipt records, and one requested decision. Receiving confirms acceptance, purchasing interprets commercial scope, and finance controls posting treatment. If a corrected invoice or credit is required, contact the supplier through a verified channel and state the disputed reference without exposing unrelated account data. Keep the supplier response with the case. A promise to issue a credit does not close the difference; the credit must arrive, be validated, and be linked to the affected invoice or open item.
Prove the final posting and preserve unused receipt capacity
Once the owners resolve the exception, compare the approved allocation with the actual ERP posting. Confirm the invoice document number, order and receipt references consumed, quantities, values, tax, posting date, and any remaining hold. Check that a correction did not consume a different receipt or leave a duplicate invoice draft in another queue. Preserve evidence of the final match result instead of treating a successful system status as proof by itself. Automated matching can succeed on tolerance or configuration that the reviewer did not intend, so the posted references still need to agree with the approved packet.
Review the receipt balances left behind. Each unused quantity should correspond to goods awaiting invoice, a known return, a cancelled commitment, or another documented state. An unexplained remainder can produce a later duplicate match or distort close reporting. For an outsourced AP lane, sample split-shipment cases by site, supplier, age, and exception cause. Look for repeated missing delivery references, delayed receipts, pack-size conflicts, and reversals posted after invoices arrive. The useful outcome is not a higher forced-match rate. It is a repeatable allocation that pays supported supplier demands while keeping unsupported quantities visible for the right owner.
Continue with three-way match support and the scope a controlled receipt exception lane.
Review the split-shipment allocation
- Original invoice and shipment references remain unchanged
- Receipt chronology includes reversals, returns, and corrections
- Supplier, purchasing, and receiving units remain visible
- Every proposed allocation reconciles quantity and value
- Residual differences have a cause, owner, and next action
- Actual posting matches the approved allocation
Common questions
Accounts payable virtual assistant FAQs
Can AP split one invoice across several receipts?
Yes, when company procedure permits it and each allocation is supported by valid receipt and order evidence. AP should not invent or backdate receipts to complete the split.
What happens when one receipt was reversed?
Keep the original receipt and reversal in the chronology, identify the reason, and match only the net quantity that remains supported unless an authorized owner provides new acceptance evidence.
Should unused receipt quantities disappear after posting?
No. Reconcile each remainder to an expected invoice, return, cancellation, or named exception so it cannot silently support a later duplicate.
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 for documented transactions, assigned responsibility, and control evidence.
- NIST least privilege glossarySupports reserving receipt creation and approval actions for authorized owners.
International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.
Contact Us to turn this article into a scoped Philippines-based staffing brief.