Bank Statement Lines

Controller 7 min read Updated July 2026

Each row of the bank's statement becomes a Bank Statement Line — the atomic unit of reconciliation. A line starts as plain imported data and ends its life matched: linked to the exact receipt, payment, journal line or deposit that explains it. This is the reference for what a line carries and the states it moves through.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials AI → the Bank Statements tab, open a statement, and its lines sit in the related list beneath it. You match and unmatch lines in the reconciliation workspace, not here.
Access you'll need. Editing lines and their match stamps requires the Accounting Admin v2 or Accounting Controller v2 permission set. The Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets can view lines but not change them.

What a line carries

Group	Fields
The bank's facts	Transaction Date · Description (the bank's wording) · Amount (signed: positive in, negative out — never zero) · Transaction Type (Deposit, Withdrawal, Check, Fee, Interest, Transfer, Other) · Reference · Check Number · Payee · Running Balance
The match stamps	Reconciled checkbox · Match Type (how it was matched: Auto / Manual / Rule-Based / Adjustment) · Matched By / Matched Date — the audit trail of who connected what, when
The connection	Exactly one source link when matched: Cash Receipt, Cash Disbursement, Journal Entry Line, or Bank Deposit — plus a link to the Bank Account Rule when a rule did the work
Extra context	Category (your own classification of the line) and, on rule-created and adjustment paths, whatever the description templates carried over

The sign carries the meaning. Amount is signed — positive is money in, negative is money out — and everything downstream trusts it: a positive line looks for receipts and deposits, a negative line for payments. A blank Transaction Type at import is even derived from it. Get signs right at import and the rest of the machinery just works.

One July statement, four finished lines

What the stamps look like when a month is done — Meridian's July lines, after reconciliation:

Line	Amount	Match Type	Source link
ACH-20260702-CORV	+$9,000.00	Auto	Cash Receipt — Corvus Consulting's rent payment
CC-INV-11406	−$2,200.00	Auto	Cash Disbursement — the CityClean payment
WIRE-ACC-0702	−$10,000.00	Auto	Cash Disbursement — the Apex Construction wire
MONTHLY ACCOUNT SERVICE FEE	−$45.00	Adjustment	Journal Entry Line — the fee journal created from the workspace

Read a finished statement this way and it becomes self-auditing: every movement of money names the exact document that explains it, who connected them, and when. The Match Type column even tells the story of how the month was closed — three lines the machine proved, one a human booked.

The integrity rules

Three guards keep every line honest, verbatim from the system:

"A statement line can match to only one source record." — one bank movement, one explanation. (A deposit covering several receipts matches a Bank Deposit — the grouping is the source.)
"A reconciled statement line must have exactly one source record linked." — no hand-waving a line to "done" without saying what it was.
"A statement line marked as not reconciled cannot have a source record linked." — and no ghost links on open lines.

Amount and date lock once a line is reconciled ("Cannot edit a reconciled statement line."), and a line matched into a completed reconciliation can't be deleted — unmatch first, deliberately.

Every guard, spelled out

The message	What it means / what to do
"Statement line amount cannot be zero."	A zero movement explains nothing and can match nothing — skip informational zero rows at import.
"Cannot edit a reconciled statement line."	Amount and date are evidence under a match. To correct a genuinely wrong line: unmatch it first, edit, rematch.
"A statement line can match to only one source record. At most one of Cash Receipt, Cash Disbursement, Journal Entry Line, or Bank Deposit can be populated."	One movement, one explanation. Several receipts behind one line means a Bank Deposit is the single source.
"A reconciled statement line must have exactly one source record linked (Cash Receipt, Cash Disbursement, Journal Entry Line, or Bank Deposit)."	No line reaches "reconciled" without naming what explains it — work through the workspace and this is automatic.
"A statement line marked as not reconciled cannot have a source record linked. Clear the source lookup or mark the line as reconciled."	The mirror rule: open lines carry no ghost links. Unmatching clears both together.
"Cannot delete this Bank Statement Line because it is reconciled to a posted transaction. Unmatch it or remove the reconciliation first."	Deleting matched evidence would orphan a reconciled document — sever the link deliberately before the line can go.

These guards hold for everyone and everything. They're enforced on the record itself — not just in the workspace — so an import, a data load, or an integration meets exactly the same walls you do. That's what makes a reconciled statement trustworthy evidence rather than a convention.

Common mistakes to avoid

Mistake	Why it hurts	Do this instead
Editing a line's amount so a near-miss will match	The statement stops being the bank's testimony — and the real cents difference (usually a fee) goes unbooked	Never bend the bank's numbers: match nothing, book the difference as an adjustment, or fix the document if that's what's wrong
Ticking the Reconciled box by hand to tidy a stubborn line	Refused without a source link — and rightly: "reconciled" without an explanation is exactly the hole audits exist to find	Match it to its document, or book it via adjustment; the stamp then writes itself
Deleting and re-importing lines to fix small typos	Matched lines refuse deletion, and re-imports risk duplicates on the still-open ones	Edit unmatched lines in place (they're editable until reconciled)
Ignoring the Type column on fees and interest	Every reader after you must rediscover that these lines need booking, not matching	Set Fee / Interest at import — it's documentation the whole reconciliation benefits from

Reference and check number are the matching keys. Auto-match's best pass pairs lines to documents by exact reference or check number. You control both ends: put real bank references on your receipts and payments, and keep the bank's reference column in your imports — every future month matches itself a little more.

Where to go next

Manual Matching & Unmatching — working the lines by hand.
AI Auto-Matching — letting the engine do it.
Importing Bank Statements — where lines come from.

Frequently asked questions

The bank's characterization — Fee and Interest in particular are worth setting on import, because they signal "this needs an adjustment or rule, not a document match" to everyone who reads the reconciliation later.

Matching is one-to-one by design. The real-world many-to-one case — several receipts in one bank deposit — is handled from the other side: group them in a Bank Deposit and match the deposit to the single line.

"Statement line amount cannot be zero." — a zero movement explains nothing and can never match anything. Banks occasionally print informational zero rows; skip them at import.

The audit answer to "who says these belong together, and when did they say it?" Every match stamps them; every unmatch clears them. Combined with Match Type (Auto, Manual, Rule-Based, AI-Suggested, Adjustment), a finished statement documents not just what explained each line but how the connection was made.

Amount and date — no ("Cannot edit a reconciled statement line."). They're what the match asserted, so changing them means unmatching first, deliberately, then editing and rematching. If the reconciliation is already completed, reopen it before any of that.

Was this article helpful?