Payment Runs & Reconciliation
A payment run calculation is incorrect
Resolve statement coverage, date, profile, balance, standing-rate and exporter problems.
Written by Katrin Erb Updated Published Use these checks when a payment run cannot be created, calculation fails or the result is unexpected.
No date is available
-
Import statement-backed balances for every selected pool.
-
Confirm that the selected pools share an overlapping range of available dates.
-
Check that the range does not overlap an existing payment run.
-
Do not select dates before the pool's first account assignment or after yesterday.
-
If no date is suggested, review the bank's interest posting schedule and branch overrides or choose a valid range manually.
Missing profile period
Every included date needs an effective interest and payout profile period. A pool using Standing Rates also needs standing-rate coverage. Review the start and end dates of each profile period and create the missing effective-dated period.
Unexpected account result
-
Confirm the account was assigned to the pool on that date.
-
Review its imported balances and any negative-balance warning.
-
Check the interest and payout tiers, tiering method and day-count convention.
-
Check whether the standing-rate floor was applied.
Non-positive balances do not earn client interest. Flinq lists negative balances for review rather than silently treating them as positive.
No exporter is available
Confirm that an active exporter supports the pool's bank and currency. Automated exporters must be configured and not failing. Review Office Settings before recreating the payment run.
Calculation remains incomplete or fails
Open the payment run and review its notifications and History. Preserve the pool names, date range, exporter, calculation status and error time before contacting Flinq support.
Keep reading