Telegram and email: send it in, review it here
On a server install, photograph a receipt in the shop and send it to the workspace's own Telegram bot, or forward a bill by email: it is read, drafted and waits for you in the app. Nothing reaches the ledger until someone confirms it, unless you told the chat it may. The desktop edition has no public intake endpoint and blocks outbound network connections unless a host is allowed, so receipts and statements there are uploaded directly in the app.
- 1
Add the workspace's Telegram bot
On a server install, the workspace owner creates a bot with Telegram's BotFather and, under Settings → Intake channels, gives its Bot token to Telegram bot, with the Book for new drafts when the workspace keeps more than one (with one, drafts land in it); saving checks the token with Telegram (on the desktop edition, outbound connections are refused until the host is allowed, and there is no server receiver to deliver messages). A bot belongs to one workspace. Once saved, the bot folds to one line; Change bot opens its form again, and Disable bot stops it at any time.
- 2
Link your Telegram account
Each member links their own account: under Link your Telegram account, Link Telegram makes a one-use link, valid for ten minutes. Open in Telegram opens the bot and sends it for you, or send the /link command it shows privately to the bot.
- 3
Send a receipt or a question
In your private chat with the bot, send a photo or PDF of a receipt — each photo of an album is a receipt of its own — a forwarded payment message, or a question in words. A receipt is read by the workspace's AI and drafted; the bot says what it read and asks what it needs — which account paid, if it cannot tell. A question in words is not answered in the chat: it is kept, like anything else that is not a payment, for someone to review in the app.
- 4
Or forward it by email
Email arrives through a mail transport the installation's operator sets up and grants to your workspace. Under Settings → Intake channels, Email connections adds one: give it a Name, choose the Mail transport if the operator granted more than one, and pick the Default currency and, when the workspace keeps more than one book, the Default book its mail is drafted into — a receiving address needs that book; with one, it is that book. Then Rotate a mail route, with the Domain the operator gives you, makes the address to forward to — shown once, so copy it then. Each photo and PDF a forwarded mail brings is read as a receipt of its own — or kept as a statement, when it is one — and a receipt with nothing attached, such as an order confirmation, is read from the message itself. An e-mail never says who sent it, so it waits until the workspace owner takes it, and then acts with the owner's access; the owner does so with Take it, on the e-mail under Intake. Until an operator grants a transport, the panel says so instead. A Gmail mailbox is planned instead, through your own Google OAuth client: under Gmail, Add a Gmail connection and Save your Google OAuth client — the one from your own Google Cloud project, whose secret is sent once. The panel lists Authorize a mailbox as the last step, which cannot be done from the app yet, so nothing is read from Gmail so far.
- 5
Send a statement too
A bank statement sent in the chat or forwarded by email is imported for you, as if you had uploaded it, and keeps its file. An OFX, CAMT, MT940, QIF or Wise file goes into the account its own account number names, once that number is remembered for the account — or, for a file of one statement naming no account, into the book's only bank account; a CSV or spreadsheet export goes into that one bank account when its columns read as a statement by themselves or as a bank's known export. The reply names the account and how many lines it holds, with a link to review them. When the book has more than one bank account and the file does not say which, the bot asks which account it is for, with a button for each; press one within a day and it is imported there — after that, upload it under Statements. A PDF or a photo of a statement is kept for the book's one bank account and read, and waits under Statements for you to check its reading and import it. A statement it cannot place, read, or you may not import stays for review in the app — a CSV is read with the message instead — so upload it under Statements to choose its account or columns.
See also: Bank accounts, statements and receipts
- 6
Tell it how you pay
Under Settings → Intake channels, People and defaults lets each linked identity have its default account, and Add a card ties the last digits of a card to the account it Pays from, so a receipt paid by that card drafts against the right account. Cash defaults name the cash account for each currency, and aliases teach it the names you use.
- 7
Review what it drafted
A payment forwarded or told to the chat waits under Inbox → Receipts → To review, in Payments told to the chat: choose the account it was Paid from and its Category, then Record payment — or Discard it. Receipts the chat brought wait beside it like any other, and beneath them, whenever there are any, Other things sent to the chat lists the rest: Confirm accepts what was read and Commit records it, while Cancel sets one aside — Commit asks Record this draft?, and Cancel asks Set this draft aside?, before either acts. Inbox → Intake shows every message that arrived and what it became.
- 8
Let it record unasked, or not
Under Settings → General, When a photographed receipt is fully read decides what the chat may do: keep it for review in the app, ask in the chat, or record it when everything is trusted — a receipt paid in cash from the sender's cash default, into a household book, with every category from a rule, a merchant's pin or the person's own choice — never above the Most recorded unasked limit of each book. A receipt paid by card is always asked about. Only the workspace owner may let it record unasked.