Using bank exports (CSV, QIF, ...) to avoid the overhead that comes from processing bills

[Derek Atkins]

Tom Van Braeckel <tomvanbraeckel at gmail.com> writes:

> I guesstimate that having a "That bill over there is actually paid by the
> transaction that is already in account such and so" feature would reduce the
> work by 25% (leaving the invoice/bill creation, population, booking and
> printing), so that might be a great first improvement.

There's a long standing open issue for that.  Solving it would require
extending the event notification system so that the biz features can see
whenever a transaction is entered into the A/R or A/P account(s) and
then process them appropriately.

> In the longer term, the importer and business features might be coupled even
> tighter:
>
>    - The importer could match transactions to "accounts payable" or from
>    "accounts receivable" to outstanding invoices, perhaps asking for manual
>    intervention when the match can't be made easily.
>    - The business features could have for a "pay bill" feature for saving
>    payment instructions for your bank to a file.

No, it's a major no-no to make the importers depend on the biz
features.  However the importer could use the aforementioned callbacks
to handle it.

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available