Earlier quoted context omitted.
I have 15 debtors, a few dozen creditors, and 5 employee credit cards. There’s enough transactions that for the 3 years I’ve been reconciling the accounts I have wanted to either write an if/elseif/else-based reconciler assistant, or hire someone, or pay my accountant to do the job. A few weeks ago, I decided, what the hell, and I spent two days writing a ChatGPT-powered reconciler assistant. It’s so damn accurate. B…
Whether something is better than nothing depends on its error rate and the consequences of an error.
Reconciliation is a knapsack problem
31–40 of 57 posts
Re: Reconciliation is a knapsack problem
#32I profoundly disagree that ML models are a good fit for transaction reconciliation. It’s at least arguable that this task is the oldest documented use of writing, and from double-entry accounting to price/time precedence in modern market microstructure, we have algorithms that align very well with human intuition. I can think of few cases where gratuitous application of even simple statistical methods would cause mor…
I have 15 debtors, a few dozen creditors, and 5 employee credit cards. There’s enough transactions that for the 3 years I’ve been reconciling the accounts I have wanted to either write an if/elseif/else-based reconciler assistant, or hire someone, or pay my accountant to do the job. A few weeks ago, I decided, what the hell, and I spent two days writing a ChatGPT-powered reconciler assistant. It’s so damn accurate. B…
Re: Reconciliation is a knapsack problem
#33Actually no. This post is about doing something akin to first in first out accounting to match the payments to the invoices.
I wonder why they aren't simply using virtual IBANs...
Re: Reconciliation is a knapsack problem
#34Earlier quoted context omitted.
I have 15 debtors, a few dozen creditors, and 5 employee credit cards. There’s enough transactions that for the 3 years I’ve been reconciling the accounts I have wanted to either write an if/elseif/else-based reconciler assistant, or hire someone, or pay my accountant to do the job. A few weeks ago, I decided, what the hell, and I spent two days writing a ChatGPT-powered reconciler assistant. It’s so damn accurate. B…
Whether something is better than nothing depends on its error rate and the consequences of an error.
Re: Reconciliation is a knapsack problem
#35lol at ai for solving deterministic knapsacks. Just get yourself a solver. And if you wanna solve billion item sized problems hire an OR scientist to write a decomposed algo. Literally after 2 minutes of search: https://arxiv.org/pdf/2002.00352.pdf
That said:
> lol at ai for solving deterministic knapsacks. > Just get yourself a solver.
I don't think these are necessarily in conflict. "write me some Z3 code to solve this knapsack problem, then run it and tell me what the output means" seems like it might actually be in the right realm. The LLM isn't doing the solving, which makes sense because I agree there's no mechanism by which an LLM would be better at it than a solver, but as a UX to the solver it seems like it'd do okay. That's genuinely value added, I don't expect most accounts or even programmers to be familiar with Z3.
Re: Reconciliation is a knapsack problem
#36Re: Reconciliation is a knapsack problem
#37Earlier quoted context omitted.
I have 15 debtors, a few dozen creditors, and 5 employee credit cards. There’s enough transactions that for the 3 years I’ve been reconciling the accounts I have wanted to either write an if/elseif/else-based reconciler assistant, or hire someone, or pay my accountant to do the job. A few weeks ago, I decided, what the hell, and I spent two days writing a ChatGPT-powered reconciler assistant. It’s so damn accurate. B…
Whether something is better than nothing depends on its error rate and the consequences of an error.
Re: Reconciliation is a knapsack problem
#38As somebody who worked as an accountant, I saw several times where automated reconciliation solutions devastated books with repeat mistakes and lacking audit logs. I saw interns do the same, too. An automated solution to reconcile statements based on LLM matches removes transparency on how your books are prepared and might create a false sense of trust in the preparation of your books. In case of an audit, people wil…
Re: Reconciliation is a knapsack problem
#39As somebody who worked as an accountant, I saw several times where automated reconciliation solutions devastated books with repeat mistakes and lacking audit logs. I saw interns do the same, too. An automated solution to reconcile statements based on LLM matches removes transparency on how your books are prepared and might create a false sense of trust in the preparation of your books. In case of an audit, people wil…
I think this is a niche issue related to accounts receivable potential errors as most companies I work with don't have the problem of constant repeating amount transactions.
Re: Reconciliation is a knapsack problem
#40I profoundly disagree that ML models are a good fit for transaction reconciliation. It’s at least arguable that this task is the oldest documented use of writing, and from double-entry accounting to price/time precedence in modern market microstructure, we have algorithms that align very well with human intuition. I can think of few cases where gratuitous application of even simple statistical methods would cause mor…
I have 15 debtors, a few dozen creditors, and 5 employee credit cards. There’s enough transactions that for the 3 years I’ve been reconciling the accounts I have wanted to either write an if/elseif/else-based reconciler assistant, or hire someone, or pay my accountant to do the job. A few weeks ago, I decided, what the hell, and I spent two days writing a ChatGPT-powered reconciler assistant. It’s so damn accurate. B…