The assistant says your most overdue customer owes CRC480,000. That sounds plausible. Before calling, though, you need to know which invoices it included, the balance date, and whether yesterday's payment was considered. Verifying an accounting AI answer means rebuilding its figure from identifiable records. Confident wording is not evidence that the answer addresses the question you intended to ask.
Ask a question you can check
Specify the company, period, currency, and selection rule. Instead of asking how collections are going, ask for this company's open CRC invoices overdue at September 30, with later payments identified separately. That creates something you can compare. For sales, explain whether you mean issued invoices, accounting revenue, or collected deposits. These are different populations even when their totals happen to match in a quiet month.
In Tario, check the active company and your permissions. The assistant queries information and prepares proposals within that context. Do not assume that an earlier discussion about another entity defines the current query. A figure may be correct for North Distribution and wrong for North Services. Sharing an accountant or trading name does not combine their business records.
Request the records behind the conclusion
A checkable answer identifies documents, dates, and filters rather than only a total. Ask for invoice numbers, original amounts, recorded payments, and the balances used. Open those documents in the application. If you cannot locate a record, request clarification before putting the answer in a collection email or journal entry. You need the business evidence, not a technical account of how the model generated its wording.
Suppose a CRC300,000 invoice has received CRC120,000 and a CRC200,000 invoice has received CRC20,000. Together they have CRC360,000 outstanding. An answer of CRC500,000 may describe invoiced value rather than debt. An answer of CRC340,000 calls for a search for another payment, adjustment, or date difference. Recalculate each invoice before arguing about the overall conclusion; that shows where the discrepancy begins.
Separate extraction from interpretation
For a PDF or image, compare extracted fields with the original file. Check number, currency, dates, quantities, and total. A screenshot can omit the discount column, while a scan can obscure a decimal. Twelve boxes containing ten units each are not twelve individual units. Ask the assistant to distinguish visible information from inference, then fix extraction errors before assessing an accounting classification.
A source document can establish supplier and amount without establishing accounting treatment. A materials purchase suggested as maintenance might actually relate to an equipment improvement. Read the description, contract, and intended use. AI can help assemble those facts, but someone familiar with the transaction must decide how it belongs in this company's books. Correct arithmetic does not settle that judgment.
Check the scope of the comparison
- Use the same company and dates, and distinguish a historical cutoff from today's balance.
- Keep currencies separate instead of adding dollars and colones as equal units.
- Identify the document types and statuses included or excluded.
- Look for later payments and corrections that explain a changed result.
A common mismatch compares September invoices with a report filtered to September payments. One follows documents; the other follows cash movements. An October payment changes the current balance of a September invoice without creating a September deposit. Write down the cutoff for your review. That short note stops colleagues from trying to reconcile two reports that answer different questions.
Review proposed actions separately
Checking data does not authorize an action. In Tario's manual AI workflows, preparing or saving a draft does not issue it. Issuance requires explicit confirmation and the applicable validations. Review the current proposal's customer, lines, currency, and totals. If you change a quantity during the conversation, read the updated proposal again; earlier approval should not become unrestricted permission for later changes.
After a timeout or error, first check whether the requested record or result already exists. Do not blindly repeat a sensitive instruction. Work may have been saved even if the final reply did not appear. Locate the record and check its state before starting another operation, particularly when colleagues are also preparing documents for the same customer.
Make the review repeatable
For an important decision, keep a short note with the question, cutoff date, documents checked, discrepancy, and resolution. For example: Customer South at September 30, invoices 104 and 109; an October 2 payment explains the CRC80,000 difference from the current balance. Avoid copying an entire conversation or unnecessary personal information. Specific evidence lets another person repeat your check without treating the chat answer as the sole source.