Allocation Rules

Allocation Rules automate the process of assigning transactions to funds. Once configured, rules match incoming transactions and allocate them instantly, reducing manual work and ensuring consistency.

Rule Types

Rules match transactions using two primary criteria:

Descriptor Matching: Match transactions based on their description or memo text. This works for both bank-imported and manually entered transactions. Choose between exact or partial ("contains") matching.

Example: Rule matches description "Weekly Offering" → allocates to General Fund.

Category Matching: For bank-connected transactions via Plaid, match based on the merchant category code. Plaid assigns categories like "Restaurants," "Utilities," or "Gas Stations" to each transaction automatically.

Example: Rule matches category "Religious Organizations" → allocates to Building Fund.

Allocation Targets

Define where matched transactions go:

Single Fund: Assign 100% of matched transactions to one fund.

Multiple Funds (Fixed Amount): Split matched transactions across multiple funds using specific dollar amounts.

Example: $500 donation → $300 to General, $200 to Missions.

Multiple Funds (Percentage): Distribute by percentage. Percentages must total 100%.

Example: Donation → 60% General, 40% Building.

Account Restriction

Rules can be scoped to specific bank accounts. This allows different allocation logic for different accounts.

Example: Restrict a rule to your "Building Fund Account" so donations to that account automatically allocate to the Building Fund, while the General checking account has its own allocation rule.

If no account restriction is set, the rule applies to all accounts.

Active/Inactive Toggle

Enable or disable any rule without deleting it. Disabled rules do not match new transactions but remain stored for reference. Use this to temporarily pause a rule during transitions or special circumstances.

Retroactive Application

After creating or modifying a rule, you have the option to apply it retroactively to unallocated transactions in your history. The system will scan past unallocated transactions and apply the new rule to matches.

Important: This only affects unallocated transactions. If a transaction has already been manually assigned, retroactive rules will not override it.

Priority System

When multiple rules could match a single transaction, the system applies them in priority order (typically by creation or explicit priority setting). The first matching rule allocates the transaction unless you allow multiple matches.

Configure rule priority by reordering rules in the Rules list. Drag-and-drop to change priority.

Best Practices

Start with broad rules (by Plaid category) for common transaction types, then add specific descriptor rules for unique needs. Regularly review unallocated transactions to identify gaps in your rules and refine them. Test new rules on a small date range before applying retroactively to your entire history.