Skip to main content Enter
ERP.AI Accounts Receivable System

Accounts Receivable System

Start now
Pricing Questions Get started
Build with Proto

Modules

Customer billingKeep customer terms and recurring billing ready for the next invoice. Invoices and creditsSend clear invoices and keep every adjustment connected to its source. Cash applicationMatch incoming cash to the right invoices and explain every remainder.
CollectionsGive overdue balances a clear next action and accountable owner. Credit controlsMake credit decisions visible before they change a customer balance. Receivables reportingExplain aging, collections and cash application with a consistent balance basis.

Accounts Receivable System

Start now
Pricing Questions Get started
Build with Proto

Processes

Prepare and send invoicesKeep draft preparation, delivery and ledger confirmation distinct. Receive and apply cashTurn confirmed receipt evidence into attributable invoice allocations.
Resolve disputes and collectKeep follow-up, dispute resolution and financial adjustments connected. Review write-offsKeep the write-off request, Controller decision and posted result separate.

Accounts Receivable System

Start now
Pricing Questions Get started
Build with Proto

Industries

Goods and distributionConnect customer billing to the goods and delivery evidence you already use. Services and retainersKeep agreed terms, recurring drafts and customer adjustments connected.
Project billing collectionsFollow up on project invoices while preserving the original billing owner.

Accounts Receivable System

Start now
Pricing Questions Get started
Build with Proto

Reference

Roles and permissionsGive each person the customer and decision scope their work needs. Reports and analyticsUnderstand customer aging, collection activity and cash application. Data modelTrace invoices, receipts and adjustments back to their governing source.
IntegrationsConnect billing, bank evidence and ledger outcomes with clear ownership. ImplementationStart with a reconciled customer population and expand after a controlled pilot. Agent and automationPrepare receivables work with an agent while retaining the assigned decisions.

Accounts Receivable System

Start now
Pricing Questions Get started
Build with Proto
All systems
Modules
Customer billingKeep customer terms and recurring billing ready for the next invoice.Invoices and creditsSend clear invoices and keep every adjustment connected to its source.Cash applicationMatch incoming cash to the right invoices and explain every remainder.CollectionsGive overdue balances a clear next action and accountable owner.Credit controlsMake credit decisions visible before they change a customer balance.Receivables reportingExplain aging, collections and cash application with a consistent balance basis.
Processes
Prepare and send invoicesKeep draft preparation, delivery and ledger confirmation distinct.Receive and apply cashTurn confirmed receipt evidence into attributable invoice allocations.Resolve disputes and collectKeep follow-up, dispute resolution and financial adjustments connected.Review write-offsKeep the write-off request, Controller decision and posted result separate.
Industries
Goods and distributionConnect customer billing to the goods and delivery evidence you already use.Services and retainersKeep agreed terms, recurring drafts and customer adjustments connected.Project billing collectionsFollow up on project invoices while preserving the original billing owner.
Reference
Roles and permissionsGive each person the customer and decision scope their work needs.Reports and analyticsUnderstand customer aging, collection activity and cash application.Data modelTrace invoices, receipts and adjustments back to their governing source.IntegrationsConnect billing, bank evidence and ledger outcomes with clear ownership.ImplementationStart with a reconciled customer population and expand after a controlled pilot.Agent and automationPrepare receivables work with an agent while retaining the assigned decisions.
Sign in
Sign in Start now
Accounts Receivable System References
Roles and permissions1 of 6
  • Roles and permissions1 of 6
  • Reports and analytics2 of 6
  • Data model3 of 6
  • Integrations4 of 6
  • Implementation5 of 6
  • Agent and automation6 of 6

Roles and permissions

Give each person the customer and decision scope their work needs.

Permissions

Summarised from the authored role permissions. Scope restrictions such as “own records” still apply; these symbols do not indicate completeness or runtime access.

Table Controller / CFO AR Manager AR Clerk Sales Rep Customer Viewer
master
Customers—No table-specific permission stated View: View unmasked Customers.CreditLimit—No table-specific permission stated—No table-specific permission stated—No table-specific permission stated—No table-specific permission stated
transaction
CreditMemos Specific actions: Approve CreditMemos above the AR Manager threshold—No table-specific permission stated—No table-specific permission stated—No table-specific permission stated—No table-specific permission stated—No table-specific permission stated
  • Controller / CFOFull read on every table in the appthe role is review and approval, not data entry
  • AR ClerkTrigger Status: Draft → Sent (fires invoice-send and gl-post-on-invoice-send)Trigger ad-hoc dunning sends
  • Sales RepCannot edit anything in this app
  • CustomerInitiate payment via portal link (handled by fin-payments)
  • ViewerCannot edit anything
