Research question: when a bookkeeping VA merges two duplicate QuickBooks Online vendor records, do bill attachments and 1099 payment history stay available on the surviving vendor?

Testing Whether Merging Duplicate QuickBooks Online Vendors Preserves Bill Attachments and 1099 Payment History

A controlled test for a bookkeeping VA checking whether a QuickBooks Online vendor merge keeps bill attachments, payment history, and 1099 report totals attached to the surviving vendor.

Testing Whether Merging Duplicate QuickBooks Online Vendors Preserves Bill Attachments and 1099 Payment History research thumbnail
On this page Jump to section

Question and scope

A duplicate vendor record splits one supplier's bills, payments, and attachments across two names. Merging the records promises a single history, but a bookkeeping VA still has to confirm what the merge actually moved. The question is whether bill attachments remain reachable, whether payment history follows the transactions, and whether the 1099 report total after the merge equals the combined total before it. The answer decides whether a merge is a safe cleanup step or whether the client should keep the records separate until year end.

The scope is one QuickBooks Online company file, two vendor records that represent the same supplier, and the bills, payments, and attachments linked to each. It includes vendors marked for 1099 tracking and vendors with no tax reporting flag. It excludes customer merges, employee records, and merges performed during a company file conversion. The test compares the surviving vendor's record and the 1099 report before and after the merge, using baseline exports rather than memory.

Why a vendor merge is a data-migration event

A merge is not a rename. The product has to decide which record survives, which fields win when the two records disagree, and where the transactions and attachments point afterward. A field such as the tax identification number, the default expense account, or the 1099 tracking flag may come from either record. If the surviving record carries the wrong value, the merged history can look complete while the tax reporting is wrong.

Attachments add a second risk because they can live at different levels. A bill attachment belongs to the bill, while a vendor-level document may belong to the vendor record. The merge may preserve one and not the other. A reviewer who only checks that the bill exists can miss a missing receipt or W-9 image. The test therefore checks each attachment path separately and records where the file was stored before the merge.

Population and baseline

Build the population from vendor pairs that share a normalized name, a tax identification number, or a bank detail, and that have activity in the current or prior year. Record each vendor's display name, company name, address, email, phone, tax identifier, 1099 flag, default expense account, and open balance. Include at least one pair with attachments on both records, one pair with payments split across the two records, and one pair where only one record is marked for 1099 tracking. Exclude pairs that the client has already decided to keep separate.

Freeze the baseline before the merge. Export the vendor list with the detail fields, the accounts payable aging detail for both vendors, the transaction list for each vendor, and the 1099 report for the year. Open every attachment and save a list of file names, transaction links, and upload dates. Capture the vendor balance detail for the same date and the exact report run time. The baseline is the only reliable record of what the file looked like before the records collapsed.

Test setup

Work in a copy of the company file when the subscription and the client permit it. A merge can be difficult to reverse, and recreating the second vendor may not restore the original identifiers or attachment links. If a copy is not possible, schedule the test outside the close window, obtain written approval, and record every field before the change. The test must be reversible without guessing which values belonged to which record.

Change one variable at a time. First merge a pair with no attachments and no 1099 flag to observe the basic transaction move. Then merge a pair with attachments on both records. Finally merge a pair where the 1099 flag and tax identifier differ. A test that combines attachments, tax status, and payment history in one merge cannot show which factor caused a missing item.

Procedure

Run the baseline comparison before the merge. Reopen the saved reports and confirm that they still match the exports, which catches ordinary drift from later bills or payments. Record the open balance, the transaction count, and the attachment count for each vendor. Then perform the merge through the normal interface and save the confirmation message, if the product shows one.

Immediately open the surviving vendor and compare every field with the baseline. Record which name, address, tax identifier, expense account, and 1099 flag survived. Run the vendor balance detail, the aging detail, and the 1099 report for the same date range. Compare the transaction count and the total payments with the sum of the two baseline records, and note any transaction that moved to a different vendor or disappeared from the list.

