REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Accounts Receivable / Cash Receipts / Applying Receipts to Invoices

Applying Receipts to Invoices

A posted Cash Receipt says "$9,000 arrived from Corvus." An application says "…and it pays the June rent invoice." Until that second step happens, the invoice still shows a balance due and the receipt still shows Unapplied Cash — this article is about connecting the two, one screen, no accounting knowledge required.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials AI → the Cash Receipts tab, open the posted receipt, and click Apply Cash Receipt.
Access you'll need. Applying receipts to invoices requires the Accounts Receivable v2 permission set (AR clerks & managers) or Accounting Admin v2 (system administrators). The Accounting Controller v2, Accounts Payable v2, and Read Only v2 sets can view receipts and their applications but not apply them.

Open the Apply screen

On any posted Cash Receipt, click Apply Cash Receipt. The screen shows the receipt's vital signs across the top — Total, Applied so far, and Unapplied — and below them, every posted invoice of this customer (in this entity) that still has a balance due and whose invoice date has already arrived:

The Apply Cash Receipt screen for MCR001024 in REDA Financials AI. The header strip shows Cash Receipt MCR001024, Customer Corvus Consulting LLP, Entity Meridian Properties US, Type Receipt, Total $9,000.00, Applied $0.00 and Unapplied $9,000.00. The Apply to Invoices section shows a required Applied Date of 02-Jul-2026, an Enforce Dimension Match toggle, Clear All and Auto Fill buttons, and one open invoice row: MSI001007 dated 01 Jun 2026, due 01 Jul 2026 shown in red, total $9,000.00, balance due $9,000.00, with an Apply Amount box reading 0.00. The footer reads Applying $0.00 of $9,000.00, Remaining $9,000.00.
Corvus has exactly one open invoice — June rent, and its due date shows in red because it's overdue. The Applied Date defaults to today and determines which accounting period the application lands in.

Fill the amounts — by hand or by button

You have three ways to say how much of the receipt goes where:

  • Type into Apply Amount on each invoice row — full control, ideal for partial payments and disputes.
  • Tick the row's checkbox — fills that invoice's full open balance (or whatever remains of the receipt).
  • Auto Fill — spreads the whole receipt across the open invoices for you; Clear All resets to zero and you start over.

The progress bar keeps score: Applying $X of $Y — Remaining $Z. You can never apply more than the receipt holds or more than an invoice is owed; the guards are hard stops, not warnings.

The same Apply Cash Receipt screen after clicking Auto Fill: invoice MSI001007's checkbox is ticked and its Apply Amount box reads 9,000.00. The progress bar is full, the footer reads Applying $9,000.00 of $9,000.00 and Remaining $0.00, and the Apply Receipt button in the header is active.
After Auto Fill: the full $9,000 is allocated to the June invoice and Remaining is $0.00. Nothing has happened yet — the allocations are only committed when you click Apply Receipt.

Commit it

Click Apply Receipt. Each allocation becomes an application record — visible immediately in the Existing Applications list, on the receipt's Applications tab, and on the invoice's Applications tab:

The Apply Cash Receipt screen for MCR001024 after applying: the header now shows Applied $9,000.00 and Unapplied $0.00. An Existing Applications list shows application CRA-06083 to invoice MSI001007 dated 02 Jul 2026 in period 2026-07, invoice total $9,000.00, invoice balance $0.00, applied amount $9,000.00, with a delete icon beside it. Below, the Apply to Invoices section shows No Outstanding Invoices — there are no posted invoices with an outstanding balance for this customer and entity.
Done: application CRA-06083 settled the invoice (balance $0.00), the receipt is fully applied, and Corvus has No Outstanding Invoices left. The trash icon beside the application is the undo — see below.

In the books, each application moves the customer's money from the deposits holding account onto their receivable:

AccountDebitCredit
Customer Deposits and Prepayments Received$9,000.00
Accounts Receivable — Trade$9,000.00

