LedgerBooks

Transactions from the bank feed or a statement import. By default this shows what is still waiting to be categorized ('For review'), which is the queue a bookkeeper works through. Money in is positive, money out is negative.

list_bank_transactions

One call that answers 'how is the business doing': cash on hand, money owed to you, money you owe, income and expenses this month and year to date, net income, overdue invoices, and how many bank transactions are waiting to be categorized. Start here when the question is general.

get_business_snapshot

Indirect cash flow statement for a period: net income adjusted for movements in receivables, payables and other balance-sheet accounts, split into operating, investing and financing, with cash at the start and end. Includes an independent tie-out against actual cash movement.

get_cash_flow

What is in every bank, cash and credit-card account right now, with the total cash available and total owed on cards. Answers 'how much money do I have'.

get_cash_position

Take a transaction out of the bank review queue by assigning it a category account, exactly as clicking Add in the app does. For money out you can also name the payee, which records a proper expense. Use match_bank_transaction instead when the transaction is a customer paying an invoice or you paying a bill.

categorize_bank_transaction

Categorize many waiting bank transactions in one approval, each to its own category (with an optional payee for money out, received_from for money in, a job, or a new description) — exactly what Add does on the For Review screen, line by line. Lines that are no longer waiting are left out and named. A payment of a specific invoice or bill, or a transfer already recorded in the company's other account, belongs to match_bank_transaction instead; categorizing it would count the money twice.

categorize_bank_transactions

The chart of accounts with each account's code, name, type, subtype and current balance. Call this when you need an account code for another tool, or to understand how the books are organised.

list_accounts

A whole-company health check, the way an accountant reviews a new client's file: debits equal credits, Accounts Receivable and Payable agree with the customer and vendor balances, Undeposited Funds makes sense, transactions stuck in For Review, accounts never or not recently reconciled, broken bank connections, balances with the wrong sign (a credit card showing a credit, a negative liability), money parked in holding accounts, overdue invoices and bills, stale drafts and unlikely dates. Use it when asked whether the books are right, before month or year end, and as the first step of any clean-up.

check_books_health

Remove every bank-feed transaction on one bank, cash or credit-card account — optionally only within a date range — cleanly undoing whatever categorizing them created (expenses, payments, feed entries), so the account can be rebuilt, usually by importing statements. Categorization rules, import history and anything entered directly are kept. Refused if any of the transactions are in a completed reconciliation. Use this for a real cleanup, after showing the person what is wrong; for one transaction use undo_bank_transaction.

clear_bank_account_feed

Which company these books belong to, its currency, fiscal year start, business contact details, tax rates on file, payment terms, and the access this connection has. Call this first if you are unsure what you are connected to.

get_company_info

Turn an accepted estimate into a draft invoice carrying the same lines, tax and discount. The estimate is marked converted and linked to the new invoice.

convert_estimate_to_invoice

Create a job (project) that invoices and expense lines can be tagged to, so its profitability can be tracked.

create_job

Post a manual journal entry. Total debits must equal total credits — the database enforces it. Lines hitting Accounts Receivable must name a customer and lines hitting Accounts Payable must name a vendor, exactly as in the app. Use this for adjustments, not for anything a proper document can record.

create_journal_entry

Create an estimate (quote) for a customer. Estimates never touch the ledger — they become real money only when converted to an invoice.

create_estimate

Create an invoice for a customer. Saved as a draft by default so it can be reviewed; pass post=true to post it to the ledger straight away, which is what makes it owed by the customer and counted as revenue. Returns the invoice number.

create_invoice

Hide an account from pickers (deactivate) or bring it back (reactivate). Its history and balance stay in every report. System accounts cannot be deactivated.

set_account_active

A bookkeeper's full check of ONE bank, cash or credit-card account: months with no transactions (a missing statement), where the transactions came from (bank connection vs which imported files, including files for a different card number), whether the connected bank account matches the account's name, entries recorded twice (entered by hand AND categorized from the bank), bank lines imported twice, money waiting in For Review, and whether its reconciliation still holds. Use it whenever someone says an account's balance looks wrong, before clearing or re-importing an account, and after importing statements.

diagnose_account

Discard the reconciliation in progress on an account: its ticks are dropped. Completed reconciliations and the books are not touched.

cancel_reconciliation

Enter a bill you owe a vendor. Saved as a draft by default; pass post=true to post it, which is what makes it a payable. Use record_expense instead when the money has already gone out.

create_bill

Take transactions waiting in For Review out of the queue without recording anything — for duplicates, pending charges that later settled under a different id, or anything that should not be in the books. Only transactions still waiting in For Review can be excluded. They can be restored later.