Walk the attachment list next. Open each bill that carried an attachment and confirm that the file still opens from the transaction. Then check any vendor-level attachment separately, because it may not follow the merge. Search the file for the old vendor name to see whether it remains anywhere in memos, bill numbers, or contact fields. Finally, recreate a test bill on the surviving vendor and confirm that the default expense account and 1099 setting match the client's intent.

Definitions and measures

A complete merge means the surviving vendor holds all transactions, all attachments remain reachable from their own records, and the 1099 total equals the combined baseline total. A partial merge means the transactions moved but an attachment, a field, or a report line did not follow. A failed merge means the surviving vendor is missing transactions or the 1099 total no longer reconciles to the combined baseline. Record the state for each level so the memo does not collapse a partial result into a pass or a failure.

Measure the result at four levels. The vendor field level shows which identity values survived. The transaction level shows whether bills and payments moved without duplication. The attachment level shows whether each file still opens from its record. The report level shows whether the 1099 total and the aging total equal the sum of the two baseline records. Report all four, because a clean transaction list can coexist with a missing W-9 or a changed tax identifier.

Worked example

Suppose a client has two records for the same supplier, one named for the legal company and one for a shortened trade name. The legal record holds three bills and a W-9 image, while the trade-name record holds two bills, one payment, and a receipt attached to a bill. The client wants one vendor before the next 1099 filing. A VA merges the trade-name record into the legal record and then checks the result against the baseline.

The transaction list shows all five bills and the payment on the surviving vendor, and the aging total matches the sum of the two old balances. One bill attachment opens normally, but the W-9 image no longer appears on the vendor record. The 1099 total matches the combined baseline because both records carried the same tax identifier. The VA records the missing W-9 as an open item, requests a fresh copy from the supplier, and notes that the merge preserved transactions but not every document. The client's accountant decides whether the missing image needs to be replaced before filing.

Evidence standard

The evidence set includes the baseline vendor list, the aging and 1099 exports, the transaction and attachment inventory, the merge confirmation, and the post-merge checks. Each claim in the memo should point to a specific artifact and the vendor record it came from. A statement that attachments survived is credible only when each file was opened after the merge, not when the bill merely still exists. Keep the raw exports and the attachment inventory rather than only a summary count.

Add at least two vendor pairs so the conclusion rests on more than one merge. Include one pair where the tax identifier or 1099 flag differs, because that is where a clean transaction move can hide a reporting problem. If an attachment cannot be opened because the file type is unsupported or the link is broken, say so and lower the confidence of the conclusion. Do not fill the gap with an assumption about how the product should behave.

Interpretation limits

A result in one company file does not prove that every QuickBooks Online edition or vendor pair behaves the same way. The outcome can depend on the subscription level, the attachment type, the field values on each record, and whether either vendor had activity in a closed period. Record the product edition, the vendor pair, and the test date so a later reviewer can judge whether the result still applies. A second pair with a different 1099 status is a useful follow-up test.

The test also cannot decide whether the two records should be merged at all. That question depends on the supplier's legal identity, the client's vendor master policy, and the accountant's view on reportable payments. The test can show what the merge preserved and what it lost. It cannot substitute for a vendor master decision, and the memo should state that boundary.

Review cadence

Repeat the test after a vendor master cleanup, after a 1099 filing season, and before a year-end close in which duplicate vendors are likely to be merged. A quarterly spot check is reasonable for a client with a large vendor list, while a client with few suppliers can review annually. Put the next review date in the client's close calendar rather than in a personal reminder. Record the previous result beside the new one so a change in merge behavior is visible immediately.

Close the review with a named owner, the exact report settings, and a date for the next check. Link the result to the duplicate vendor review and the 1099 vendor data guide so the next reviewer starts from the same evidence. If the merge lost an attachment or changed a tax identifier, convert the finding into a written cleanup rule with an approval step. The test explains the state; the accountant decides what belongs in the vendor master.

Sources