Vendor rules for QuickBooks receipt coding that code most receipts for you

What a vendor rule does

A vendor rule is a standing instruction: when a receipt from this vendor arrives, code it this way. It answers the same question a preparer would otherwise answer by hand, again and again, for every fuel slip and every phone bill.

A full rule says more than the expense account. In a QuickBooks Online file, a well coded receipt may also need a class, a location, a customer or project, a billable flag, and a memo. A rule can carry all of these. For example: Shell always goes to Car & Truck:Fuel, class Field Ops. Or: the client's phone carrier always goes to Utilities:Telephone, location Main Office.

The value of rules comes from repetition. Most small businesses buy from the same set of vendors every month. Once those recurring vendors have rules, most recurring vendors are coded the same way every time, by whoever is on the file, without anyone looking them up. That consistency is worth as much as the time saved. A profit and loss where fuel sometimes lands in Auto and sometimes in Travel is harder to trust and harder to explain to a client.

This guide covers which vendors deserve a rule, how to write one, where it should live, and how to keep rules accurate as clients change.

Which vendors deserve a rule

Not every vendor should get a rule. The test is simple: does every purchase from this vendor belong in the same place?

• Good candidates. Fuel stations for a company with field vehicles. Software subscriptions. Phone and internet providers. Insurance carriers. Parking and tolls. Specialist suppliers who sell one kind of thing, like a lumber yard for a framing contractor.
• Poor candidates. Big-box and online stores that sell everything. One receipt from a warehouse club may hold office supplies, cleaning products and snacks for the team. A rule would code all of it to one account, which is wrong more often than right.
• Borderline cases. Restaurants can be client meals, team meals or travel meals. A hardware store can be job materials or shop supplies. Here a rule can set the most common account and leave the receipt for review when the amount is unusual.

Start with the vendors that appear most often in the client's last three months of expenses. A rule for a vendor seen once a year saves almost nothing. A rule for a vendor seen every week pays back immediately. For a contractor example, our page on receipt capture for construction companies shows typical fuel and supply vendors.

How to design a rule that stays right

A rule is only useful if it is right every time it fires. A few habits keep rules accurate.

• Match the vendor precisely. Use the vendor name as it appears on receipts. Watch out for brands that share a name with unrelated businesses.
• Use the client's own lists. Pick the account, class and location from the client's QuickBooks Online lists, not a generic category. If the client tracks jobs, decide whether the rule sets a customer or project, or leaves it for the preparer.
• Be careful with billable. Mark a vendor as billable only if every purchase from it is rebilled to a customer. Otherwise leave billable off and let the preparer decide.
• Write a memo pattern. A short memo such as "Fuel, field vehicles" helps anyone reading the ledger later.
• Keep one rule per vendor per client. Two rules that disagree create confusion about which one wins.

Then test. Apply the new rule to last month's receipts from that vendor and check the result. If even one receipt would have been coded wrong, either narrow the rule or leave that vendor for review. A rule that is right nine times out of ten still creates the tenth error silently, which is worse than no rule.

How rules and AI suggestions work together

Modern receipt tools suggest coding with an AI model that looks at the vendor, the line items and the client's history. Suggestions are useful for vendors you have never seen. For vendors you know well, a rule is better, because it is your decision, written down, and it does not drift.

In ReceiptQBO, vendor rules override the AI. When a rule exists for a vendor, the rule's coding is used, and the audit trail records that the rule was applied. When no rule exists, the AI model proposes the coding from the client's own chart of accounts, classes and locations.

This split also makes review faster. Each receipt has a confidence score for vendor, date, total, tax and account, and each client has a threshold, 90 percent by default. Receipts at or above it are approved and posted automatically. Receipts below it wait in one review queue across all clients, lowest confidence first. As your rules cover more recurring vendors, more receipts clear review without a person touching them, and the queue holds mainly the new and unusual items that genuinely need a human eye. You can see the review flow on our how it works page.

Client level rules versus practice wide rules

