Authorized amount
Client, invoice, currency, balance, due terms, payment methods, mandate or consent, delivery evidence, dispute state, and provider.
Agency collection should make payment easy while keeping invoice authority, client communication, provider events, settlement, fees, disputes, refunds, and accounting reconciliation clear.
Client, invoice, currency, balance, due terms, payment methods, mandate or consent, delivery evidence, dispute state, and provider.
Send, remind, promise, pay, authenticate, fail, retry, settle, allocate, receipt, refund, dispute, chargeback, payout, and reconcile.
The invoice, provider event, payout, bank movement, fee, receipt, balance, client message, and accounting result remain connected.
The useful product is the one your team can keep current while preserving ownership, evidence, and the client relationship.
Model deposits, milestones, retainers, recurring invoices, partial payments, cards, bank payments, currencies, payment failures, refunds, and disputes.
Send a verified invoice, collect online, handle authentication, retry a failure, record a promise, settle, allocate, issue a receipt, and reconcile.
Test duplicate payment, chargeback, wrong invoice, expired link, mandate change, provider outage, currency difference, refund, and unidentified payout.
Confirm successful payment is not inferred before provider and bank evidence settle and the correct invoice and accounting records update.
Confirm current plan availability, limits, integrations, and migration behavior directly with each provider.
Evaluate invoice links, cards, bank methods, recurring payments, reminders, retries, mandates, authentication, fees, settlement, payouts, refunds, disputes, chargebacks, receipts, currencies, and reconciliation.
No. Provider authorization, capture, settlement, payout, bank receipt, allocation, and accounting status can occur at different times.
Use card and bank payments, partial payment, failed authentication, retry, refund, chargeback, multi-currency fee, payout, and reconciliation scenarios.
Start with one active client and the hardest normal exception.