> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Days Since Last Bank Reconciliation, Sage

> Days Since Last Bank Reconciliation counts how long it has been since you last tied your Sage cash book to the actual bank statement, the cleanest single signal of whether your reported cash position can still be trusted. How to read it, why it matters, and how to act on it.

**Card class:** [Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type)

> Days since the last completed bank reconciliation. The UK Bacs cycle assumes weekly recon; gaps over 7 days compound and inflate close-cycle workload.

## At a glance

> The number of days since your last completed bank reconciliation in Sage, the point at which the cash book was last tied line-for-line to the actual bank statement. This is the cleanest single measure of whether your reported cash position can still be trusted. The longer the gap, the more unmatched transactions pile up, the more likely an error or a missed payment hides in the float, and the heavier the eventual reconciliation becomes. UK businesses on a weekly Bacs cycle should reconcile at least weekly, so anything past 7 days is a flag and anything past a full month is a control problem. The card reads the Cash Management module's reconciliation status per bank account, dimension-tagged in Sage Intacct so finance can see which specific account has gone stale and who owns it.

|                              |                                                                                                                                                                                                                        |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**           | The elapsed days between today and the statement date of the most recently completed bank reconciliation for the account, read from the Cash Management module's reconciliation records.                               |
| **Per account**              | Tracked per bank account. A business with current, deposit, and foreign-currency accounts gets a reading for each; the card surfaces the worst (most stale) by default and lets finance drill to the specific account. |
| **Completed vs in-progress** | Only a completed (posted) reconciliation resets the clock. A reconciliation started but not finalised does not count, because an unfinished recon does not give you a trustworthy cash position.                       |
| **Bank feeds**               | Where Intacct bank feeds or imported statements are connected, the card can distinguish "statement available but not reconciled" from "no statement yet," which separates a process lag from a banking lag.            |
| **Currency**                 | Each account is read in its own currency; the days count is currency-independent. Multi-Entity Console surfaces the staleness per entity.                                                                              |
| **Entity scope**             | Card respects the dashboard entity filter.                                                                                                                                                                             |
| **Dimensional cut**          | The reconciliation record carries the bank account and entity through, so finance can pivot by Entity or Location to see which site's cash book is behind.                                                             |
| **Time window**              | `RT`                                                                                                                                                                                                                   |
| **Alert trigger**            | `>7d` aligned to the Bacs cycle, sentiment `bank_recon`. Configurable per workspace. Monthly-recon businesses may set 35 days; high-volume operations may want 3.                                                      |
| **Roles**                    | owner, finance                                                                                                                                                                                                         |

## Calculation

Calculated automatically from your Sage data. The card subtracts the statement date of the most recent completed reconciliation from today, per bank account, and surfaces the longest gap. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

A UK B2B stationery brand on Sage Intacct, single entity, GBP base currency, roughly 7M GBP annual revenue, settling supplier Bills via weekly Bacs runs and collecting customer payments by Bacs and card through a BigCommerce B2B portal. Three bank accounts: a main current account, a deposit account, and a EUR account for EU suppliers. Snapshot 14 Apr 26. The card surfaces the worst account.

| Bank account                                        | Last completed recon (statement date) | Days since |
| --------------------------------------------------- | ------------------------------------- | ---------- |
| Main current account                                | 09 Apr 26                             | 5          |
| EUR supplier account                                | 21 Mar 26                             | 24         |
| Deposit account                                     | 31 Jan 26                             | 73         |
| **Days Since Last Bank Reconciliation (this card)** | **31 Jan 26**                         | **73**     |

Five things to notice:

1. **73 days on the deposit account is the headline, and it is past the 7-day alert by an order of magnitude.** The card surfaces the worst account because a single stale account is enough to mean the consolidated cash position is unverified. The deposit account moves rarely, which is exactly why it gets forgotten, and exactly why a fraud or a bank error there can sit undetected for months. The fix is mechanical (reconcile it) but the value of the card is that it made an invisible gap visible. Nobody chooses to leave an account unreconciled for 73 days; they simply never see the counter.
2. **The main current account at 5 days is healthy and inside the Bacs cycle.** This is the account that matters most operationally because it is where the weekly Bacs runs settle and where customer receipts land. At 5 days it is being reconciled roughly weekly, which is the correct cadence for a Bacs-cycle business. The card confirms the discipline is holding on the account that needs it most, while flagging the neglected ones. That contrast is the useful read: not "are we reconciling" but "are we reconciling everything."
3. **The EUR account at 24 days is the quiet risk because of FX.** An unreconciled foreign-currency account does not just risk missed transactions, it risks an FX revaluation that has drifted from reality. EU supplier payments settle here, and 24 days of unreconciled activity means the GBP value of the EUR balance on the books may not match what the bank actually holds once revaluation is applied. Pair this card with [FX Currency Exposure](/nerve-centre/kpi-cards/sage/fx-currency-exposure) to see whether a stale foreign account is also carrying material currency risk.
4. **A long gap directly inflates the period-close workload.** Every day unreconciled is more unmatched transactions to clear, and clearing them at month-end under time pressure is how errors get rushed through. Read this card next to [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/sage/period-close-on-time-rate-12mo): stale reconciliations are one of the most common reasons a close runs late, because the cash position cannot be signed off until the bank ties out. Reconciling weekly is not bureaucracy, it is what keeps the close fast.
5. **The cross-signal to watch is a stale recon alongside a confident-looking cash number.** A business can show a healthy AR Balance and a comfortable cash figure while the bank has not been reconciled in 73 days, which means that comfortable cash figure is unverified. Any AP-stretch or investment decision made on an unreconciled cash position is made partly blind. This is why the card is a Hero: it gates the trustworthiness of every cash-based decision. Reconcile first, then decide.

