Check the next due date and future payment amount.
See that this account needs PDF delivery because an email is missing.
Check the previous statement separately / Actual Odoo screenEnlarge screenshot ↗
02 / Collections team
Check the previous statement separately
Review when the previous statement was prepared.
Compare its original balance with the remaining amount.
See Paid status without confusing it with today’s account balance.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Separate today’s debt from an earlier statement.
The business problem
Sending a well-formatted statement is not enough if the amount is wrong. Reconciled payments, transferred credits and newer transactions can be counted in the wrong scope or counted twice.
What we changed
Payment reconciliation, credit handling and statement scope were refined so current debt and earlier statement status can be reviewed separately.
What the team can do now
The collections team can explain the current amount due and the payment status of earlier statements from the same workspace.
A real account / Current balance and statement history
The previous statement is paid. The account still has a balance.
These two tabs belong to the same customer. The earlier statement is fully paid, but today’s account includes additional open activity.
Due now
$1,322.24
Total open
$13,972.81
Previous statement remaining
$0.00
Previous statement status
Paid
What the screen shows
The Latest Statement tab follows the invoices and credits included in that statement. Balance Today shows the current account.
What the team does next
Follow up on the current amount due without asking the customer to pay an already-settled statement again.
What the next team receives
The person preparing the next statement can see the current balance, the prior payment status and the delivery requirement together.
How the work moves
Follow the work from one decision to the next.
01
Read today’s balance
Separate the amount due now from the total open account balance.
02
Check previous statements
See which earlier statement amounts are already paid.
03
Review the cutoff
Keep each statement tied to the transactions it includes.
04
Prepare the right delivery
Check the customer’s delivery settings before preparing the statement.
Built, used, refined
How the workflow improved over time.
Carry moved credits into statements
Refined visibility of credits that had moved between accounting contexts.
Correct duplicate payment effects
Reworked open-item and payment calculations so payment effects are not counted twice.
Align credits and collectible balances
Refined due-now, credit and statement delivery behavior.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 52882c2, c3fa8b0, 3435405.
Build notes and background
Financial workflowsData integration
The boundaries we made explicit.
Payment evidence must not be counted twice
The August correction refined how reconciled and unapplied amounts enter the open-item calculation.
Due now is not total open balance
Future maturity buckets and currently collectible amounts remain distinct.
A snapshot is not a new posting
Statement preparation does not itself settle invoices or create an accounting result.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
Built on Captivea CAP modules and Odoo. This case describes the subsequent Pro-A-Motors extensions and refinements recorded in the reviewed repository; it does not attribute the original CAP implementation to Toro.
