"Doesn't connect properly with DBS Ideal though so bummer — have to import transactions from DBS manually."

That's a real comment from a Singapore business owner, posted on Reddit, describing their experience with QuickBooks Online. It was posted five years ago. It's still happening today. The thread is still getting new replies from people with the exact same problem.

DBS is Singapore's largest bank. QuickBooks is one of the most recommended accounting tools in Singapore. They don't work together properly. And that's not a bug. It's a structural problem.

Why the Bank Feed Keeps Breaking

QuickBooks uses third-party data aggregators — companies like Plaid and Yodlee — to connect to bank accounts globally. These aggregators scrape or access bank data through APIs that banks provide.

The problem for Singapore businesses is that DBS, OCBC, and UOB's business banking systems — DBS Ideal, OCBC Velocity, UOB BizSmart — were built for the Singapore market, not for US-based aggregators. The connections are fragile, frequently updated by the banks without notice, and often incompatible with how QuickBooks expects data to be formatted.

When the connection breaks — and it will — QuickBooks support can't fix it directly. They escalate to the aggregator. The aggregator needs to update their integration. This takes days to weeks. Meanwhile your reconciliation falls behind.

The Hidden Cost of Manual CSV Imports

The common workaround is to download your bank statement as a CSV file from DBS Business Online and import it manually into QuickBooks.

This sounds like a minor inconvenience. Over a year, it isn't.

If you import weekly (which is what you need to stay current):

• 10 minutes per import
• 52 imports per year
• 8.7 hours per year of pure data entry

That's before you account for the formatting issues. DBS CSV exports don't always match what QuickBooks expects. Dates format differently. Transaction descriptions truncate. Duplicate transactions appear when you re-import a period that overlapped. Each one needs manual review.

At a conservative SGD 50 per hour for a business owner's time, that's SGD 435 per year just to work around a broken integration. For a finance assistant's time, it's a similar number. This is money and time you're spending to fix a tool that's supposed to save you time.

Why QuickBooks Has This Problem in Singapore

QuickBooks was built for the American market. Its Singapore version is a localised adaptation — GST support was added, the currency defaults to SGD, and some local payment methods are supported.

But the bank feed architecture is American. The aggregators are American. The prioritisation for fixing Singapore-specific bank connection issues is, understandably, lower than fixing issues that affect millions of users in the US.

This isn't QuickBooks being negligent. It's a fundamental mismatch between a global product and a local market's banking infrastructure.

What OCBC and UOB Users Experience

DBS Ideal gets the most complaints, but OCBC Velocity and UOB BizSmart users face similar issues. The connection works for a few weeks, then stops. Transactions start duplicating or missing. Reconnecting requires going through an authentication flow that sometimes loops without completing.

Some users have given up on bank feeds entirely and import manually as a matter of routine. Others hire a bookkeeper specifically to manage the manual reconciliation. Both are expensive solutions to a problem that shouldn't exist.

What Actually Works for Singapore Banks

Singapore-built accounting tools have native integrations with DBS, OCBC, and UOB. Native means the integration was built specifically for these banks' APIs, maintained directly by the software team, and updated immediately when the banks make changes.

This is different from using a third-party aggregator. When DBS updates their business banking platform — which they do regularly — a native integration is updated in coordination. A third-party aggregator finds out when it breaks.

ArcPay was built for Singapore. DBS, OCBC, and UOB bank feeds are native integrations, not third-party workarounds. When a connection breaks, the team fixes it directly — not through a chain of escalations to a US-based aggregator.

If you've been importing CSV files every week as a workaround for a bank feed that won't stay connected, that's not how it's supposed to work.

Start your free 14-day trial →

No credit card required. Connect your Singapore bank in under 2 minutes.