<HTML><HEAD>
<STYLE id=eMClientCss>BLOCKQUOTE.cite {
PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px
}
BLOCKQUOTE.cite2 {
MARGIN-TOP: 3px; PADDING-TOP: 0px; PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px
}
.plain PRE {
FONT-SIZE: 100%; FONT-FAMILY: monospace; WHITE-SPACE: pre-wrap; FONT-WEIGHT: normal; FONT-STYLE: normal
}
.plain TT {
FONT-SIZE: 100%; FONT-FAMILY: monospace; WHITE-SPACE: pre-wrap; FONT-WEIGHT: normal; FONT-STYLE: normal
}
A IMG {
BORDER-TOP: 0px; BORDER-RIGHT: 0px; BORDER-BOTTOM: 0px; BORDER-LEFT: 0px
}
#x94bf38cf5bc34860a42d461e157dd03e {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
.plain PRE {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
.plain TT {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
BODY {
FONT-SIZE: 12pt; FONT-FAMILY: Tahoma
}
#x94bf38cf5bc34860a42d461e157dd03e DIV.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0cm 0cm 0pt
}
#x94bf38cf5bc34860a42d461e157dd03e LI.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0cm 0cm 0pt
}
#x94bf38cf5bc34860a42d461e157dd03e SPAN.MsoHyperlink {
TEXT-DECORATION: underline; COLOR: blue; mso-style-priority: 99
}
#x94bf38cf5bc34860a42d461e157dd03e SPAN.MsoHyperlinkFollowed {
TEXT-DECORATION: underline; COLOR: purple; mso-style-priority: 99
}
#x94bf38cf5bc34860a42d461e157dd03e DIV.MsoAcetate {
FONT-SIZE: 8pt; FONT-FAMILY: "Tahoma","sans-serif"; MARGIN: 0cm 0cm 0pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
#x94bf38cf5bc34860a42d461e157dd03e LI.MsoAcetate {
FONT-SIZE: 8pt; FONT-FAMILY: "Tahoma","sans-serif"; MARGIN: 0cm 0cm 0pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
</STYLE>
<STYLE title=signatureStyle>DIV.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0cm 0cm 0pt
}
LI.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0cm 0cm 0pt
}
SPAN.MsoHyperlink {
TEXT-DECORATION: underline; COLOR: blue; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
TEXT-DECORATION: underline; COLOR: purple; mso-style-priority: 99
}
DIV.MsoAcetate {
FONT-SIZE: 8pt; FONT-FAMILY: "Tahoma","sans-serif"; MARGIN: 0cm 0cm 0pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
FONT-SIZE: 8pt; FONT-FAMILY: "Tahoma","sans-serif"; MARGIN: 0cm 0cm 0pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
</STYLE>
</HEAD>
<BODY>
<DIV>Cristian, I believe I have figured out the issue.<BR><BR>There are a number of Scheduled Transactions, some payments and some deposits, in my KMyMoney file. I like to keep track of upcoming transactions and have set the "Number of days to preview scheduled transactions in ledger" to 14. Using this setting, any scheduled transactions that occur within the next 14 days are shown in the associated ledger. When each future ledger line is viewed one sees, depending on the transaction type, either a Payment or Deposit and a balance reflective of the change the line item would bring. In addition to this I often enter scheduled transactions a few weeks in advance of their due date. For example: I have a scheduled transaction for a credit card payment. The statement is often received mid month with payment due the following month. I'm one who like s to get these things out of the way as soon as they arrive so I'll often head to my banks website as soon as I receive the statement and schedule a Post-dated payment for the following month. Here's where I believe the problem comes in.<BR><BR>Let's assume its September 28th and the actual balance in my account is $5,500. With KMyMoney set to preview scheduled transactions in the ledger, any scheduled transactions that occur within the next 14 days are listed. Also listed are any post-dated transactions, such as the above noted credit card payment that will occur on October 10th. If a deposit of $3,500 is scheduled to be made September 30th, a balance of $9,000 would be shown next to this transaction. If the above noted credit card payment is $1,500 then the balance listed next to the credit card entry would be $7,500. Using this view and as long as the deposit occurs as scheduled, there are sufficient funds to cover the credit card payment. What I've discovered though is that KMyMoney does not account for "future scheduled transactions" in the alert calculation. If "Number of days to preview scheduled transactions in ledger" to 0, the final balance on the account, including the post-dated credit card payment would be $4,000. This of course is below the limit set and of course reflects the true state of the account.<BR><BR>Currently KMyMoney does not consider future scheduled transactions in its Alert calculations. If one does not use ""Number of days to preview scheduled transactions in ledger" then I can see how this approach is appropriate. Under the circumstances I've described, which is setting the "Number of days to preview scheduled transactions in ledger" to a value greater than 0 then shouldn't KMyMoney consider this in its Alert calculation and warn users accordingly? </DIV>
<DIV> </DIV>
<DIV><SPAN id=x94bf38cf5bc34860a42d461e157dd03e>I copied this reply to the forum so others would see the my findings and be able to comment accordingly.</SPAN></DIV>
<DIV><SPAN></SPAN> </DIV>
<DIV> </DIV>
<DIV id=signature_old>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: Tahoma">
<DIV>___________________________</DIV>
<DIV> </DIV>
<DIV>Robert Blackwell</DIV>
<DIV> </DIV>
<DIV><SPAN id=xcfbb073af4c242a580438e7201ef2fb0>
<DIV><SPAN id=x6b17bfa2f8074cafadec8a9df9574d86><SPAN style="FONT-SIZE: 13.5pt; FONT-FAMILY: Webdings; COLOR: #008040">ΓΌ</SPAN><SPAN style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d'><SPAN lang=EN-GB style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial Narrow","sans-serif"; COLOR: #008040'>Please consider the environment before printing this email</SPAN></SPAN></DIV></SPAN></SPAN></DIV>
<DIV> </DIV>
<DIV><A href="http://www.blackwellgallery.com">Blackwell Gallery</A></DIV></DIV></DIV>
<DIV> </DIV></BODY></HTML>