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.
- E-commerce ERP
- Features
- Receivables and payments
Receivables and payments
Receivables and payments for the order and stock cycle.
OverviewOverdue receivables×
E-commerce ERP · Receivables and payments
New
Overdue receivables
Invoices
| Account | Due date | Outstanding amount | Currency | Status | |
|---|---|---|---|---|---|
| ACC-120 | 18 Oct | 320 | CRR-5713 | Overdue | |
| ACC-110 | 05 Oct | 470 | CRR-6794 | Overdue | |
| ACC-110 | 10 Oct | 310 | CRR-7261 | Overdue | |
| ACC-130 | 08 Oct | 960 | CRR-4802 | Overdue | |
| ACC-120 | 14 Oct | 840 | CRR-7380 | Overdue |
6 of 6 records
ACC-120Invoices · INV-91150
OverdueDue date18 Oct
Outstanding amount320
CurrencyCRR-5713
What you can do
Keep the decision attached to the record
An invoice marked Posted establishes the receivable; Captured and Settled are payment transaction states. Keep the processor account, period and transaction links so a fee or chargeback cannot disappear inside a net deposit. Finance Manager follows the posted invoice’s due date and outstanding balance alongside processor transactions. A captured charge records a processor event; the invoice balance still needs review. Settlement lines carry sale, refund, fee and chargeback amounts and their match status. The settlement period closes only after Finance Manager resolves unmatched and variance lines.
How the work is organized
- Follow the receivable. Review the invoice account, due date, outstanding amount and related sales order.
- Match the transaction. Keep the processor account and unique transaction key with the captured or refunded event.
- Review the period. Compare settlement lines with transactions and leave unmatched or variance lines open.
What to agree during setup
Agree which payment account serves each entity, who records invoices and who reviews settlement periods. Rehearse a captured charge with a fee, a duplicate transaction key and an unmatched settlement line. Compare gross, fee and net amounts before reconciling. A posted invoice, captured charge and reconciled deposit are separate states, so give each exception a named Finance Manager owner.
When a customer asks whether an order is paid, Finance Manager should check the invoice balance and the linked payment transaction. A processor fee changes the deposit amount without changing what the customer paid. Use the settlement line to explain that difference before closing the period.
Check the handoff on an actual case
A channel payment is captured for an order, but the processor deposit is lower after fees. Finance checks the payment transaction, identifies the fee line in the settlement and verifies whether any unmatched or variance line remains. The invoice’s outstanding amount and the settlement period are reviewed separately before the period is reconciled.
Sales Manager can answer the customer about the billed order; Finance Manager owns the outstanding amount and payment match. Keep a variance in the settlement queue until its line and related transaction agree. Do not treat a lower net deposit as an invoice underpayment without first checking fees.
What your team sees
- Overdue receivables — The main queue for posted customer invoice, with its status and source context.
- Settlement variances — Related follow-up work that needs a second check.
Follow the work through
- Follow this handoff: Check the linked stages and exception path.
- Review the data model before importing open records.
What it keeps track of
Data model- Invoices
- Customer invoices, due dates and outstanding balances.
- Invoice lines
- Billed lines supporting each invoice total.
- Payment accounts
- Processor accounts used to collect and settle payments.
- Payment transactions
- Captured charges, refunds and chargebacks per processor.
- Processor settlements
- Processor settlement periods closed only after reconciliation.
- Processor settlement lines
- Settlement lines matched against processor transactions.
- Accounts
- Entity-scoped customer accounting identity.
Who uses it
Permissions- Finance Manager
- Owns invoices, processor transactions and settlement review.
- Sales Manager
- Supplies order context.
- Admin
- Maintains entity and currency reference settings.
Set up E-commerce ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.