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.
- Lease Finance Operations
- Features
- Evidence and decisions
Evidence and decisions
Keep the source document, reviewer decision and action result traceable.
OverviewLease Invoices Past Due×
Lease Finance Operations · Evidence and decisions
New
Lease Invoices Past Due
Lease invoices
| Invoice number | Lessor | Due date | Total amount | Amount paid | Balance due | |
|---|---|---|---|---|---|---|
| LI-19120 | LSS-50135 | 08 Oct | 220 | 70 | BD-326 | |
| LI-88955 | LSS-59434 | 12 Oct | 580 | 730 | BD-838 | |
| LI-23805 | LSS-72487 | 11 Oct | 670 | 680 | BD-964 | |
| LI-93136 | LSS-42182 | 09 Oct | 930 | 620 | BD-570 | |
| LI-19620 | LSS-46900 | 12 Oct | 560 | 590 | BD-350 |
6 of 6 records
BD-326Lease invoices · LI-19120
DraftLessorLSS-50135
Due date08 Oct
Total amount220
Amount paid70
Days past dueDPD-192
What you can do
Follow the evidence to the outcome
A lease invoice can have the original invoice image, an approval email and later correspondence attached to its record. Review decisions hold the subject, reviewer, outcome, decision time and any conditions. Operation receipts hold the action type, reference, actor, occurrence date and result. Together these records let a Controller reconstruct what someone reviewed and what the native action did.
An approval decision and an operation receipt answer different questions. The first says who approved, rejected or returned a subject. The second says whether a configured operation such as lease invoice approval, payment release or billing send ran and what result it recorded. Finance can compare both with the invoice or payment’s current state when an exception is investigated.
How the work is organized
- Attach. The preparer places the supporting file on the relevant business record.
- Decide. The reviewer records an outcome and any conditions on the decision trail.
- Verify. The operator checks the action receipt and follows a failed or partial result.
What to agree during setup
Define a consistent attachment type and naming rule for invoices, remittance advice, bank statements and approval correspondence. Decide what information belongs in decision conditions and what belongs in a note. Set a retention practice for source documents and require a reviewer to identify the subject reference clearly. A file on the wrong parent record can be harder to find than a missing file.
Agree who monitors failed, partial or skipped operation results. The receipt may contain a document link and details, but the team still needs an owner to resolve the underlying transaction. Ensure the finance team member list accurately reflects active reviewers and their organization. Decide how an External Auditor will get read access without being able to change the operational record.
Check the handoff on an actual case
AP prepares a lessor invoice with its source PDF attached. The Controller reviews it and uses the invoice approval action. Open the review decision and check the reviewer, subject, approval outcome and conditions. Open the operation receipt and check the action type, reference, actor and result. The invoice should now show the approved state. A later question about the amount can be answered from the source, decision and current record together.
Repeat with a scheduled payment. Treasury invokes release and then checks the payment release receipt. If the result is failed or partial, keep the receipt and investigate before treating the payment as released in the bank. For partner billing, the send receipt gives the same action-level trace. These cases make the evidence trail useful during close review and later audit.
What your team sees
- Lease Invoices Pending Approval — Charges that need a review decision and supporting evidence.
- Lease Payments Awaiting Reconciliation — Released movements whose bank evidence needs a match.
- GL Entry Review — Journal context for close evidence review.
Follow the work through
Follow invoice review and payment or payment reconciliation.
What it keeps track of
Data model- Record attachments
- Parent-agnostic evidence files attached to any business record in this app.
- Review decisions
- Approval trail: who approved, rejected or returned a bill, invoice, payment or journal entry, when and under what conditions.
- Operation receipts
- Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
- Team members
- Finance staff who prepare, review and approve finance operations, with their role and approval limit.
- Lease invoices
- Lessor lease invoices: amount due, due date, approval status and the balance still payable.
- Lease billings
- Lease billings issued under a lease arrangement, with amounts, payment received status and balance outstanding.
- Lease payments
- Lease payment movements in and out, matched to a lease invoice or billing and reconciled to the bank.
- Journal entries
- General ledger header balancing debits and credits for a period.
Who uses it
Permissions- AP Specialist
- And AR Specialist attach source documents.
- Controller
- Makes invoice decisions and reviews action outcomes.
- Treasury Analyst
- Checks release evidence.
- External Auditor
- Reads the retained trail.
Set up Lease Finance Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.