Bank feeds and automated reconciliation — how they work, and what they do not do

Reconciliation is treated as an accounting task. It is data entry with a checking step appended. This article sets out the three ways a feed can be connected, what happens to a transaction once it arrives, and an honest account of what automation does not solve.

IN SHORT

A bank feed delivers every transaction directly into the ledger, daily, in the form the bank already publishes it. Rules propose the coding; a person reviews the exceptions rather than entering everything. Reconciliation stops being a month-end exercise because it is never allowed to fall behind. For most Caribbean businesses this is the single largest available reduction in manual finance work and the one with the shortest payback.

SECTION 1

The pattern

Bank reconciliation is treated everywhere as an accounting task. It is not. It is data entry with a checking step appended to the end of it, and the two halves have entirely different values.

The shape is the same in almost every business. The statement arrives after month end. It runs to several hundred lines. One person sits with it and works through those lines, matching what they can, keying what they must, querying what they cannot place. That takes three to five days, and until it is finished nothing downstream can happen — no reliable cash position, no creditor listing, no margin, no close.

The uncomfortable fact underneath is that the bank has already published all of this in machine-readable form. Every transaction, with its date, amount, description and reference, exists as structured data on the institution’s systems. It is then rendered into a document for a person to read, and a business pays a second person to convert it back into structured data by typing it. The work is not merely slow. It is a round trip that did not need to be made.

THE RETYPING AUDIT — take last month’s statements for every account you hold. Count the lines. Multiply nothing, adjust nothing. That number is how many times, in one month, somebody in your business re-entered information the bank had already published in a form a computer could read. Most businesses have never counted it, and the figure is usually between four hundred and two thousand.

The practice persists for three ordinary reasons. The work is invisible — it appears on no report and produces no output anyone sees. It has always been done this way, so it reads as the nature of the job rather than as a choice. And nobody has ever put a price on it, because the person doing it is salaried and would be present either way.

SECTION 2

The Caribbean variant

Six regional conditions make bank reconciliation heavier here than it needs to be — and one of them is a genuine constraint rather than a habit.

Multiple institutions are the norm, not the exception. A typical regional business holds local currency and United States dollar accounts, frequently at different institutions, and often a third account for a specific purpose — payroll, a loan, a project. Each is a separate statement, a separate reconciliation and a separate manual process.

Feed availability genuinely varies by institution. This is the real constraint and it should be stated plainly. Some regional banks support direct connections; some provide scheduled file exports that can be imported automatically; a few still deliver statements only as documents. The right answer differs by bank and sometimes by account type, and any adviser who tells you every account can be connected has not checked.

Cash-heavy trading complicates matching. Where takings are lodged as consolidated deposits, the statement shows one figure against many underlying sales. The feed delivers the deposit accurately and promptly; composing it back to the day’s trading still requires a defined process at the point of lodgement.

Cheques remain in circulation. Presentation lag creates reconciling items that are genuine timing differences rather than errors. Automation removes the keying but does not remove the cheque, and a ledger that assumes instant settlement will misstate the position.

Multi-currency accounts carry two rates. The same transaction has a transaction rate and a period-end revaluation rate. Handled manually this is a monthly project; handled at the point of entry it is a setting.

Statement formats are inconsistent. Layouts change without notice, descriptions are truncated differently by different institutions, and reference fields are used inconsistently. This matters for rule-building, and it is why rules require a settling-in period rather than working perfectly from the first week.

SECTION 3

What it costs

The figures below are indicative, drawn from advisory experience across the region rather than from survey.

The hours, expressed properly. A moderately active account of four to six hundred lines a month takes roughly six to ten hours to key and match by hand. Three accounts is most of a working week, every month, spent converting a document back into data.

Error rates that automation does not have. Manual transcription carries a small but persistent error rate, and errors in a bank reconciliation are unusually expensive because they surface late, are hard to trace, and frequently require the whole month to be re-walked to find them.

Everything downstream waits. Reconciliation is the gate. The cash position, the creditor listing, the margin analysis and the close all sit behind it. A close that takes six weeks commonly contains four weeks of waiting for reconciliation and two weeks of accounting.

Detection delay on unauthorised transactions. Where accounts are reconciled monthly and late, an unrecognised debit can sit undetected for thirty to sixty days. Most banking dispute and chargeback windows are shorter than that, so the delay does not merely postpone discovery — it can extinguish the remedy.

