Settings and activity
3 results found
-
39 votes
Hi team, we appreciate your feedback and have been taking this on board as the team closely consider improvements to our auto reconcile experience.
Currently, we are working on a new settings panel that'll provide more control of what you would like auto reconciliation to be driven by.
I will share another update as this comes to life and keep you updated of it's release here. 🙂
An error occurred while saving the comment 
Babak Yeganegy-Bruckhoff
supported this idea
·
An error occurred while saving the comment Babak Yeganegy-Bruckhoff
commented
It would be very helpful if JAX could be improved by ensuring a higher weighting is applied to high confidence matching criteria such as matching unique customer identifiers in the incoming payment references. We had a recent case where the unique identifier matched but was not given sufficient weighting , therefore other criteria was referred to with a lower confidence threshold (in our case the first name) which auto-reconciled to the wrong account.
-
722 votes
Thanks for your feedback on Single Sign-On(SSO). We last updated this idea in October 2025, and we’re sorry it’s taken some time for us to provide another. We will do our best to keep you more informed of progress as it continues.
Where SSO is today
We’ve built an SSO capability for accountant and bookkeeper partner practices using OpenID Connect (OIDC). We ran a closed beta with a small group of partners, which is now complete, and those partners are connected. We’re still confirming how and when other accounting and bookkeeping partners can access it. SSO isn’t currently available to businesses or IT providers. We’ll share access details in a future update once they’re confirmed.
What we’re looking at next
We’re exploring what it would take to offer SSO to small businesses. Business needs differ from accountant and bookkeeper partners’, so we’re looking at:
- how a business and its users…
Babak Yeganegy-Bruckhoff
supported this idea
·
-
36 votesBabak Yeganegy-Bruckhoff
shared this idea
·
JAX performs well for inbound transaction reconciliation, but its handling of outbound transactions generates enough misallocations that any time saved is lost through manual re‑allocation. Because there’s no way to differentiate between inbound and outbound transactions, we’ve been forced to disable JAX.
A simple option to enable JAX for inbound transactions only would make the feature far more usable in practice.