How do bank rules automatically code transactions in Kontuly?

Applies to Kontuly 0.2 beta Updated

In Kontuly, click Rules on the Banking screen to open Auto-categorisation rules. Each rule codes any imported transaction whose description matches your text to the account you choose, so regular items don't need coding by hand.

  1. Click Rules at the top of the Banking screen.
  2. Choose how to Match. Contains matches your text anywhere in the description, ignoring capitals: UBER matches "Uber *Trip Sydney". Regex is for advanced patterns.
  3. Type the Pattern.
  4. Choose the account under Assign to.
  5. Choose the Bank account. Keep All bank accounts, or pick one, for example a card-fees rule for the credit card only.
  6. Choose a Tax rate if needed. Only when this rule's transactions need a different GST rate from the account's own (registered businesses only).
  7. Leave Apply automatically on import ticked and click Add rule.

When do rules run?

  • On transactions imported from a CSV or PDF file, into the bank account the rule is for. The import summary says how many were auto-assigned.
  • Not on transactions you add by hand or with Quick Input.
  • Whenever you click Apply rules on the Banking screen. That runs every rule, paused ones included, over the unassigned lines only. Use it after adding a rule.

When more than one rule matches, the most recently added rule wins. A line coded by a rule is just like one you coded yourself: you can unassign it.

Change, pause or delete a rule

  • Edit: click the rule's pencil icon, change it, then Save rule. Editing doesn't recode lines already coded; click Apply rules to run it over waiting lines.
  • Pause: untick Apply automatically on import. The rule shows as paused.
  • Delete: click its bin icon.

Can a rule code customer or supplier payments?

No. Accounts Receivable and Accounts Payable aren't offered: payments from customers and to suppliers are matched to invoices and bills. A rule can assign to another bank account, which records a transfer.

Tips

  • Keep patterns specific. ATM could catch more than you expect.
  • Check the auto-assigned lines after each import until you trust your rules.

Rule didn't code something? See Why didn't my bank rule code a transaction?

More about banking and reconciliation