Overview
Some banks restrict certain account types — including Lines of Credit (LOC), loans, and investment accounts — from being shared via their API connections. This is not a LedgerSync limitation. It is an internal policy decision made by the bank itself.
Chase Bank is a prime example. Chase's API is among the cleanest and most reliable connections LedgerSync supports — it either works or it doesn't, with no ambiguity. However, Chase has made the deliberate decision not to expose Line of Credit, loan, or investment account statements through their API due to their own internal regulations. This applies regardless of which third-party fintech application is requesting the data.
What LedgerSync Still Receives
Even when a bank restricts statement access for LOC or loan accounts, LedgerSync will typically still receive transaction data for those accounts. So while you won't get a formal PDF bank statement for a Chase Line of Credit, the individual transactions will still flow through.
The Best Workaround: Running Balance Report
For Line of Credit accounts — particularly Chase LOC — the Running Balance Report is the recommended solution.
Here's why it works especially well for LOC accounts:
How to Use the Running Balance Report:
This gives you what you need for reconciliation purposes without requiring a formal PDF statement.
Does This Apply to Other Banks?
Yes. Chase is used here as an example, but other financial institutions may similarly restrict API access for certain account types. If you encounter a situation where statements are not flowing for a specific loan, LOC, or investment account — even though the bank connection appears healthy — the most likely cause is a bank-side restriction on that account type.
In all such cases, check whether transactions are still flowing, and if so, use the Running Balance Report as your reconciliation backup.
Need Help?