Manage / maintain View Specific actions— No table-specific permission statedPermissions also apply to agents

Working roles

7 rules

AR Clerk

Prepares local invoices, reviews cash proposals and applies permitted receipts. Cannot replace Controller write-off approval.

AR Manager

Maintains collection policies, investigates disputes, manages holds and requests write-offs. Credit approval follows the configured threshold.

Controller / CFO

Owns the financial review, higher-tier adjustments and write-off decisions. Reconciles the AR population to its ledger owner.

Sales Rep

Reads assigned-customer aging within account-owner scope.

Customer

Sees only their own permitted invoices and payment context.

Viewer

Receives the intended aggregate read-only reporting scope.

Admin

Configures identities and integration access; administrative access is not permission to replace an independently assigned financial decision.

The roles

Controller / CFO

Owns the AR function. Approves WriteOffs, signs off on the period-end aging, and reviews DSO and bad-debt trend. The named approver on the GL post handoff to fin-accounting.

Permissions and screens
  • Full read on every table in the app
  • CRUD on WriteOffs (sole approver — PendingApproval → Approved)
  • Approve CreditMemos above the AR Manager threshold
  • Read Customers.CreditLimit, PaymentsReceived.BankAccount, and BankFeedTransactions.BankAccount (unmasked)
  • Sign off on ARAgingSnapshots at period close
  • Cannot edit Invoices, PaymentsReceived, or CreditMemos directly — that's AR Clerk / AR Manager scope
  • the role is review and approval, not data entry
Pending Write-OffsPendingApproval
Write Off NumberInvoiceCustomerAmount
Overdue AR QueueSent
Invoice NumberCustomerIssue DateDue Date
Open DisputesOpen
Dispute NumberInvoiceCustomerRaised At
Pending Write-OffsWriteOffs
PendingApproval
  • WO-12605 INV-19541 in 9 d
  • WO-31809 INV-94576 in 10 d
  • WO-26540 INV-31841 6 d
  • WO-18340 INV-11502 in 10 d
  • WO-80033 INV-17904 11 d
WO-12605
Invoice
INV-19541
Customer
CUS-176
Amount
14,192.01
Reason
Bankruptcy
RequestedBy
SD

Write-off approval waits for the controller / cfo.

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.

Permissions and screens
  • CRUD on Customers (AR fields — CreditLimit, DefaultDunningPolicy, DefaultBillingTerm, StatementCadence), DunningPolicies, Disputes, CollectionsCases, CreditHolds, LateFees (waive)
  • CRUD on CreditMemos (approve up to threshold)
  • CRUD on WriteOffs as Draft → PendingApproval (routes to Controller)
  • Read on Invoices, InvoiceLines, PaymentsReceived, PaymentApplications, BankFeedTransactions, ARAgingSnapshots
  • View unmasked Customers.CreditLimit
  • Cannot post WriteOffs to Approved (Controller only)
Pending Write-OffsPendingApproval
Write Off NumberInvoiceCustomerAmount
Overdue AR QueueSent
Invoice NumberCustomerIssue DateDue Date
Unapplied CashDraft
Payment NumberCustomerMethodAmount
Check
Pending Write-OffsWriteOffs
PendingApproval
  • WO-12605 INV-19541 in 9 d
  • WO-31809 INV-94576 in 10 d
  • WO-26540 INV-31841 6 d
  • WO-18340 INV-11502 in 10 d
  • WO-80033 INV-17904 11 d
WO-12605
Invoice
INV-19541
Customer
CUS-176
Amount
14,192.01
Reason
Bankruptcy
RequestedBy
SD

Write-off approval waits for the controller / cfo.

AR Clerk

The operational role — the day-in / day-out AR seat. Drafts and sends Invoices, applies PaymentsReceived against open Invoices, processes CreditMemos under threshold, sends manual dunning when a Customer-specific situation calls for it.

Permissions and screens
  • CRUD on Invoices and InvoiceLines while Status IN (Draft, Sent)
  • Trigger Status: Draft → Sent (fires invoice-send and gl-post-on-invoice-send)
  • CRUD on RecurringInvoiceSchedules (cannot delete an Active schedule without AR Manager)
  • CRUD on PaymentsReceived and PaymentApplications — including reviewing and confirming the auto-matched proposals from payment-application-auto-match
  • CRUD on CreditMemos and CreditMemoLines while Status IN (Draft) (AR Manager approves)
  • Read on BankFeedTransactions, DunningEvents, DunningPolicies, Disputes, Customers, BillingTerms, InvoiceTemplates
  • Trigger ad-hoc dunning sends
  • Read Customers.CreditLimit masked
