AI financial review starts with the report, rather than the prompt. A clear question is useful, but it cannot fix a missing period, an ambiguous header, or a source total that does not agree with the supporting rows.
For Ask Jabby, the starting point is an Excel export whose layout the team can review during onboarding. You can keep your existing accounting system. The important questions are what the report represents and whether that structure stays consistent.
1. Start with the report you actually use
Choose an export that your finance team already understands. For a month-over-month revenue question, that may be an income statement. For a category-level cost question, you may need a more detailed supporting report.
Before sharing a layout, identify:
- The company the report belongs to.
- The reporting period and accounting basis.
- The currency and unit, such as dollars versus thousands of dollars.
- The measure each numeric column represents.
- Whether a column is a single month, a year-to-date total, or another cumulative period.
An export from QuickBooks or Yardi is one possible input. Neither platform is a prerequisite. The report structure is what the Ask Jabby team reviews.
2. Keep the headers consistent
A stable header row helps distinguish account names, period columns, and values. Once a layout is confirmed, keep the column meanings and header wording consistent in the next export.
Adding a new month’s column can fit the same workflow when its period is clear and the existing template remains consistent. If the structure changes, tell the team before treating it as another instance of the previous layout.
3. Check the totals before the upload
Compare the report with the version your team uses for financial review. Confirm that supporting rows and totals make sense in the source workbook.
For example, consider a sample report showing revenue of $270,000 and cost of revenue of $175,000. Gross profit is $95,000. If the total in your export says something different, understand that discrepancy before relying on a margin comparison.
These are illustrative figures. The useful habit is to resolve the source disagreement, rather than expecting a fluent explanation to make it disappear.
4. Make period labels explicit
“June” needs a year. “Q2” needs a date range. “YTD” needs the period it ends in.
Keep monthly and cumulative measures distinguishable. Comparing a monthly expense with a year-to-date total produces an unhelpful result even when the arithmetic is correct.
5. Have a plan for restatements
A workbook can change after its first upload. Record which version is current and tell the reviewer when a previously uploaded period has been revised.
In Ask Jabby, operators can delete uploaded reports. When replacing a report, confirm that the workspace uses the intended version before asking for a new multi-period comparison.
A short handoff checklist
Before a layout review, be ready to explain:
- Which business question the report should answer.
- What each header and numeric column means.
- Which months or periods are included.
- Which totals your team uses to check the report.
- Who will upload, review, and replace future reports.
Keep financial attachments out of the initial contact email. Talk to the Ask Jabby team first to discuss the setup process and an appropriate way to share a sample.
You can also explore the product workflow or read about company access and data controls.