The only difference I can see between the Apple Credit Card transaction download response (<CREDITCARDMSGSRSV1>, the one that works in Quicken) and the Apple Savings Account transaction download response (<BANKMSGSRSV1>, the one that DOES NOT work in Quicken) is that is that the Apple Savings file doesn't include the <AVAILBAL> field.
<AVAILBAL>
<BALAMT>18842.26
<DTASOF>20231231120000[0:GMT]
</AVAILBAL>
Judging by the amount shown here, that's the credit limit balance, so no reason to expect one in savings account statement.
The individual transactions are almost the same in both message requests with the 'Memo' field featuring in the savings account transaction data but not in the credit card.
Credit Card Account <CREDITCARDMSGSRSV1> transaction example:
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20231230120000[0:GMT]
<TRNAMT>-0.99
<FITID>fee2bd93-691d-4de4-8120-dcb284fe95
<NAME>APPLE.COM/BILL ONE APPLE PARK WA
</STMTTRN>
Savings account <BANKMSGSRSV1> transaction example:
<STMTTRN>
<TRNTYPE>CREDIT
<DTPOSTED>20231218120000[0:GMT]
<TRNAMT>0.89
<FITID>522e01bc-59d8-4f22-99a7-c360ed7a8b
<NAME>Daily Cash Deposit
<MEMO>Rewards
</STMTTRN>
These look like very simple file structures, no obvious differences in the files from Apple. If I was to hazard a guess as a layman, I would say that Quicken has an issue with its BANKMSGSRSV1 parsing that it doesn't have with its CREDITCARDMSGSRSV1 parsing.
