Cash Flow Forecasting and Bank Reconciliation in Business Central

Ask any owner or finance director what number they check first thing in the morning, and it is almost never revenue and almost never profit. It is cash. Profit is an accounting opinion that can be perfectly healthy while the company quietly runs out of money to pay its people. Cash is the fact that keeps the lights on. Business Central understands this, which is why it ships with a cash flow forecasting engine that projects your liquidity forward and a bank reconciliation function that ties your ledger back to reality. Most implementations use one of these two features badly and the other one not at all. This guide covers both properly, from a practitioner who has set them up and cleaned up after teams who did not.

The message up front: cash flow forecasting and bank reconciliation are two halves of one discipline. The forecast tells you where the money is going; the reconciliation proves where it actually went. A forecast built on an unreconciled bank balance is fiction, and a reconciliation with no forward view is just tidy history. Run them together and finance stops guessing.

1. Why cash visibility is the number that keeps owners awake

There is a well-worn phrase in finance that profit is vanity, cash is sanity, and cash flow is reality. It survives because it is true. A business can post a strong profit and loss statement and still fail, because profit recognises revenue when it is earned, not when the money lands, and it recognises many costs before or after the cash actually moves. The gap between those two timings is working capital, and working capital is exactly where companies get into trouble. You can be profitable and insolvent at the same time, and the first you know of it is the morning a payment bounces.

Cash visibility is the antidote. It is the ability to look at a calendar of the next several weeks or months and say, with reasonable confidence, how much money you will have on any given date, and whether that number ever dips below zero or below the covenant your bank imposes. That single view changes behaviour. It tells you when you can safely commit to a large purchase, when you need to chase a slow-paying customer harder, when to draw on a facility, and when to delay a discretionary spend by two weeks so it lands after a big receivable clears. Without it, finance manages cash by looking at the current bank balance and hoping, which works right up until the month it does not.

In Abu Dhabi and the wider region, this pressure is sharpened by long customer payment cycles, project-based revenue that lands in irregular lumps, and multi-currency exposure that moves the value of your receivables between the day you invoice and the day you collect. A business here often has plenty of value on its balance sheet locked up in receivables and work in progress while the current account runs thin. Cash flow forecasting is how you see that squeeze coming with enough runway to act on it, rather than discovering it when a supplier calls about an overdue payment.

Business Central does not solve the underlying working-capital problem for you, but it does give you the instrument to see it clearly, and seeing it clearly is most of the battle. The feature that does this sits inside the broader finance module. If you want the wider context of how the general ledger, receivables, payables and reporting fit together, the Business Central financial management pillar covers the whole finance backbone, and this article zooms into the cash and treasury corner of it.

2. How cash flow forecasting works in Business Central

Business Central's cash flow forecast is not a spreadsheet bolted on the side. It is a proper feature built on a small set of setup objects that, once configured, pull directly from your live transactional data so the forecast refreshes itself as the business runs. Understanding the moving parts keeps you from treating it as a black box.

The foundation is the cash flow chart of accounts, sometimes called cash flow accounts or cash flow setup. This is a separate, deliberately simple structure, distinct from your financial chart of accounts. Where your general ledger might have hundreds of accounts, the cash flow chart of accounts is a short list of the categories that matter for liquidity: receivables, payables, liquid funds, fixed asset disposals and acquisitions, cash flow from operations, and so on. The reason it is separate is that a forecast needs to be readable at a glance. You do not want to project cash across three hundred ledger accounts; you want to see a handful of meaningful buckets and the net position they produce.

Sitting alongside those cash flow accounts is the cash flow setup card, where you tell Business Central a few essential things: which general ledger accounts represent your liquid funds so the system knows your starting bank position, and how the various data sources map into the forecast. This mapping step is the part teams most often skip or rush, and it is the part that determines whether the forecast is trustworthy. If the mapping is wrong, the numbers are wrong, and a wrong forecast is worse than no forecast because it invites confident bad decisions.

