Skip to content

Jesse

← Customer Feedback for GnuCash

My feedback

3 results found

  1. Improved Job Expense & Invoice Tracking

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Feature Request  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Jesse commented  · 

    I've found two workarounds! see https://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1543027-transaction-classifications

    An error occurred while saving the comment
    Jesse commented  · 

    I'll second that I'd be willing to pay someone to work on it. I'm a sole trader so don't have a lot of $$ to contribute but I'd certainly be willing to put in some to help get this done.

    P.S. This seems to be the same request as http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1543027-transaction-classifications

  2. Allow for multiple vendors to charge to a Job

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Feature Request  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Jesse commented  · 

    I've found two workarounds: See https://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1543027-transaction-classifications

    An error occurred while saving the comment
    Jesse commented  · 

    YES this is sooo needed! and has been asked for since 2011 http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1543027-transaction-classifications
    and again http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1668975-improved-job-expense-invoice-tracking

    I'm willing to contribute to a bounty for this feature if anyone knows how to do that.

  3. Transaction Classifications

    580 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    51 comments  ·  Feature Request  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Jesse commented  · 

    I believe I have found an interim workaround!! You can use "Customers" to achieve classifications.

    Create two dummy customers: Property_Customer_1 and Property_Customer_2
    Give them special Customer Numbers such as "Prpty_1" and "Prpty_2" so that they are clearly separate from any real customers. You could even enter the addresses of each property if you wanted.

    Next you need to start entering your expenses using the business "Bill" function.
    Create three Vendors: Electricity, Water & Rates
    When you enter a bill for Property_1 enter the Customer "Property_Customer_1" as the 'Default Chargeback Project Customer'
    If you want to further subdivide your classifications this is where Customer Jobs come in. Lets say you wanted to separate Utility Bills from Rates and also record Maintenance Expenses. You could create three Jobs for Property_Customer_1, and when entering each Bill assign it to that job.

    The best report I've found to date is the "Customer Summary" report because it shows income, expenditure, the % difference (labelled as markup), and the profit. It also allows you to select which accounts to sum as the income and which as the expense.

    If these are investment properties you could use the invoice feature to attribute income to the dummy customers

    One important note is that there is no way to DELETE a customer once you have created it! You can change every part of the customer, including the customer number, so if you create too many rename those you don't need to BLANK and change their customer number to 000000 or something similar, then the next time you want to create a new customer change one of these BLANK customer's instead.

    Hope this helps. :-)

    P.S.
    In my specific case as a stage performer and producer. I create a customer for each project/show, sometimes they are dummy customers but sometimes, such as when performing in a festival, they are real customers. In both cases I can see how much it has cost me to produce that particular show. If I'm producing multiple shows in a single festival I use a different Job for each one.

    P.P.S.
    I've also just discovered another workaround here: https://bugzilla.gnome.org/show_bug.cgi?id=113772#c6

    An error occurred while saving the comment
    Jesse commented  · 

    Have found two duplicate requests for this same feature:
    http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1599121-allow-for-multiple-vendors-to-charge-to-a-job
    http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1668975-improved-job-expense-invoice-tracking
    I'm willing to contribute some $$ to getting this done, does anyone know to do that?

    Jesse supported this idea  · 
    An error occurred while saving the comment
    Jesse commented  · 

    The "Jobs" feature would be ideal except that it currently (GnuCash 2.6.1) only allows you to group transactions for a "single vendor" or a "single customer". I want to group all the transactions for a single 'project'. Using Jobs would allow one to group all the Water bills for Property 1 and all Water bills for Property 2. But doesn't allow one to group all Water, Electricity and Rates for Property 1 together.

    My specific case is that I'm a stage performer and producer. I would like to groups all expenses and income, associated with performing at a particular festival.

Feedback and Knowledge Base

(thinking…)