Skip to main content
Categorizing transactions one by one works fine for a handful of entries, but not for the thousands of similar transactions a typical crypto business generates. Automation Rules let you describe a pattern once (the conditions) and tell Breezing what to do with every transaction that matches it (the actions).

​
How Rules Work

You manage rules on the Rules V2 page in your company dashboard. Each rule has four parts:
  1. Conditions: which transactions the rule matches. A transaction must satisfy every condition on the rule. When a single condition lists several values (for example, three tokens), matching any one of them is enough.
  2. Actions: the fields the rule sets on matching transactions, such as the transaction account or a VAT rate.
  3. Order: the rule’s position in the list. Rules apply from top to bottom, and each rule finishes all of its matching transactions before the next one starts.
  4. Active toggle: inactive rules stay in your list but are skipped when rules are applied.
Rules never touch locked transactions, spam, or transactions that are still being processed, so your closed periods stay closed.
The Rules V2 page replaces the original Rules page, which is marked as deprecated in the sidebar. Existing rules from the old builder have been migrated, and new rules should be created in Rules V2.

​
Creating a Rule

  1. Navigate to Rules V2 and click Add Rule.
  2. Give the rule a clear name (e.g., “Client ABC inbound = Sales”). A short description helps your teammates understand the intent.
  3. Add your conditions. Use the search box at the top of the condition panel to jump straight to a field instead of scrolling.
  4. Add one or more actions and pick the value for each.
  5. Click Preview. Breezing shows how many transactions currently match your conditions, along with a sample of up to 15 of them, so you can sanity-check the rule before it touches anything.
  6. Click Save. Saving stores the rule; it does not apply it yet.

​
Conditions You Can Match On

Conditions are grouped into five sections in the rule builder:
  • Transaction: Direction (in or out), Type, Synced status, Internal flag, Function name (the smart contract method, useful for catching things like stake or addLiquidity calls), and the Skip Net Gain/Loss flag.
  • Assets: Tokens, Fee tokens, and Chains.
  • Accounting: Accounts, Asset accounts, and Fee asset accounts already assigned to the transaction. This is handy for finding transactions that still have no account.
  • Values: Amount, Amount (FIAT), Fee, Fee (FIAT), Net Gain/Loss, and Cost basis, each with range operators so you can target things like “any transfer above 10,000 USD”.
  • Company: Wallets, Folders, Contacts, and review Status.
Combining sections is where rules get precise. For example: Contacts equals “Blockchain Customer” plus Direction equals “In” matches every inbound payment from that customer, and nothing else.

​
Actions You Can Apply

  • Transaction Account, Asset Account, and Fee Asset Account: assign general ledger accounts from your chart of accounts.
  • Accounting Description: set the description that syncs to your journal entries in Xero or QuickBooks.
  • Note and Extra label: add internal context for your team.
  • Status: set the review status, for example to flag matches for a second look.
  • Internal: mark or unmark transactions as internal transfers.
  • Value Added Tax (VAT): apply a VAT or sales tax rate, as described in Applying VAT/Sales Tax.
  • Skip Net GL and Skip Net GL Reason: exclude matches from gain/loss calculations, the same flag covered in Avoid Gains/Losses on Staking & LPs. Pairing a Function name condition with this action is the fastest way to keep staking and bridging out of your cost basis.
  • Custom Price Ref: link matches to one of your manual token prices.
  • Xero Tracking Category and QuickBooks Class: these appear as actions once the respective integration is connected, so rules can assign cost centers during categorization.
When setting the Transaction Account, you can pick (auto) instead of a fixed account. Breezing then resolves the account from your balance sheet mapping, the same logic as the Auto Apply feature described in Internal Transfers & Trades. This is the right choice for rules that target transfers between your own wallets.

​
Rule Order and Priority

Rules apply sequentially, from the top of the list down. If two rules set the same field on the same transaction, the rule that runs later determines the final value. A practical way to structure your list:
  1. Put broad, catch-all rules near the top (e.g., “everything on the Treasury wallet goes to Digital Assets”).
  2. Put narrow exceptions further down (e.g., “transfers from the Treasury wallet to Exchange X are internal”). Because the exception runs later, it gets the final say on the transactions where both rules overlap.
You can reorder rules at any time; the order column on the Rules V2 page reflects the sequence.

​
Applying Rules

Saved rules do not run on their own. You decide when they run:
  • Apply a single rule using the apply button on its row. Inactive rules cannot be applied until you activate them.
  • Apply All runs every active rule in order, top to bottom.
Applying runs as a background task, so you can keep working while Breezing processes the matches. Every change is written to the transaction history with the rule’s name attached, so you can always trace which rule set a value on a transaction. Locked transactions are never modified, which means you can safely re-run rules after importing new activity without disturbing periods you have already closed and synced. A common month-end workflow: import the latest transactions, click Apply All, then filter the dashboard for transactions that still have no account. Whatever remains is genuinely new territory that needs a human decision, and possibly a new rule.

​
Managing Rules

  • Activate or deactivate a rule to include or exclude it from Apply All without deleting it.
  • Edit a rule to refine conditions or actions. Use Preview again before saving to confirm the new match count.
  • Delete removes the rule itself. It does not revert changes the rule already made; those stay on the transactions and in their history.

​
Rules via the API

Everything above is also available programmatically, which is useful if you manage many clients with similar setups. See the API reference for creating rules, listing rules, updating rules, and applying rules.
Last modified on July 6, 2026