Once the accounts and setup exist, you create one or more cash flow forecast cards. A forecast card defines a named projection with its own settings: the source types it includes, the taxonomy it uses, and optionally an overdue-payment handling rule that shifts past-due receivables and payables forward into the near term rather than pretending they already settled on their original due date. You can maintain several forecasts in parallel, for example a conservative one and an optimistic one, which is genuinely useful when you want to show a board a range rather than a single deceptively precise line.

Business Central also provides an assisted setup guide for cash flow forecasting that walks you through creating the chart of accounts, the setup card and an initial forecast, and it can even generate a default structure and schedule an automatic periodic update. I recommend running the assisted setup on a first implementation to get a working baseline quickly, then refining the account mapping by hand once you can see real numbers flowing. The guide gets you to a running forecast in minutes; the refinement is where the accuracy comes from.

The practitioner's insight: keep the cash flow chart of accounts short. The temptation is to mirror your general ledger for the sake of detail, and it always backfires. A forecast with fifty categories is a forecast nobody reads. Eight to twelve buckets that map cleanly to how the business thinks about cash will be used every week. Detail is not the same as insight, and in a forecast, less structure usually means more clarity.

3. The sources that feed the forecast

A cash flow forecast is only as good as the transactions feeding it, and Business Central's strength here is that it draws from the live subledgers rather than asking you to key figures in by hand. Each source is a different kind of future cash movement, and knowing what each one contributes helps you judge how complete and how reliable the picture is.

• Receivables (customer entries): every open sales invoice with a due date is a projected cash inflow. Business Central places the amount on the expected payment date so the forecast shows money arriving when the customer is contractually due to pay. This is usually the largest single inflow source, and its accuracy depends entirely on how realistic your due dates are versus how customers actually behave.
• Payables (vendor entries): every open purchase invoice is a projected outflow on its due date. Together with receivables this forms the core operating cash picture, the timing mismatch between what you are owed and what you owe, which is the heart of working capital.
• Fixed assets: budgeted asset acquisitions and disposals feed the forecast as future outflows and inflows. A planned capital purchase of equipment three months out shows up as a cash drain on the projected date, so a large capex commitment does not ambush the liquidity position.
• General ledger budget: Business Central can pull from a G/L budget to represent expected income and expenditure that is not yet captured as a specific invoice, for example recurring salaries, rent and utilities. This fills the gap between the concrete open documents and the predictable-but-not-yet-documented movements.
• Cash flow manual revenues and expenses: for one-off or irregular items that live in none of the subledgers, such as an expected tax refund, a dividend, a loan drawdown or a planned repayment, you enter manual revenue and expense records with their own dates and recurrence. This is the escape hatch for everything the automated sources cannot know about.
• Sales and purchase orders: depending on configuration, open orders that have not yet become invoices can also contribute, giving an earlier and more forward-looking picture at the cost of some certainty, because an order is a weaker commitment than an invoice.

The art of a good forecast is combining these sources without double counting and without leaving gaps. The subledger sources are automatic and accurate as far as they go, but they only know about transactions that already exist in the system. The budget and the manual entries are how you extend the forecast beyond the documents you have already raised, into the predictable rhythm of the business. A forecast that uses only receivables and payables is honest but short-sighted; it sees the next few weeks of documented movements and goes blind after that. Layering in the budget and manual items is what turns a short-range collections view into a genuine multi-month liquidity plan.

The honest limitation: the forecast believes your due dates. If your customers routinely pay thirty days late and your invoices say net thirty, the forecast will show cash arriving a month before it actually does, every single time. Business Central offers overdue-payment handling to push past-due amounts forward, but it cannot predict habitual lateness on invoices that are not yet overdue. Calibrate expected payment dates against real customer behaviour, or build a conservative forecast that discounts optimistic due dates, otherwise the projection will be structurally too rosy.

4. Reading and acting on the forecast

