On Feb 3, 2010, at 11:44 PM, TR wrote:
> I have decided to use the text "Job***" as payee info"
> 2010/02/04 Corporation X, Job842
In the current Ledger you can have real metadata:
2010/02/04 Corporation X ; Job: 842
Then you can query via the metadata:
ledger reg %Job
Or for a particular value:
ledger reg %Job=842
And you can even tabulate accounts based on the Job:
ledger reg --pivot=Job
> The last issue (projects spaning year ends) is the worst. I've
> settled on an opening entry, dated at the previous year end.
> Per job reports have open beginnings, all other income statement type
> reports get a finite begin date.
You can use "effective dates" to place a real transaction into a specific
timeframe for reporting purposes:
2010/02/04=2010/01/31 ...
In this case, 2010/01/31 is the effective date. To report with effective
dates, use the --effective option.
> I've tried to use the (code) space but I found it easier to play with
> the data on the back-end when it was defined as the payee.
When you use metadata (see above), you can access the data via value expression
such as 'tag("Job")'. For example:
ledger reg -F '%(payee) %(tag("Job"))\n'
> I looked at sub accounts for each project but the chart of accounts
> becomes so unwieldy. I have company-mode setup with a back-end I
> created so the chart of accounts will pop-up for my assistants to
> select from.
There are other users here who have dealt with similar issues in depth. I'll
let them chime in at this point.
John