Overdue AR QueueSent
Invoice NumberCustomerIssue DateDue Date
Unapplied CashDraft
Payment NumberCustomerMethodAmount
Check
Active Dunning QueueSent
Invoice NumberCustomerDue DateOpen Balance
Overdue AR QueueInvoices
StatusSentPartiallyPaidOverdueoverdue
Sent
INV-29825CUS-131810 aging bucket
INV-30692CUS-02990 aging bucket
PartiallyPaid
INV-95076CUS-129850 aging bucket
INV-74765CUS-104890 aging bucket
Overdue
INV-85702CUS-085760 aging bucket
INV-45158CUS-107940 aging bucket
Sales Rep

Account-owner read-only on own Customers' AR. Nudges the buyer when a deal goes overdue without exposing GL detail.

Permissions and screens
  • Read on Customers where Customer.AccountOwner = self
  • Read on Invoices, PaymentsReceived, ARAgingSnapshots, DunningEvents, CollectionsCases, CreditHolds scoped to those Customers
  • Cannot see Customers.CreditLimit (masked), PaymentsReceived.BankAccount (masked), or any other Customer's data
  • Cannot edit anything in this app
My Customers' Aging (Sales)
NameBilling EmailOpen ARBalanceOn Credit Hold
My Customers' Aging (Sales)Customers
Youopen ar balance > 0
NameBilling EmailOpen ARBalanceOn Credit HoldStatement Cadence
Customer 225[email protected]10,521.6531,640.35None
Customer 963[email protected]15,343.5641,567.43Monthly
Customer 858[email protected]23,142.9322,056.10Quarterly
Customer 559[email protected]32,768.013,000.33None
Customer 905[email protected]8,853.3912,102.19Monthly
Customer 487[email protected]29,178.5340,547.75Quarterly
Customer

The buyer. Implicit role accessed through the customer payment portal — sees own open Invoices, can pay via the fin-payments-issued portal link, downloads own Invoices and Statements.

Permissions and screens
  • Read on own Invoices and InvoiceLines (filtered by Customer = self)
  • Read on own PaymentsReceived and PaymentApplications
  • Initiate payment via portal link (handled by fin-payments)
  • Cannot see other Customers, internal notes, dunning history, credit limit, or any AR Manager / AR Clerk surfaces
  • No write access on AR tables — payments flow through fin-payments and create PaymentsReceived here on clearing
Viewer

Executive read-only on aging and DSO. The owner, board member, or external auditor seat.

Permissions and screens
  • Read on Invoices, Customers (financial fields masked except OpenARBalance), ARAgingSnapshots, CollectionsCases, WriteOffs, DunningEvents, and all reports
  • Cannot see Customers.CreditLimit, PaymentsReceived.BankAccount, or BankFeedTransactions.BankAccount
  • Cannot edit anything
Latest AR Aging Snapshot
CustomerAs Of DateCurrent AmountBucket1 To30
Latest AR Aging SnapshotARAgingSnapshots
AsOfDate = MAX(AsOfDate)
CustomerAs Of DateCurrent AmountBucket1 To30Bucket31 To60
CUS-19316 Sep3,234.859,593.3828,872.62
CUS-20722 Sep17,158.9018,561.969,622.13
CUS-23014 Sep14,719.6612,021.8813,850.40
CUS-04029 Sep16,852.1245,628.8744,035.93
CUS-03713 Sep8,733.9411,264.121,223.42
CUS-11407 Sep25,581.5513,167.5317,147.56

Access boundaries

Apply customer ownership, field masking and action permissions consistently to lists, exports, references and APIs. Test both permitted and rejected requests before rollout. Bank and processor references retain their sensitive-field controls.

Admin

Systems administrator. Owns configuration, integration health, and user provisioning for the AR system. Not a day-to-day AR operator.

  • Full CRUD on all tables
  • Manage RBAC and role assignments
  • Configure BillingTerms, InvoiceTemplates, DunningPolicies (with AR Manager)
  • Configure inbound feeds from CRM, pm-billing, fin-tax-compliance, and the bank API
  • Configure outbound integrations to fin-accounting (GL JEs), fin-payments, document store, and email
  • Cannot post a WriteOff without Controller approval and cannot reverse a posted GL JE
Controller / CFO

