Can a corporate purchasing-card program's system-generated Sales Tax Report substitute for individual vendor invoices to prove Utah sales/use tax compliance?

Plain-English summary

A corporate purchasing-card program asked the Commission to confirm that its system-generated Sales Tax Report — built from data in its own database plus information vendors supply electronically at the point of sale — could substitute for individual vendor-generated invoices when a corporate cardholder needs to demonstrate sales/use tax compliance in a Utah audit. This final letter consolidates the Commission's position into a single reference document, following up on an earlier December 8, 1995 determination letter and additional correspondence.

The Commission confirmed a taxpayer must maintain documentation sufficient to show eight things for each transaction: (1) the transaction date, (2) the vendor, (3) the purchaser, (4) the total sale amount and total tax paid, (5) enough item detail to distinguish taxable from nontaxable items, (6) the delivery address, (7) FOB (freight/shipping terms) information, and (8) after-sale adjustments (discounts, returns, allowances) that are traceable back to the original transaction.

Evaluating the purchasing-card system's actual capabilities against that checklist, the Commission found:

• Vendor and purchaser identity are captured automatically from the program's own database — fine.
• Sale amount, tax amount, and transaction/processing date are entered by the vendor at point of sale — fine, if the vendor actually supplies them.
• A 160-character free-text description field can satisfy the "item detail" requirement, but only if the program keeps taxable and nontaxable items in separate transactions — no mixing them together in a single charge. Without that segregation, an entire "mixed" transaction (taxable and nontaxable items combined) would have to be taxed as a whole, unless the taxpayer separately documents the split.
• The system's delivery-address data is captured only by city/state/zip — which may not be precise enough where a single zip code spans more than one Utah taxing jurisdiction. To fix this, the corporate client can either adopt (and document adherence to) a policy of shipping all card purchases to the purchaser's mailing address, or separately maintain more precise delivery-address documentation.
• Using the same unique "supplier reference number" to link an original transaction to any later discount, return, or allowance adjustment satisfies the traceability requirement.

Subject to those conditions, the Commission accepted the automated Sales Tax Report as adequate documentation, but only to the extent the vendor actually supplies the required information — if the report falls short on any transaction, the corporate client must supplement it with other evidence of compliance to avoid an assessment. The opinion also stressed that this doesn't relieve the vendor of its own separate tax collection and recordkeeping duties under Utah law.

What this means for you

Businesses using corporate purchasing/procurement cards

An automated purchasing-card report can stand in for individual vendor invoices in a Utah audit, but only if it actually captures all eight required data elements for every transaction — and specifically, only if taxable and nontaxable purchases are never combined into a single charge. Build that segregation into your card program's transaction rules from the start.

Companies with imprecise delivery-address data

If your system only tracks delivery by zip code, adopt (and document) a policy of shipping purchases to a fixed mailing address, or maintain a separate, more precise delivery-address record — otherwise you risk not being able to establish the correct Utah taxing jurisdiction for sourcing purposes.

Vendors participating in a purchasing-card program

Confirming this ruling doesn't shift your own tax collection and recordkeeping obligations onto the cardholder's program — you retain your own separate compliance duties under Utah law regardless of what data you feed into a customer's automated reporting system.

Common questions

Q: What are the core elements Utah requires in sales/use tax documentation?
A: Transaction date, vendor, purchaser, total sale and tax amounts, item detail separating taxable from nontaxable items, delivery address, FOB information, and traceable after-sale adjustments.

Q: Can an automated purchasing-card report replace individual vendor invoices?
A: Yes, if it captures all the required elements and the vendor actually supplies the underlying data — otherwise the taxpayer must supplement it with other evidence.

Q: What happens if taxable and nontaxable items are combined in one purchasing-card transaction?
A: The entire mixed transaction becomes taxable, unless the taxpayer separately documents the taxable/nontaxable split.

Q: Does this ruling apply to my company's purchasing program?
A: Not automatically. This is a private letter ruling binding only on the Commission as to this taxpayer's specific facts and system. Another taxpayer can't rely on it as binding, though it may carry weight in a later appeal depending on how closely the facts match.

