Write a vendor coding guide that still respects the job

A construction vendor coding guide should state the usual treatment, the evidence needed and the exceptions that require review. It should not assign every purchase from one supplier to the same job or expense category. The vendor tells you who was paid; the invoice and field records explain what was purchased and where it belongs.

Use this guide to make repeated decisions consistent while keeping unusual transactions visible to the person authorized to decide them.

Create one instruction card per recurring pattern

Use these fields: vendor identity; normal transaction pattern; approved category or item; job-information source; required supporting document; exceptions; decision owner; effective date; and last review date. Link the guide to the company’s approved chart of accounts and active job list.

Avoid rules based only on a shortened bank description. Intuit’s bank-rule guidance distinguishes raw bank text from simplified descriptions and explains rule conditions. Check which text a rule actually uses. A broad vendor match can process transactions that need different treatment.

Worked example: one supplier, four different purchases

Illustrative transactions. A contractor buys from Harbor Supply throughout the month. The name appears consistently in the card feed, but the supporting documents show different uses.

The instruction card can help identify Harbor Supply as the payee. It cannot turn the merchant name into proof of job, purpose or accounting classification. Flag missing evidence instead of using last month’s job as a default.

Make exceptions specific enough to act on

Write “ask the project manager for the job and phase when the invoice has no job reference,” rather than “use judgment.” For shared purchases, point to the approved allocation method and the person who can approve it. For equipment, direct the item to the responsible accountant’s policy rather than inventing a dollar cutoff.

If a supplier serves both projects and the office, say so on the card. If a recurring charge changes purpose after a contract ends, update the effective date and preserve the prior instruction. Someone reviewing an older entry should be able to see the rule that applied at the time.

Test before turning on automation

Gather representative transactions, including exceptions, and apply the proposed instruction without posting changes. Compare the suggested result with the source documents and the approved treatment. Keep a short record of mismatches and the revised rule.

Start with review-required suggestions when the pattern depends on information outside the bank feed. Where automatic posting is considered, have the authorized owner confirm the scope and inspect results after a change. Software convenience does not establish that a transaction belongs to the correct construction project.

Keep job coding and account coding separate

The account or item describes the type of activity. The job identifies the project. In systems that support project reporting, those are related but different dimensions. Intuit’s Projects documentation describes assigning transactions to projects; your internal guide should explain which source supplies that assignment.

Review the guide when a new project starts, a supplier’s role changes, or an exception repeats. Use the missing-receipt handoff for evidence requests and the invoice approval map for decisions beyond the bookkeeper’s authority.

A dedicated construction bookkeeper works more consistently when these instructions can be followed and questioned without relying on the owner’s memory.