(Organizations that balance their ledger by cost center will see an additional pair of Dimension Clearing lines keeping each dimension's receivable in balance — automatic, and requiring only that the entity has a Dimension Clearing account configured.)

The matching rules — with the exact messages

The Apply screen only offers what the rules allow, so you rarely meet these — but they explain a missing invoice, and they guard API and import paths identically:

The messageWhat it means
"Cash Receipt must be posted before applications can be created."Drafts hold no money yet — post first.
"The Sales Invoice must be Posted before a receipt can be applied to it."Draft invoices have no balance to settle.
"Cash Receipt and Sales Invoice must have the same Customer."Corvus's money can never pay a Brightline bill.
"The Cash Receipt and Sales Invoice must belong to the same Entity."The standard screen is same-entity; group settlement is its own feature — Cross-Entity AR Settlement.
"Cash Receipt and Sales Invoice must be on the same Ledger. Receipt Ledger and Invoice Ledger do not match."Both documents must live in the same set of books.
"Currency mismatch: both documents must use the same currency…"Dollars settle dollar invoices; route foreign collections through a matching-currency account.
"Applied Amount must be greater than zero."Zero applications explain nothing.
"Applied Amount exceeds the Cash Receipt unapplied balance."You can't spend more of the receipt than remains.
"Applied Amount exceeds the Sales Invoice outstanding balance."An invoice can't be over-settled.
"An Accounting Period is required for the Cash Receipt application."Derived from the Applied Date automatically — the date must land in an existing period.
"Application Date {0} is before the invoice date {1}. A receipt cannot settle an invoice before the invoice exists…"You can't relieve a receivable before the invoice that creates it — the books would show a negative receivable on every date in between. A future-dated invoice won't appear in the list at all; hold the money as an unapplied deposit and apply it on or after the invoice date.
"Application Date {0} is before the cash receipt date {1}. An application cannot be dated before the receipt it draws from…"The settlement can't predate the money it moves. Use an Applied Date on or after the receipt date.
"Application Date {0} falls on or before the AR book closure date ({1})."Closed books accept no new settlements — use a current open date.
"Cash Receipt Applications cannot be modified. Remove and re-create instead."Applications are insert-and-delete only — the audit trail stays simple.
"Cannot remove application dated {0} — the AR books are closed through {1}."Un-applying is also a books event; closed periods protect both directions.

Common mistakes to avoid

MistakeWhy it hurtsDo this instead
Forcing a near-match ("only 40 cents off")An application asserts same money; the 40 cents is usually a bank fee that now hides inside a wrong matchApply nothing; book the difference via a reconciliation adjustment or correct the document
Applying on-account money without customer instructionThe customer meant it for a disputed invoice — now their statement starts an argumentLeave it as Unapplied Cash until the instruction arrives (that's what the field is for)
Backdating the Applied Date casuallyThe settlement lands in a prior period's books and distorts closed-period AR — and it can never sit before the invoice or the receipt itself, or the receivable goes negative on the dates in betweenDefault (today); backdate only to an earlier open period, and never before the invoice date or the receipt date
Deleting and re-creating applications to "edit" amounts repeatedlyEach churn writes and removes ledger entries — noisy audit trailPlan the allocation on the staging screen (Clear All / Auto Fill) before Apply Receipt commits it
Skipping the receipt and marking invoices paid via journalNo application trail, no unapplied tracking, aging liesMoney always enters as a receipt; applications settle invoices

Un-applying

Applied to the wrong invoice? Click the trash icon beside the application in the Existing Applications list (or delete it from the Applications related list). The invoice's balance due comes back, the receipt's Unapplied Cash comes back, and every accounting entry the application created is removed. Applications can't be edited — remove and re-create is the rule, which keeps the audit trail simple. Two protections: applications on a voided receipt are locked, and removals in closed periods are refused.

Partial payments are normal. Meridian's tenant Brightline once paid $7,500 against a $13,500 invoice. The application was simply $7,500 — the invoice stayed open for the remaining $6,000 and showed in aging until the rest arrived. Apply what was paid, never force a match.

Where to go next

  1. Auto-Apply Cash Receipts — the same matching, automated oldest-first.
  2. Customer Account Ledger — see the running result of invoices and applications.
  3. Applying Credit Memos — settling invoices with credits instead of cash.
  4. Voiding & Refunding Receipts — when the receipt itself is wrong.

Frequently asked questions

Check the matching rules above in order: is the invoice posted, this customer's, this entity's, the same currency, and does it still have a balance due? The most common answer is that it's already paid — or still in Draft. One more: an invoice dated in the future is deliberately hidden until its invoice date arrives — until then its receivable doesn't exist yet, so there is nothing to settle. Hold the receipt as unapplied cash and apply it on or after that date.

Yes — enter amounts on as many rows as you need; each row becomes its own application record. That's the normal way to record a tenant's single transfer covering several months.

The accounting date of the application — which period the settlement lands in (the period is derived automatically from it). It defaults to today; backdate it only when the settlement genuinely belongs to an earlier open period, and never earlier than the invoice date or the receipt date — the settlement can't exist before the documents it connects.

For organizations that track receivables by dimension (cost center): switched on, the receipt only settles invoice balances in its own dimension. Leave it off ("All invoices") unless your controller has told you otherwise.

Currencies: never — both documents must match. Entities: not from this screen; when both entities have opted into cross-entity settlement, your accounting team can create the application deliberately — the workflow and the intercompany bookkeeping are covered in Cross-Entity AR Settlement.

Three places, always consistent: the receipt's Applications tab, the invoice's Applications tab, and the Apply screen's Existing Applications list. Each application names its amount, date and accounting period; the ledger entries it created sit on the Accounting Transactions lists.

Two hard stops protect the books: "Applied Amount exceeds the Cash Receipt unapplied balance." and "Applied Amount exceeds the Sales Invoice outstanding balance." Lower the amount to what's actually available on both sides.

Was this article helpful?