Citations and references

No specific Utah statutes or administrative rule numbers were cited in the extracted text of this opinion; the Commission's checklist of required documentation elements is stated directly in the ruling itself.

Source

• Landing page: https://tax.utah.gov/commission/rulings/
• Original PDF: https://files.tax.utah.gov/tax/commission/ruling/96-039.pdf

Original ruling text

96-039

Response
February 26, 1996

Attention:
Alice Shearer

Commissioner

Re.:
Advisory Opinion: XXXXX for Sales/Use Tax Record-keeping Requirements.

Dear
Commissioner Shearer:

With
respect to the above referenced matter, thank you for your determination letter
dated December 8, 1995. We are very
pleased with the determination of the Commission.

As
you know, the December determination letter assumes the resolution of various
issues that were addressed in earlier correspondence from the Commission. Since we believe it is important for
taxpayers to refer to a single document to find all the Commission's views, we
offered to draft for your review such a determination letter. Following a telephone message left for you
and a follow-up conversation with XXXXX of your Office, you agreed to this
idea. Our draft is attached here.

We
hope that you find that this draft fairly reflects guidance presented by the
Commission throughout our correspondence.
For the most part, the draft follows the outline of the January 8
letter, although points raised previously by the Commission in other letters
are incorporated as well.

We
would appreciate it if you would call us to let us know your reaction to the
draft. Please call me at your earliest
convenience at XXXXX. Once again, we are very grateful for the attention that
you and your staff have given to our ruling request and we appreciate the
opportunity to present this draft to you.

Very
truly yours,

XXXXX

Tax
Attorney

XXXXX

Dear
XXXXX:

We
have reviewed your request for a ruling that the XXXXX are an acceptable
substitute for vendorenerated invoices for purposes of demonstrating purchaser
compliance with Utah's sales/use tax laws.

A
taxpayer is required to maintain sufficient sales tax documentation to
demonstrate the following:

1)
Transaction date (usually the purchase date for sales tax purposes and the
delivery date for use tax purposes).

2)
Vendor.

3)
Purchaser (Corporate Client/Cardholder).

4)
Total amount of sale and total amount of sales or use tax paid.

5)
Sufficient item detail to distinguish between taxable and nonaxable items.

6)
Delivery address.

7)
FOB information.

8)
After-sale adjustments for discounts, returns, allowances, etc. must be
traceable back to the original transaction.

As
we understand your system, your software will generate a Sales Tax Report based
on (1) information residing in your database; and (2) information supplied
electronically by the vendor at the point of sale. The information residing in your database will automatically
identify the vendor and the purchaser (items 2 and 3 above). The system allows the vendor to input the
total amount of the sale and the total amount of tax (item 4); the transaction
date or the processing date (item 1); and a shipping address zip code (which
may only partially satisfy item 6); and a 160 character free text field that is
used for description (item 5). At the
Cardmember's direction, the vendor can input additional information in a
optional field, called the Cardmember Reference field.

You
indicate that your system identifies the delivery point of shipped items by
city, state and zip code (based on either the vendor's zip code for �take�
transactions or the �ship to� zip code in �ship to� transactions). This information will not be sufficient to
identify the precise Utah taxing jurisdiction when there is more than one
taxing jurisdiction in a single zip code.
However, if the taxpayer (your corporate client) implements a policy
requiring that all card purchases be shipped to the mailing address, the policy
will satisfy Utah audit requirements so long as adherence to the policy is
properly documented. In the alternative, separate documentation of delivery
address must be maintained. (Item 6.)

After-sale
adjustments for discounts, returns, allowances, etc. must be traceable back to
the original transaction. The use of
the same �supplier reference number� for both the original transaction and any
subsequent adjustments for discounts, returns, allowances, etc. is acceptable.
(Item 8.)

