Skip to content

Mon–Fri 9:00am – 5:30pm

Limited Get 30 days free on any paid plan. Start free trial
Banking

Recurring transactions that code themselves.

In short

Bank rules are on Business and above. After you upload a CSV, matching descriptions get the account or payee you set, so the next statement needs less clicking.

What you can do

Set the rule, forget the coding.

Tell SwiftBooks Pro once how to treat a regular transaction.

📐

Create rules

Match when the description contains, starts with, or equals the text you set.

🔄

Apply on the next CSV

Matching lines are coded when you import the statement.

🏷️

Account or payee

Each rule can set the account, vendor, customer or expense category.

Why it matters

Consistent coding, zero effort.

⏱️

Save time

Recurring transactions stop needing manual attention.

📚

Consistent

The same transaction is always treated the same way.

✅

Same coding next time

The same description is treated the same way on the next import.

FAQ

Common questions

What are bank rules in SwiftBooks Pro?

On Business and above, rules match description text on a CSV import and apply the account or payee you set.

What can trigger a rule?

A match on the description (contains, and similar operators). The rule runs when you import the next CSV, then you Reconcile.

Can a rule set the account?

Yes. A rule can set the account, vendor, customer or expense category. You can still edit a line before you Reconcile.

Can I edit a transaction that a rule coded?

Yes. Auto-coded transactions remain fully editable before they're reconciled.

Code once, not forever

Repetition handled automatically.

Set the rule once. The next CSV import applies it. Bank rules are on Business and above.