These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Royalty Accounting
- Features
- Cash and reconciliation
Cash and reconciliation
Apply verified payment events within both cash and document balances.
OverviewVerified Cash Receipts×
Royalty Accounting · Cash and reconciliation
New
Verified Cash Receipts
Cash receipts
| Name | Provider event ID | Amount USD | Received at | Verified | Partner | |
|---|---|---|---|---|---|---|
| Receipt 197 | PEI-166 | 840 | 11 Oct | Yes | BP-6909 | |
| Receipt 538 | PEI-195 | 110 | 09 Oct | Yes | BP-7727 | |
| Receipt 710 | PEI-805 | 450 | 12 Oct | Yes | BP-8394 | |
| Receipt 321 | PEI-264 | 290 | 05 Oct | Yes | BP-8115 | |
| Receipt 518 | PEI-564 | 210 | 13 Oct | Yes | BP-3184 |
6 of 6 records
Receipt 197Cash receipts · CR-77978
YesProvider event IDPEI-166
Amount USD840
Received at11 Oct
PartnerBP-6909
What you can do
Match cash to posted value
Cash work begins with a receipt from a provider event. The Cash Reconciler confirms its unique event identity, amount, time and partner before treating it as verified money. An application then links that receipt to a posted accounting document. The applied amount must remain positive and stay within both the unused receipt and the outstanding document amount.
How the work is organized
- Verify receipt identity. Keep the provider event reference with the receipt so a repeated delivery maps to the same cash.
- Apply against posted value. Select the intended document and limit the application to the remaining amount on both sides.
- Reconcile effects. Read the persisted applications and operation receipt before considering the action complete.
A receipt can be split across eligible documents when the amounts warrant it. Each application has its own date and amount, and a reversed application keeps its reversal time. The Cash Reconciler can explain how much of a receipt remains after valid applications. The partner on the receipt and counterparty on the document give a direct identity check.
What to agree during setup
Name the provider feed and its event identity rule. Decide who may mark a receipt verified, who may apply it, and who resolves a disputed match. Reconcile provider data against the partner list before the first live run. Agree whether a corrected provider event supersedes an earlier event or arrives with a new identity, since this affects duplicate handling.
Define how the team handles partial payments. A partial receipt should reduce the outstanding amount only by its actual application. A new delivery of the same provider event must not create a second receipt or a second reduction. Keep the operation key and receipt result available when the payment provider times out or sends a delayed acknowledgement.
Check the handoff on an actual case
Take a posted royalty invoice and a verified receipt for the same partner. Apply part of the receipt and inspect the saved application. Compare the applied amount with the original receipt and document gross amount. Apply the remaining eligible portion and recalculate from the persisted application rows. The source receipt and document should remain explainable from their individual records.
Repeat the provider event and attempt a second application beyond the receipt’s unused amount. Both attempts should fail safely or return the established result. Test a receipt marked No in verification; it should remain in the unverified queue. If an application is reversed, retain the original and reversal date so the ledger review can distinguish the changed balance from a missing transaction.
What your team sees
- Verified Cash Receipts — Confirmed provider events ready for matching and balance review.
- Unverified Cash Receipts — Payment events needing identity or amount verification.
- Posted Documents — Eligible accounting documents whose remaining amounts can be checked.
Follow the work through
What it keeps track of
Data model- Cash receipts
- Verified cash receipts imported from provider payment events.
- Cash applications
- Applications of verified receipts against posted accounting documents.
- Accounting documents
- Invoice, credit, expense and adjustment documents that carry royalty operations.
- Business partners
- Licensees and counterparties that royalty documents are issued to.
- Operation receipts
- Stable operation keys and result states for every guarded action.
Who uses it
Permissions- Cash Reconciler
- Verifies receipts and applications.
- Ledger Controller
- Compares cash effects with posted books.
- Independent Reviewer
- Investigates unresolved operation results.
- Finance Viewer
- Reads permitted outcomes.
Set up Royalty Accounting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.