## Sibling cards merchants should reference together

| Card                                                                                            | Why pair it with Days Since Last Bank Reconciliation                                               |
| ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Cash Collected](/nerve-centre/kpi-cards/sage/cash-collected)                                   | Reconciliation is what confirms the cash you think you collected actually landed.                  |
| [Cash Application Rate](/nerve-centre/kpi-cards/sage/cash-application-rate)                     | Unapplied receipts often surface during reconciliation; the two cards diagnose each other.         |
| [AP Aging 60+ Days](/nerve-centre/kpi-cards/sage/ap-aging-60-days)                              | An unreconciled bank means you may not know your true cash before deciding which suppliers to pay. |
| [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/sage/period-close-on-time-rate-12mo) | Stale reconciliations are a leading cause of a late close.                                         |
| [Period Close Status](/nerve-centre/kpi-cards/sage/period-close-status)                         | The close cannot finalise until cash ties out; this card is an upstream gate.                      |
| [FX Currency Exposure](/nerve-centre/kpi-cards/sage/fx-currency-exposure)                       | A stale foreign-currency account compounds reconciliation risk with FX risk.                       |
| [Sage Health Score](/nerve-centre/kpi-cards/sage/sage-health-score)                             | Reconciliation freshness is a control-hygiene input to the composite.                              |

## Reconciling against Sage

**Where to look in Sage:**

The native Sage Intacct views to run side by side with this card:

> **Cash Management → Reconcile** (the bank reconciliation workspace showing last-reconciled date and outstanding items per account)
> **Cash Management → Bank Accounts** (the list of accounts with their reconciliation status and most recent statement date)
> **Reports → Cash Management → Bank Reconciliation Report** (the formal recon output, including the reconciled balance and the uncleared float)
> **Reports → Cash Management → Outstanding Checks and Deposits** (the uncleared items that accumulate while an account goes unreconciled)
> **Interactive Custom Report (ICR)** built on the Cash Management data source listing each bank account's last completed reconciliation date and computing the days elapsed

The reconciliation date on this card is the statement date of the last completed (posted) reconciliation, which is what the Cash Management → Reconcile screen shows as the last-reconciled point. A reconciliation that has been started but not finalised does not reset the date in either place. For Multi-Entity Console accounts, check each entity's bank accounts, because a consolidated view can hide a single neglected account inside an otherwise tidy group.

Common reconciliation pitfalls:

* **Started but not posted.** A part-done reconciliation sitting in progress does not reset the clock. Finalise it, or the card correctly continues to count from the last completed one.
* **Statement date vs reconciliation date.** The card uses the statement-period end date, not the date someone clicked reconcile. If you reconcile a March statement in mid-April, the clock resets to the statement end, not to today.
* **Auto-matched bank feeds.** Where bank feeds auto-match transactions, an account can look "matched" without a formal reconciliation being completed. Matching is not reconciling; only a completed reconciliation resets this card.

**Why our number may legitimately differ from a Sage Intacct Cash Management view:**

| Reason                            | Direction               | Why                                                                                                                   |
| --------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Statement date vs action date** | Either                  | Card counts from the statement-period end; a staff member may have reconciled it on a later calendar date.            |
| **In-progress reconciliations**   | Card may read higher    | A part-done recon does not reset the clock until it is posted.                                                        |
| **Auto-match vs reconcile**       | Card may read higher    | Bank-feed auto-matching looks like progress but is not a completed reconciliation.                                    |
| **Per-account vs consolidated**   | Either                  | Card surfaces the worst account; a consolidated dashboard tile may show an average or only the main account.          |
| **Dormant accounts**              | Card may read very high | A rarely-used deposit or escrow account can show a huge gap that is low-risk; finance may choose to exclude it.       |
| **New accounts**                  | Card may read undefined | An account with no completed reconciliation yet has no baseline date; the card flags it as never reconciled.          |
| **Multi-entity timing**           | Either                  | Entities on different close calendars reconcile on different cadences; the consolidated worst-case can look alarming. |

**Cross-connector reconciliation:**

