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.
- Accounts Receivable System
- Who it's for
- Project billing collections
Project billing collections
Follow up on project invoices while preserving the original billing owner. Accounts Receivable System brings the relevant customer balances, collection decisions and receipt evidence into the shared workspace. Configure the source ownership and access boundaries before migration.
How Accounts Receivable System is set up for you
Source ownership
The project billing service issues and financially owns its invoice. The AR collection reference carries the source invoice, current version and confirmed open balance; it cannot issue another invoice or revenue journal.
Adjustment handoffs
Send credit or application requests to the billing owner and wait for its actual result. An accepted request is not a completed balance change, and a stale callback cannot replace the latest confirmed version.
Customer communications
Declare which service owns dunning for the selected population. Keep shared invoice references and communication history so a customer does not receive duplicate reminders from two systems.
Invoices, collections cases, dunning events.
Features to start with
Roles on the team
- AR Manager
- Owns the operational AR machine. Configures dunning policies, manages collections cases, releases credit holds, and approves credit memos under threshold. Escalates write-offs to the Controller.
- AR Clerk
- The operational role — the day-in / day-out AR seat. Drafts and sends Invoices, applies payments received against open Invoices, processes credit memos under threshold, sends manual dunning when a Customer-specific situation calls for it.
Set up Accounts Receivable System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.