Skip to main content
Most issues in Finluency come down to one of a few root causes: an account connection that needs attention, a recurring transaction that wasn’t set up or has gone stale, or a forecasted entry that doesn’t reflect reality. The sections below walk you through the most common problems and how to resolve them.
Finluency is currently in early access, which means the product is actively evolving. Some features may change, and you may occasionally encounter rough edges. Your feedback directly shapes what gets built next — please share anything unexpected with the team through the early access contact.
An unexpected balance is almost always explained by one of the following:
  1. Pending transactions — Transactions that have been initiated but haven’t cleared yet will affect your displayed balance. Check whether any pending items are inflating or deflating the number you see.
  2. Missing account connections — If one of your accounts isn’t connected, its transactions won’t appear in your dashboard. Verify that all of your accounts show as connected and active.
  3. Recurring transactions not configured — If a regular outflow or inflow isn’t set up as a recurring transaction, Finluency won’t include it in your projected balance. Review your recurring transactions to make sure they match your real-world obligations.
If none of these explain the discrepancy, reach out through the early access contact and include the account name and the amount you’re seeing versus what you expect.
After connecting a new account, transactions may take a moment to sync. Wait a few minutes and refresh your dashboard before troubleshooting further. If transactions still don’t appear:
  • Verify the account type is supported — Finluency currently supports checking accounts, savings accounts, credit cards, and lines of credit. If your account falls outside these types, it may not populate transaction data yet.
  • Check the connection status — Navigate to your account settings and confirm the connection shows as active, not errored or expired.
  • Reach out for support — During early access, the team can investigate connection issues directly. Contact support through finluency.com and describe the account type and institution.
When you reach out, include the name of the financial institution and the type of account. This helps the team diagnose connection issues much faster.
If a transaction appears under the wrong account, you can edit it directly from the transaction detail view. Select the transaction, open its edit panel, and reassign it to the correct account. Save your changes, and the transaction will move immediately. If you find this happening consistently with a particular account, it may indicate a connection configuration issue — in that case, review your account connections or contact support.
Your forward balance is a projection built from everything Finluency knows: posted transactions, pending items, recurring obligations, budget allocations, and forecasted entries. If the number looks off, work through this checklist:
  • Recurring transactions — Are all of your regular income and expense items entered? A missing subscription, payroll run, or monthly payment can shift the projected balance significantly.
  • Forecasted transactions — Have you added the one-time or irregular items you know are coming? A large expected payment or deposit that isn’t in your forecast won’t appear in the projection.
  • Pending items — Pending transactions contribute to your balance but haven’t cleared yet. If several large items are pending, they may be pulling the forward number in an unexpected direction.
  • Budget allocations — If you’ve set budget entries, they factor into the forward model. Check whether any budgeted amounts are larger or smaller than your actual expected spend.
There are a few reasons a recurring transaction might drop out of your forecast:
  • It was edited or deleted — Check your list of recurring transactions to confirm the entry still exists and its details are correct.
  • An end date was set — If a recurring transaction was configured with an end date that has now passed, Finluency will stop projecting it beyond that date. Open the transaction and update or remove the end date if the recurring obligation is ongoing.
  • It was manually resolved — In some cases, marking a recurring transaction as resolved can remove it from future projections. Review the transaction’s status and reactivate it if needed.
It’s common for a forecasted or recurring transaction to post at a slightly different amount or date than anticipated. When this happens:
  1. Let the posted transaction stand — Once a transaction posts, it reflects the real, cleared amount. Posted transactions take precedence over forecasts in your balance calculation.
  2. Update the recurring or forecasted entry — If the difference is systematic — for example, a subscription that increased in price — edit the recurring transaction so future projections use the correct amount.
  3. Remove the duplicate forecast — If a forecasted transaction and the corresponding posted transaction are both showing, remove or resolve the forecasted entry to avoid double-counting.
Currently, Finluency does not have an undo function for deleted recurring transactions. To restore it, re-create the recurring transaction manually with the same details: payee, amount, frequency, and start date.
The ability to recover deleted items is on the product radar. Because Finluency is in early access, this kind of feedback directly influences the development roadmap — let the team know this matters to you.
When your cash flow timeline looks wrong end-to-end, run through this checklist from the top:
  1. All accounts connected — Confirm every account you want included in your cash flow view is connected and syncing.
  2. Recurring transactions up to date — Review your full list of recurring transactions. Add any that are missing and update any that have changed in amount, frequency, or end date.
  3. Forecasted transactions entered for known items — Add forecasted transactions for any anticipated income or expenses that aren’t covered by your recurring entries — one-time invoices, irregular purchases, tax payments, and so on.
  4. Budget allocations reviewed — If you use budget transactions, make sure they reflect your actual intended spend for the period.
  5. Pending items acknowledged — Keep in mind that pending transactions haven’t cleared yet and can shift once they post.
Working through these steps in order resolves the vast majority of timeline discrepancies.
Finluency is in early access, and the team is actively supporting users directly. If you have a question, run into an issue, or want to share feedback, reach out through the early access contact on the Finluency website at finluency.com. The team will get back to you personally.
The more detail you include — what you expected to see, what you actually saw, and the account or transaction involved — the faster the team can help you.