Skip to main content
Five tools cover recurring bills. query_bills reads (pick a view), three tools write (pick an action), and get_upcoming_money shows the next fortnight in both directions. Full parameters for every tool are on the tools reference.
AI2Fin spots recurring payments in your transaction history and turns them into bills automatically — subscriptions, rent, insurance and other regular costs show up without manual setup. A pattern can also be recurring income (patternType: "recurring_income"), so rent you receive or a salary is handled by the same tools.

Reading bills

query_bills

period on the financial view is financial_year, year_to_date, calendar_year, all_time or custom. Financial-year bounds come from the country on your profile (July–June for AU and NZ, April–March for the UK, India and Canada, October–September for the US, calendar year elsewhere), so “how much have I paid Telstra this FY?” is one call:

get_upcoming_money

Money coming in and going out over the next days (default 14): bills due, expected income you’ve recorded, later dates of recurring income, and estimated pay days from your employers. Filter with direction (in, out, move, all) or placeId; set includeEstimates: false to drop the pay-day guesses. Each row carries direction, certainty (scheduled or estimated), status (upcoming, due_today, overdue, partly_received…) and the amount still to come; totals are per currency.

Managing bills

create needs merchantName, amount, firstDueDate and frequency (WEEKLY, FORTNIGHTLY, MONTHLY, QUARTERLY, YEARLY); categoryId, isTaxDeductible, businessUsePercentage, autoPayEnabled and notes are optional. There is no separate toggle tool — pausing is an update. delete permanently removes the pattern and its scheduled payments but keeps its bank transactions, unlinked.
On pay, pass transactionId to link an existing transaction as the payment; leave it out and a transaction is created for you unless createTransaction: false. Paying is money out only — an income pattern is refused unless you give a real deposit transactionId.
Run auto_link with dryRun: true to preview matches before anything is written; suggest_patterns (defaults: 3 occurrences over 365 days) changes nothing.

Good to know

  • Statuses. A pattern is isActive true or false. An occurrence is pending, paid, or overdue (past due and unpaid).
  • Monthly totals in the summary view normalise each frequency: weekly × 4, fortnightly × 2, quarterly ÷ 3, yearly ÷ 12.
  • Confirmation. Clients other than Meta Muse (which asks the user itself) get a needsConfirmation preview on the first write call and repeat it with confirmToken to execute. Muse is also never offered delete, create, update or batch_update on occurrences — those are done in the app.
  • Plans. All five tools are on every plan, with only the global rate limit.
  • Older names. The pre-consolidation bill tools are no longer registered — the rename table maps each one to its view or action.

Next steps

Transaction tools

Query, analyse and edit transactions

Full tools reference

Every parameter and return shape