exclude_bank_transactions

Retrieve the full record behind an id returned by `search`, as readable text plus structured fields. Use this to read a document, contact, item or account in full after finding it.

fetch

Looks for anything recorded twice: bank lines imported twice (a CSV over the bank feed, overlapping files), the same statement line on two different accounts (a file imported into the wrong account), and documents entered twice — expenses, bills, invoices, customer payments, checks, and a bill paid through Pay Bills that was also recorded as an expense. Repeated charges that each came from their own bank line (four fees on one day) are deliberately NOT reported. Defaults to the last 12 months.

find_duplicate_transactions

Import a statement that has been read and TIES into a bank or card account's For Review, exactly like importing the bank's CSV: lines already in the account are skipped, lines previously excluded come back, nothing is categorized except by the company's own bank rules. The plan shown before approval is the real import run and rolled back, so the counts are exact. Refused for a statement that does not tie or was already imported.

import_statement

Every job (project) with the income tagged to it, the costs tagged to it, and the resulting profit and margin. Jobs are an optional tag on invoices and expense lines.

list_jobs

Customers, with contact details and how much each currently owes. Search by name, company or email.

list_customers

Everything you sell, with its price, whether it is a product or a service, whether it is taxable, and which income account it posts to.

list_items

List any kind of document in the books: invoices, estimates, sales receipts, credit memos, customer deposits, customer payments, bills, expenses, checks, purchase orders, vendor credits, bill payments or journal entries. Filter by status, customer or vendor, date range, amount, and whether anything is still outstanding.

list_transactions

Vendors, with contact details, how much you currently owe each, and whether they are tracked for 1099 reporting.

list_vendors

Tie a bank transaction to the document it actually is: a deposit to the customer invoice it pays, or a withdrawal to the vendor bill it pays. This records the payment rather than booking new income or expense, which is what stops the same money being counted twice. Paying more than the document's balance leaves the remainder as a credit.

match_bank_transaction

The month-end close checklist for one month: for every bank and card account, are that month's transactions in, all categorized, and reconciled; drafts left in the month; money still in Undeposited Funds; vendors paid every month that have nothing this month (a missing bill); and expense or income accounts that moved unusually against the previous three months. Defaults to last month.

month_end_close_check

Post a draft invoice to the ledger. This is what makes it owed by the customer and counted as revenue. Balanced journal entries are created by the posting engine.

post_invoice

Income and expenses over a period, grouped into income, cost of goods sold, expenses and other, with gross profit, operating income and net income. Optionally compares to the previous period of the same length.

get_profit_and_loss

Read an uploaded bank or credit-card statement: the account it belongs to, its period, opening and closing balances and every transaction line — and PROVE the reading by checking the lines reproduce the statement's own closing balance to the cent. A statement that does not tie is never imported. It is read on our own servers first; only a statement that cannot be read that way is sent to the AI reader. Reading saves the result with the file (so it is not read twice); it never changes the books. A statement can only be imported after its reading ties.

read_statement

One customer's details, current open balance, available credit, and their recent invoices and payments.

get_customer

Everything about one document, including its line items, totals, tax, discount, who it is with, what has been paid or applied against it, and the journal entry it posted. Identify it by document number (for example 42, or INV-0042) or by id.

get_transaction

One vendor's details, what you currently owe, and their recent bills, expenses and payments.

get_vendor

Reconcile a bank or card account to a statement. Best with a statement that has been uploaded and read (statement): each statement line is matched to the entry in the books with the same amount within a week, the account's opening balance is used on a first reconciliation, and anything on the statement the books lack is named. Without a statement, give end_date and ending_balance and everything uncleared through that date is ticked. It completes only when the difference is exactly $0.00; otherwise the ticks are saved in progress and the plan says what is off. The plan shows the engine's own figures before anything is saved.

reconcile_account

Where each bank and card account stands on reconciliation: reconciled through which date and to what statement balance, any reconciliation in progress (with its difference), and uploaded statements waiting to be reconciled next. Give an account for its history.

reconciliation_status

Record a payment the business has already made to a vendor, and apply it to that vendor's open bills. This only writes the payment into the books — it never sends, moves or initiates any money. Name the bank, cash or credit-card account it was paid from. Give explicit allocations, or leave them out and it is applied to the oldest bills first.

record_bill_payment

Record money a customer has already paid, and apply it to their open invoices. This only writes the payment into the books — it never charges a card or moves any money. Give explicit allocations, or leave them out and the payment is applied oldest invoice first. A payment larger than what is owed leaves the remainder as a credit on the customer's account.

record_payment