You
indicate that in order to support your system's tax logic, nonaxable and
taxable purchases are to be processed as separate transactions i.e., no �mixed� purchases of taxable and
nontaxable items in the same transaction.
This is sufficient to meet the requirement of item 5 above. Note that
without this segregation, the total charge of any �mixed� transaction
(containing taxable and nontaxable charges) would have to be taxed, unless
separate documentation were retained by the taxpayer.

Based
on these facts and on the provisos contained in this letter, the Sales Tax
Report provided by your system will meet our data reporting requirements
provided that the vendor actually supplies the information described. If the Report does not adequately document the
required information, the taxpayer (i.e., your c__orporate client__) will
have to supplement the report with evidence of compliance to avoid
assessment. Obviously, if there are
deviations from the facts provided here, this opinion may be negated.

Nothing
in this opinion is to be consi:rued as relieving the vendor of any of its tax
collection and recordeeping responsibilities as outlined under Utah law and
administrative rules.

For
The Commission,

Alice
Shearer

Commissioner

XXXXX

RE:
Advisory Opinion Purchasing Card Sales Tax Reports

Dear
XXXXX

We
have reviewed your request for a ruling that the XXXXX are an acceptable
substitute for vendorenerated invoices for purposes of demonstrating purchaser compliance
with Utah's sale and use tax laws. We
find as follows:

A
taxpayer is required to maintain sufficient sales tax documentation to
demonstrate the following:

1.
Transaction date (usually the purchase date for sales tax purposes and delivery
date for use tax purposes).

2.
Vendor.

3.
Purchaser (Corporate Client/Cardholder).

4.
Total amount of sale and total amount of sales or use tax paid.

5.
Sufficient item detail to distinguish between taxable and nonaxable items.

6.
Delivery address.

7.
FOB information

8.
After-sale adjustments for discounts, returns, allowances, etc. must be
traceable back to the original transaction.

As
we understand your system, your software will generate a Sales Tax Report based
on (1) information residing in your database, and (2) information supplied
electronically by the vendor at the point of sale. the information residing in
your database will automatically identify the vendor and the purchaser (items 2
and 3 above). The system allows the
vendor to input the total amount of the sale and the total amount of the tax
(item 4), the transaction date or the processing date (item I ), a shipping
address zip code (which may only partially satisfy item 6), and a 160 challcter
free text field that is used for description (item 5). At the Cardmember's direction the vendor can
input additional information in an optional field, called the Cardmember
Reference field.

You
indicate that your system identifies the delivery point of shipped items by
city, state and zip code (based on either the vendor's zip code for �take�
transactions or the �ship to� zip code in �ship to� transactions). This information is not sufficient to
identify the precise Utah taxing jurisdiction when the zip code covers more
than a single taxing jurisdiction.
However, if your corporate client implements a policy requiring that all
card purchases be shipped to the purchaser's mailing address, the policy will
satisfy Utah audit requirements to long as adherence to the policy is properly
documented. In the alternative,
separate documentation of delivery address must be maintained (item 6).

After-sale
adjustments for discounts. returns, allowances, etc. must be traceable back to
the original transaction. The use of
the same unique �supplier reference number� for both the original transaction
and any subsequent adjustments for discounts, returns, allowances, etc. is
acceptable (item 8).

You
indicate that in order to support your system's tax logic, nonaxable and
taxable purchases are to be processed as separate transactions -- i.e., no
�mixed purchases of taxable and nonaxable items in the same transaction. This is sufficient to meet the requirement
of item 5 above. Note that without this
segregation, the total charge of any �mixed transaction� (containing taxable
and nontaxable charges) is taxable unless separate documentation is retained by
your corporate client.

Based
on these facts and on the provisos contained in this letter, the Sales Tax
Report provided by your system will meet our data reporting requirements
provided that the vendor actually supplies the information described. If the Report does not adequately document
the required information, your corporate client must supplement the report with
evidence of compliance to avoid assessment.
Obviously, if there are deviations from the facts provided here, this
opinion may be negated.

Nothing
in this opinion is to be construed as relieving the vendor of any of its tax
collection and record-keeping responsibilities under Utah law.

For
the Commission,

Alice
Shearer

Commissioner