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
- Counterparties and entities
Counterparties and entities
Keep lessors, billing partners and legal entities consistent across transactions.
OverviewLease Invoices Settled×
Lease Finance Operations · Counterparties and entities
New
Lease Invoices Settled
Lease invoices
| Invoice number | Lessor | Total amount | Amount paid | Balance due | Status | |
|---|---|---|---|---|---|---|
| LI-42660 | LSS-69601 | 210 | 740 | BD-316 | Paid | |
| LI-16547 | LSS-77944 | 200 | 570 | BD-665 | Paid | |
| LI-63987 | LSS-73453 | 880 | 450 | BD-964 | Paid | |
| LI-42209 | LSS-30456 | 890 | 680 | BD-504 | Paid | |
| LI-93268 | LSS-16355 | 220 | 930 | BD-931 | Paid |
6 of 6 records
BD-316Lease invoices · LI-42660
PaidLessorLSS-69601
Total amount210
Amount paid740
What you can do
Establish the parties before the transaction
A lessor record gives AP a stable name, contact and remittance city for the party sending a lease invoice. A business partner record gives AR the billing contact, payment terms and credit context for the party receiving a billing. Organizations identify the legal entity whose books hold the document. When staff select these records on an invoice or billing, later review can follow the transaction to the correct party and entity.
The lessor and partner masters each have their own status. An inactive lessor or a partner on credit hold needs attention before a new transaction is advanced. Team members also link to an organization, so their finance role and approval limit can be reviewed in the right context. The records keep these distinctions visible when a finance team handles several entities.
How the work is organized
- Maintain. Admin updates legal entities, contacts, payment terms and statuses.
- Select. AP and AR choose the correct counterparty and organization when preparing a document.
- Review. Controller checks cross-entity exceptions before a financial decision.
What to agree during setup
Set a naming convention for organization codes and agree which legal entity owns each lease-related flow. Check base currency and country on the entity master. Decide who may make a lessor active or clear a partner from credit hold. Define how duplicate counterparties are found and merged before they produce separate invoice histories.
Agree which lessor details AP must check before approval, including tax identity and remittance destination. Decide which partner contact receives billing questions and how changes to terms are documented. The team should also decide how to handle a counterparty that changes name while prior invoices and billings must retain a traceable history.
Check the handoff on an actual case
Set up an active organization and a lessor assigned to it. AP records an invoice and confirms that both records point to the intended organization. Review a second invoice for that lessor in a different period; the counterparty history should remain findable. Have the Controller check the remittance information before approval and make a note of any discrepancy.
Then prepare a billing for a partner with a defined payment term. AR confirms the billing contact and entity before sending. Put a rehearsal partner on credit hold and agree how the AR team should resolve the exception. The important check is that an operator can identify the correct party and entity before entering an amount, rather than cleaning up an incorrect association after payment.
What your team sees
- AP Bills Worklist — Lessor and organization context for payables awaiting work.
- AR Invoice Register — Partner and billing context for receivables follow-up.
- Treasury Payment Register — Counterparty links beside cash movements.
Follow the work through
Follow invoice review and payment or billing and collection.
What it keeps track of
Data model- Lessors
- Counterparties that grant leased assets: lessor master with contact, remittance and tax identity.
- Business partners
- Business partner master for lease counterparties and billing contacts.
- Organizations
- Legal entities and business units whose books this app keeps; every document belongs to one organization.
- 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.
Who uses it
Permissions- Admin
- Maintains the master records.
- AP Specialist
- Checks lessor identity.
- AR Specialist
- Checks the billing partner.
- Controller
- Handles authority and entity exceptions.
- Treasury Analyst
- Verifies the payee or payer on payment records.
Set up Lease Finance Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.