| Card                                                                            | Expected relationship | What the comparison reveals                                                                                                                          |
| ------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Cash Collected](/nerve-centre/kpi-cards/sage/cash-collected)                   | Verification          | Collections you recorded should match deposits the bank shows. Reconciliation is where any discrepancy surfaces.                                     |
| [Sage Cash Applied Today](/nerve-centre/kpi-cards/sage/sage-cash-applied-today) | Daily loop            | A high daily application rate with a stale reconciliation means cash is being applied to Invoices faster than it is being verified against the bank. |
| [AP Aging 60+ Days](/nerve-centre/kpi-cards/sage/ap-aging-60-days)              | Decision gate         | Deciding which late suppliers to pay on an unreconciled cash position is a blind decision. Reconcile first.                                          |
| [Period Close Status](/nerve-centre/kpi-cards/sage/period-close-status)         | Dependency            | The close depends on cash tying out. A stale reconciliation blocks a clean close.                                                                    |
| [Sage Health Score](/nerve-centre/kpi-cards/sage/sage-health-score)             | Component             | Reconciliation freshness feeds the control-hygiene component of the composite.                                                                       |

The cross-channel point is that no commerce platform can tell you whether your bank is reconciled, because none of them touch your bank statement. Sage Intacct's Cash Management module is the only system that ties recorded cash to actual bank cash, and this card turns that buried status into a live counter. The dimensional carry-through means a stale account points at the specific entity and owner responsible, so the gap closes with a named action rather than a general reminder.

## Known limitations / merchant FAQs

**Why is 7 days the default alert when many businesses reconcile monthly?**
Because the default assumes a UK Bacs cycle, where payment and collection runs happen weekly and weekly reconciliation keeps the float small and errors catchable. A business that genuinely runs a monthly recon discipline can move the threshold to 35 days. The point of the default is not to force weekly reconciliation on everyone, it is to surface accounts drifting past the cadence the business intends. Set the threshold to your actual policy and let the card flag the exceptions.

**Does auto-matching from a bank feed count as reconciliation?**
No. Auto-matching pairs transactions but does not produce a completed, posted reconciliation that ties the cash book to the statement and signs off the float. The card only resets on a completed reconciliation. This is deliberate, because an account can be fully auto-matched and still be wrong if a transaction is missing from one side entirely. Matching is helpful; reconciling is the control.

**What if an account is dormant?**
A rarely-used deposit, escrow, or savings account can show a large gap that is genuinely low-risk. Finance can either exclude dormant accounts from the card or accept the high reading as informational. The safer practice is to still reconcile dormant accounts periodically, because a forgotten account is exactly where an error or a fraudulent transaction can sit undetected longest.

**Why does the clock reset to the statement date, not the day I reconciled?**
Because the meaningful measure is how current your verified cash position is, which depends on how recent the statement you reconciled was, not on when you happened to do the work. Reconciling a March statement in mid-April resets the clock to the end of March, correctly showing that your cash is verified only as far as March. This keeps the card honest about coverage rather than activity.

**Sage Intacct vs Sage 50 / 100 / 200 / X3?**
This connector targets Sage Intacct's Cash Management module. Every Sage product has a bank reconciliation function, but the data structure, status flags, and API differ. Sage 50 and 200 are UK SMB products with their own reconciliation screens; Sage X3 is a different mid-market ERP. The days-since concept ports directly; the field map and connector do not. If you run one of those, reach out about connector availability.

**Does a stale reconciliation actually cause problems, or is it just tidiness?**
It causes real problems. An unreconciled account means your reported cash is unverified, so any cash-based decision is partly blind. It means errors, duplicate payments, and missing receipts accumulate undetected. It means the period close runs slower because cash cannot be signed off. And on a foreign-currency account it means FX revaluation may have drifted. Reconciliation is a control, not housekeeping; the days count is a control-health gauge.

**How does this relate to the period close?**
Closely. A clean, on-time close depends on cash tying out, and cash cannot tie out until the bank is reconciled. A stale reconciliation is one of the most common reasons a close slips. Read this card as an upstream gate to [Period Close Status](/nerve-centre/kpi-cards/sage/period-close-status): keep reconciliations current through the period and the close is far less likely to run late.

**Multi-entity: does the card show one number or many?**
It tracks every bank account across the scoped entities and surfaces the worst (most stale) by default, because a single neglected account is enough to mean the consolidated cash position is unverified. Drill in to see the per-account and per-entity breakdown. Entities on different close calendars will reconcile on different cadences, so read the per-entity view before reacting to a consolidated worst-case.

**How fresh is the reconciliation status itself?**
The card refreshes on the standard cadence, typically within 5 to 15 minutes of a reconciliation being posted in Intacct. Finalise a reconciliation and the counter resets on the next refresh. If you have just completed one and the card still shows the old gap, give it a refresh cycle or force a manual refresh from the dashboard.

***

### Tracked live in Vortex IQ Nerve Centre

*Days Since Last Bank Reconciliation* is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.