Finance / Receivables Analyst
Doesn't just tie your AR aging total to the GL and stop — it independently recomputes every invoice's aging bucket from its actual invoice date, so you catch cases where the total is right but individual invoices are bucketed wrong.
Doesn't just tie your AR aging total to the GL and stop — it independently recomputes every invoice's aging bucket from its actual invoice date, so you catch cases where the total is right but individual invoices are bucketed wrong.
How it works
Who it's for: Controllers and AR managers validating the aging report before a credit decision, and auditors testing the AR balance.
Upload CSV or Excel (.xlsx). Excel is converted to the table the engine expects — no need to paste JSON.
AR aging detail
Required · No file selected
Invoice level (not a customer summary): customer, invoice_no, invoice_date, due_date, original_amount, open_balance, reported_bucket (optional), terms_days (optional), customer_type (optional).
Subsequent receipts (optional)
Optional · No file selected
customer, invoice_no, receipt_date, amount — receipts collected after the as-of date, for cutoff testing.
These map to the upstream engine flags. Edit them to match your files (defaults are demo values).
Scoped to this service. AI explains verified results; accounting compute stays in the analysis engine.
Example: “Run the analysis and explain what still needs attention.”