Owns the AR function. Approves WriteOffs, signs off on the period-end aging, and reviews DSO and bad-debt trend. The named approver on the GL post handoff to fin-accounting.

  • Full read on every table in the app
  • CRUD on WriteOffs (sole approver — PendingApproval → Approved)
  • Approve CreditMemos above the AR Manager threshold
  • Read Customers.CreditLimit, PaymentsReceived.BankAccount, and BankFeedTransactions.BankAccount (unmasked)
  • Sign off on ARAgingSnapshots at period close
  • Cannot edit Invoices, PaymentsReceived, or CreditMemos directly — that's AR Clerk / AR Manager scope
  • the role is review and approval, not data entry
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.

  • CRUD on Customers (AR fields — CreditLimit, DefaultDunningPolicy, DefaultBillingTerm, StatementCadence), DunningPolicies, Disputes, CollectionsCases, CreditHolds, LateFees (waive)
  • CRUD on CreditMemos (approve up to threshold)
  • CRUD on WriteOffs as Draft → PendingApproval (routes to Controller)
  • Read on Invoices, InvoiceLines, PaymentsReceived, PaymentApplications, BankFeedTransactions, ARAgingSnapshots
  • View unmasked Customers.CreditLimit
  • Cannot post WriteOffs to Approved (Controller only)
AR Clerk

The operational role — the day-in / day-out AR seat. Drafts and sends Invoices, applies PaymentsReceived against open Invoices, processes CreditMemos under threshold, sends manual dunning when a Customer-specific situation calls for it.

  • CRUD on Invoices and InvoiceLines while Status IN (Draft, Sent)
  • Trigger Status: Draft → Sent (fires invoice-send and gl-post-on-invoice-send)
  • CRUD on RecurringInvoiceSchedules (cannot delete an Active schedule without AR Manager)
  • CRUD on PaymentsReceived and PaymentApplications — including reviewing and confirming the auto-matched proposals from payment-application-auto-match
  • CRUD on CreditMemos and CreditMemoLines while Status IN (Draft) (AR Manager approves)
  • Read on BankFeedTransactions, DunningEvents, DunningPolicies, Disputes, Customers, BillingTerms, InvoiceTemplates
  • Trigger ad-hoc dunning sends
  • Read Customers.CreditLimit masked
Sales Rep

Account-owner read-only on own Customers' AR. Nudges the buyer when a deal goes overdue without exposing GL detail.

  • Read on Customers where Customer.AccountOwner = self
  • Read on Invoices, PaymentsReceived, ARAgingSnapshots, DunningEvents, CollectionsCases, CreditHolds scoped to those Customers
  • Cannot see Customers.CreditLimit (masked), PaymentsReceived.BankAccount (masked), or any other Customer's data
  • Cannot edit anything in this app
Customer

The buyer. Implicit role accessed through the customer payment portal — sees own open Invoices, can pay via the fin-payments-issued portal link, downloads own Invoices and Statements.

  • Read on own Invoices and InvoiceLines (filtered by Customer = self)
  • Read on own PaymentsReceived and PaymentApplications
  • Initiate payment via portal link (handled by fin-payments)
  • Cannot see other Customers, internal notes, dunning history, credit limit, or any AR Manager / AR Clerk surfaces
  • No write access on AR tables — payments flow through fin-payments and create PaymentsReceived here on clearing
Viewer

Executive read-only on aging and DSO. The owner, board member, or external auditor seat.

  • Read on Invoices, Customers (financial fields masked except OpenARBalance), ARAgingSnapshots, CollectionsCases, WriteOffs, DunningEvents, and all reports
  • Cannot see Customers.CreditLimit, PaymentsReceived.BankAccount, or BankFeedTransactions.BankAccount
  • Cannot edit anything
ERP•AI workspace

Start now Accounts Receivable System

Create your ERP.AI account and get started with Proto.

Start now Download agent
Next · reference 2 of 6Reports and analytics

Customize Accounts Receivable System. With Proto, your desktop AI agent.

Ask Proto to help you customize Accounts Receivable System.

Customize
Accounts Receivable System.
Ask: “Adapt Customer billing.”
ProtoYour desktop AI agent
Download nowFree install · ~1 GB · AI usage extra
macOSWindowsLinux

Bring your first idea to Proto.

Keep this page open while you install Proto. Connect your account and model, then paste this into a new chat.

AI usage is paid separately. You can edit the prompt before copying.

ERP.AI

Business apps and the Proto desktop agent.

  • Business Apps
  • Proto
  • Workflows
  • Headless SaaS
  • Enterprise
  • Pricing
  • Contact
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
© 2026 ERP•AI. All rights reserved.
System status

Your Privacy, Your Choice

We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy

Manage Your Cookie Preferences

We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.

Learn more about how we use cookies

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.

These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.

These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.

These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.