QuickBooks Error C=19 -- A/R or A/P Transaction Cannot Be Added
QuickBooks Desktop blocks an invoice or bill with error C=19 when linked A/R or A/P transactions are damaged; we explain the trigger and the repair path.
Error C=19 stops QuickBooks Desktop the moment it tries to save an invoice or a bill. The code sits on the receivable or payable side of the entry, and in our repair work it usually traces back to damaged or unreconciled linked transactions inside the company file. Here is what the code is telling you and what our engineers do about it.
The message you see
When the save fails, QuickBooks displays:
QuickBooks is unable to add an A/R or A/P transaction.
Some releases show only the code, C=19, in a small dialog with no further text. Either way the save was refused, so the invoice or bill is not in the file even if the form is still open. Repeated saves will not get past the block until the linked records behind the entry are repaired.
What does C=19 mean?
Invoices post to accounts receivable. Bills post to accounts payable. Behind each entry, the program keeps link records that tie a transaction to its related pieces. The pieces are the payment that settles an invoice, the credit that offsets a bill, and the bill payment that closes a payable. C=19 means the posting engine reached one of those linked records and could not complete the chain. The linked transaction is damaged, or its state does not match what the new entry expects, so QuickBooks refuses the save rather than write a half-formed transaction.
What triggers it?
The triggers we see most often:
- An interrupted save. A power cut, a dropped network connection, or the program closed mid-write can leave a linked transaction half posted.
- A damaged payment or bill payment, so the invoice or bill it points to can no longer link cleanly.
- Orphaned links left behind by a condense, a restore, or a merge that did not finish properly.
- General data damage anywhere in the linked chain, which a Verify will usually flag.
Is the fault in your file or in your installation?
Work that out before changing anything. Create a portable copy of the company file and open it on a second computer running the same version of QuickBooks or a newer one. If C=19 appears there too, the fault is in the data and the steps below apply. If the file opens and saves normally there, the company file is healthy and the installation on the original computer needs a repair or a reinstall.
How do you clear C=19?
Make a backup of the company file first. Every step below assumes you have one.
If Verify reports damage
- Go to File > Utilities > Verify Data.
- If Verify reports a problem, run File > Utilities > Rebuild Data. Rebuild changes data, so keep that backup safe.
- Run Verify again once Rebuild finishes and wait for a clean result.
- Re-enter and save the invoice or bill that failed.
If a linked transaction is the damage
When the save still fails after a clean Rebuild, the linked transaction itself is usually the block. Signs include a payment that will not open, an invoice that shows paid while the payment never left undeposited funds, or a payable whose bill payment sits in the register with no link.
- Open the Customer Center for an A/R problem or the Vendor Center for an A/P problem, and find the customer or vendor involved.
- Open each transaction tied to the failing entry and note the date, amount, and reference of anything that looks wrong.
- Delete the damaged linked transaction. Leave the invoice or bill you are trying to save alone.
- Re-enter that transaction and link it to the invoice or bill as before.
- Save the original invoice or bill again.
If Verify and Rebuild both pass
Some link damage sits below the level the built-in checks can reach. If both come back clean and C=19 still blocks the save, the file needs repair work at the database level. Our engineers rebuild the linked transaction chain directly and hand back a file that verifies clean. See our QuickBooks error code repair service for how the process runs.
Keeping C=19 from coming back
- Close the program normally. Never power a machine off while a save, a Rebuild, or a condense is running.
- Verify the file on a steady rhythm; monthly suits a busy file. Rebuild only when Verify reports a problem.
- Back up before heavy posting days and before housekeeping such as a condense or a period copy.
- In multi-user mode, host the company file on the server that holds it and keep the connection stable. Most interrupted writes we see trace back to a network drop mid-save.
- When the file grows heavy, condense it to a chosen cutoff date instead of carrying every historical transaction forward. Smaller files verify faster and break less.