Knowledge Base
A plain-English reference for the dashboard. Each entry explains one field or behavior, so a term that looks unfamiliar is quickly clear, and correct behavior never reads as a surprise.
What each field on a transaction means, and when it should be filled in or left empty.
The Customer field is only used for revenue, the money you receive. On a bill or invoice that you pay, an expense, there is no customer, so the field stays empty. The company the invoice is addressed to, your own company, belongs in the Corporation field, not Customer.
The party you pay on an expense, the merchant or supplier. It holds the name only, without invoice numbers or addresses.
Which of your own registered companies a transaction belongs to. It fills automatically only when that company is registered in the client's Registry (Companies). This prevents the AI from inventing a company. Tip: register each company and add its "Also appears as" aliases (for example HLRI, BBMS) so it is recognised even with typos, abbreviations, or a missing space.
The money-flow view of a transaction: From is the party the money comes from (the payer), To is the party it goes to (the payee). This complements Vendor and Customer, which is the role view.
The tax nature of a transaction. The AI infers it, business by default for company documents. If the transaction matches one of your registered bank accounts, that account's Business or Personal tag takes over as the source of truth. This is separate from Account Type.
The accounting class of the line under GAAP and IFRS (for example Income, Expense, Cost of Goods Sold, Fixed Asset). It anchors the GIFI code so the two never conflict.
A short, human-friendly label under the Account Type (for example Subcontractors, Utilities, Meals & Entertainment). The AI always proposes the most likely one.
The most specific international IFRS and GAAP financial-statement element for the line (for example "Cost of sales", "Repairs and maintenance expense"). It is advisory detail for accountants.
The Canadian CRA tax-return code. It is derived from, and kept consistent with, the Account Type, and you can still refine it. GIFI is Canada-only, while the Account Type and IFRS Tag are international.
What the AI captures from an upload, and the choices it makes on purpose so your figures stay faithful to the original.
The AI decides whether a document is an expense or revenue from your perspective, using the document's own labels (Bill To, Ship To, From account, Paid to). If a document names two parties and neither is clearly you, it flags the direction as uncertain rather than guessing.
Amounts are captured exactly as printed on the document and are never converted at capture. Converting to your books' base currency happens separately, so the original figure is always preserved.
A date written in a non-Gregorian calendar (for example Jalali or Hijri) is left blank for you to set, rather than being guessed or mis-converted.
If a file has no financial transaction in it (for example a random photo or a note), the AI correctly produces no transaction. That is expected, not an error.
How work moves from an upload to approved books, with you in control of every entry.
Transactions the AI extracts from an upload are created as pending drafts under the selected client. Nothing posts to your books automatically. You review and approve each one in Record Keeping (use the Pending filter). Make sure the correct client is selected before uploading.
No entries match your search. Try a shorter term, for example "GIFI" or "currency".
If a term or behavior isn't covered here, our team is happy to walk you through it. You can also start a free trial and see the dashboard for yourself.