New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import Bank Statement #2184
Comments
|
This looks good. Clearbooks, Quickbooks, Xero etc do this sort of thing. It would be good to emulate what they do. One pain point I found with Clearbooks (my package) was processing each new entry one at a time when the purchase/payment is with a new customer. We are an online shop/manufacturer that receives many sales and buys many small items. There can be hundreds to do each week so its slow one at a time. For each entry in a statement a new customer may have to be created which take many mouse clicks and page loads. If it could be done in a grid view that enabled setting the required fields on many entries at once it would be easier. ie, pick existing entity/create new entity, payment method, sales tax rate, assign to invoice (if one exists), etc Then process many at once. One thing that Clearbooks does well is to auto-select the customer based on bank statement description field (based on your previous assignments) and then autofill the required data. It would be good to do this too. |
+1 to have a simple way to import bank data from csv and have a quick booking window. Features required per line:
Attached is a sample CSV from a bank in Europe (converted to xlsx, as github does not accept csv). |
@neilLasrado @rohitwaghchaure @nabinhait is this still pending for v8? |
@joezsweet please don't ask "pending in v8" question - if you can replicate it, please check or just tag and move on |
@rmehta yeah sorry ..i better ask if it is actively under development |
don't ask anything - just tag based on your understanding 😊 |
👍 |
I really like this one. I would suggest that in the setup area for account module a sysadmin can define the csv format of the file. e.g. column 1 is desc, column 2 is date, column 3 is credit, etc. That way the feature is not tied to any specific export |
Ok. I have started working on this after sharing the first draft of the specification at https://github.com/frappe/erpnext/wiki/Bank-Transaction-Management-:-Feature-Specification-(v0.1) Introduction The aim of this feature is to manage all the erpnext transactions related to bank account easily. This includes creating and updating payment entries, mapping payment entries to invoice, mapping payment entries to transactions in bank statement. Usecases Reconcile existing payment entries Create payment entries based on the bank transactions Create journal entries based on the bank transactions Feature Design Import Statements This feature is designed to implement it in phases to improve the usability. Ideally we should provide a mechanism to connect to the bank account directly, which should retrieve the statements automatically. Once the statement transactions are imported, we should examine each one of them and handle them appropriately. It isn't very clear whether all the banks provide an easy way of importing the statements via some API that ERPNext could use. More work needs to be done in this area to find a good way of connecting to bank and importing the statements automatically. So this specification only deals with the second stage where it assumes the statements are already imported in csv format manually. Handle Statement Format It is unlikely that all the banks would generate the statements in the same format. However it is assumed that all of them will be able to provide necessary information in csv format. The required information elements are:
Identify transactions automatically Statement management process
Draft Statement Management Process
Provide provision to update the invoices in case auto assignment hasn't done the right mapping
|
Can you please add value date which already exist in any bank statement which will help in the future calculting agio bank and also in treasury. |
We had a similar use case and resolved it in a two step fashion:
The biggest issue we came across is that each and every bank has a different output format, some banks even have so many options that strongly impact the output. A standard (such as pain.001 for payment files) is so far not yet established. Also, the data content varies from very good to extremely poor (date and amount being the worst; no reference or the like). We only import received payments (to close debtors), as paid payments can be done as payment entries and then a payment file generated (pain.001) and uploaded to the bank for execution. This is currently available as app for ERPNext... |
@SOLOSOFTMA, could you please elaborate a bit more on your requirement of value date? The statement will have a start date and end date, which need not be same as the start and end date of payment manager statement. Perhaps we could automate the start date as last date of previously processed statement. |
In morocco and french countries they use also value date which generally equal to posting date +2 days we need it in treasury |
Sorry, your requirement is still not clear to me. Are you saying the payment entry posting date should be transaction date+2 even though statement has the right transaction date? |
Scenario: On Payment Entry (Cheque Receipt from Customer)
On Reconciliation
Is the reconciliation accounting entry handled in the new design? |
I doubt, certainly not tested. Where it works best is no manual payment entries and just import the transactions from bank statement and let the tool create the payment entries. This is a precursor to automatic payment handling, not just reconciliation tool. ie when we start getting the bank transaction feeds, if the payment entry is already created, we should be able to find the corresponding entry and reconcile it. If not, create a new payment entry from the tool and reconcile it. |
@nabinhait #12472 looks unmerged. Did you close this by mistake? |
So..... is ERP Next already supporting .OFX files? |
Sync Logic:
The text was updated successfully, but these errors were encountered: