0 incidents in the last 7 days
1 incidents in the last 30 days
Last check: 2 minutes ago
Last known issue: 29 days ago
Resolved New OAuth connections unavailable
We're currently investigating the unavailability of new OAuth connections to Brex, Bank of America, Chase and CapitalOne. The current behavior is reported as being redirected to the Expensify Inbox after attempting to connect for the first time. Existing connections are currently unaffected. More updates to come.
Resolved Chase connections are currently unavailable
Existing Chase connections will not be automatically updated and manual syncing of connections will work intermittently at best. During this downtime, it will not be possible to connect a new Chase account for expense import or to send or receive reimbursements.
Resolved Bank of America and Chase Card Import and Plaid connection outage
Our Bank of America and Chase connections are currently down and during this time you will not be able to make new connections or update existing cards. This outage also affects the ability to add accounts via Plaid for payment accounts. We are monitoring the outage and will update once resolved.
Resolved Chase connections will not update automatically until Tuesday March 16, 2021.
Automatic updating of Chase connections will be temporarily paused starting Friday, March 12, 2021, and resume Tuesday, March 16, 2021. During this time you can manually update your connection from the Settings > Account > Credit Card Import page of your account.
Resolved Bank of America Disruption
We are aware of a recent issue that affects all Bank of America customers. Specifically, they will not be able to import new credit card transactions assigned via both the personal and domain settings. We are actively working with our Bank of America partners to resolve this issue and will post an update as soon as we have a resolution.
Resolved Wells Fargo Connection Issues
Wells Fargo has identified an issue on their side where they are not correctly processing some of our data transfer requests. This means that cards currently connected might not be able to update and new cards might not be able to connect. They are investigating the issue and we'll update this status as we hear updates from them.
Resolved Outbound emails not sending
An issue has been identified with system-generated Expensify emails not sending. This will include the weekly reminder email and notifications of reports which are ready for approval. The team are actively investigating this. You can see which tasks need your attention from your Expensify Inbox at www.expensify.com/inbox. In addition, email replies from Concierge were not sending in a timely fashion, so if you have been emailing in there may have been a delay on responses.
Resolved Wells Fargo transaction import paused
A recurrence of a previous incident has occurred whereby duplicate transactions are being imported for connected Wells Fargo credit cards. Expensify has paused the importing of transactions for these cards whilst Wells Fargo investigate to avoid any immediate impact and confusion caused by working with these duplicates. You can still connect and assign cards from Wells Fargo, but no transactions will import.
Resolved Unable to connect or export with NetSuite SuiteSignOn
Any customers connected to NetSuite via SuiteSignOn may be encountering "Login Error. Please check your credentials" in Expensify when syncing or exporting to NetSuite, or "This feature is not available to your company" in NetSuite when connecting to Expensify. A known fix is to switch your NetSuite connection to update your Expensify Bundle, disconnect from NetSuite, and reconnect with Token-Based Authentication. The team is working hard to bring SuiteSignOn back as soon as possible. Reach out to [email protected] for anything else.
Resolved Errors and slow upload speeds for receipt uploads and PDF exports
We are currently working to fix an issue that is affecting how you upload receipts through the web app and mobile app, and export reports to PDF through the web app. You might see errors that suggest your file "might be corrupt or have illegal characters in it", or receive an email saying "Unfortunately the SmartScan did not work. Please upload manually". We're sorry for interrupting your work, and are working to fix this as quickly as possible. We'll update you here shortly.