Audit consequences. Late or incomplete bank reconciliation is among the most common control observations in regional audits, and it drives additional testing. It is also the first thing a lender or acquirer asks to see, because it is the fastest proxy for whether the rest of the records can be trusted.

The bank publishes structured data. A document is made from it so a person can read it. Your business then pays somebody to turn the document back into structured data. Automating the feed does not add a step — it removes two.

SECTION 4

What the capability actually does

This is worth setting out mechanically, because the phrase “bank feed” is used loosely and covers three quite different arrangements.

How the connection is actually made

Direct connection. The ledger holds a read-only authority to the account and retrieves transactions on a schedule, usually daily. Nothing can be moved, paid or instructed through it; the authority permits reading only. This is the preferred arrangement wherever the institution supports it.

Scheduled file delivery. The bank exports transactions to a structured file on a defined schedule and the file is imported automatically. Slightly less immediate than a direct connection, functionally equivalent once running, and available at several regional institutions that do not offer direct feeds.

Statement conversion. Where only documents are available, statements are converted to structured data on receipt. This retains most of the benefit — no keying, consistent structure, automatic matching — while depending on somebody obtaining the statement. It is the fallback, not the target.

What happens once transactions arrive

Rules propose the treatment. A rule is a condition and a treatment: where the description contains a given payee, code to a given account, with a given tax treatment and cost centre. Rules are built from the first weeks of live data rather than in advance, because real descriptions differ from expected ones. After sixty days a typical business has rules covering seventy to eighty-five per cent of lines by volume.

Matching against what is already in the ledger. Where an invoice has been raised or a bill entered, the incoming transaction is matched to it rather than coded afresh. The system handles one-to-one matches, one payment settling several invoices, part payments and payments net of charges — each of which is a distinct manual step in a keyed process.

Everything else goes to an exception queue. Unmatched, ambiguous or new transactions are queued for a person. This is the work that actually needs judgement, and it is a small fraction of the total. The queue is reviewed daily, which means it is reviewed while somebody still remembers the transaction.

Reconciliation becomes a state rather than an event. Because the feed is continuous and the queue is cleared daily, the account is reconciled to yesterday at any moment. There is no month-end reconciliation to perform — only a month-end confirmation that the state has held, which is a different and much shorter task.

Duplicates and gaps are detected structurally. The system knows the running balance and the sequence. A missing day, a duplicated import or a balance that does not agree is flagged immediately rather than discovered as an unexplained difference six weeks later.

The trail exists without being created. Every transaction carries its source, its arrival time, the rule that coded it or the person who did, and any subsequent change. This is the evidence an auditor asks for, and nobody has to assemble it.

What a bank feed does not do

Stating this matters, because oversold automation is why finance teams distrust it.

It does not know the business reason for a transaction. A payment to a supplier who supplies three departments still requires somebody to say which one.
It does not compose a consolidated cash lodgement back into the sales that made it up. That is solved at the point of lodgement, not at the bank.
It does not remove genuine timing differences. Unpresented cheques and deposits in transit are real, and they remain reconciling items.
It does not decide anything. It proposes; a person confirms. The rule is a suggestion with a good record, not an authority.
It does not fix a chart of accounts that is wrong. Automating coding into badly designed accounts produces wrong answers faster.

SECTION 5

How the Accounting Services BPO Division delivers it

Feed viability is established before anything is promised. Part of the Diagnostic is checking, institution by institution and account by account, which of the three connection types is available. The transition plan states which accounts will be connected directly, which by file, and which by conversion.

Read-only authority, always. The division holds retrieval access and never payment authority. Banking mandates and signing rights remain entirely with the client. This is not a courtesy — it is the control that makes the whole arrangement acceptable to a lender, an auditor and a board.

Rules are built and tuned over the first sixty days. From live data, with coverage tracked as a number so improvement is visible. A business should be able to see the proportion of lines coded by rule rising week by week rather than being told that it is.

The queue is reviewed daily, not weekly. Exceptions are cleared while the transaction is recent. Anything requiring a business decision — which department, which project, is this expected — is escalated to the client the same day rather than accumulating into a month-end query list.