Setting up the forecast is only worth doing if someone reads it and acts on it, and Business Central presents the output in a few complementary ways designed for exactly that. The point of the forecast is not to admire the chart; it is to trigger decisions early enough that they are cheap.

The most visible surface is the cash flow chart, which can sit as a stack or cue on the role centre home page so finance sees the liquidity trend the moment they open the system. The chart plots projected cash position over a series of periods, typically weeks or months, and the shape of the line is what matters. A line trending steadily upward is comfortable. A line that dips toward or below zero at any future point is an early warning with time still on the clock, which is precisely when a warning is useful. A dip six weeks out is a problem you can solve by accelerating a collection or delaying a payment; the same dip discovered on the day is a crisis.

Underneath the chart you can drill into the periods. Business Central lets you view the forecast by day, week, month or quarter, and moving between these granularities changes what you can see. A monthly view is right for board reporting and medium-term planning. A weekly or even daily view is what you need when cash is tight and the question is not whether you can pay this month but whether you can pay in the third week of it, before the big receivable clears in the fourth. Being able to zoom the period is the difference between strategic comfort and operational survival, and tight periods are exactly when the daily view earns its place.

Because you can maintain multiple forecast cards, you can run simple what-if analysis by comparing them. Build one forecast on conservative assumptions, where you discount uncertain inflows and assume customers pay late, and another on planned assumptions using contractual due dates. The spread between the two is your risk band, and showing decision-makers a band rather than a single line is both more honest and more useful. It reframes the conversation from a false precision of a single number to a realistic range, which is how cash should actually be discussed. You can also test a scenario by adding a manual expense for a contemplated purchase and watching whether it pushes the projected line below zero at any point, which is a fast and safe way to pressure-test a spending decision before you commit to it.

The discipline that makes all of this real is refreshing the forecast on a schedule. Business Central can recalculate the forecast automatically on a recurring basis through a job queue entry, and I strongly recommend setting that up so the numbers are never stale. A cash flow forecast that is recalculated once a quarter is a historical curiosity; one that refreshes every night is a live instrument the team can trust. Automate the recalculation, put the chart where people already look, and the forecast stops being a project deliverable and becomes part of the daily rhythm.

5. Bank account setup and management

We now cross from the forward-looking half of treasury to the backward-looking half, and it starts with getting your bank accounts set up correctly in Business Central, because everything about reconciliation depends on this foundation. A bank account in Business Central is a master record, created and maintained as a bank account card, and it represents one real account at one financial institution. The mapping should be one card to one real account, cleanly, with no shortcuts.

Each bank account card carries the essential identity of the account: the bank name, account number, IBAN and SWIFT or BIC where relevant, and the currency the account operates in. That currency setting matters more than teams expect. A bank account card is tied to a currency, and if the account is a dirham account, its card should be a dirham account. Most organisations operate several bank accounts, an operating account, a payroll account, perhaps separate accounts for different currencies or different entities, and each of those becomes its own card. There is no practical limit that matters here; you create as many bank account cards as you have real accounts, and Business Central keeps the ledger entries for each of them separate.

The link between the bank account card and the general ledger is worth being deliberate about. Each bank account has a corresponding general ledger account, and payments and receipts posted against the bank account flow through to that G/L account. The bank account card holds the detailed, transaction-level view of everything that has moved through that account, while the linked G/L account holds the summarised financial view. Reconciliation, at its core, is the act of proving that these two views agree with each other and with what the bank itself reports. Getting the setup right, one card per real account, correct currency, correct linked G/L account, is what makes the reconciliation that follows straightforward rather than a monthly fight.

For multi-currency operations, which are the norm rather than the exception in this region, the currency handling deserves attention. A foreign-currency bank account records its entries in that currency, and Business Central handles the exchange to your local reporting currency using the exchange rates you maintain. This means a dollar account can be reconciled in dollars against a dollar bank statement, while the general ledger still reports everything in dirhams. That separation is exactly what you want; you reconcile in the currency the bank speaks, and the system takes care of translating the result into your books. Where currency handling goes wrong is almost always stale exchange rates, so keeping the exchange rate table current is part of clean bank management, not an afterthought.

6. The bank reconciliation process, step by step

Bank reconciliation answers one deceptively simple question: does what Business Central thinks is in the bank match what the bank actually says is in the bank? The two disagree for perfectly legitimate reasons at any moment in time, and reconciliation is the disciplined process of accounting for every one of those differences until nothing is left unexplained.

The differences fall into a few predictable categories. There are outstanding items you have recorded but the bank has not yet processed, such as a payment you posted that has not yet cleared, or a deposit in transit. There are items the bank has recorded that you have not yet entered, such as bank charges, interest, direct debits or standing orders that hit the account without a document in your system. And there are, occasionally, genuine errors on either side. A reconciliation is complete when every difference between your ledger and the bank statement has been assigned to one of these explained categories, and the residual unexplained difference is zero.

In Business Central the mechanism for this is the bank account reconciliation. The essential flow, at a functional level, runs like this:

Walking through that in words: you create a bank account reconciliation for the account, record the statement's ending balance and date, and bring in the statement lines. Business Central then helps you match those statement lines against the open bank account ledger entries, the payments and receipts you have already posted. There is a suggest-lines capability that proposes matches automatically based on amount and date, and it clears the bulk of the routine items in one pass. What remains after the automatic matching is the interesting part: the lines that did not match. Those are either items on the statement you have not yet recorded, which you enter, or items in your ledger the bank has not yet cleared, which you leave as outstanding. When every line is accounted for and the calculated difference between your adjusted balance and the statement balance reaches zero, you post the reconciliation, and the matched entries are marked as cleared so they never confuse a future reconciliation.

The reason to do this on a regular cadence, monthly at the least and weekly for a busy operating account, is that small unexplained differences are easy to find when they are fresh and nearly impossible to find months later buried under thousands of transactions. A reconciliation that is a month behind is a reconciliation where every discrepancy is a forensic exercise. Kept current, it is a fifteen-minute routine. The discipline of cadence is worth more than any feature.

7. Automatic bank statement import

Keying bank statement lines in by hand is slow, error-prone and completely unnecessary in a modern setup, and Business Central supports importing the statement so the machine does the transcription. There are two broad routes, and which one you use depends on your bank and your region.

The first route is file import. You download a statement file from your bank's portal in a supported format and import it into the bank account reconciliation. Business Central natively supports common structured formats, and the widely used one internationally is the ISO 20022 camt.053 bank statement format, a standardised XML statement that most modern banks can produce. There is also broad support for delimited and other file layouts through the data exchange framework, which lets you define a mapping from whatever column structure your bank exports into the fields Business Central expects. The data exchange definition is the piece that makes a nonstandard bank file usable; you configure it once per bank format, and thereafter every statement from that bank imports cleanly. This is the pragmatic path in markets where direct bank connections are limited, and it works reliably as long as the file format is consistent.

The second route is an automated bank feed, where Business Central connects to the bank through a service and pulls transactions without a manual download at all. In some markets this is delivered through built-in bank integration or through connectors and extensions from the AppSource marketplace that link to regional banks or aggregation services. When a feed is available and reliable it is the better experience, because there is no file to fetch and the data lands automatically, but availability varies by country and by bank, so it should not be assumed. In many regional deployments the honest reality is that structured file import via camt.053 or a mapped file format is the dependable option, and a live feed is a nice-to-have that depends on what your specific bank supports.

Whichever route you use, the payoff is the same. Once the statement lines are inside Business Central as structured data rather than a PDF you are reading off a second screen, the automatic matching can go to work, and the reconciliation collapses from an afternoon of manual comparison into a review of the handful of lines the system could not match on its own. The import is not the goal in itself; it is what makes the automatic matching possible, and the matching is where the time is actually saved.

8. Payment reconciliation journals and automatic matching

