Skip to content
  • There are no suggestions because the search field is empty.

What is the purpose of the Plaid integration?

WickedFile gives you the ability to integrate your shops Bank Account & Credit Cards

What Is the Purpose of the Plaid Integration?

WickedFile is built to optimize and reconcile the AP process for auto repair shops. But here’s an important reality:

Vendor statements only cover a portion of your part activity.

Many vendors in auto repair operate on:

  • Net-30/60 statement accounts

  • COD/Credit Card only accounts (like dealerships)

  • One-off or sublet vendors

If you only rely on statements to manage AP, you are only seeing part of the picture.

That’s where the Plaid integration comes in.

The Core Purpose of Plaid

Plaid connects your bank and credit card accounts to WickedFile in a secure, read-only manner. It allows WickedFile to see actual transaction activity — not just documents.

This matters because:

  • Statements only show activity for statement vendors.

  • COD vendors often do not send statements.

  • Card purchases happen daily.

  • Checks are written outside the statement cycle.

Plaid ensures WickedFile can see all spend activity, not just statement-based spend.

1. See Which Invoices/Statements Have Already Been Paid — And Which Haven’t

A major benefit of the Plaid integration is payment visibility.

WickedFile can determine:

  • Which invoices have reconciled to bank transactions (signifying payment)

  • Which vendor statements have already been paid

  • Which ones remain outstanding (not paid)

Instead of relying on memory, spreadsheets, or assumptions, you have transaction-backed clarity.

This is especially valuable in multi-location environments where payment timing can vary.

2. Visibility Into Part Transactions Missing Invoices

When Plaid is integrated, WickedFile pulls in real bank and credit card transactions — including purchases from parts vendors.

This allows you to see something critical:

Which part transactions do not have an associated invoice uploaded.

If a transaction exists but no invoice has been uploaded:

  • There is no extracted part data.

  • There is no PO-to-RO visibility.

  • There is no coding in the AP Hub.

  • There is no part-level accountability.

In other words, the visibility on those parts is not available.

Plaid exposes these gaps by surfacing transactions that have money movement but no supporting invoice in WickedFile. That gives you the opportunity to upload the missing documentation and bring those parts back into a controlled, reconciled workflow.

3. Ensuring COD Vendor Spend Is Fully Accounted For

When a transaction is reconciled to an invoice, WickedFile displays the part status (code) next to it — such as:

  • Sold to Customer

  • Inventory Purchase

  • Shop Supply Purchase

  • Bought for RO Not Sold

  • Uncategorized Spend

This allows you to ensure that for COD vendors — where there is no statement safety net — the transaction side is paid, and the part side is fully accounted for.

You’re not just confirming the money went out.

You’re confirming the parts tied to that money are properly coded within your AP process.

The Bottom Line

The purpose of the Plaid integration is to give WickedFile full visibility into your shop’s actual spend — beyond just statement vendors.

Statements cover a portion of your AP activity.

Plaid covers the rest.

Together, they create a complete, disciplined, financially accountable AP process — exactly what modern auto repair operations need.