Files
Statements, receipts, and historical workbooks.
Month-end workbench
Neltik turns repeat files into reviewed workbooks.
Upload statements, receipts, and recurring spreadsheets. Neltik learns your rows, flags uncertainty, and exports the workbook your team actually uses.
may_close_output.xlsx
review queue
82 ok
9 review
Source row
Amount
Result
Status
Correction saved
Next run remembers this row pattern.
Workflow
Files go in. Uncertainty gets reviewed. A workbook comes out.
The product story is visible on the page because it is the product: a structured path from messy monthly input to clean, reviewed output.
Engine
Your examples, notes, schema, and memory.
Review
Only the uncertain rows ask for judgment.
Workbook
A clean Excel file ready for close.
Proof Grid
The spreadsheet is the brand.
The landing page should feel like Neltik already touched the work: rows organized, decisions visible, and every correction turning into memory.
Engine memory
3 signals
Example
OXXO TIENDA usually maps to Office supplies.
Correction
Uber with executive card is Travel.
Note
Ask before changing VAT treatment.
Engines
Bank statements to classified Excel.
Mexican bank PDFs, multi-entity taxonomies, historical examples, and reviewable confidence in one loop.
Receipts to structured workbook rows.
Vendor, total, date, category, and notes pulled from repeat receipt batches into a consistent spreadsheet.
Security
Built for the files finance teams actually handle.
-
Review before export
Low-confidence rows stay visible until a person accepts or corrects them.
-
Every correction becomes memory
The next month starts from what your team already decided.
-
Audit-ready output
Decisions, examples, notes, and generated workbooks stay attached to the run history.
Bring one month of real files.
The first useful answer is not a demo. It is a workbook you can inspect.
Open the workbench