Reconcilia Cloud · Singapore bank integration accounting

Reconciliation, resolved.

Two statements. One amber line. Close faster. Your daily DBS, UOB and OCBC feeds land where the ledger lines already sit.

Bank feed

Cleared

  • 01 DBS operating account · daily feed 12 Nov
  • 02 OCBC payroll account · daily feed 12 Nov
  • 03 UOB collection account · daily feed 11 Nov

Ledger

Matched

  • 01 Takings and card settlement
  • 02 Payroll run · monthly
  • 03 GST set-aside transfer

Reconciliation starts with a feed. Three of your accounts land here before your first coffee. Everything else waits for your authorisation, not ours.

Where your feed lands

What actually arrives from your bank.

A feed connection gives the platform transaction data for the accounts you authorise: date, amount, currency, description, and the reference string where the bank supplies one. That is the raw material — nothing more is claimed for it.

  • Feeds DBS, OCBC, UOB 3
  • Fallback Statement import Any
  • First run Previous full month 1

You can revoke a connection at any time through the bank. Reconciliation data already imported stays in your workspace for the periods you have closed.

Bank feed · DBS · UOB · OCBC · IRAS

  • DBS
  • UOB
  • OCBC
  • IRAS

Setting up a connection

Most Singapore SMEs doing this have no IT team.

They should not need one. Connection setup is a guided sequence with the bank consent step explained before it starts, not after it fails.

  1. Step one

    Pick the account

    DBS is usually the first connection an SME makes — it is often the operating account. OCBC and UOB connect the same way, so nothing about the process changes between banks.

  2. Step two

    Authorise at the bank

    Authorisation happens through the bank's own consent flow. The platform never receives your banking credentials, and no payment instructions originate from Reconcilia Cloud.

  3. Step three

    Pull the first month

    Start with the previous full month. It gives you a complete reconciliation cycle to compare against work you have already done by hand, which is the fastest way to judge whether the platform's matching agrees with your own.

Bank by bank

Three local feeds, and what is different about each.

Reconciling only part of your cash position gives you a partial picture of what cleared. That is why connecting all three matters more than connecting the biggest one well.

DBS

Consent flow

DBS is one of the standard feeds for Singapore SMEs and the account most teams connect first. Authorisation happens through the bank's own consent flow, after which the platform pulls transaction data for the accounts you selected.

Setup takes a few minutes per account, and the first import can reach back through historical months if you want a parallel run against a completed close.

OCBC

Consent flow

OCBC connects the same way. A common pattern for an SME is a main operating account at one bank, payroll at another, and a separate account for GST set-aside — which is exactly why the three-connection layout pays off on a manual close.

Reconciling only part of your cash position gives you a partial picture of what cleared.

UOB

Reference normalisation

UOB feed support covers the operating and collection accounts most SMEs hold there. Reference strings from UOB transactions are normalised before matching, which reduces the common failure where a payment reference carries extra characters the ledger does not have.

If a collection account receives customer payments with varied reference formats, that normalisation is what keeps the match rate from collapsing.

Accounts elsewhere

A supplementary account at any other institution still reconciles.

Download the statement in a supported format, upload it, and the file lands in the same reconciliation workspace. No second tool, no second spreadsheet.

This is also the fallback when a feed is temporarily unavailable. Reconciliation does not stall waiting for a connection to recover.

A Singapore bank branch exterior detail — powder-coated steel panel and brushed metal handle, no signage.

Statement import · the same reconciliation workspace

Multi-account structure

Accounts grouped by currency and purpose.

A USD receivable account reconciling against SGD books uses the transaction-date rate, and the FX difference is tracked rather than absorbed. If you hold accounts in several currencies, the cash view consolidates them with the conversion shown.

Currency

Separate per currency

SGD, USD and other accounts reconcile against their own books. Cross-currency differences show against the transaction date, not the reporting date.

Purpose

Grouped by what they do

Operating, payroll and set-aside accounts sit in groups you name. A GST set-aside account reads as a group, not as another number in a long list.

Combined view

Group position, one screen

The consolidation shows the conversion alongside the total, so you can see the group position and the per-account position without switching screens.

When a feed stalls

A stalled feed never runs silently.

Feeds occasionally need reauthorisation, usually after a bank-side credential change or an extended consent expiry. The platform flags a stalled feed rather than silently showing stale data.

That flag is the one alert worth acting on immediately. A reconciliation built on a feed that stopped three days ago looks complete and is not. When the flag appears, re-run the bank consent step and the missing days backfill into the same workspace.

First import date range

Pull one month, not one year.

Pulling a full year on day one creates a large exception queue before you have learned the interface. One month is enough to form an opinion.

The comparison works because you already know what your manual close produced. Run the platform against the same month, compare the exception list to the list you carry now, and judge the platform from that.

Next step

Connect your first bank and see the month close.

If a step stalls, the contact page reaches the Singapore team directly. Onboarding help is part of the support commitment on every plan. For the closest fit and the payment-frequency options that suit your team, the pricing page carries the plan structure in full.

Privacy notice

We keep a few cookies so your bank feed stays signed in and your reports render right. What we store