Martin Michlmayr <[email protected]> writes:
> * Eric Abrahamsen <[email protected]> [2014-05-19 09:59]:
>> ~ Monthly
>> ; Payee: Tax Dodgers, Inc
>> Assets:Merchants:5231 7000 RMB ; regular salary
>> part
>> Assets:Receivable 3000 RMB ; receipts
>> Income:Salary
>
> Is this just an example or something you actually use? I'm asking
> becaue I don't understand this transactions. Why would
> Assets:Receivable go up every month? Also, what it
> Assets:Merchants:5231? Surely, if you're paid monthly, your bank
> account would go up, and not some Assets:Merchants account.
Yup, that's the real transaction: "Merchants" is the name of my bank :)
>> After a few weeks I have 1920.90 RMB in my virtual receipt account, and
>> I hand them in (but they haven't paid me the reimbursement yet):
>>
>> 05/04 ! Tax Dodgers, Inc
>> * (Assets:Receipts) = 0 RMB
>> Assets:Merchants:5231 1920.90 RMB
>> Assets:Receivable
>>
>> When the reimbursement comes through I clear the whole transaction, and
>> add an aux date.
>
> This whole approach looks a bit complicated and fragile to me. I'll
> explain the workflow I use. I'm not sure it's better, but it works
> for me:
[...]
> I think this workflow follows a logical approach: when you spend
> money, you have an asset that can be reimbursed (Assets:Reimbursable).
> When you do an expensive report, it becomes a receivable
> (Assets:Receivable). And finally, this receivable goes away when you
> get paid.
The main difference is, in my case it _isn't_ a reimbursement -- it is
money spent entirely on my own behalf. The receipts are simply an excuse
for the company to give out funds without paying payroll taxes. To me
these receipts are the perfect definition of "virtual": no money is
moving between accounts, but at the same time I'd like to know how much
I've got, and how much I still need. The manual balancing is a bit
questionable, but it seems like a fine trade-off.
> Now I understand that it might be slightly different if I were a
> contractor rather than an employee. In that case, I can see an
> argument for booking these expenses a actual Expenses: rather than
> Assets:Reimbursable. (After all, they are expenses for your business
> regardless of whether you get reimbused or not.)
>
> You could tag with them with your client, and then use
> ledger reg Expenses: tag client
> to get a list in order to bill them. This would just be income and
> not a reimbursement as with a true employee.
>
> I believe this approach should work for most people. Now in your
> case, we need to be slightly more creative. It sounds as if got paid
> $40 if you had a receipt for $40, even though you only spent $20 (no
> need to confirm). I have one idea how to handle this. It's not
> currently supported by ledger, but it's a feature that I realized a
> few days ago would be useful.
>
> It would be nice if ledger would allow you to run 'reg' or 'bal' on
> tags. In order words, you could have:
[...]
I tried ("Project" is another tag in my files):
$ ledger reg --limit 'tag("Project")'
And it worked correctly. I don't know if that would do what you're
trying to achieve below, with keeping track of nights, but maybe give it
a shot?
> I have a use case for this: I track points I receive when I stay in a
> hotel. In addition to points, the number of nights stayed count
> towards lifetime status. This isn't something I track in ledger
> (since it's not really an asset), so I just put it in a comment.
> However, it would be nice to do:
> ledger reg --account=tag('Nights')
> to get the total number of nights I've achieved.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