There is a second, closely related feature that often gets confused with bank account reconciliation, and understanding the distinction sharpens how you work: the payment reconciliation journal. Where bank account reconciliation is about proving your bank balance is correct, the payment reconciliation journal is about applying incoming and outgoing payments to the customer and vendor entries they settle, using the bank statement as the trigger. In practice these two jobs overlap, and the payment reconciliation journal handles both the application and the bank reconciliation in one flow for the payments it processes.

The workflow is elegant when it clicks. You import a bank statement into the payment reconciliation journal, and Business Central attempts to match each statement line to an open entry automatically. For an incoming payment, it tries to find the customer and the specific invoice being paid; for an outgoing payment, the vendor and the bill being settled. The matching logic looks at several signals: the amount, the document number if the customer quoted it, the bank account or name of the counterparty, and text on the statement line. When it finds a confident match it proposes to apply the payment to that invoice, so a single import can clear dozens of open receivables and payables in one reviewed pass.

The quality of that automatic matching is not fixed; it improves with how you and your customers behave. Business Central can learn and use text-to-account mapping rules, so that a recurring statement narrative, a particular bank charge description or a regular direct debit, is automatically routed to the correct account every time it appears. Each rule you set up removes a class of manual work permanently. And the single biggest lever on match rates is not inside the system at all: it is whether your customers put your invoice or document number on their payment reference. When they do, matching is nearly automatic; when they send a round-sum payment covering four invoices with no reference, someone has to unpick it by hand no matter how good the software is.

The honest caution: automatic matching is a proposal, not a posting. It is genuinely tempting, once the match rate is high, to trust the suggestions and post the journal without reviewing the lines the system was unsure about. Resist that. The matches the engine is confident about are almost always right; the ones it flagged as uncertain are exactly where a misapplied payment or a wrong customer will slip through and quietly corrupt your receivables aging. Review the uncertain lines every time. The automation earns its keep on the easy ninety percent so you can spend your attention on the hard ten, not so you can skip the review entirely.

9. Common reconciliation problems and how to resolve them

Reconciliation goes wrong in a small number of recurring ways, and recognising the pattern is most of the cure. Across implementations these are the problems I see over and over, with the resolution that actually works.

• A persistent small difference that will not clear. Almost always this is a bank charge, interest, or a fee the bank posted that you never recorded, or a rounding and currency difference on a foreign account. The fix is to stop hunting for it as an error and add it as a legitimate ledger entry. If the amount is a bank cost, post it; if it is an exchange difference on a foreign-currency account, let Business Central's currency handling account for it rather than forcing the number.
• Outstanding items that never clear. A payment you posted months ago still shows as outstanding because it was never actually presented, or it was a duplicate, or the original was voided at the bank. These stale outstanding items pollute every future reconciliation. Investigate any outstanding item older than a normal clearing cycle and either confirm it is genuinely in transit or reverse it. An outstanding list that only grows is a warning sign.
• Round-sum payments covering multiple invoices. A customer pays one lump sum against several invoices with no breakdown, and the automatic matching cannot allocate it. The resolution is manual application, splitting the receipt across the specific open invoices it settles. Prevent the recurrence by asking that customer to remit with invoice references, or agree a standing allocation rule if they always pay the oldest first.
• Duplicated bank statement lines. Re-importing a statement that overlaps a previously imported one creates duplicate lines and a reconciliation that will not balance by exactly the doubled amount. The fix is disciplined import boundaries: import each statement period exactly once, and if you must re-import, remove the prior lines first. A difference that is precisely double a known transaction is the fingerprint of this problem.
• Timing differences at period end. A payment posted on the last day of the month that clears the bank on the first of the next is not an error; it is a genuine outstanding item that resolves itself next period. The mistake is trying to force it to zero within the month. Leave it outstanding, and it clears naturally in the following reconciliation.
• Wrong currency or stale exchange rate on a foreign account. A foreign-currency reconciliation that is off by a small percentage usually means the exchange rate used to translate does not match the bank's rate on the day. Reconcile the foreign account in its own currency so the operational match is exact, and treat the reporting-currency translation as a separate, expected difference that the currency revaluation handles.

The thread running through all of these is that most reconciliation problems are not software problems; they are process and data problems that the software faithfully reflects. The difference between a team that reconciles in fifteen minutes and one that dreads it for a day is rarely the tooling. It is whether outstanding items are investigated promptly, whether statements are imported cleanly once, and whether customers are nudged toward payment references. Fix the process and Business Central makes the reconciliation almost boring, which is exactly what a reconciliation should be.

10. Controls, segregation of duties and month-end discipline

Cash is the asset most exposed to error and to fraud, so the treatment of cash flow and bank reconciliation is not only about accuracy, it is about control. Even in a small finance team, some separation of responsibilities around cash is worth building deliberately, because the reconciliation is one of the most important detective controls a business has.

The principle worth protecting is that the person who can move money should not be the only person who reconciles the account. If one individual can both create and release a payment and also perform and post the bank reconciliation with no independent review, the reconciliation loses much of its value as a control, because the same person could conceal an irregular payment by adjusting the reconciliation to match. In a larger team you separate these roles outright. In a small team where full separation is impractical, you compensate with an independent review: someone other than the preparer looks at the posted reconciliation, and someone senior reviews the bank statements independently of the person who processes payments. Business Central's permission sets and user role assignments are the mechanism for enforcing who can do what, and setting them thoughtfully around the cash functions is time well spent.

Around month-end, the discipline that keeps cash trustworthy comes down to a short, repeatable checklist rather than heroics. Reconcile every bank account for the period and drive each to a genuine zero difference, not an approximate one. Investigate and clear or carry forward every outstanding item, and challenge anything unusually old. Confirm that the cash flow forecast has been refreshed so the forward view reflects the newly reconciled starting position. Ensure bank charges, interest and any direct debits the bank applied have been captured in the ledger. And keep the reconciliation records, because a posted, evidenced reconciliation is exactly what an auditor will ask to see, and being able to produce a clean run of them turns the audit conversation about cash from an interrogation into a formality.

The controls insight: a reconciliation is only a control if it is independent and it is timely. A reconciliation performed a quarter late by the same person who releases the payments is theatre, not control. Performed monthly, driven to a real zero, and reviewed by a second pair of eyes, it is one of the cheapest and most powerful safeguards a business has over its most vulnerable asset. Treat it as a control first and a bookkeeping chore second.

Final thoughts

Cash flow forecasting and bank reconciliation look like two separate tasks, one a planning exercise and the other a bookkeeping routine, and treating them separately is exactly why so many finance teams do both of them badly. They are the forward and backward views of the same reality. The reconciliation establishes, beyond doubt, how much money you truly have right now; the forecast takes that verified starting point and projects it forward so you can see the squeezes and surpluses coming while there is still time to act. A forecast built on an unreconciled balance is guesswork with a chart, and a reconciliation with no forward view is a tidy record of a problem you could have seen coming.

Business Central gives you both in one system, drawing on the same live transactional data, which is its real advantage over the spreadsheet-and-bank-portal approach most businesses limp along with. The cash flow forecast pulls from your actual receivables, payables, budgets and planned capital movements and refreshes itself on a schedule. The bank reconciliation imports your statements, matches most of the work automatically, and proves your ledger against the bank. Neither feature is difficult to run once it is set up correctly. The difficulty, as always, is the discipline: short and readable cash flow accounts, realistic due dates, clean single imports, prompt investigation of outstanding items, and an independent eye on the reconciliation.

Get that discipline right and cash stops being the thing that keeps the owner awake and becomes just another number the team sees clearly and manages calmly. For the wider picture of how these treasury functions sit within the full finance module, the financial management pillar is the companion read, and for the complete tour of what the platform covers end to end, the Business Central features complete guide puts cash and treasury in the context of everything else the system does.

Related reading: Business Central financial management, Business Central features: the complete guide.