Re: [GNC] Manual Documentation - Import CSV
I’d welcome input from other accountants to review the proposed terminology, over and above the huge amount of work David Cousens has done on the documentation. Posts https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118164.html * Proposal https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118165.html * Terms "Split" and "Multi-split" usage is inconsistent and ambiguous * Agree with term "entry" for each line https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118193.html * Term "Import Account" is confusing https://lists.gnucash.org/pipermail/gnucash-user/2026-January/119038.html * Directed to revised code https://lists.gnucash.org/pipermail/gnucash-user/2026-January/119041.html * Nice to use accounting terminology * Propose simple/compound import rather than multi-split/multi-line * Support radio button to select option https://lists.gnucash.org/pipermail/gnucash-user/2026-January/119045.html * Term "split" originates in the code * Favour multi-entry for components and multi-line for CSV transaction * (glossary discussion omitted) https://lists.gnucash.org/pipermail/gnucash-user/2026-January/119050.html https://lists.gnucash.org/pipermail/gnucash-user/2026-January/119066.html * Simple/Compound/Journal-Memorandum transaction * (view comment omitted) Discussion After carefully working through the CSV import process and researching accounting terms, these comments address the thread. All agree the import process and docs contain confusing or ambiguous elements. Abstraction in coding simplifies complex systems by hiding implementation details behind simple interfaces, much like 2D maps represent a 3D spheroid. In double-entry accounting, a simple journal entry records a single debit and a single credit affecting exactly two accounts. A compound journal entry records a transaction that affects more than two accounts, so that either the debit side, credit side, or both are split across multiple accounts while total debits still equal total credits. The term "split" is used in many ways and becomes confusing with GnuCash documentation emphasising the code abstraction, where all transactions are modelled as splits (even simple two-account ones), over formal accounting usage that reserves "split" for compound entries where at least one side (debit, credit, or both) distributes across multiple accounts. The term "transaction" is simpler and more intuitive for users than the stricter accounting term "journal entry" or just "entry". Revised Tooltip Text (pending code/radio button review): Multi-line tooltip: * Disable: Each CSV line forms one simple transaction to Import Account. * Enable: Multiple consecutive CSV lines combine to form one compound transaction. Each line must provide Account and Amount, and the first line must also include Date and Description. The importer automatically groups consecutive lines into the same transaction. It starts a new transaction whenever any transaction-specific field (Transaction ID, Date, Number, Description, Notes, Transaction Commodity, or Void Reason) contains different, non-empty information. Import Account tooltip: Apply a single source account to all imported transactions. The other side of the transaction can be provided in a Transfer Account column, or left for the Import Matcher to assign. Regards > ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
> On 01/03/2026 8:55 AM PST Adrien Monteleone > wrote: > > Then a 'split' is the single line item in the transaction and is either > a debit or credit. (all transactions having at least one of each, with > Memorandums having none/empty splits) > > This would remove the 'multi-split' terminology confusion and is more of > a convention on our part here on the list in our referencing, and I > think I'll adopt it from here on out. > Since all journal entries have at least one split and there is the other half of the transaction (ignoring the memos), when I'm helping someone with a "multi-split" import, I suggest that the "multi-split" allows for unlimited debits and/or unlimited credits for a single journal entry, but multiple debits and/or multiple credits is not required, so any "multi-split" journal entry can be a simple journal entry. I import more simple journal entries using "multi-split" CSV than compound journal entries. I've considered working on the CSV documentation, which I'm thinking is more important than the difference between "multi-split" or "multi-line" or some other terminology, but I do appreciate that translations are important too. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
I like the idea of: Simple Transaction Compound Transaction Journal/Memorandum (optionally) Then a 'split' is the single line item in the transaction and is either a debit or credit. (all transactions having at least one of each, with Memorandums having none/empty splits) This would remove the 'multi-split' terminology confusion and is more of a convention on our part here on the list in our referencing, and I think I'll adopt it from here on out. The only place I can see in the UI that might assist with this is in Basic Ledger View to change the text "-Split Transaction-" to say "-Compound Transaction-" for clarity. I'm not sure how this would affect translations though. There might be a few places in the documentation to tweak as well, but I haven't looked it over in some time. Regards, Adrien On 1/1/26 3:17 PM, Patrick James via gnucash-user wrote: 1. Simple Journal Entry [=standard accounting terminology for a journal entry with exactly one debit and one credit] 2. Complex Journal Entry [=standard accounting terminology for a journal entry that has more than one debit or more than one credit; "compound journal entry" is also equally acceptable terminology] 3. Then there is another type of entry which does not meet either definition above, and that's a "Memorandum Journal Entry" [=no debit entry, and thus no credit entry]. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
When I added the glossary to the Guide several years back, I thought that creating links from the first occurrence of a term to its glossary entry would be helpful, but I didn't have the gumption to pore through to locate said first occurrence and create the links. Of course, that wouldn't necessarily help those people who are not reading cover to cover, as you note. Linking every occurrence in the docs to their glossary entries would be disruptive to most, though. Perhaps just all instances in the Basics, though. I have given up the mantle of documentarian, so the insertion of links will have to depend on someone else. Thanks John, i have to admit to not having read the Guide in full for a long time now. If not up front, perhaps links to the glossary definitions from the basics section. I think Victor's comment has some value as most people are unlikely to do a cover to cover read, even when starting out. I certainly didn't, I just went in looking for information about how to do specific tasks. That may have been because I was doing a masters in accounting at the time and I was using GnuCash to do the accounting exercises and thesis work. Cheers David On Fri, 2026-01-02 at 08:30 -0800, John Ralls wrote: -- David Cousens ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Thanks John, i have to admit to not having read the Guide in full for a long time now. If not up front, perhaps links to the glossary definitions from the basics section. I think Victor's comment has some value as most people are unlikely to do a cover to cover read, even when starting out. I certainly didn't, I just went in looking for information about how to do specific tasks. That may have been because I was doing a masters in accounting at the time and I was using GnuCash to do the accounting exercises and thesis work. Cheers David On Fri, 2026-01-02 at 08:30 -0800, John Ralls wrote: > Dave, > > It’s not up front, but it’s > there: https://www.gnucash.org/docs/v5/C/gnucash-guide/gnc-gloss.html > > I don’t think I’ve ever seen a book with a glossary anywhere but as > an appendix at the back. > > Regards, > John Ralls > > > > On Jan 1, 2026, at 22:02, David Cousens > > wrote: > > > > It would be nice to have a glossary of Gnucash terminology with > > appropriate definitions up front possibly after or before the > > basics > > section in the guide and then move towards a consistent use of that > > terminology throughout the documnetation as a whole. That however > > is a > > large task and as the documentation is maintained by a fairly > > diverse > > group, not necessarily going to be easy to get consistent agreement > > on > > terminology or to co-ordinate such an effort. > -- David Cousens ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
I have definitely seen glossaries at the beginnings of documents. They tend to be more useful there, as the reader is unlikely to skip past it without knowing it exists. Glossaries at the back also exist, but to know it is there requires a careful reading of the table of contents. And careful reading is not common. > On Jan 2, 2026, at 11:30 AM, John Ralls wrote: > > Dave, > > It’s not up front, but it’s there: > https://www.gnucash.org/docs/v5/C/gnucash-guide/gnc-gloss.html > > I don’t think I’ve ever seen a book with a glossary anywhere but as an > appendix at the back. > > Regards, > John Ralls > > >> On Jan 1, 2026, at 22:02, David Cousens wrote: >> >> It would be nice to have a glossary of Gnucash terminology with >> appropriate definitions up front possibly after or before the basics >> section in the guide and then move towards a consistent use of that >> terminology throughout the documnetation as a whole. That however is a >> large task and as the documentation is maintained by a fairly diverse >> group, not necessarily going to be easy to get consistent agreement on >> terminology or to co-ordinate such an effort. > > ___ > gnucash-user mailing list > [email protected] > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Dave, It’s not up front, but it’s there: https://www.gnucash.org/docs/v5/C/gnucash-guide/gnc-gloss.html I don’t think I’ve ever seen a book with a glossary anywhere but as an appendix at the back. Regards, John Ralls > On Jan 1, 2026, at 22:02, David Cousens wrote: > > It would be nice to have a glossary of Gnucash terminology with > appropriate definitions up front possibly after or before the basics > section in the guide and then move towards a consistent use of that > terminology throughout the documnetation as a whole. That however is a > large task and as the documentation is maintained by a fairly diverse > group, not necessarily going to be easy to get consistent agreement on > terminology or to co-ordinate such an effort. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Your suggestion for 3rd item (memorandum entry) could be folded into first item (simple entry) if debit and/or credit are zero or blank. Less known is that Quicken uses 'NReminder' for their data format, and more likely known is that large financial institutions codes it as 'Journal' for Transaction Type. For investment account there is also 'Corporate Action' Transaction Type as well, and not sure that would be accommodated or folded into another. -Original Message- From: Patrick James Sent: Thursday, January 01, 2026 4:18 PM To: Gnucash Users Subject: Re: [GNC] Manual Documentation - Import CSV flywire, I'm addressing your proposed UI changes 1 to 3. 1. Rename Multi-split to Multi-line 2. Move Account field under Multi-line checkbox 3. Dim/disable Account field when Multi-line enabled -- I agree with the basic premise that the "multi-split" could/should be changed to better align with its accounting objective and/or a better user experience. That said, I'm not convinced that "multi-line" is better than "mutli-split." I would be nice if one could find the term that incorporates accounting terminology and improve the user interface. I propose something like: "Simple import" and "Complex import" This avoids the question of what does "multi-line" mean with a csv file that's 100 lines. This also alerts the user that "complex import" probably needs something more than a simple bank download. Hopefully the user would ask the basic question, "What is a complex import?" Or, alternatively, think something like, "I don't know what a 'complex import' is, but I only need a 'simple import' for my workflow." Now moving forward to the justification: 1. Simple Journal Entry [=standard accounting terminology for a journal entry with exactly one debit and one credit] 2. Complex Journal Entry [=standard accounting terminology for a journal entry that has more than one debit or more than one credit; "compound journal entry" is also equally acceptable terminology] 3. Then there is another type of entry which does not meet either definition above, and that's a "Memorandum Journal Entry" [=no debit entry, and thus no credit entry]. Although the accounting definitions above are mutually exclusive, in that a simple journal entry cannot be a compound journal entry, and, a compound journal entry cannot be a simple journal entry, the same is not true when importing a "Multi-split" CSV file. A "Multi-split" import can result in both simple journal entries as well as compound journal entries. I realize that you point out, "Single-line/Multi-line terms are equivalent to Simple/Split Transaction terms used in the Guide for 2/2+ accounts respectively and also related to Register View styles for Basic Ledger and Transaction Journal." I suggest the documentation should be updated, or, at a minimum, the csv documentation should be updated if it is not appropriate/practical/favorable to change the documentation for the basic ledger. As far as your suggestions around the "multi-split" checkbox, I generally agree a change would be favorable. I personally suggest something like two radio buttons, where only one can be selected: * "Simple import" above the select account pull down. * "Complex Import" The radio button selection should take care of your proposed UI change 3, as the selection of one would disable the other option. These changing of only the terms/UI would not be breaking changes in that the actual import would not change. That said, I don't know how much work it would be to make the changes to the UI and use the previously saved settings. > On 12/31/2025 9:26 PM PST flywire wrote: > > > Continuing on from the thread > https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118164. > html > > My concern is the GnuCash CSV Importer UI and docs are confusing > because the terminology is not clear and the Account field (for > single-line mode) appears before the Multi-split checkbox decision > point that determines the import mode. > > Single-line mode (one line = one transaction, two accounts): > * Source Account: Set once in the assistant or via CSV column > * Transfer Account: CSV column or Import Matcher (defaults to > Imbalance) > > Multi-line mode (one line = one split, 2+ accounts): > * All data per-line; no common Account field > * Groups consecutive lines by identical/blank transaction info (Date, > Description, etc.) > > Every transaction needs: Date, Description, Amount(s), Account(s). > > Single-line/Multi-line terms are equivalent to Simple/Split > Transaction terms used in the Guide for 2/2+ account
Re: [GNC] Manual Documentation - Import CSV
Patrick I think your suggestions have some merit. Ire wrote a lot of the CSV import documnetation a number of years ago after Geert had rewritten the CSV importer and tended to use the terminology that had been in common use in the GnuCash community at the time. There is also however a need for consistency with the rest of the documentation in making changes. The origin of "split" is in the code itself as that is the name given to the data structure which stores each entry in a transaction. My accounting background makes me tend to prefer "entry" as the name for the components of a transaction. Changing the complete code base is however an even more massive task that changing the documentation In the context of the CSV file itself multi-line makes some sense as each entry of a multi entry transaction is on a new line with the first line having the information relevant to the transaction as a whole(date, description etc) and those fields are blank in the subsequent lines in the CSV file for that multi-entry transaction. I tend to favour using multi-entry, entry when referring to the components of a transaction in a general sense and multiline when referring to the representation of that multi-entry transaction within the csv file. It would be nice to have a glossary of Gnucash terminology with appropriate definitions up front possibly after or before the basics section in the guide and then move towards a consistent use of that terminology throughout the documnetation as a whole. That however is a large task and as the documentation is maintained by a fairly diverse group, not necessarily going to be easy to get consistent agreement on terminology or to co-ordinate such an effort. On Thu, 2026-01-01 at 13:17 -0800, Patrick James via gnucash-user somesomewrote: > flywire, > > I'm addressing your proposed UI changes 1 to 3. > > 1. Rename Multi-split to Multi-line > 2. Move Account field under Multi-line checkbox > 3. Dim/disable Account field when Multi-line enabled > > -- > > I agree with the basic premise that the "multi-split" could/should be > changed to better align with its accounting objective and/or a better > user experience. That said, I'm not convinced that "multi-line" is > better than "mutli-split." I would be nice if one could find the term > that incorporates accounting terminology and improve the user > interface. > > I propose something like: > > "Simple import" > and > "Complex import" > > This avoids the question of what does "multi-line" mean with a csv > file that's 100 lines. This also alerts the user that "complex > import" probably needs something more than a simple bank download. > Hopefully the user would ask the basic question, "What is a complex > import?" Or, alternatively, think something like, "I don't know what > a 'complex import' is, but I only need a 'simple import' for my > workflow." > > Now moving forward to the justification: > > 1. Simple Journal Entry [=standard accounting terminology for a > journal entry with exactly one debit and one credit] > > 2. Complex Journal Entry [=standard accounting terminology for a > journal entry that has more than one debit or more than one credit; > "compound journal entry" is also equally acceptable terminology] > > 3. Then there is another type of entry which does not meet either > definition above, and that's a "Memorandum Journal Entry" [=no debit > entry, and thus no credit entry]. > > Although the accounting definitions above are mutually exclusive, in > that a simple journal entry cannot be a compound journal entry, and, > a compound journal entry cannot be a simple journal entry, the same > is not true when importing a "Multi-split" CSV file. A "Multi-split" > import can result in both simple journal entries as well as compound > journal entries. > > I realize that you point out, "Single-line/Multi-line terms are > equivalent to Simple/Split Transaction terms used in the Guide for > 2/2+ accounts respectively and also related to Register View styles > for Basic Ledger and Transaction Journal." I suggest the > documentation should be updated, or, at a minimum, the csv > documentation should be updated if it is not > appropriate/practical/favorable to change the documentation for the > basic ledger. > > As far as your suggestions around the "multi-split" checkbox, I > generally agree a change would be favorable. > > I personally suggest something like two radio buttons, where only one > can be selected: > > * "Simple import" above the select account pull down. > * "Complex Import" > > The radio button selection should take care of your proposed UI > change 3, as the selection of one would disable the other option. > > These changing of only the terms/UI would not be breaking changes in > that the actual import would not change. That said, I don't know how > much work it would be to make the changes to the UI and use the > previously saved settings. > > > > > On 12/31/2025 9:26 PM PST fl
Re: [GNC] Manual Documentation - Import CSV
flywire, I'm addressing your proposed UI changes 1 to 3. 1. Rename Multi-split to Multi-line 2. Move Account field under Multi-line checkbox 3. Dim/disable Account field when Multi-line enabled -- I agree with the basic premise that the "multi-split" could/should be changed to better align with its accounting objective and/or a better user experience. That said, I'm not convinced that "multi-line" is better than "mutli-split." I would be nice if one could find the term that incorporates accounting terminology and improve the user interface. I propose something like: "Simple import" and "Complex import" This avoids the question of what does "multi-line" mean with a csv file that's 100 lines. This also alerts the user that "complex import" probably needs something more than a simple bank download. Hopefully the user would ask the basic question, "What is a complex import?" Or, alternatively, think something like, "I don't know what a 'complex import' is, but I only need a 'simple import' for my workflow." Now moving forward to the justification: 1. Simple Journal Entry [=standard accounting terminology for a journal entry with exactly one debit and one credit] 2. Complex Journal Entry [=standard accounting terminology for a journal entry that has more than one debit or more than one credit; "compound journal entry" is also equally acceptable terminology] 3. Then there is another type of entry which does not meet either definition above, and that's a "Memorandum Journal Entry" [=no debit entry, and thus no credit entry]. Although the accounting definitions above are mutually exclusive, in that a simple journal entry cannot be a compound journal entry, and, a compound journal entry cannot be a simple journal entry, the same is not true when importing a "Multi-split" CSV file. A "Multi-split" import can result in both simple journal entries as well as compound journal entries. I realize that you point out, "Single-line/Multi-line terms are equivalent to Simple/Split Transaction terms used in the Guide for 2/2+ accounts respectively and also related to Register View styles for Basic Ledger and Transaction Journal." I suggest the documentation should be updated, or, at a minimum, the csv documentation should be updated if it is not appropriate/practical/favorable to change the documentation for the basic ledger. As far as your suggestions around the "multi-split" checkbox, I generally agree a change would be favorable. I personally suggest something like two radio buttons, where only one can be selected: * "Simple import" above the select account pull down. * "Complex Import" The radio button selection should take care of your proposed UI change 3, as the selection of one would disable the other option. These changing of only the terms/UI would not be breaking changes in that the actual import would not change. That said, I don't know how much work it would be to make the changes to the UI and use the previously saved settings. > On 12/31/2025 9:26 PM PST flywire wrote: > > > Continuing on from the thread > https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118164.html > > My concern is the GnuCash CSV Importer UI and docs are confusing because > the terminology is not clear and the Account field (for single-line mode) > appears before the Multi-split checkbox decision point that determines the > import mode. > > Single-line mode (one line = one transaction, two accounts): > * Source Account: Set once in the assistant or via CSV column > * Transfer Account: CSV column or Import Matcher (defaults to Imbalance) > > Multi-line mode (one line = one split, 2+ accounts): > * All data per-line; no common Account field > * Groups consecutive lines by identical/blank transaction info (Date, > Description, etc.) > > Every transaction needs: Date, Description, Amount(s), Account(s). > > Single-line/Multi-line terms are equivalent to Simple/Split Transaction > terms used in the Guide for 2/2+ accounts respectively and also related to > Register View styles for Basic Ledger and Transaction Journal. > > References: > * > https://github.com/Gnucash/gnucash/blob/stable/gnucash/gtkbuilder/assistant-csv-trans-import.glade#L46-L55 > * > https://github.com/Gnucash/gnucash/blob/stable/gnucash/gtkbuilder/assistant-csv-trans-import.glade#L527-L530 > > > > Proposed UI changes: > > 1. Rename Multi-split to Multi-line > 2. Move Account field under Multi-line checkbox > 3. Dim/disable Account field when Multi-line enabled > 4. Update tooltip-text > 5. Update documentation to describe > > Multi-linetooltip-text: > > * Disable: Each CSV line is one complete transaction. > * Enable: Multiple consecutive lines form one transaction. Each line > provides details for a single account or split, and the first line must > include the main transaction information such as Date and Description. > > The importer groups consecutive lines into the same
Re: [GNC] Manual Documentation - Import CSV
Continuing on from the thread https://lists.gnucash.org/pipermail/gnucash-user/2025-November/118164.html My concern is the GnuCash CSV Importer UI and docs are confusing because the terminology is not clear and the Account field (for single-line mode) appears before the Multi-split checkbox decision point that determines the import mode. Single-line mode (one line = one transaction, two accounts): * Source Account: Set once in the assistant or via CSV column * Transfer Account: CSV column or Import Matcher (defaults to Imbalance) Multi-line mode (one line = one split, 2+ accounts): * All data per-line; no common Account field * Groups consecutive lines by identical/blank transaction info (Date, Description, etc.) Every transaction needs: Date, Description, Amount(s), Account(s). Single-line/Multi-line terms are equivalent to Simple/Split Transaction terms used in the Guide for 2/2+ accounts respectively and also related to Register View styles for Basic Ledger and Transaction Journal. References: * https://github.com/Gnucash/gnucash/blob/stable/gnucash/gtkbuilder/assistant-csv-trans-import.glade#L46-L55 * https://github.com/Gnucash/gnucash/blob/stable/gnucash/gtkbuilder/assistant-csv-trans-import.glade#L527-L530 Proposed UI changes: 1. Rename Multi-split to Multi-line 2. Move Account field under Multi-line checkbox 3. Dim/disable Account field when Multi-line enabled 4. Update tooltip-text 5. Update documentation to describe Multi-linetooltip-text: * Disable: Each CSV line is one complete transaction. * Enable: Multiple consecutive lines form one transaction. Each line provides details for a single account or split, and the first line must include the main transaction information such as Date and Description. The importer groups consecutive lines into the same transaction until it finds a line where any transaction‑specific field (Transaction ID, Date, Number, Description, Notes, Transaction Commodity, or Void Reason) contains different, non‑empty information. Accounttooltip-text: Apply a single source account to all imported transactions. The other side of the transaction can be provided in a Transfer Account column, or left for the Import Matcher to assign. Regards > ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
The term "Import Account" is itself confusing to me, and perhaps a bit devilish. I assume that it's meant to refer to the account that is common to all the transactions (David's Checking Account, say). But this idea is murky at best when each transaction involves at least one other account-- and gets truly confusing when discussing complex transaction imports. I suspect that's why the original text uses "import or base account". This can easily be cleared up by placing an explanatory definition at the beginning of the section: The term "Import Account" will be used to refer to the account that is common to all the transactions in the csv file, typically the account from which the transactions in the csv file originated. Or some such... David T. On Nov 10, 2025, 1:37 AM, at 1:37 AM, flywire wrote: >Let's not include any devils. > >Three things could be clarified in >https://www.gnucash.org/docs/v5/C/gnucash-manual/trans-import.html#trans-import-csv >: > > - > > whether the CSV import file uses single-account format, where each >row is a full transaction imported into one account, or multi-account >format, where each row represents part of a transaction and specifies >its own account > > - > > distinguishing the Account shown in the importer from the Account >shown in the file grid (where I'm suggesting Importer form label >changes) > > - using the term "Import Account" consistently instead of "import or > base account" > >Regards > >> >___ >gnucash-user mailing list >[email protected] >To update your subscription preferences or to unsubscribe: >https://lists.gnucash.org/mailman/listinfo/gnucash-user >- >Please remember to CC this list on all your replies. >You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Let's not include any devils. Three things could be clarified in https://www.gnucash.org/docs/v5/C/gnucash-manual/trans-import.html#trans-import-csv : - whether the CSV import file uses single-account format, where each row is a full transaction imported into one account, or multi-account format, where each row represents part of a transaction and specifies its own account - distinguishing the Account shown in the importer from the Account shown in the file grid (where I'm suggesting Importer form label changes) - using the term "Import Account" consistently instead of "import or base account" Regards > ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
How does one go about updating the documentation? I'd like tot put in some updates. On Sat, Nov 8, 2025 at 3:27 AM sunfish62--- via gnucash-user < [email protected]> wrote: > Interesting idea; improving documentation is always welcome, but the devil > is in the details... > > ___ > gnucash-user mailing list > [email protected] > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > -- _ Richard Losey [email protected] Micah 6:8 ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Apologies, I intended to suggest renaming the label not the field: 2. Rename the form field label "Account" to "Import Account" Regards On Sat, 8 Nov 2025 at 20:26, [email protected] wrote: > Item 2 in your suggestions isn't documentation, but requires a change in > code. > > On Nov 8, 2025, at 12:28 PM, flywire wrote: >> >>2. Rename the form field currently labeled "Account" to "Import Account" >> >> ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Manual Documentation - Import CSV
Interesting idea; improving documentation is always welcome, but the devil is in the details... Item 2 in your suggestions isn't documentation, but requires a change in code. As for "split", "multi-split" and GnuCash usage of the same, there has been a long standing ambiguity on their use. There was a discussion some years back concerning this, with some pointing out that the documentation was inconsistent. Sometimes, "split" referred to a single entry in a transaction, while other times, it referred to the presence of more than two entries in a transaction. Similarly, "multi-split" has been used inconsistently, although in general it refers to the presence of more than two entries in a transaction. I believe that in the Guide, we settled on referring to Note that I used the term "entry" to refer to the lines in a transaction that link an amount to an account. One person in the earlier discussion suggested using "entry" for each line so as to disambiguate the language, and I think they were right in that assessment. David T. On Nov 8, 2025, 12:28 PM, at 12:28 PM, flywire wrote: >I'd like to raise a documentation issue for discussion. > >I didn’t fully understand the import functionality for multi-line >transactions until Geert Janssens explained it a few years ago. It's a >neat >feature that works very well, but the manual section could be clearer, >particularly for users trying to understand how GnuCash handles CSV >imports >with multi-line transactions. > >The relevant documentation pages are: > > - CSV Transaction Import: >https://www.gnucash.org/docs/v5/C/gnucash-manual/trans-import.html#trans-import-csv > - Multi-split Transactions: >https://www.gnucash.org/docs/v5/C/gnucash-manual/trans-multi-enter.html > >GnuCash uses the term "Split" for transactions involving more than two >accounts. "Multi-split" is an unreasonable term for a file with a >simple >two-account transaction. "Multi-line" would be a clearer and more >accurate >term for users trying to understand CSV imports, equally inclusive of >simple two-account and split transactions. > >Also, it’s not always clear which account the term "Account" refers to >in >the documentation or the import dialog, since both the form and the CSV >file may contain an account field. The only way to tell is by reading >the >surrounding text carefully. > >To make the documentation clearer, I suggest: > >1. Use the term "Import Account" consistently instead of "import or >base > account" >2. Rename the form field currently labeled "Account" to "Import >Account" > 3. Add a "File Fields" label above the CSV file grid to make it easier > to refer to those fields > 4. Update documentation to describe the two supported CSV formats more > explicitly: > - One line per transaction, imported into a single account as a > simple transaction, using either a transfer account field or one > automatically assigned by the Import Matcher >- Multiple lines per transaction, with each line specifying its own > account, imported as either a simple or split transaction > 5. Use the term/label "Multi-line" instead of "Multi-split" > >These tweeks could help users better understand the CSV format, >particularly the multi-line format. > >I’d appreciate any comments. > >Regards >___ >gnucash-user mailing list >[email protected] >To update your subscription preferences or to unsubscribe: >https://lists.gnucash.org/mailman/listinfo/gnucash-user >- >Please remember to CC this list on all your replies. >You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