A named reviewer signs the reconciliation each month. Preparation and review are separated by person and by system permission, which is the segregation a department of one structurally cannot provide.

Unrecognised debits are escalated immediately. Anything that does not match and is not expected is raised the day it appears — inside the window in which a dispute can still be raised with the institution rather than after it has closed.

SECTION 6

Where to start

In the next thirty days. Run the retyping audit — count the lines on last month’s statements across every account. Then telephone each institution and ask one question: does this account support a direct feed, a scheduled file export, or neither? The answers take a morning to obtain and they determine everything that follows.

In thirty to ninety days. Connect the highest-volume account first, not the simplest one — the benefit is proportional to line count and you want the value visible early. Expect the first three weeks to feel slower while rules are built, and say so in advance, because the team will otherwise conclude it is not working. Coverage climbing past seventy per cent is the point at which the change becomes self-evident.

Beyond ninety days. Extend to every account, including the dormant ones, which are where unnoticed charges accumulate. Then change the discipline: review the exception queue daily rather than at month end. The technology delivers the transactions; the daily habit is what converts that into a reconciled position and a nine-day close.

The test: can you state your cash position, fully reconciled, as at close of business yesterday? Not estimated, not as at last month end. Yesterday. If not, the constraint is almost never the accounting.

REFERENCE

Frequently asked questions

What is a bank feed in accounting?

A connection that delivers transactions from the bank into the accounting ledger automatically, usually daily, in structured form. Rules then propose the coding and the system matches transactions against invoices and bills already recorded, so a person reviews exceptions instead of entering every line.

Is a bank feed secure? Can it move money?

A properly configured feed uses read-only authority. It can retrieve transaction information and nothing else — it cannot initiate a payment, alter a mandate or instruct the bank. Banking mandates and signing rights remain entirely with the account holder.

What if our bank does not support direct feeds?

Most of the benefit is still available. Many institutions provide scheduled file exports that can be imported automatically, and where only documents exist, statements can be converted to structured data on receipt. The keying disappears in all three arrangements; only the immediacy differs.

How long does it take before the coding rules are accurate?

Rules are built from live data rather than in advance, because real bank descriptions differ from expected ones. Expect roughly sixty days to reach coverage of seventy to eighty-five per cent of lines by volume, with the first three weeks feeling slower than the manual process it replaces.

Does automation eliminate bank reconciliation?

It eliminates the data entry, not the reconciliation. Genuine reconciling items — unpresented cheques, deposits in transit, timing differences — remain real and still require review. What changes is that reconciliation becomes a continuous state rather than a multi-day month-end exercise.

How much time does a connected bank feed actually save?

A moderately active account of four to six hundred lines a month takes roughly six to ten hours to key and match manually. Across three accounts that is most of a working week each month, recovered almost entirely — and, more valuably, the close no longer waits behind it.

NEXT STEP

Request the Finance Function Diagnostic

A 45-minute scoping conversation covering volumes, systems, entities, close cycle and reporting needs; a written recommendation on tier, scope, division of labour and transition plan; and a fixed-scope service proposal priced by process, with service levels and exit terms stated.

Contact us: Dawgen Global · Accounting Services BPO Division: [email protected] · dawgen.global/contact-us

Continue reading: “Do you need a ledger, or an operating system?” · “The shoebox is now a camera.” · “Nine days to close, not ninety.”

Indicative figures are drawn from advisory experience across the region and are not survey output.

About Dawgen Global

Dawgen Global is an independent, integrated multidisciplinary professional services firm headquartered at 47 Trinidad Terrace, New Kingston, Jamaica, serving more than 15 territories across the Caribbean. Founded and led by Dr. Dawkins Brown, Executive Chairman, the firm is independent and not affiliated with any international network. It delivers a full suite of professional services under one roof: audit and assurance; tax advisory; IT and digital transformation; risk management; cybersecurity; actuarial and insurance regulatory advisory; HR advisory; mergers and acquisitions; corporate recovery; business advisory and strategy; accounting BPO and virtual CFO services; and legal process outsourcing.

The proposition is simple: big-firm capability without the big-firm price. Dawgen Global’s integrated approach is built for the specific complexities and opportunities of the Caribbean market, helping organizations make sharper, better-informed decisions that drive measurable progress.

To explore a partnership, reach out: