Blackline experienced a minor incident on October 18, 2026 affecting Transaction Matching and Transaction Matching and 1 more component, lasting 17h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 19, 2026, 02:14 AM UTC
Since the October 2026 release, some users get an error when they create a manual match in Transaction Matching and select certain reason codes. When this happens, the match isn't created. Existing matches and transaction data aren't affected. The issue occurs only when all of the following are true: - The user is working in the Preparer role. - The match set isn't an ad hoc match set. - The selected reason code is configured to take its value from a data source field. This affects manual matches created from Unmatched Transactions, including matching and creating an item in the same step. Workarounds: - Choose a reason code that isn't configured to use a data source field, or create the match without a reason code where the match set allows it. - Have a user working in a role other than Preparer create the match.
- monitoring Oct 19, 2026, 05:06 AM UTC
BlackLine has deployed a fix for the Transaction Matching issue reported. You should be able to resume normal activities. We will continue to monitor the situation to ensure there are no additional issues. We will confirm when the service is fully operational.
- resolved Oct 19, 2026, 09:08 AM UTC
BlackLine has confirmed that the service is fully operational and we apologize for any inconvenience this issue may have caused.