Let's clarify this:
Credit card transactions and brokerage trades have two dates: AFAICT so far:
1. For CC, the "posted date" or "transaction date", for brokerages the
"trade date"; this is the date at which you make the purchase or traded the
stock (when it filled, not when you placed an order, e.g. a limit order
could have been placed days before).
2. The "settlement date", which is the date at which the transaction is
applied against your account.
The period between posted and settlement dates is a sort of limbo
("settlement period"? there may be a better name for this).
What may be happening is that you're looking at transaction dates but the
report is generated for settlement dates. That would explain you seeing
some dates prior to the download.
If you'd like to keep things simple, import everything at settlement dates.
That's what I do myself, and for the most part my balance assertions don't
have to be moved manually too often.
One day the whole issue of posting precise dates for each side of a
transaction will be handled elegantly. I haven't cared too much myself yet,
but I see so much interest for it from many people.
On Mon, May 9, 2016 at 12:33 AM, Jason Chu <[email protected]> wrote:
> It's not even the importing, the statements have this artifact also.
>
> Statement 1 covers 2016-01-02 to 2016-02-01. It contains transactions
> between those dates.
> Statement 2 covers 2016-02-02 to 2016-03-01. It includes a transaction
> from 2016-02-01 (or even 2016-01-31!). I assumed this was because the date
> of the transaction was the date it was charged, not the date it was debited
> (or whatever the term is) from the account.
>
> On Sun, May 8, 2016 at 9:15 PM Zhuoyun Wei <[email protected]> wrote:
>
>>
>> 2016-05-08 21:10:14 yegle <[email protected]>:
>> >
>> > On Sun, May 8, 2016 at 9:00 PM, Jason Chu <[email protected]> wrote:
>> >
>> > The problem is that postings are inserted before the statement end
>> in the next billing cycle (because of random
>> > delays in the charge processing systems) so the balance assertion
>> can't be against any given date.
>> >
>> >
>> >
>> > There's an effective date plugin (don't remember the git repo though),
>> which can help organize the transactions that
>> > happen on day X and settled on day Y.
>> >
>> > For me I just move the transaction to the billing cycle that matches
>> the statement, and add the real transaction date
>> > in the narration field.
>> >
>>
>> Ditto here. For credit card transactions, I use the settled date as
>> directive date in the Beancount file, and keep sale date in metadata.
>>
>> > --
>> > Yuchen Ying
>> > http://about.me/yegle
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Beancount" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to
>> > [email protected].
>> > To post to this group, send email to [email protected].
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/
>> > CAFL5w3VEbJJAFTm3-kLea6xFWAwwVvcoZ77amufDka0MoDspiQ%40mail.gmail.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> Zhuoyun Wei
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Beancount" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/20160509041529.GB17975%40eden.wzyboy.org
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/CAFFHUgsxUWq7YbPrvoReBYoB9adiVHppgj_Bdhn7SqG-nnJzUw%40mail.gmail.com
> <https://groups.google.com/d/msgid/beancount/CAFFHUgsxUWq7YbPrvoReBYoB9adiVHppgj_Bdhn7SqG-nnJzUw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/CAK21%2BhOHTy7Jshg07CPjsJcCO1UhCauNHSHPZ-NjKJ%3DaqJSkhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