For a practice with many clients, the next question is where a rule should live.

Client level rules belong to one company. They use that client's exact account names, classes and locations. Most rules should be client level, because two clients rarely share the same chart of accounts. Fuel might be Car & Truck:Fuel for one client and Vehicle Expenses for another, with different classes.

Practice wide rules are templates you apply across clients. They work when your firm standardizes charts of accounts by industry. If every contractor client uses the same fuel account and the same field class, one template saves you writing the same rule twenty times. They also help new clients start well on day one.

A sensible approach is to keep a small set of practice wide templates for the most universal vendors, then let preparers add client level rules for the rest. When a client's chart differs from the template, the client level rule should win. In ReceiptQBO, practice wide rule templates are part of the Firm plan, along with a threshold per client and roles per client. See pricing for what each plan includes.

QuickBooks bank rules and receipt rules are different tools

QuickBooks Online has its own bank rules, and it is worth being clear about how they differ from receipt rules.

A bank rule acts on lines in the bank feed. It reads the bank description and amount, and categorizes the line. It never sees the receipt, so it cannot read sales tax, tips or line items, and it cannot tell a client meal from a team lunch.

A receipt rule acts on the document. It knows the vendor from the receipt itself, which is often clearer than a bank description full of processor codes. And because the receipt is then matched to the bank line, the coding ends up on the transaction with the image attached.

Running both on the same vendor can cause conflicts. If a bank rule auto-adds a fuel charge to one account while the receipt rule codes it to another, you get either a mismatch or a duplicate. Pick one place to code each recurring vendor. Many practices keep bank rules for lines that never have receipts, such as transfers and loan payments, and use receipt rules for purchases. Our guide to matching receipts to bank transactions covers how the two records meet.

Keeping rules accurate over time

Rules age. Clients add classes, rename accounts, start new lines of business and change suppliers. A rule written last year can quietly start coding to an account the client no longer uses.

• Review each quarter. List each client's rules and check that every account, class and location still exists and still makes sense.
• Watch chart of accounts changes. When a client merges or renames accounts, update rules the same day.
• Retire unused rules. A rule that has not fired in six months is clutter. Remove it.
• Look at corrections. If reviewers keep changing the coding a rule produced, the rule is wrong or too broad.
• Record who changed what. An audit trail of rule changes helps when a client asks why something was coded a certain way.

Add the quarterly rule review to your close checklist for the last month of each quarter. It takes a few minutes per client and keeps the automation honest. Our guide to a monthly missing receipts workflow fits well alongside it.

Turning corrections into rules in one click

The easiest way to build a strong rule set is not to sit down and write rules from scratch. It is to capture the decisions your team already makes.

In ReceiptQBO, a QuickBooks receipt scanner built for QuickBooks Online, any correction a preparer makes in review can be saved as a vendor rule in one click. Change a receipt from Office Supplies to Job Materials with the right class, save it as a rule, and every future receipt from that vendor for that client is coded the same way. The audit trail records the rule being applied each time, so a reviewer can always see why a receipt was coded as it was.

Over the first few months, the rule set grows from real work instead of guesses. The review queue shrinks to receipts that need judgment. To see how the AI model codes a receipt before any rules exist, upload one receipt on the home page without an account and look at the proposed QuickBooks account.

Questions about vendor rules for receipt coding

Which vendors should get a coding rule?

Recurring vendors where every purchase belongs in the same place, such as fuel, software, phone and insurance. Stores that sell many kinds of goods are better left to review.

Do vendor rules override AI coding in ReceiptQBO?

Yes. When a rule exists for a vendor, its coding is used instead of the AI suggestion, and the audit trail records that the rule was applied.

Should rules be per client or practice wide?

Most rules should be per client because charts of accounts differ. Practice wide templates suit firms that standardize charts by industry and are part of the Firm plan.

How often should I review vendor rules?

Once a quarter, and whenever a client changes their chart of accounts. Remove rules that no longer fire and fix rules reviewers keep correcting.