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.
Feature · Finance and close
Example screen with sample data
Finance and close
Keep customer settlement, supplier release and period-close evidence tied to their source records.
OverviewBills Awaiting Approval×
ERP + CRM · Finance and close
New
Bills Awaiting Approval
Approval waits for the finance manager
| Bill number | Vendor | Due date | Total amount | Currency | Match variance | |
|---|---|---|---|---|---|---|
| BLL-83531 | VND-122 | 23 Oct | 680 | CRR-9202 | 380 | |
| BLL-31574 | VND-088 | 19 Oct | 910 | CRR-8097 | 100 | |
| BLL-91653 | VND-007 | 11 Oct | 420 | CRR-7759 | 340 | |
| BLL-18140 | VND-169 | 24 Oct | 450 | CRR-9322 | 30 | |
| BLL-49333 | VND-233 | 21 Oct | 60 | CRR-1126 | 290 |
6 of 6 records
VND-122Bills · BLL-83531
Pending approvalDue date23 Oct
Total amount680
CurrencyCRR-9202
Match variance380
Posting stateUnposted
What you can do
Explain the financial result from its source
Accountant prepares invoices from eligible customer scope and follows receipts into their invoice applications. A bank receipt can remain unapplied while the team identifies the correct customer or invoice. Amount received, amount applied and amount available should stay distinguishable throughout that investigation.
On the supplier side, an approved bill can enter a payment run. Finance Manager independently releases the prepared instruction. Sending and clearing require their own evidence. Period-close work then brings these transactions together with journals, depreciation and the assigned reconciliation tasks for each entity and accounting period.
How the work is organized
- Customer settlement. Invoice applications identify the cash and invoice involved. Discounts, withholding and write-offs remain separately attributable so an invoice’s paid state has an understandable settlement basis.
- Supplier release. A payment run retains its preparation and release identities, bank account and currency. The released instruction remains distinct from a later bank confirmation or returned payment.
- Close evidence. Close tasks have owners, due dates and retained completion evidence. Dependencies connect prerequisite work to later review and period sign-off.
What to agree during setup
Agree which employees prepare financial records and which Finance Manager decides approvals. Establish the journal and settlement authority policy, the open-period rules and the treatment of corrections. Review bank accounts, currencies and exchange-rate sources before importing transactions that depend on them.
Decide how incoming bank references are matched to customers and who resolves unidentified receipts. Set the review route for discounts or write-offs. For supplier release, rehearse a changed instruction and a rejected bank outcome. Define close tasks for the actual entity and period, including the evidence Finance Manager needs before moving from Open through soft close to hard close.
Check the handoff on an actual case
Use a customer invoice that receives a partial payment. Accountant records the receipt, applies the eligible amount and leaves the remaining invoice balance explainable. Then record another receipt that cannot yet be matched. It should remain visible as unapplied cash rather than being assigned to a convenient invoice merely to clear the queue.
Prepare a supplier payment run from an approved bill. Finance Manager checks the current instruction and releases it as a different employee from the preparer. Follow the bank result before treating the payment as cleared. If the bank rejects it, retain that outcome and investigate the obligation that still needs settlement.
At period end, complete the related reconciliation task and retain its evidence. Ask Finance Manager to inspect an unresolved prerequisite before attempting close. Correct the underlying transaction through its supported correction path, then refresh the affected close evidence. A completed task label should be backed by the reconciled records it represents.
What your team sees
- Unapplied Customer Cash — Receipts with amounts still available for attribution to customer invoices.
- Supplier Payment Release — Prepared runs waiting for independent financial release.
- Close Tasks Due — Dated close work with its owner, state and evidence attachment.
Follow the work through
What it keeps track of
Data model- Invoices
- Customer invoices posted to AR and Revenue with tax, delivery and settlement status.
- Invoice items
- Invoice line items carrying quantity, price, discount and tax detail.
- Payments received
- Incoming customer cash recorded to bank with unapplied receipt status.
- Payment applications
- Allocations of received cash to specific invoice remainders.
- Bills
- Supplier bills matched to PO prices and accepted goods or services.
- Payment runs
- Prepared supplier payment runs requiring independent release.
- Payments made
- Outgoing payments with settlement confirmation state.
- Bank statement lines
- Statement lines imported from a bank account pending reconciliation.
- Journal entries
- Balanced accounting entries posted to the ledger for a period and entity.
- Journal entry lines
- Debit and credit lines of a journal entry with account, cost center and amount.
- Accounting periods
- Fiscal periods per entity with the open and close state the close checklist drives.
- Close tasks
- Required close checklist tasks for an entity period.
- Close dependencies
- Ordering and blocking dependencies between close tasks.
- Close templates
- Reusable close checklist templates defining required tasks and dependencies.
Who uses it
Permissions- Accountant
- Prepares transactions and reconciliation evidence.
- Finance Manager
- Decides financial approvals, releases supplier payments and reviews period close.
- Admin
- Maintains reviewed connection settings.
Set up ERP + CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.