Connecting a bank account or credit card gives WickedFile the charges and payments to compare against your documents. It is the one integration an admin can set up without contacting support, because Plaid handles the sign-in and WickedFile never sees or stores your banking credentials.

This article covers the steps, which accounts are worth connecting, what to expect after the first sync, and what still works if your institution is not supported.

Every other integration on that screen is set up by the WickedFile team, for the reasons in why you cannot connect an integration yourself.

Transactions arrive as a feed, and each one can be tied to the document that explains it.

That matters most for vendors who do not send statements. A parts house you pay by card at the counter has no month-end statement to check against, so the card charge is the only record that the purchase happened. Without the feed, an invoice that was never uploaded has nothing to be missing from.

The feed also lets a reconciled statement show the payment that settled it, which is covered in bank payments on a statement.

Connect the operating account and the cards used for parts and shop purchases.

Payroll, savings and an owner's personal card do not need to be connected. Each additional account adds transactions with no parts behind them to a screen that works best as a short list.

Allow one sync cycle before judging the result. A freshly linked account shows Last sync · never until the first pull completes.

The card shows a count such as 0 of 1 synced. If that is still zero after a day, the link exists but nothing is coming through it, which is worth a support ticket.

Renaming accounts early makes the transaction list easier to read. Bank feeds arrive with names like CHECKING 4471, and renaming that to Cedar Springs operating tells you which shop a charge belongs to at a glance.

Once transactions are arriving, the Transaction Viewer is where you read them.

Plaid supports most institutions but not all, and some smaller banks and credit unions are missing.

If yours is unsupported, the rest of WickedFile works as normal. Statements, invoices, part coding and repair order matching are all unaffected. What you lose is the ability to spot a card purchase with no invoice behind it, so counter purchases depend on somebody bringing the receipt in.

Tell support which institution it is. Coverage requests are recorded, and knowing which banks customers use is how they get prioritised.