Two Provider Invoices Swapped Accepted-Work Reconciliation Packets: Hold and Reconcile Both Payments

A swapped accepted-work packet creates two problems at once: each invoice may look approved while pointing to somebody else's evidence, and the original approval trail may no longer prove what was paid. Treat both invoices as unresolved until the evidence is separated.

Start by freezing the payment state, preserving the original files, and assigning each invoice a reconciliation owner. Do not replace the crossed documents in place. Keep the original packet, the corrected packet, the reason for the correction, and each new approval together.

The useful test is simple: can a reviewer follow one invoice from provider, contract version, billing period, deliverables, acceptance-and-adjustment status, plus final amount without relying on the other invoice? If not, it is not ready for payment.

• Hold or pause both invoices in the payment workflow.
• Preserve the original packets and approval history.
• Create a separate reconciliation file for each invoice.
• Prevent credits, recoveries, plus tax and payment-release decisions until review is complete.

Which records belong to each provider invoice?

Build one ledger per invoice. Put the invoice number, provider legal name, contract or order reference, contract version, billing period, currency, tax treatment, and requested payment amount at the top. Do not begin with the accepted-work packet. Begin with the invoice itself, then work backward to the agreement and forward to acceptance.

For each billed line, identify the exact deliverable and quantity or service period, agreed price, acceptance record, plus any exception. If an invoice has a charge that cannot be tied to its own supporting record, mark that line unresolved rather than assigning it by resemblance.

Federal Acquisition Regulation guidance provides a useful evidence model, even where it does not govern the relationship. It identifies an invoice's contract authorization and description, quantity, unit price, plus extended price as core invoice content, and says payment authorization should be supported by receiving or acceptance documentation. See FAR 32.905, effective March 13, 2026.

The contract controls the definition of accepted work. The place and method of acceptance should come from the agreement or order, not from an invoice label. FAR 46.503 likewise requires a contract to specify the place of acceptance.

How do you separate crossed accepted-work packets?

Make two controlled working copies, one for Invoice A and one for Invoice B. Give every source item an identifier and note where it came from. The original crossed packet remains read-only evidence. The new ledgers are the reconciliation workpapers.

Match records using hard identifiers first: contract or order number and invoice number; provider legal entity, service date, milestone reference, purchase order line, plus named acceptor. Use narrative descriptions only as supporting context. Similar wording, similar amounts, or the same project name do not prove ownership.

Then run a negative check. For every document placed in Invoice A's ledger, explain why it cannot belong to Invoice B. This catches the common error where a team proves that a document fits one invoice but never proves that it was excluded from the other.

Record the result line by line: matched or partly matched; disputed, duplicate, missing, or not applicable. A partly matched line should not inherit approval from the rest of the invoice.

• Copy each original packet without changing its contents.
• Index every source document before sorting it.
• Match by identifiers before reading descriptions.
• Document exclusions as well as matches.
• Escalate missing or conflicting evidence to the contract and delivery owners.

Were payment, tax, credit, or recovery decisions made from the wrong packets?

Check the audit trail before correcting the ledger. Review payment status and payment date; remittance reference, approval history, tax calculation, credit memo, dispute notes, plus any recovery action for both invoices. The goal is to identify decisions already made from crossed evidence, not to assume that no decision was affected.

If neither invoice has been paid, keep both on hold until the corrected evidence and approvals are complete. If one has been paid, determine whether the payment itself was correct or the supporting file was wrong, including whether both were wrong. Those are different outcomes and need different records.

Do not reverse, recover, or issue a credit merely because packets were crossed. Confirm the contractual amount and delivered scope; acceptance and prior payment position first. Payment timing also depends on the applicable agreement and rules. FAR 32.904, effective March 13, 2026, describes due-date treatment for proper invoices and accepted performance in federal contracting, but it is not a substitute for the parties' own contract or legal advice.

Tax treatment needs the same discipline. Preserve the tax calculation that was used, identify which invoice and commercial terms it relied on, and route any changed tax outcome to the person responsible for tax review. Do not infer tax treatment from an accepted-work packet.

How should the corrected ledgers be approved before payment?

Approval should follow the corrected evidence, not repeat the old approval. The delivery or receiving owner confirms what was accepted, while the contract owner confirms the applicable scope and price. Finance confirms the invoice amount and payment status, including any credit or recovery treatment. The tax owner reviews tax only where a tax decision is affected.

Each approver should see the original mismatch and corrected ledger; unresolved exceptions and the requested decision. A generic approval such as "looks good" does not tell a later reviewer whether the person approved delivery, price, tax, or payment.

The final payment record should name the invoice number used in the remittance. FAR 32.906, effective March 13, 2026, says federal payment or remittance advice uses the contractor invoice number alongside government or contract information. That is a practical control for keeping payment evidence tied to the corrected invoice file.

Keep the completed ledger and approvals; provider correspondence, payment evidence, and exception decision together. The IRS says a business may choose a recordkeeping system suited to its needs when it clearly shows income and expenses, and that supporting documents provide information needed for books and records. See IRS recordkeeping guidance, last reviewed May 1, 2026.

What should happen when evidence is still missing?

Keep the affected invoice line unresolved. Ask the provider for a corrected invoice or line-level breakdown, plus supporting delivery evidence when the source documents cannot establish the charge. Ask the internal delivery or contract owner to confirm whether work was accepted or rejected, partly accepted, or still under review.

Do not let a clean line pull a disputed line through approval. Split the invoice only if the contract, payment process, and evidence permit it, and document the reason. Federal guidance allows payment for accepted partial deliveries where the contract permits and the price can be calculated from contract terms, but your own agreement and payment policy control the decision.

Close the reconciliation only when every line has an evidence status and every exception has an owner and disposition, with the payment action matching the corrected ledger.